Lights being forced to 366 (via Apple Homekit)

[RefineryX]

Description: Hue lights via HomeKit are not changing to user choice of brightness and colour. When trying and change the lights, it looks like something is getting pushed back and the light are defaulting back to 366. I have created a video to show this behaviour (here).

Findings so far:

• This behaviour happens when using both Deconz (via Conbee ii) and also via the Philips Hue plugin (connected via official bridge) - only when using HomeKit.
• I can change colour and brightness via the HA GUI and via Deconz GUI.
• I have tested via the current iOS 12.4 and the new iOS 13 (PB 5) with both the same results.
• I have also reset my lights to see if that resolves and also a clean HA install.... no luck.

366 looks like it is the default hue colour. Could this be an issue with the power on activity? https://github.com/dresden-elektronik/deconz-rest-plugin/issues/1014

Home Assistant Log:

Deconz Log:

21:39:13:964 discovery server date: Wed, 14 Aug 2019 20:39:13 GMT
21:39:13:964     local time seems to be ok
21:40:12:788 Current channel 15
21:40:12:797 Device TTL 6540 s flags: 0x7
21:41:12:786 Current channel 15
21:41:12:795 Device TTL 6480 s flags: 0x7
21:41:18:809 dev /dev/ttyAMA0
21:41:18:810 GW firmware version: 0x264a0700
21:41:18:810 GW firmware version is up to date: 0x264a0700
21:41:55:928 0x001788010247FA7B error APSDE-DATA.confirm: 0xE9 on task
21:42:05:670 delay sending request 183 dt 0 ms to 0x001788010247FA7B, cluster 0x0300
21:42:05:675    0x001788010247FA7B force poll (2)
21:42:05:711    0x001788010247FA7B force poll (2)
21:42:05:868 send move to color temperature 366 to 0x001788010247FA7B

Setup:

• Home Assistant: 0.97.2 (hassio)
• Hass.io Core Add-on: deCONZ: 3.1
• Hardware: Conbee ii

[daanvb]

I have just set this up and I am also noticing the same behaviour. My lights go to 153 though...

[RefineryX]

@daanvb - what lights do you use? I think mine goes to 366 as it is the default hue value.

[daanvb]

Tried on 3 Philips Hue A19 White and Colour bulbs. All exhibit the same behaviour and go to colour temperature 153 when I try and change them in HomeKit.

Also whenever I open the bulb settings in HomeKit to change colour, it defaults to the ‘temperature’ colour ring first which it didn’t do when connected to the Hue bridge.

[ebaauw]

This behaviour happens when using both Deconz (via Conbee ii) and also via the Philips Hue plugin (connected via official bridge) - only when using HomeKit.

I’m not sure what you’re saying here. Are you using Home Assistent to expose the lights to HomeKit? Is this happening both to Hue lights connected to deCONZ as well as to Hue lights connected to the Hue bridge?

[daanvb]

This behaviour happens when using both Deconz (via Conbee ii) and also via the Philips Hue plugin (connected via official bridge) - only when using HomeKit.

I’m not sure what you’re saying here. Are you using Home Assistent to expose the lights to HomeKit? Is this happening both to Hue lights connected to deCONZ as well as to Hue lights connected to the Hue bridge?

I can’t speak for @SimplyGardner but for me, I am exposing the lights via the HomeKit component in HomeAssistant. I have just moved all the lights over to use DeCONZ in HomeAssistant instead of the Philips Bridge (where the colour picker in HomeKit worked fine)

I am now experiencing the issue that @SimplyGardner is reporting.

[ebaauw]

Did you use the native HomeKit feature of the Hue bridge, or did you also expose the lights connected to the Hue bridge through HA?

[daanvb]

Did you use the native HomeKit feature of the Hue bridge, or did you also expose the lights connected to the Hue bridge through HA?

Previously I used the native HomeKit feature of the Hue bridge to control lights via HomeKit and this was fine. The lights were exposed via the Hue integration in HA for automations etc but we’re excluded from the HomeKit component (to avoid duplicate lights appearing in HomeKit)

[Fienberber]

I'm experiencing the same problem too. I'm using diyhue with some esp's and mi light bulbs. I think the problem is due to how the plugin (homebridge-hue) exposes the lights to homekit. I'm experiencing jumping of colors in the apple home app if I try to set the lights with the temperature gradient. But this is not due to some sort of communication problem because it occurs when I try to set the temperature in a scene. And when creating scenes homekit does not send data to the hue bridge (to my knowledge). I have no problem with other RGBW lights that don't use homebridge-hue.

Hoping this can help.

[ebaauw]

I'm experiencing the same problem too

Are you using HA or homebridge-hue to expose your lights to HomeKit? In the first case: it has nothing to do with homebridge-hue, in the second case: it's not the same problem.

[ebaauw]

@daanvb I hate to be fingerpointing, but it looks like an issue with HA. Hue lights report back the closest ct value when setting a light colour through xy. It seems like HA uses that as a hint to update the colour temperature, setting ct. Then, the Hue light reports back the closest xy value on setting ct, which HA takes as a hint to update xy, etc. Basically HA should check colormode and not take action on changed ct values unless colormode is ct (and similar for xy).

To confirm, you could try and set a yellow-white-ish colour and see high ct values (up to 500) and a blue-white-ish colour to see low ct values (down to 153).

As far as I know, only Hue lights report back their actual state (rather than the last state set), and only Hue lights update the attributes for another colour mode, so you won't see this behaviour for other lights.

[daanvb]

@ebaauw I think you are correct that this is a HA issue. I've done a little more digging and found some threads raised regarding this.

https://github.com/home-assistant/home-assistant/issues/23394 https://github.com/home-assistant/home-assistant/issues/24513 https://github.com/home-assistant/home-assistant/issues/19251

[dodepier]

I have exactly the same issue with homekit and Lifx on Hassio 0.98.1

[someguythatcodes]

I've had a play around with this and it looks like when you pick a colour in Apple's Home colour picker, it sends the hue and saturation values followed by the colour temperature value to homeassistant.

The reason the behaviour described in this issue is happening is due to the fact that the hue and saturation are sent first from the Home app, which home assistant acts upon and changes the colour to the selected colour. The problem occurs because the colour temperature value is sent after the hue and saturation which homeassistant acts upon and sets the colour temperature, which causes the light to return to the previously selected colour temperature.

This does only seem to be a problem with Apple's Home app, as I've tried using other apps such as "Controller for HomeKit" and "Eve for HomeKit" which both work fine

I've made a change to the "type_lights.py" in my developer environment to only change the colour temperature in homeassistant if the value is different to the previous value which seems to be working well.

[daanvb]

@someguythatcodes can/will this be officially integrated into the plugin

[RefineryX]

@someguythatcodes that's great - thanks for looking into this - its greatly appreciated. What would be the next steps on this? Wondering if a PR could be added to HA?

[someguythatcodes]

I will look into doing a PR into HA for this soon

[daanvb]

I will look into doing a PR into HA for this soon

That would be amazing thank you!

[someguythatcodes]

I think Apple may have fixed this in iOS 13.1 as it seems to be working for me after the update

[daanvb]

I have tried it too and it does seem to be working for me as well

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.