Home Assistant migration messed with Hubitat

[celest marsh]

I migrated my home server from TrueNAS to Proxmox VE. In the old setup, I had a baremetal image running as a VM, and Home Assistant was giving me errors that this was definitely not recommended (it worked fine).
In the new setup, I used this script to set up the virtual machine
https://community-scripts.github.io/ProxmoxVE/scripts?id=haos-vm
It can access all 20 LiFX lights, my WLED closet light, all the other services EXCEPT hubitat. Multiple forum threads point at this being a firewall issue but I cannot find any details about exactly how people resolved it. I do not have the firewall enabled in Proxmox currently, so I'm not sure why it would just drop the connection to this one node.

I could really use some help to figure this out. Hubitat does everything I need it to and I really do not want to replace it with a 100$ SkyConnect stick unless that really is the only way to resolve this effectively.

[vague musk]

I guess you mean this hacs Hubitat integration?
Did you preserver the IP address of HA after the migration?
Did you already tried to follow the Troubleshooting section of the custom component docs (especial the "Checking device capabilities" and "Logging" part) ?

btw. don't take any offers serious, which calls 100$ for a ZBT-1 😉

[celest marsh]

That's correct - the Hubitat HACS integration. When I migrated, it would not load no matter what so I did what has worked in the past - I removed it and then when I attempt to add it back, I get the following error:

Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 167, in check_config
await self._check_api()
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 307, in _check_api
await self._api_request("devices")
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 467, in _api_request
raise e
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 414, in _api_request
async with aiohttp.request(
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 1391, in aenter
self._resp = await self._coro
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 690, in _request
await resp.start(conn)
File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1059, in start
message, payload = await protocol.read() # type: ignore[union-attr]
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/streams.py", line 644, in read
await self._waiter
aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/config/custom_components/hubitat/config_flow.py", line 100, in async_step_user
info = await _validate_input(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hubitat/config_flow.py", line 474, in _validate_input
await hub.check_config()
File "/config/custom_components/hubitat/hubitatmaker/hub.py", line 169, in check_config
raise ConnectionError(str(e))
ConnectionError: Server disconnected

I can ping Hubitat from the host server - not sure how to try to ping it from within the VM. Because this error occurs when trying to add the integration back, I don't even get to where I can enable debug logging or get any device statuses.

[celest marsh]

Oh, and I did preserve the IP address post-migration.

Restoring it from the backup caused it to pull the static IP again.

[vague musk]

You can use the terminal add-on to ping and also make calls against their api with curl as described in the Troubleshooting section of the custom component docs