Custom Component: Hubitat

BlueMoon23 · August 29, 2022, 3:16pm

I have several Fibaro radiator valves attached to my Hubitat which I would like to control from HA, but don’t understand how the data is brought in to HA and I get errors when I try to change the value, can you help? My issue is this:
I have set the device up in MakerAPI, and I can see the data for the battery and the temperature in HA, as two entities (1) sensor.“name”.battery and (2) sensor.“name”.temperature. However, when I try to change the heating set point in HA, I get an error.

Furthermore, the entity sensor.“name”.heatingsetpoint is not available.

I have set the log up to debug, and if I set the heatingsetpoint in Hubitat, I can see the value in the log as MakerAPI posts it.

When I use the simple thermostat card, if I click on “N/A”:

I can see the target temperature:

I just can’t adjust it, without getting the error.

Any ideas what I am dong wrong?

Great integration BTW, just about everything else works on it.

jason0x43 · August 29, 2022, 7:29pm

If you could post the device data from Hubitat, I’ll see if I can figure out what’s going on.

BlueMoon23 · August 30, 2022, 5:53pm

Sure, here are the details from the device:

{
  "id": "104",
  "name": "Fibaro Heat Controller Thermostat Head",
  "label": "Harry's Bedroom Radiator Valve",
  "type": "Fibaro Heat Controller Thermostat Head",
  "room": "Harry's Bedroom",
  "attributes": [
    {
      "name": "battery",
      "currentValue": 39,
      "dataType": "NUMBER"
    },
    {
      "name": "thermostatOperatingState",
      "currentValue": null,
      "dataType": "ENUM",
      "values": [
        "heating",
        "pending cool",
        "pending heat",
        "vent economizer",
        "idle",
        "cooling",
        "fan only"
      ]
    },
    {
      "name": "supportedThermostatModes",
      "currentValue": null,
      "dataType": "JSON_OBJECT",
      "values": [
        "auto",
        "off",
        "heat",
        "emergency heat",
        "cool"
      ]
    },
    {
      "name": "temperature",
      "currentValue": 21.3,
      "dataType": "NUMBER"
    },
    {
      "name": "temperature",
      "currentValue": 21.3,
      "dataType": "NUMBER"
    },
    {
      "name": "heatingSetpoint",
      "currentValue": 10,
      "dataType": "NUMBER"
    },
    {
      "name": "thermostatMode",
      "currentValue": "auto",
      "dataType": "ENUM",
      "values": [
        "auto",
        "off",
        "heat",
        "emergency heat",
        "cool"
      ]
    },
    {
      "name": "thermostatSetpoint",
      "currentValue": null,
      "dataType": "NUMBER"
    },
    {
      "name": "coolingSetpoint",
      "currentValue": null,
      "dataType": "NUMBER"
    },
    {
      "name": "supportedThermostatFanModes",
      "currentValue": null,
      "dataType": "JSON_OBJECT",
      "values": [
        "on",
        "circulate",
        "auto"
      ]
    },
    {
      "name": "thermostatFanMode",
      "currentValue": null,
      "dataType": "ENUM",
      "values": [
        "on",
        "circulate",
        "auto"
      ]
    }
  ],
  "capabilities": [
    "Configuration",
    "Actuator",
    "Refresh",
    "Battery",
    {
      "attributes": [
        {
          "name": "battery",
          "dataType": null
        }
      ]
    },
    "TemperatureMeasurement",
    {
      "attributes": [
        {
          "name": "temperature",
          "dataType": null
        }
      ]
    },
    "Thermostat",
    {
      "attributes": [
        {
          "name": "temperature",
          "dataType": null
        },
        {
          "name": "heatingSetpoint",
          "dataType": null
        },
        {
          "name": "coolingSetpoint",
          "dataType": null
        },
        {
          "name": "thermostatSetpoint",
          "dataType": null
        },
        {
          "name": "thermostatMode",
          "dataType": null
        },
        {
          "name": "thermostatFanMode",
          "dataType": null
        },
        {
          "name": "thermostatOperatingState",
          "dataType": null
        },
        {
          "name": "supportedThermostatModes",
          "dataType": null
        },
        {
          "name": "supportedThermostatFanModes",
          "dataType": null
        }
      ]
    },
    "Sensor"
  ],
  "commands": [
    "auto",
    "configure",
    "cool",
    "emergencyHeat",
    "fanAuto",
    "fanCirculate",
    "fanOn",
    "heat",
    "off",
    "refresh",
    "setCoolingSetpoint",
    "setHeatingSetpoint",
    "setThermostatFanMode",
    "setThermostatMode"
  ]
}

Byarnell05 · September 19, 2022, 1:54am

Hello, asking this question again with a bit more info. I have 4x Inovelli Light Strips that when I try to adjust the color of them while the light is on it will change the color and then immediately turn them off.

These are the HA logs, I turned the light on and then adjusted the color:

Front Door Mantle Light turned off triggered by service light.turn_on
6:31:17 PM - 6 minutes ago - Brad
Front Door Mantle Light turned on triggered by service light.turn_on
6:31:09 PM - 6 minutes ago - Brad

These are the logs from HE from the same command sequence:

dev:1314 2022-09-18 06:31:16.935 pm infoFront Door Mantle Light: Switch Multilevel report received with value of off (0)
dev:1314 2022-09-18 06:31:16.920 pm debugFront Door Mantle Light: SwitchMultilevelReport(value: 0, targetValue: 0, duration: 0)
dev:1314 2022-09-18 06:31:16.909 pm infoFront Door Mantle Light: Basic report received with value of off (0)
dev:1314 2022-09-18 06:31:16.907 pm debugFront Door Mantle Light: BasicReport(value:0)
dev:1314 2022-09-18 06:31:14.808 pm infoFront Door Mantle Light: Bulb is off. Turning on
dev:1314 2022-09-18 06:31:14.806 pm infoFront Door Mantle Light: setColor([hue:83, saturation:100.0])
dev:1314 2022-09-18 06:31:14.801 pm infoFront Door Mantle Light: Switch Multilevel report received with value of on (99)
dev:1314 2022-09-18 06:31:14.797 pm debugFront Door Mantle Light: SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0)
dev:1314 2022-09-18 06:31:14.784 pm infoFront Door Mantle Light: Basic report received with value of on (99)
dev:1314 2022-09-18 06:31:14.782 pm debugFront Door Mantle Light: BasicReport(value:99)
dev:1314 2022-09-18 06:31:14.737 pm infoFront Door Mantle Light: on()
dev:1314 2022-09-18 06:31:08.611 pm infoFront Door Mantle Light: Switch Multilevel report received with value of on (99)
dev:1314 2022-09-18 06:31:08.608 pm debugFront Door Mantle Light: SwitchMultilevelReport(value: 99, targetValue: 0, duration: 0)
dev:1314 2022-09-18 06:31:08.599 pm infoFront Door Mantle Light: Basic report received with value of on (99)
dev:1314 2022-09-18 06:31:08.596 pm debugFront Door Mantle Light: BasicReport(value:99)
dev:1314 2022-09-18 06:31:07.468 pm infoFront Door Mantle Light: on()
--- Live Log Started, waiting for events ---

Amy info would be greatly appreciated! Thanks!

jason0x43 · September 19, 2022, 2:54am

Have you tried turning on debug logging for the integration in HA? That should show a bit more detail around what commands are being sent to Hubitat.

Byarnell05 · September 19, 2022, 9:50pm

Ok finally figured out where to turn on debug logging and pulled what I could.

The light was off so I started by turning it on:

2022-09-19 14:48:34.983 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547779668112] Received {'type': 'call_service', 'domain': 'light', 'service': 'turn_on', 'service_data': {'entity_id': 'light.front_door_mantle_light_2'}, 'id': 71}
2022-09-19 14:48:34.987 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.front_door_mantle_light_2>
2022-09-19 14:48:34.996 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: EventTask(event=<Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.front_door_mantle_light_2>)
2022-09-19 14:48:36.289 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=light.front_door_mantle_light_2, old_state=<state light.front_door_mantle_light_2=off; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:47:11.077180-07:00>, new_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(298.8, 100.0), rgb_color=(249, 0, 255), xy_color=(0.378, 0.151), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>>
2022-09-19 14:48:36.292 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: EventTask(event=<Event state_changed[L]: entity_id=light.front_door_mantle_light_2, old_state=<state light.front_door_mantle_light_2=off; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:47:11.077180-07:00>, new_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(298.8, 100.0), rgb_color=(249, 0, 255), xy_color=(0.378, 0.151), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>>)
2022-09-19 14:48:36.295 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547837102736] Sending {"id":2,"type":"event","event":{"c":{"light.front_door_mantle_light_2":{"+":{"s":"on","lc":1663624116.288921,"c":"01GDBVJWSAYBPV19C5MBRMXXXQ","a":{"color_mode":"hs","brightness":252,"hs_color":[298.8,100.0],"rgb_color":[249,0,255],"xy_color":[0.378,0.151]}}}}}}
2022-09-19 14:48:36.298 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547779668112] Sending {"id":3,"type":"event","event":{"c":{"light.front_door_mantle_light_2":{"+":{"s":"on","lc":1663624116.288921,"c":"01GDBVJWSAYBPV19C5MBRMXXXQ","a":{"color_mode":"hs","brightness":252,"hs_color":[298.8,100.0],"rgb_color":[249,0,255],"xy_color":[0.378,0.151]}}}}}}

I gave it a second and then tried to adjust the color and this is what followed:

2022-09-19 14:48:55.035 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547779668112] Received {'type': 'call_service', 'domain': 'light', 'service': 'turn_on', 'service_data': {'entity_id': 'light.front_door_mantle_light_2', 'hs_color': [45, 100]}, 'id': 72}
2022-09-19 14:48:55.039 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.front_door_mantle_light_2, hs_color=[45, 100]>
2022-09-19 14:48:55.048 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: EventTask(event=<Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.front_door_mantle_light_2, hs_color=[45, 100]>)
2022-09-19 14:48:55.222 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=light.front_door_mantle_light_2, old_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(298.8, 100.0), rgb_color=(249, 0, 255), xy_color=(0.378, 0.151), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>, new_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(43.2, 100.0), rgb_color=(255, 183, 0), xy_color=(0.537, 0.438), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>>
2022-09-19 14:48:55.225 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: EventTask(event=<Event state_changed[L]: entity_id=light.front_door_mantle_light_2, old_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(298.8, 100.0), rgb_color=(249, 0, 255), xy_color=(0.378, 0.151), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>, new_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(43.2, 100.0), rgb_color=(255, 183, 0), xy_color=(0.537, 0.438), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>>)
2022-09-19 14:48:55.230 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547837102736] Sending {"id":2,"type":"event","event":{"c":{"light.front_door_mantle_light_2":{"+":{"lu":1663624135.22211,"c":"01GDBVKGBXVCE46XBD6071R4YS","a":{"hs_color":[43.2,100.0],"rgb_color":[255,183,0],"xy_color":[0.537,0.438]}}}}}}
2022-09-19 14:48:55.236 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547779668112] Sending {"id":3,"type":"event","event":{"c":{"light.front_door_mantle_light_2":{"+":{"lu":1663624135.22211,"c":"01GDBVKGBXVCE46XBD6071R4YS","a":{"hs_color":[43.2,100.0],"rgb_color":[255,183,0],"xy_color":[0.537,0.438]}}}}}}
2022-09-19 14:48:57.325 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=light.front_door_mantle_light_2, old_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(43.2, 100.0), rgb_color=(255, 183, 0), xy_color=(0.537, 0.438), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>, new_state=<state light.front_door_mantle_light_2=off; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:57.325260-07:00>>
2022-09-19 14:48:57.328 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: EventTask(event=<Event state_changed[L]: entity_id=light.front_door_mantle_light_2, old_state=<state light.front_door_mantle_light_2=on; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], color_mode=hs, brightness=252, hs_color=(43.2, 100.0), rgb_color=(255, 183, 0), xy_color=(0.537, 0.438), friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:36.288921-07:00>, new_state=<state light.front_door_mantle_light_2=off; min_mireds=153, max_mireds=500, supported_color_modes=['color_temp', 'hs'], friendly_name=Front Door Mantle Light, supported_features=19 @ 2022-09-19T14:48:57.325260-07:00>>)
2022-09-19 14:48:57.331 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547837102736] Sending {"id":2,"type":"event","event":{"c":{"light.front_door_mantle_light_2":{"+":{"s":"off","lc":1663624137.32526},"-":{"a":["xy_color","color_mode","brightness","rgb_color","hs_color"]}}}}}
2022-09-19 14:48:57.334 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [547779668112] Sending {"id":3,"type":"event","event":{"c":{"light.front_door_mantle_light_2":{"+":{"s":"off","lc":1663624137.32526},"-":{"a":["xy_color","color_mode","brightness","rgb_color","hs_color"]}}}}}

jason0x43 · September 20, 2022, 2:56am

Hmmm…it doesn’t look like anything odd is coming from HA. There’s a command to turn the light on, a state change event, and then the light just seems to shut off.

Could you try enabling debug logging for the Hubitat integration to see specifically what the integration is doing?

Byarnell05 · September 20, 2022, 2:18pm

I’m assuming this is what you were referring to, this is the debug logging from the MakerAPI integration in Hubitat.

app:11122022-09-20 06:57:02.250 am debugdevice event: {"name":"lastActivity","value":"2022 Sep 20 Tue 6:57:02 AM","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":null,"data":null}
app:11122022-09-20 06:57:02.235 am debugdevice event: {"name":"switch","value":"off","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":"physical","data":null}
app:11122022-09-20 06:57:00.185 am debugdevice event: {"name":"saturation","value":"100.0","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":null,"data":null}
app:11122022-09-20 06:57:00.178 am debugdevice event: {"name":"hue","value":"37","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":null,"data":null}
app:11122022-09-20 06:57:00.147 am debugdeviceItem called
app:11122022-09-20 06:57:00.145 am debugExecuting with secondary command: setColor [[hue:37, saturation:100.0]] on device: Front Door Mantle Light
app:11122022-09-20 06:57:00.066 am debugdevice event: {"name":"lastActivity","value":"2022 Sep 20 Tue 6:57:00 AM","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":null,"data":null}
app:11122022-09-20 06:57:00.056 am debug[COLOR_MAP]
app:11122022-09-20 06:57:00.048 am debug[childOff, childOn, childRefresh, childSetLevel, componentOff, componentOn, componentRefresh, componentSetLevel, configure, customEffectStart, customEffectStop, hold, off, on, pixelEffectNext, pixelEffectPrevious, pixelEffectStart, pixelEffectStop, push, refresh, reset, setAssociationGroup, setColor, setColorTemperature, setConfigParameter, setHue, setIndicator, setLevel, setSaturation, startLevelChange, startNotification, stopLevelChange, stopNotification]
app:11122022-09-20 06:57:00.045 am debug[{"hue": 37, "saturation": 100.0}]
app:11122022-09-20 06:57:00.044 am debugsetColor
app:11122022-09-20 06:57:00.043 am debugfindDevice called
app:11122022-09-20 06:57:00.042 am debugsendDeviceCommandSecondary called
app:11122022-09-20 06:56:59.980 am debugdeviceItem called
app:11122022-09-20 06:56:59.979 am debugExecuting command: on on device: Front Door Mantle Light
app:11122022-09-20 06:56:59.962 am debugfindDevice called
app:11122022-09-20 06:56:59.961 am debugsendDeviceCommand called
app:11122022-09-20 06:56:54.123 am debugdevice event: {"name":"power","value":"6","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":"W","type":null,"data":null}
app:11122022-09-20 06:56:54.119 am debugdevice event: {"name":"lastActivity","value":"2022 Sep 20 Tue 6:56:54 AM","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":null,"data":null}
app:11122022-09-20 06:56:51.165 am debugdevice event: {"name":"lastActivity","value":"2022 Sep 20 Tue 6:56:51 AM","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":null,"data":null}
app:11122022-09-20 06:56:51.156 am debugdevice event: {"name":"switch","value":"on","displayName":"Front Door Mantle Light","deviceId":"1314","descriptionText":null,"unit":null,"type":"digital","data":null}
app:11122022-09-20 06:56:49.993 am debugdeviceItem called
app:11122022-09-20 06:56:49.992 am debugExecuting command: on on device: Front Door Mantle Light
app:11122022-09-20 06:56:49.951 am debugfindDevice called
app:11122022-09-20 06:56:49.950 am debugsendDeviceCommand called

jason0x43 · September 20, 2022, 11:52pm

You can enable debugging logging for the Hubitat integration in HA:

logger:
  default: info
  logs:
    hubitatmaker: debug
    custom_components.hubitat: debug

Then in your HA log you’ll see messages like this when working with devices:

2020-05-19 08:28:18 DEBUG (MainThread) [custom_components.hubitat.light] Turning off Basement Hearth Lights
2020-05-19 08:28:18 DEBUG (MainThread) [hubitatmaker.hub] Sending command off() to 1510

After looking at your log again, though, I wonder if the issue is that the integration is only sending hue and saturation with the set color, and possibly the light driver you’re using is filling in the level with 0, which would turn off the switch. I’ll try to get out a beta release you can try in a bit.

jason0x43 · September 21, 2022, 12:18am

I just published v0.8.2b1. Assuming you’re using HACS, go to the Hubitat integration card in HACS, click the three-dot menu, and click Redownload, then choose “Show beta versions” and install 0.8.2b1. You may also need to click the Update button first.

Byarnell05 · September 21, 2022, 2:00am

Awesome, I’ll give it a shot now!

Byarnell05 · September 21, 2022, 2:06am

Just downloaded that version and gave it a test and am happy to say that fixed the issue! Thanks for your help!

sdholden28 · September 29, 2022, 2:06am

@jason0x43 would you mind having a look at this post? I’m unsure where the problem lies, but I suppose its possible that it might be something with the habitat integration.

