[RELEASE] Home Assistant Device Bridge (HADB)

Yes, and whats more interesting, If I use home assistants outside ip https://, and I check "require secure connection, it works. But I cant get it to work on the local IP.
Not using secure connection on the local, I just keep getting websocket error

Is the local IP of your HA setup routable from your Hubitat hub?

It should be, its on the same network, now HA it running on a nuc in docker, but I can hit it from any machine on my network. I just selected debug in he and the message is "no route to host (host unreachable) which is so strange. Is there a way for me to ping from inside HE?

This is a wrapper for ping from Hubitat. Maybe give it a try? [Release] Hubitat Ping

1 Like

I will, here is my setup, i have tried with and without http://

Is the port correct, given how you have it hosted in Docker? Maybe you need to forward a port in Docker and/or use a different port in the Hubitat app config.

Yea, all the forwarding is done in my docker compose, The ip is pingable from hubitat using hubitat ping that you sent me.

That is odd. I am out of my depth with Docker in this case. @bradford.clarke mentioned earlier in this thread that he runs HA in Docker and was successfully using HADB. Can you share any tips on what it takes to get it working, @bradford.clarke?

@tomw @beyondunreal

I just checked my HA configuration in Portainer (i run my containers within Open Media Vault on my Pi based NAS) and the only thing i seem to recall having to tweak was to make sure HA was set up on the host network and not as a bridge.

1 Like

I figured it out. The HE hub's local IP address was banned in HA ip_bans.yaml. I cleared that out, restarted HA and it connected!

3 Likes

Version 0.1.50 comes with an option to ignore unavailable or unknown states as discussed earlier and improved lights support.

5 Likes

Please advise how to resolve the error below.

parsing error

Thanks

Please install the following driver.

3 Likes

Great, this driver worked, the error is now gone.
Thanks

1 Like

It seems like maybe we should make that driver required in HPM and also mention it in the manual install instructions. Or else just handle that error more gracefully. What do you think @ymerj?

5 Likes

Making the component required is a way to handle the error more gracefully :wink:

5 Likes

Just here to say thank you for this integration. You have made me retake my backburner project and breadth new life into it. I have thoroughly enjoyed and destroyed/redesigned my whole infra at home, lol. Keep up this magnificent work. If you'd allow me to suggest, a search box while selecting the entities would be swell, but not a deal breaker for me either.

4 Likes

Cool, I agree. I made that change in the HPM manifest.

Anyone who wants to pick up that change immediately should Repair the HADB package in HPM.

It's not urgent for most people, though, so the next Upgrade would presumably also pick up this change also.

4 Likes

Only thing left is updating the first post to that effect... @SmartHomePrimer if you can find the time

1 Like

A huge thank you to the devs for making this awesome bridge! Bringing some of the HA-supported devices into HE is super handy.

Note to HADB Devs: I found a potential bug or incompatibility in HADB's parsing logic for thermostats, as HADB recognizes my Tado thermostats but ignored my Drayton Wiser ones. It turns out that the latter thermostats use a heating_mode / state of 'auto', which HADB discards due to the "auto: / return" on lines 341-342 of the driver. I deleted line 341 and that's fixed all my thermostats. Is this change worth applying to the release version, or would my fix break the driver for others?

1 Like