Hubitat Package Manager is for community apps and drivers. Hubitat-developed apps and drivers are included as part of the platform software. Thus, you two are probably referring to the same thing -- or possibly multiple different offerings, but all community-offered in either case.
That being said, Govee does have a local API (somewhat limited and not supported on all devices), and it is possible support for this will be added in a future platform release. Some of their devices, again not all and again not necessarily the entire featureset, are also Matter-capable and can be integrated that way on compatible hubs. Both of these are (or would be) built-in options.
I was referring to the appliance API integration, and LG does now have a published API, and also because @bobbyD hinted in the community thread it might come to HE as a native app. I get that it is a cloud based API and not "local" but don't we have other integrations that are as well?
I noticed in your screen show that HPM is installing a new instance of HA Device Bridge Configuration.
I noticed today that mine has done the same thing and won’t match the currently installed version that is of course linked to the running app.
I’ve tried all the usual unmatch/match/repair in just about every conceivable sequence but HPM refuses to pick up on the pre existing instance of that app code that is part of HE-HA.
Any ideas how to get HPM to recognise it’s existence?
What is the most efficient method in trying to figure out which repository is causing the issue, instead of trial and error? Or is there another cause of this error?
From what I can tell, a "null" got injected into the master repo apparently.
You can detect it by clicking on the Info button, top right. (circle with I)
If you use your browser's search for null, you might get a match:
I believe you can remove that with a simple (but odd) recipe:
Go to Package Manager Settings and scroll down to Available Repositories:
Click Add a Custom Repository and a URL field will become available. Type "test" into that field and click Next. An error will be displayed, saying your URL is invalid (expected) and that should cause the null to be removed.
I did the "add repository", but had trouble completing the match. A few times of opening HPM, adding repository, and closing the app eventually got everything working correctly. Thank you!
Add Repository is a step that is intended to fail.
What it does is force a "rebuild" causing the null to be dropped. The null is in there, and just zooming through the process of trying to add a repo, causes it to be rebuilt. You don't need another repository, they are already all there. This 'recipe' just takes advantage of the fact that the table gets rebuilt, and drops nulls. Coincidence really.
I understood that. The failure was expected. However, doing a match afterwards would quit randomly, not begin at all, or other weirdness. So just mentioned I retried a few times "for good measure".
I am not sure if this is a Blink Integration issue or an HPM issue.
I cannot get Blink to go away since I don't use those cameras anymore. I have had this problem for a long time and finally at point I want it to go away.
Someone messaged me and pointed me to the HPM developer documentation and CLI tools. I followed the recommended process and used the hpm tool to generate the manifest, which created it as packageManifest.json:
