[RELEASE] Home Assistant Device Bridge (HADB)

Hubitat has built-in Generic Component drivers for many attributes, but not for all. Thus, custom child component drivers had to be written for HADB to work properly.

4 Likes

I’m sure the next readings will be higher since it’s been relocated, lol.

The HA graphs are also nifty

DAC can't check that directly like looking for HealthStatus. I will work up something to check for the connection and toggle a virtual device.

I could add Health check capability and HealthStatus attribute to it. Will that help?

2 Likes

Version 2.23:

  • Add health check capability
8 Likes

THANK YOU!

I was just hacking the code and was going to open a PR with a result nearly the same as your commit.

I was thinking a better change would be only mark HealthStatus as offline if the connection was still down 2 minutes (or so) after the connection was closed. This would avoid HealthStatus flapping unnecessarily.

There are two situations where the HealthSatus could be considered offline: closed and reconnecting. Either one makes the bridge inoperable. I think the HealthStatus should reflect the connection state as it is.

If ones wish to make use of a particular delay, perhaps it would be better handled with an automation.

1 Like

I have a rule that essentially does this.

My HA issue seems to have been a Midea integration that I had installed. I was bringing over the unit to HE and it seemed to be hanging the bridge. Once I removed it, the bridge stopped hanging periodically.

Any ideas on how to get a ikea bulb to behave properly. I have a couple of the dimmable temperature changing one’s no RGB and seeing errors in the log when they are used. I’ve tried using a few different drivers but no luck.

Make sure you are using the Generic Component CT as the driver type.

4 Likes

That was it, i thought i’d tried that one :face_with_peeking_eye:

2 Likes

@ymerj
Just a thought and a question....

Is there a driver for bringing over TTS speakers from HA? Is that even something that could be done?

Thinking of moving my alexa over to HA. There have been some changes on the amazon end and HA supposedly has the kinks worked out of the authentication. Echo Speaks on the HE side doesn't seem to be in any active queue for updates.

In HA the domain “TTS” refer to the integration itself, not the speaker. Furthermore, nothing comes back through the bridge when a message is spoken.

The only thing I can do is adding a special handling for the custom service call on the parent driver device.

1 Like

Version 2.24:

  • Add special handling for TTS request on custom service call function (only tested with Google Translate)

Example:

On the device page:

As an automation:

2 Likes

I create a pull request to add support for entities of input_datetime. It is working on my system.

I duplicated the line for 'event', but I don't think the descriptive text string I left in place is appropriate.

I wonder why you choose “Event” over other entity type. For what I can tell, the purpose off this entity is only to set a time whereas the event entity act more like a button device.

When you say it works, how are you using the event component device to set the time?

( I messaged you the same response, you can folow up here or in PM, as you wish. )

2 Likes

Version 2.25:

  • Add support for datetime entity. Thanks to @jlv
3 Likes

Updated through Packet manager the HA to HE device bridge this morning 7 10 2026

and now all my devices I had set up are not working and there not clicked in the App they show up as child devices but don’t work at all. I am running the latest updates 2.5.0.159 on the hub and had to do a restore to previous to get them back but devices still don’t show up in the integration page. Any help would be appreciated. I don’t want to have to go back and re add these devices to get back to where I was.

I suspect a mismatch between the app “includeList” and the driver “filterList”.

Can you post the device data section from the parent driver and the settings from the info page of the app?

Not sure what you are asking the device data section from the parent driver. Where is that information on the Hubitat hub. Thank you for the reply!