Alarm entities are not supported by HADB.
Mirroring a helper switch in HA for each state might offer a workaround.
2 Likes
Thank you. Can you mirror a 3-position switch? ARM/DIS ARM/ AWAY ARM
Perhaps there is a convoluted way of doing this in HA but there is no such thing in HE anyway.
And definitely no support from HADB.
1 Like
I do this with three helpers for my presence: Away, Home, and Work
I have an automation in HA that changes each of these switches when I enter/leave Home or Work zones.
The summary is:
Triggers-
Presence Leaves Home
Presence Enters Home
Presence Leaves Work
Presence Enters Work
Actions-
If Presence = Home, set Helper Home to on, else set Helper home to off
if Presence = work, set Helper Work to on, else set Helper Work to off
If Presence = Away, set Helper Away to on, else set Helper Away to off
Then I can use the helpers to trigger events in HE.
2 Likes
Hi a strange one for my HADB integration. It appears that all of my devices are communicating but the HA app saily failed to communicate and the HA has a failed log as per below. Anyone have any suggestions ?
Logger: homeassistant.config_entries
Source: config_entries.py:761
First occurred: 18:36:13 (4 occurrences)
Last logged: 19:12:44
Error setting up entry Hubitat (b49ad369) for hubitat
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 761, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hubitat/init.py", line 39, in async_setup_entry
hub: Hub = await Hub.create(
^^^^^^^^^^^^^^^^^
hass, config_entry, len(cast(dict[str, Any], hass.data[DOMAIN])) + 1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/config/custom_components/hubitat/hub.py", line 324, in create
await hubitat_hub.start()
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 197, in start
await self._start_server()
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 503, in _start_server
await self.set_event_url(self.event_url)
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 247, in set_event_url
await self._api_request(f"postURL/{url}")
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 449, in _api_request
raise RequestError(resp)
custom_components.hubitat.hubitatmaker.error.RequestError: GET http://192.168.0.96/apps/api/1485/postURL/http:%2F%2F192.168.0.45:46347?access_token=b49ad369-bba1-488c-80d5-1b3890bb9834 - [404] Not Found
Are you perhaps referring to the other HE to HA integration?
The HADB integration in this thread is HA to HE. It has no custom HA code whatsoever. The HA logs you shared appear to be from the other integration linked above.
5 Likes
This continues to be the most valuable integration I use ... having HA available for stuff HE doesn't support - yet having all those devices available for programming in HE ... well - that is just the cat's pajamas man! One example - my Tapo cameras tie to HA. All of the cameras have a person detection entity which is fed to HE via HADB ... I have very quick notification on HE when the tapos "see" a person in the detection zone. It is great for when we are away from home as we can trigger automations based on these detections. All thanks to this integration. Merely ONE example.
10 Likes
Ok I need some hand holding here. Any help would be appreciated.
So I’m trying to integrate Hubitat into HA. I have both HE and HA up and running. All my devices are in HE and I want to share them with HA.
I went into Hubitat package manager and download home assistant device bridge , it was successfully installed. However it’s not showing up in my apps ? If I remember correctly I need to go to the app code and install it somehow. However I forget how what I’m I missing here?
HADB brings devices from HA into HE, not the other way around.
A couple posts above yours, ogiewon links to what you may be seeking.
4 Likes
Thanks
If you are talking about getting it to show up in your apps after you have installed the code, there is an "add user app" button at the top of the apps page to get the app to actually be able to use the app.
Also, what @hydro311 said...... I think you want the other integration that shares the HE devices to HA.
3 Likes
It seems that every time I run an update on the Home Assistant Hub, and restart it, HADB is (recently) not able to gracefully recover?
Am I the only one seeing this? It shows open connection in the driver and Reconnecting for the status.
I was going to poke around the code but thought I would ask first. Thanks.
No issues after updating mine.
4 Likes
I have had no issues after updating.
2 Likes
No issues here whatsoever.
2 Likes
If there have been any issues, they have resolved themselves. I haven’t had to fiddle with anything for my HA devices to work in Hubitat
3 Likes
I did not experience that but just hit "initialize" in the parent driver, it will reconnect immediately.
1 Like
Are you perhaps confusing the Hubitat integration for Home Assistant with HADB? The former (Hubitat > HA) has needed a reload on occasion after an HA update, but the HADB integration (HA > Hubitat) doesn’t install anything on HA and should not be affected by HA updates (other than a temporary interruption when HA restarts after an update).
I will add to others experiences, in that I have not had any issues with HADB after an HA update.
1 Like
No - I am aware of that issue also. Several times I have restarted Home Assistant and had this issue recently. Initialize doesn't work. Rebooting Hubitat clears it. Of course when I do it deliberately I can't reproduce the issue. I did see some initializing events in the log but I didn't have debug turned on so didn't get much:
2025-12-18 12:56:04 - WebSocket error, reconnecting.
2025-12-18 12:56:06 - initializing...
2025-12-18 13:39:16 - initializing...
But this looks like it is something in my environment so will keep an eye out for it. Thanks for all of the responses.
2 Likes
The reconnect logic in HADB starts at 2s, and then doubles every failed connection attempt, up to a maximum of 600s, or 10 minutes. Thus, if HA is down for a while, it could take up to 10 min before the HE hub even attempts to reconnect to HA. This logic is in place to prevent having the hub constantly trying to reconnect to a HA hub that might be powered off for hours/days.
4 Likes