This has started happening again or it never stopped and I didn’t notice.
Just updated home assistant and even with debug turned on I don’t get much.
WebSocket error, reconnecting
Then just Initializing and Closing connection.
Restart of Hubitat and everything works.
Not sure what is going on but will keep playing around with it.
If you want to reconnect immediately, press "initialize".
If it still show a websocket error, it's because HADB cannot reach your HA instance. Make sure you can reach HA in a browser with its IP on the same subnet as HE.
Other possibilities: bad access token, wrong port, secure access on HA (https)
When this happens - and it doesn't happen every time - initialize does not work as noted. Same subnet, same IPs, same ports, nothing changes.
I have set a notification on Hubitat to let me know of a persistent reconnect situation so I can explore more.
How often do you reboot your Hubitat hub? The reason I ask is that hubs that run for a long time between reboots, sometimes slowly degrade performance due to possible memory leaks. The Hubitat team is aware of this and are working on identifying and resolving issues.
One possible workaround that some users employ, myself included, is to automatically reboot the hub periodically. I have a Rule Machine rule set up to reboot the hub every Saturday at 5am. I have had this rule in place for 7+ years with no ill effects, and my hub runs very smoothly.
Just an idea for you to ponder. 
Yes - good idea. I used to have them reboot weekly but got away from that. I will reinstitute it and see how things go.
Version 2.21:
This change is getting things ready for the Hubitat 2.5.x release. There is no change to the HADB functionality. It simply allows HADB to properly work with the upcoming HE Web UI changes in 2.5.x.
Big changes coming?????
It's not anything very crazy -- just some left-nav menu tweakery.
Hopefully nothing breaking to any of the older packages in HPM.
Shouldn't break anything. By default older "apps", even if they are "integrations", will continue to show up as "apps". Because it has been updated, HADB will now show up as an integration.
Well the weekly reboot didn't clear the issue. Hub was rebooted on Sunday and early this morning it happened again. It seems likely this is something in the underlying Hubitat architecture as I have had a similar issue with the abode integration when it simply wouldn't reconnect and eventually I had to move it off onto one of my other hubs. I have been slowly disabling things and moving them to Home Assistant to reduce the load on my hubs as they all seem to get overloaded after a while and behave unusually. But for now a reboot is all that seems to clear this.
dev:39882026-04-08 06:07:45.831 AMdebugClosing connection...
dev:39882026-04-08 06:07:45.830 AMinfoinitializing...
dev:39882026-04-08 06:06:59.621 AMdebugClosing connection...
dev:39882026-04-08 06:06:59.620 AMinfoinitializing...
dev:39882026-04-08 06:06:57.070 AMdebugClosing connection...
dev:39882026-04-08 06:06:49.130 AMdebugClosing connection...
dev:39882026-04-08 06:06:49.129 AMinfoinitializing...
dev:39882026-04-08 06:06:49.105 AMwarndescription logging is: true
dev:39882026-04-08 06:06:49.104 AMwarndebug logging is: true
dev:39882026-04-08 06:06:49.103 AMinfoupdated...
dev:39882026-04-08 06:06:35.632 AMinfoinitializing...
dev:39882026-04-08 03:16:01.680 AMinfoinitializing...
dev:39882026-04-08 03:15:59.701 AMdebugsent ping but didn't receive pong within 30000ms (after 6648 successful ping/pongs)
dev:39882026-04-08 03:15:59.665 AMwarnWebSocket error, reconnecting.
The issue you are experiencing seems to emerge from your particular setup. Perhaps someone better verse in networking could suggest a path to investigate.
Download the Hubitat app
