Custom Component: Hubitat

This morning I noticed that my devices were updating in Home Assistant each time I update them in Hubitat but automations were not triggering.

In other words - Light device (Hubitat) turns on or off and Light device (Home Assistant) turns on or off. However any automations setup in Home Assistant that trigged based on Light device (Home Assistant) turning on and off were not working.

So I went through one of the automations and deleted the Light device (Home Assistant) trigger and then added it back in and it now works.

I am running the latest of everything and show no updates pending.

This does not appear to be happening to all automations - only some of them. But so far I cannot see anything different with this particular set of rules. Simple device triggers. Just posting here to see if anything has noticed anything similar?

I’ve deleted my original post. My fault - I’m new to Home Assistant and hadn’t thought to check if there was a HACS update when I updated the Core. Sorted now.

After the latest update (2024.07) I’ve noticed that events aren’t getting to Home Assistant consistently. Specifically, I have an automation that sets lights to 23% and then waits for motion to start dimming them up. The set level command works but then the motion event isn’t seen by Home Assistant. Checking in the HA log book there are no events for today but several for yesterday. Checking in Hubitat the motion events are there as expected.

Any help is appreciated.

Try enabling debug logging for the integration, then look at the home-assistant.log file after you notice issues and see if any errors are being reported by the integration.

Also…

  1. Are all the devices coming from Hubitat not working, or just some?
  2. Are all devices of a certain type (e.g., motion sensors) not working, or are some of them working and some of them not?

I am going to turn on debug logging but after spot checking a bunch of device coming over from Hubitat the logbook events appear to be populating. I’ll try and report back in a couple days.

I am getting the exact same error as you after migrating the server running my Home Assistant VM to Proxmox and redoing my HA setup so that it is a proper virtual appliance. Which side had the firewall rules and what did you do to change them, if you feel comfortable providing some more detail?

Error text

This error originated from a custom integration.

Logger: custom_components.hubitat.config_flow
Source: custom_components/hubitat/config_flow.py:100
integration: Hubitat (documentation, issues)
First occurred: 6:22:10 AM (1 occurrences)
Last logged: 6:22:10 AM

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’ve just bought a Hubitat Elevation C8 in order to add Zigbee and Z-Wave to my Home Assistant setup. The hub is working fine and I can control a Zigbee Smart Socket as expected. However, when I try to add the integration to Home Assistant all I get is “Unexpected error”. I tried turning on debug logging in configuration.yaml but the only log entries I see are:

2024-12-02 13:10:16.452 DEBUG (MainThread) [custom_components.hubitat.hubitatmaker.hub] Setting host to 192.168.0.10
2024-12-02 13:10:16.453 INFO (MainThread) [custom_components.hubitat.hubitatmaker.hub] Created hub <Hub host=192.168.0.10 app_id=Home Assistant>
2024-12-02 13:10:16.482 ERROR (MainThread) [custom_components.hubitat.config_flow] Unexpected exception

I’m obviously missing something pretty basic here. In the integration configuration page, the only fields I filled in were the host IP, the name of the Maker API (Home Assistant) and the access token. Do I need to fill in any of the optional fields?

When I try to access the Get Device Info URL on the Maker page, eg http://192.168.0.10/apps/api/3/devices/3?access_token=eee733e7-d433-4e8f-a56e-d4970f6c4728 then it returns the expected result.

Could there be some config that I need to change on the hub?

Any help or pointers would be much appreciated.

I don’t think you’re missing anything, although that error makes it hard to tell. I just pushed out v0.9.39 that updates the config flow code and shows more error context, so that may make it easier to see what’s happening.

@jason0x43, thanks for the quick response. It’s sorted now! :slight_smile: As I feared, it was user error :roll_eyes: I was entering the Maker API label, ie ‘Home Assistant’ in the config page but having re-read your setup instructions I noticed that they mention “the 2, 3 or 4 digit number after /apps/api/ in any of the Maker API URLs”. I couldn’t find that magic number anywhere, but having exported the json config I found it!

