[BUG] 2.5.0.135 breaks HomeKit Bridge RGBW devices, including Virtual RGBW Bulb

Get Help
, ,
1

After updating from 2.4.2 to 2.5.0.135, RGBW devices exposed through the built-in HomeKit Bridge show No Response in Apple Home.

This is reproducible with a Hubitat Virtual Generic RGBW Bulb, so it does not appear to be related to Zigbee, Tuya, the physical bulb, or a third-party device driver.

Observed behavior:

  • The RGBW device works correctly inside Hubitat.
  • State changes are transmitted to Apple Home.
  • Apple Home initially updates the accessory state/icon.
  • Shortly afterward, Apple Home reports No Response.
  • Generic Bulbs, Generic Dimmers, and other Zigbee devices exposed through HomeKit continue to work normally.

Additional isolation test:

Google Home controls the same RGBW light normally:

  • On/off works
  • Dimming works
  • Color changes work

A virtual dimmer/switch mirrored to the same RGBW bulb also works normally inside Hubitat.

So the RGBW device itself, Hubitat control, and external integration in general are functional. The failure appears specific to Apple Home via Hubitat’s built-in HomeKit Bridge when the device is exported as an RGBW-class accessory.

Hub details:

  • Hub model: C-7
  • Platform version: 2.5.0.135
  • Previous working version: 2.4.2

This appears specific to RGB/RGBW HomeKit accessory export in the built-in HomeKit Bridge.

2

There's a few of us experiencing this (or a similar) issue, but good to know you've identified a previous working version, that might help @gopher.ny pin down the problem.

Can you confirm that reverting to 2.4.2.x resolves it ?

3

I have not reverted back to 2.4.2 yet.

Instead, I created virtual dimmers/switches and mirrored them to the RGBW bulbs inside Hubitat. That workaround works and restores basic control, including on/off and dimming, but it obviously does not provide color selection from Apple Home.

So at this stage I can confirm:

  • RGBW devices worked before updating from 2.4.2 to 2.5.0.135
  • The issue appeared immediately after the update
  • Virtual dimmer/switch workaround works
  • Direct RGBW export to Apple Home still fails
  • I have not yet confirmed whether reverting to 2.4.2 resolves it
4

Could be that something change between 2.5.0.135 and 2.5.0.143, but it works for me.
What kind of a driver does the affected device use?

5

I am having the same problem with devices exposed to the homekit bridge integration. I have three devices no response, a govee strip, a hue floor lamp and a virtual rgbw. they all show no response but the other devices work fine. I am on hubitat 2.5.0.143