jason0x43 · September 29, 2022, 3:08am

Hmmm…so the Hubitat integration is installed and working on that system? This isn’t a blueprint being created on a system with the hubitat integration installed and then used on a system without it? Or maybe the system had two instances of the Hubitat integration installed, and the one used to create the integration that was used as the basis for the blueprint was removed?

From the error, it looks like HA was trying to load a config entry for the Hubitat integration that doesn’t exist. I’ve never used blueprints, so I’m not sure how much information a blueprint contains about a system when device triggers are used. I’ll try to take a look at it in the near future.

sdholden28 · September 29, 2022, 1:18pm

Yes, hubitat integration has been installed and working on this system, without issue. I’m going down the path that you’ve gone down apparently, in moving everything but zwave/zigbee onto Home Assistant. This is the first issue I’ve run into with the integration, IF that’s where the issue is. Only one habitat integration has ever been installed on this system, and it was only installed once. I haven’t removed and readded or anything like that. The only thing I do with the integration itself is add additional devices on the habitat maker API side, and then reload the integration to pick them up. I took what you’ve taken from the log snippet, thinking there could be something wrong with the specific habitat entity I was using in the automation I made from the blueprint, even though that same entity seems to work fine if I just make an automation from scratch. So I removed the entity on the hubitat maker api side, reloaded the integration in HA, and removed the orphaned entity, restarted, and added the entity back all around. No change. Then I made another automation from this same blueprint using a DIFFERENT hubitat entity AND lifx entity compared to the first time. Same result, same error. What I really don’t understand is what gets loaded on reboot that apparently doesn’t cause any problems until then. As I said, the automation from the blueprint works perfectly when used immediately after creation. No issues, no delays, no errors, no crazy log entries, nothing. On reboot however, something is being checked that is causing some sort of reference problem, even though its not presenting a usage issue, or any issue at all that I can tell, until its checked. I turned on debug logging and there’s the log output below. It looks like there’s an issue with how one of the triggers from the blueprint is being passed? I don’t know why it would be any different than a scratch automation with the same trigger. In this case its showing device 514 which is the one I originally used to discover this problem. I can confirm however that this same error follows whatever hubitat device I use when creating the automation from the blueprint.

2022-09-29 08:21:57.367 DEBUG (MainThread) [hubitatmaker.hub] Loaded device list
2022-09-29 08:21:57.367 DEBUG (MainThread) [hubitatmaker.hub] Loading device 514
File "/config/custom_components/hubitat/device_trigger.py", line 90, in async_validate_trigger_config
hubitat_device, _ = get_hubitat_device(hass, device.id)
File "/config/custom_components/hubitat/device_trigger.py", line 213, in get_hubitat_device
File "/config/custom_components/hubitat/hub.py", line 471, in get_hub
2022-09-29 08:21:57.483 DEBUG (MainThread) [hubitatmaker.hub] Loaded device 514

jason0x43 · September 30, 2022, 11:21pm

I was able to replicate the issue locally. It looks like it’s only happening when devices in the blueprint are in the “hubitat” domain. The only such devices I know of offhand are push buttons, which are handled differently than other device types. Devices that are managed by Hubitat but that use standard HA domains, like lights and switches (which are in the “light” and “switch” domains) seem to work fine.

I’ll try to look into it more this weekend to see what’s going on.

potts-mike · October 2, 2022, 1:02pm

I’m sharing a nest doorbell from hubitat to HA. In Hubitat the button is exposed to trigger actions but it doesn’t appear to be come over to HA. I tried the native nest/HA integration but it’s not exposed there either.

k8gg · October 2, 2022, 4:04pm

=== Nothing to do with this Hubitat integration thread, but in the spirit to help @potts-mike ===
In the HA integration page for Nest, the doorbell press would be a device trigger event to kick off your automation(s).

And on the Nest integration page there’s this screen capture:

… so are you saying you are not seeing the “Doorbell pressed” trigger from the drop-down?

======

(Maybe we should move to a new thread to discuss the Nest Doorbell and the HA Nest Integration…)

potts-mike · October 2, 2022, 5:45pm

I was wanting to pull the button press over from hubitat but the native integration seems easy enough. I can fleets if we’re to far off topic.

jason0x43 · October 2, 2022, 8:54pm

Whether the button shows up or not depends on what kind of device information Hubitat is sending over. If you want to post the capabilities for your Nest device here I can take a look. However, I’d say that if you’re already running HA, you may want to just go with that. Support for cloud-based devices like Nest is generally going to be better (or at least more up-to-date) in HA than Hubitat.