And there was me thinking about justifying a NabuCasa subscription.
1 Like
Version 2.16:
- Add support for gas detector (@ritchierich)
- Add new lock custom component (@ritchierich)
- Compensate for restrictions imposed by ezdashboard in mediaPlayer and locks
- Simplify handling of "off" thermostat mode
- Filter out setCoolingSetpoint/setHeatingSetpoint calls that are the opposite of current thermostat mode (basilisk487)
11 Likes
Thank you for your continued support of HADB and willingness to accept drivers from community members!
8 Likes
Definatley a big effort (maybe more than you originally bargained for, eh?). So great that @ymerj has been consistently willing to put in so much personal time to this.
6 Likes
Has something gone fooey with the package manifest for this version?
HPM has decided to duplicate my app code claiming Home Assistant Device Bridge Configuration is not installed. And the new code instance (which of course is not the one in use by my app) only has release notes for 2.15 despite HPM reporting 2.16 is installed.
I’ve tried unmatching, deleting the extra app code, matching up, updating/repairing in every variant I can think of and always end up with a duplicate app code instance again at the end of it.
For now the app code instance in use I imported manually via the GitHub URL to the .groovy file but I still get 2.15 in the release notes only?
Do you have HPM 1.9.3 shown in top right corner on main page?
Older versions of HPM have issues with the current hub platform and code will be duplicated.
Also FYI the latest "Home Assistant Device Bridge" App shows 2.15 as the newest change in the changelog in the code. The last 2.16 release may have not had any changes to the app itself. Code is here and has not changed for 2 months: HE-HA-control/haDeviceBridgeConfiguration.groovy at main · ymerj/HE-HA-control · GitHub
I also did confirm the packageManifest has a possible problem. However it looks like it has been this way for 4 years. This issue can cause Match Ups to go wrong and result in duplicated code.
Notice the name here. This is SUPPOSED to exactly match the name of the app in the code. The match up works by matching the namespace and name.
Here is the actual app code:
Name is not the same. So what this can do is cause the MatchUp to not detect this as being part of the package. So when you run the match then update it will install a new version of that code, not updating the original.
The dirty fix is to first Unmatch in HPM, then edit the name in your in-use code to match the manifest. Then run a matchup again. This should make it match that code to your existing install. Now if you repair or Update it should not create a duplicate. At this point it is matched on the UID number of the app code so it will retain that match even if the app name changes (as long as you don't unmatch it again).
@ymerj There is a fix for this which could be applied to the manifest. There is an option for alternate names in case you rename an app or driver. So you could either fix the name in the manifest and add the old one as an alternate, or add the current app name as the alternate. I could mock up an example if needed. The alternate name is not well documented but I have it in my ZEN17 driver package. Hubitat/packageManifest/zooz-zen-relays.json at main · jtp10181/Hubitat · GitHub
2 Likes
The app was unchanged in the last update so it is still showing version 2.15 which is the correct version for the app.
Indeed and I don't know how come it would cause problems now after so long and numerous matchup done by many over that time. Was something changed in HPM?
I don't know much about HPM (I don't use it) and I'm reluctant to mess with something that was working before. @csteele please advise.
The name was never changed. It is the original name when the file was created 4 years ago.
@ymerj I didn’t know about this HPM feature before @jtp10181’s post but this could give you the opportunity to rename all the component drivers with the HADB prefix.
2 Likes
Yes, this cross my mind too.
2 Likes
Nothing has changed in this regard, it has always matched on the name and namespace AFAIK. @csteele has purposely not changed much of the core functions to avoid breaking anything. This is not the first time I have seen a dev have this info wrong in the manifest causing such issues. It is not thoroughly explained in the docs the importance of having the name and namespace exactly matching the app/driver code.
How many people really install it all by hand then match up with HPM (thats a lot of files)? And how many of those would notice it created duplicate code? The issue would only occur if you installed manually, or unmatched, or deleted HPM, then run a Match. If you install from HPM it is linked to the app code UID and matching again would not change anything.
I did a simple test on a different hub that did not have this on it already.
- Installed HADB via HPM.
- Unmatched it right away.
- Run Match UP and accept the match (do not mark it as current)
- Now check the View Apps and Drivers list, you will noticed the "Home Assistant Device Bridge configuration" is not in the list, because that component did not match. (See screenshots below)
- Now run an update and it should want to do one for HADB
- Accept the update
- You will see it reinstalls the app it thinks is missing
- Check your apps code and there will be a duplicate
Unmatch and re-matched (versions do not populate until you update):
Clean Install with all components:
Update where it states the main app is missing:
Duplicated apps codes:
I could do a PR with a proposed fix but I know a lot of devs would just rather fix it themselves instead of dealing with PRs.
4 Likes
Go ahead. Much simpler for me... and I will learn something.
3 Likes
Thank you @jtp10181 for fixing the manifest.
5 Likes
Minor update 2.17:
- Fix some devices not updating their health status
2 Likes
Hi and thank you for this integration app.
For my Reolink external POE cameras i am missing the Siren being exposed to hubitat, might it need a generic driver?
Which looks like this in HA
siren.reolink_video_doorbell_poe_w_siren
The only siren i can see exposed is "siren on Event"
Thanks
There is no support for sirens at the moment. If you would like to get support for it, some logs and testing will be required on your part.
2 Likes
Happy to help please feel free to PM me with requirements
Hi, my C5 is showing that there is an update for Home Assistant Device bridge app, I have tried a few times to do the update but I keep getting this error, I have tried a repair app and a manual copy of the raw code
Does that mean you could reach the file directly but not from HPM?
Yes, so I went directly to https://raw.githubusercontent.com/ymerj/HE-HA-control/main/haDeviceBridgeConfiguration.groovy and copied this. But it will not update through Package Manager
