So it’s a deconz thing?
The color mode 2 thing is an issue from Deconz side. I’ve seen it reported from one other user and it’s from the raw json datafrom deconz afaik.
The warning comes from when the integration gets unexpected values which was introduced this summer IIRC
But it might have existed for a long time without anyone knowing or something changed in deconz recently. I don’t know
If its just the warning you want to get rid of you can change logging for deconz integration to error.
Or is there also a second issue? For me preferably issues are reported on GitHub. Its so easy to loose track of discussions on the forums.
1 Like
Thanx, got what I wanted to know from discussion here: seems this is not a problem that will cause DeConz to start crashing again. I can live with the log error…
I hope I’ve never been the source of deconz crashing 
Next time don’t wait two weeks being annoyed with a behaviour 
Sorry. This thread is for the deConz integration not ZHA
Apologies. Since I’m using the deCONZ ConBee II hub I thought that this was the right place.
Easy mistake
Who knows how to zoom in deconz with iPhone?
I stumbled upon this error when diagnosing a room lighting automation.
It seems that when I call IKEA lights with turn on, only with brightness set, I get this error. But if I use light color (say Kelvin) as another variable in the automation, it doesn’t complain anything.
I did have an issue where controlling a DeConz light group with only brightness didn’t do anything - I only got the error in the log. Switching to control individual lights remedied this, but I still got the error. Adding the Kelvin to be controlled at the same time remedied the error in the log as well.
Now, I also noticed I get the error (after a fresh HASS restart) even when manually controlling the lights in HA gui. Only after I touch the color temp slider, the error stops appearing.
The hard part is that I don’t know which lights trigger the error, since I get that from some other lights still.
This is most probably a deCONZ side issue, so the best thing to do is to report it on GitHub - dresden-elektronik/deconz-rest-plugin: deCONZ REST-API plugin to control ZigBee devices
Should be fix in v2.19.1 
Bug Fixes
- Fix OTA handling and looping for newer devices from Ikea, Ledvance and others
Let’s see…
Maybe this is more related to this post. How do you get the OTA files into deconz to be uploaded to the devices?
Originalpost: https://community.home-assistant.io/t/filetransfer-to-addon-how-to-deconz-addon/479118
I can confirm it is fixed in2.19.1
Regarding the latest version, deconz 2.19,1, I see that one person has reported on github that Philips Hue Dimmers are not working. So I am naturally a litle sceptical about upgrading as I have a lot of Hue Dimmers. Have anyone else experienced this? Or are your Hue Dimmers just fine after upgrading to 2.19.1?
My Hue Dimmer switches are only partly working since the update to 6.16.0.
It is currently not possible to tab through different scenes when clicking the “on” Button.
Maybe its related
I use Deconz 2.19.1 and have plenty of Hue dimmers. I have seen no difference. They all work
How are you performing that? Is it with phoscon or in home assistant?
Two more persons have confirmed the issue at github so I stay with the older version for now.
I let Home Assistant update deCONZ to 2.19.1 (or 6.17.0 in HA) and almost instantly had problems with my Danfoss Ally thermostats; they disconnected/connected almost constantly.
Going back to the previous version fixed the problem.