Custom Component: Hubitat

2025-01-28 19:35:02.716 DEBUG (MainThread) [custom_components.hubitat.hubitatmaker.hub] Received event: {'name': 'temperature', 'value': '67.5', 'displayName': "Kade's Sensor - Temperature & Humidity0", 'deviceId': '2172', 'descriptionText': None, 'unit': '°C', 'type': None, 'data': None}																									

The temperature update event from Hubitat says the temperature is in °C (which I agree doesn’t make sense). Is your hub set to use °C as the default, or is there a unit setting for that temperature sensor?

I have been searching all over and messing with stuff since I posted those logs and everywhere that I have found a temp unit it is set to F. I was digging around on the device today, which is a Shelly Plus H&T, and found that the webhook that is used to send the temp info to hubitat seems to be in C and I’m assuming the driver then converts it to F because it displays correctly on hubitat. I’m gunna continue to do some digging though. The thing that I don’t understand is if I reload the hubitat integration in HA, the temps show up correctly. It’s only when they get the next update that it goes crazy.

Hi,
I have a Zoom ZEN31 RGMW dimmer connected to Hubitat, with the details listed below. In Hubitat, I am using the standard built-in driver (Zooz RGBW Dimmer) and have an RGBW strip connected.


{"name":"Zooz Zen31 LED Controller","label":"Porch LED Strip Zone 1","type":"Zooz RGBW Dimmer","id":"829","date":"2025-03-27T01:18:47+0000","model":null,"manufacturer":null,"room":"Porch","capabilities":["Refresh","ReleasableButton","Light","Switch","PushableButton","Configuration","Actuator","PowerMeter","HoldableButton","ChangeLevel","LightEffects","SwitchLevel","Sensor","DoubleTapableButton"],"attributes":{"greenLevel":"100","dataType":"NUMBER","values":null,"effectName":"Disabled","power":"8.4","released":"1","switch":"on","doubleTapped":"1","level":"99","redLevel":"100","lightEffects":"{0=Disabled, 6=Fireplace, 7=Storm, 8=Rainbow, 9=Polar Lights, 10=Police}","numberOfButtons":"4","pushed":"1","held":"1","blueLevel":"100"},"commands":[{"command":"configure"},{"command":"doubleTap"},{"command":"doubleTap"},{"command":"hold"},{"command":"hold"},{"command":"off"},{"command":"on"},{"command":"push"},{"command":"push"},{"command":"refresh"},{"command":"release"},{"command":"release"},{"command":"setBlueLevel"},{"command":"setEffect"},{"command":"setGreenLevel"},{"command":"setLevel"},{"command":"setNextEffect"},{"command":"setPreviousEffect"},{"command":"setRedLevel"},{"command":"startLevelChange"},{"command":"stopLevelChange"}]}

I can set the effects of the dimmer using hubitat.send_command and calling the setEffect method. However, I can’t seem to figure out how to set the colors from an HA automation.
I tried:

  - service: light.turn_on
    target:
      entity_id: "light.porch_led_strip_zone_1"
    data:
      color_name: "red"
      brightness_pct: "100"

and:

  - service: hubitat.send_command
    data:
      entity_id: "light.porch_led_strip_zone_1"
      command: setRedLevel
      args: '100'

  - service: hubitat.send_command
    data:
      entity_id: "light.porch_led_strip_zone_1"
      command: setGreenLevel
      args: '0'

  - service: hubitat.send_command
    data:
      entity_id: "light.porch_led_strip_zone_1"
      command: setBlueLevel
      args: '0'

and this for white:

  - service: light.turn_on
    target:
      entity_id: "light.porch_led_strip_zone_1"
    data:
      color_temp_kelvin: "3000"
      brightness_pct: "100"

Nothing is getting the strip to change colors. The strip works fine directly in Hubitat.

Any suggestions?

Can you control the light through Home Assistant not using an automation? You shouldn’t need to send low-level commands – you should be able to use standard Home Assistant light control actions, like “turn on” with brightness and color options.

If you do want to send a low-level command, the standard command uses hue, saturation, and and level (although your driver may do something different).

Hi Jason,
You’re right, in HA under Entities, it’s just showing on/off capabilities! Do you know why it might only be showing on/off in HA while it has full color capabilities in Hubitat?

Check the device capabilities. By default, any light will have on/off functionality. The integration also looks for ColorControl, ColorTemperature, and SwitchLevel capabilities to know if the light supports color, color temp, and dimming functionality.

Hey @jason0x43 I’ve switched back to Hubitat for now as I was having some issues forwarding my USB sticks through unraid to my VM. I’ve been noticing some issues with door contact updates and even some commands. I can turn a switch on and off in Hubitat but it won’t always work in HA. Have you seen anything like that lately?
I haven’t set up the event server, is that necessary? Motion sensors are working and zigbee door contacts are working (better).
Terrible data collection and issue presentation, I’m sorry haha.

Since some things are updating it sounds like the event server is working properly. If the event server wasn’t properly configured, no devices would be updating in HA. A good way to diagnose that would be to enable debug logging, then try toggling a problematic switch and see what messages show up in the log.

From the integration’s perspective, it doesn’t really matter what type of device you’re using. Zigbee, zwave, or wifi all work the same – Hubitat deals with the device, and just sends events to HA and responds to commands from HA. Are the devices in question 100% reliable in Hubitat, and only failing to update in HA, or are they also failing to update in Hubitat sometimes?

1 Like

Yea open and close updates immediately in Hubitat but not always in HA.

Ultimately I just got HAOS working baremetal on my old Mac Mini, which is what I wanted for quite some time. Zigbee stick and Z-Wave stick were recognized immediatly and seem to be working well, so I think I’ll migrate back to that. Sorry to bug ya. Hope all is well.

That’s exactly what I have – HAOS running directly on a Mac Mini. It’s pretty great! So much faster than a Pi. :slight_smile:

1 Like

So I’m having an issue where the Mac Mini won’t fully boot if my Zigbee and Z-Wave dongles are connected.
Do you have that issue?
The issue with the Mac is I don’t think there’s an accesible bios… or maybe there is…

Hmmm…no, I don’t think I’ve ever had that happen. I have a Sky Connect and an Aeotec 700-series Zwave dongle, and the Mac boots up fine with them attached.

Mine’s a 2013 Mac Mini with a Fusion Drive. The only OS on it is HA (no dual booting or anything). It’s been pretty stable since I installed HA on it.

1 Like

I am running a hubitat C8 and using maker api . The issue is latency. The C8 and HA are on the same subnet. Any idea? Also I hooked up a c7 and paired two device and attached that to HA But shortly after all devices from the C7 go unaviable. Thoughts?

What kind of latency are you seeing? You can try turning on debug logging (see the project README), then see how it takes an event to show up in the log when a device does something. That could indicate whether the C8 is slow to send events or HA is slow to process them.

For the C7 issue, I would again recommend enabling debug logging and checking to see if you’re getting events from the hub. A common issue is that Hubitat is unable to send messages to the integration due to configuration issues.

I’ve read this (and even searched it) but I do not understand what the words mean. “Open the inegration’s options and run through the options flow.”

My assumption is go to Settings - Devices - Integrations… from there I can’t find any settings or “flows” that give me the option to delete the device. I did remove the device from Maker in HE already.

Open the integration and tap the settings button, then step through the settings dialogs that pop up. It used to be more obvious, but the UI has gotten a bit more streamlined in the last few versions.

2 Likes

Thanks for the info. I’m ditched habitat and bought some new hardware

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

This integration has nothing to do with HADB. You might want to post your question on the Hubitat forum.

Based on the log data the user provided, he is not having issues with HADB. HADB does not use any Home Assistant custom code. It simply uses HA’s websocket interface to ‘listen’ for data changes and to send updates. HADB brings HA devices into HE.

Based on the log data, it appears @ebbeckn is probably using @jason0x43’s Hubitat to Home Assistant integration. The error seems to indicate that HA is not able to connect to the user’s Hubitat Hub using the 192.168.0.96 IP address.

@ebbeckn - Is your Hubitat Hub still using the 192.168.0.96 IP address?
Did you make any changes to your HE hub, like accidentally removing the MakerAPI App that HA was talking to?

1 Like