Thanks again for your efforts and assistance :+1:

Oops, I should have noticed the part of your screenshot that said app_id=Home Assistant. :slight_smile:

Glad to hear you got it working! For future reference, you can see the app ID in any of the test URLs on the Maker API page in Hubitat, or in the page URL when you open the Maker API in Hubitat.

1 Like

Do I need to buy a separate Hubitat hub if I have the ‘GoControl CECOMINOD016164 HUSBZB-1 USB Hub’ already?

My goal is to integrate my Acurite 5 in 1 weather station.

If the weather station supports Zigbee or Zwave, then the HUSBZB-1 will help. However, I think the AcuRite uses 433 MHz signaling, so neither the HUSBZB-1 nor Hubitat would be able to talk to it directly.

There is a cloud-based Hubitat driver that pulls data from your AcuRite web dashboard, so having a Hubitat would let you use that. I haven’t seen an equivalent integration for Home Assistant (which is surprising; it shouldn’t hard too hard to write one), but there are numerous tutorials for using Home Assistant with a 433MHz RF controller to directly receive data from AcuRite sensors.

1 Like

Just installed HA and this integration and everything came across from HE no worries at all. Mainly want to use HA for the dashboards and a few other things that HE won’t do. I’ve tried reading a bit but i’m lost at how to trigger a virtual switch i have in HE from a HA dashboard. I’m sure you guys are all over it or can point me in the right direction on what i should be reading up on?

double check you even need that now, i know when i changed over years ago there was a lot of stuff that worked in HA now so there was know need for virtual switch any more

A virtual switch in Hubitat should show up as a switch entity in HA. You can just add that entity to a dashboard using one of HA’s suggested elements, such as a tile, and you should have a functioning switch control. Toggling the switch in HA should toggle the switch in Hubitat, and vice versa.

I made a typo it’s actually a virtual button but i have changed it to a switch thinking that might be easier and it was and i’ve got it working no worries that way.

Ah, buttons are a bit less intuitive to work with since you don’t get entities for them.

1 Like

Hi, I am just learning and setting up the Hubitat to HA integration as well, but am running into a different issue. Getting a “Unexpected Error” as well. Going into the logs I am seeing a Timeout Error. I have the correct IP address (192.168.1.104), App ID (3), and Token. But it does not seem to want to communicate?
I apologize in advance, I am very new to Hubitat and HA, but I am trying very hard to learn as much as I can before I post!

Posted snips of the logs below, let me know if you need to see more.

Log in HA:

2024-12-28 20:03:28.804 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-28 20:03:28.806 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hubitat which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-12-28 20:16:15.240 ERROR (MainThread) [custom_components.hubitat.config_flow] Unexpected exception: Connection timeout to host http://192.168.104/apps/api/3/devices
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1115, in _wrap_create_connection
    sock = await aiohappyeyeballs.start_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 82, in start_connection
    sock = await _connect_sock(
           ^^^^^^^^^^^^^^^^^^^^
        current_loop, exceptions, addrinfo, local_addr_infos
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 174, in _connect_sock
    await loop.sock_connect(sock, address)
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 641, in sock_connect
    return await fut
           ^^^^^^^^^
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 703, in _request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        req, traces=traces, timeout=real_timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 548, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1056, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1400, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1369, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1112, in _wrap_create_connection
    async with ceil_timeout(
               ~~~~~~~~~~~~^
        timeout.sock_connect, ceil_threshold=timeout.ceil_threshold
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ):
    ^
  File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
The above exception was the direct cause of the following 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(
               ~~~~~~~~~~~~~~~^
        method, f"{self.api_url}/{path}", params=params, connector=conn
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ) as resp:
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 1456, in __aenter__
    self._resp = await self._coro
                 ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 707, in _request
    raise ConnectionTimeoutError(
        f"Connection timeout to host {url}"
    ) from exc
aiohttp.client_exceptions.ConnectionTimeoutError: Connection timeout to host http://192.168.104/apps/api/3/devices
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 471, 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: Connection timeout to host http://192.168.104/apps/api/3/devices
2024-12-28 20:21:23.240 ERROR (MainThread) [custom_components.hubitat.config_flow] Unexpected exception: Connection timeout to host http://192.168.104/apps/api/3/devices
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1115, in _wrap_create_connection
    sock = await aiohappyeyeballs.start_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 82, in start_connection
    sock = await _connect_sock(
           ^^^^^^^^^^^^^^^^^^^^
        current_loop, exceptions, addrinfo, local_addr_infos
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 174, in _connect_sock
    await loop.sock_connect(sock, address)
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 641, in sock_connect
    return await fut
           ^^^^^^^^^
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 703, in _request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        req, traces=traces, timeout=real_timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 548, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1056, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1400, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1369, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1112, in _wrap_create_connection
    async with ceil_timeout(
               ~~~~~~~~~~~~^
        timeout.sock_connect, ceil_threshold=timeout.ceil_threshold
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ):
    ^
  File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
The above exception was the direct cause of the following 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(
               ~~~~~~~~~~~~~~~^
        method, f"{self.api_url}/{path}", params=params, connector=conn
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ) as resp:
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 1456, in __aenter__
    self._resp = await self._coro
                 ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 707, in _request
    raise ConnectionTimeoutError(
        f"Connection timeout to host {url}"
    ) from exc
aiohttp.client_exceptions.ConnectionTimeoutError: Connection timeout to host http://192.168.104/apps/api/3/devices
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 471, 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: Connection timeout to host http://192.168.104/apps/api/3/devices
2024-12-28 20:23:55.239 ERROR (MainThread) [custom_components.hubitat.config_flow] Unexpected exception: Connection timeout to host http://192.168.104/apps/api/3/devices
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1115, in _wrap_create_connection
    sock = await aiohappyeyeballs.start_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 82, in start_connection
    sock = await _connect_sock(
           ^^^^^^^^^^^^^^^^^^^^
        current_loop, exceptions, addrinfo, local_addr_infos
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohappyeyeballs/impl.py", line 174, in _connect_sock
    await loop.sock_connect(sock, address)
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 641, in sock_connect
    return await fut
           ^^^^^^^^^
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 703, in _request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        req, traces=traces, timeout=real_timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 548, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1056, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1400, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1369, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/connector.py", line 1112, in _wrap_create_connection
    async with ceil_timeout(
               ~~~~~~~~~~~~^
        timeout.sock_connect, ceil_threshold=timeout.ceil_threshold
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ):
    ^
  File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__
    raise TimeoutError from exc_val
TimeoutError
The above exception was the direct cause of the following 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(
               ~~~~~~~~~~~~~~~^
        method, f"{self.api_url}/{path}", params=params, connector=conn
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ) as resp:
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 1456, in __aenter__
    self._resp = await self._coro
                 ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client.py", line 707, in _request
    raise ConnectionTimeoutError(
        f"Connection timeout to host {url}"
    ) from exc
aiohttp.client_exceptions.ConnectionTimeoutError: Connection timeout to host http://192.168.104/apps/api/3/devices
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 471, 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: Connection timeout to host http://192.168.104/apps/api/3/devices

Log on Hubiitat (removed token info to ********):

[app:3](http://192.168.1.104/logs?tab=past&appId=3#)2024-12-28 08:22:14.556 PM

debug

Testing URL is http://192.168.1.104/apps/api/3/devices?access_token=ddac7081-30c1-479a-ab87-*************

[app:3](http://192.168.1.104/logs?tab=past&appId=3#)2024-12-28 08:22:14.555 PM

debug

Initialize called

Thank you in advance.

Just to add to this, I installed the Firefox add on in HA, and I can reach the Testing URL from the Hubitat log from the browser in HA. So apparently they can reach each other on the network. The Hubitat logs shows the calls from that browser test.
Thanks

Hi everyone. I was able to solve my problem. The issue was putting “https://” in front of my Hubitat (C-8 Pro) IP address when configuring the HA integration. I hope this will help future integrators to not miss this simple distinction.

2 Likes