I thought when I switched over to use Matter instead of CocoHue to manage my Hue lights (all Philips hue on an hue hub) everything worked ok. However there is something funny going on.
Basically every time I trigger the same room scene, using room lighting I get a slightly different scene. Every time it is re-triggered it changes again slightly until it ends up significantly different.
To illustrate I took some screen snaps of what the hue app reported.
This was the original colours specified.
This was how it was setup in room lighting
This was the first time the scene was triggered.
![IMG_1624|648x500]
(upload://uj50WZT4mHBkdBCbDtSUUEjdXiQ.jpeg)
This was the second time triggered, lounge wall light 5 has changed
This was the third time triggered lights 5 and 4 have changed.
This was the fourth time triggered lights 5,4 and 2 have changed
I basically used the same setup as I had used for CocoHue just cloning the original and changing to the new Matter device and associated lights.
Has anyone else experienced this or any ideas?
Here are the photos of the log for the five lights.
It's not exactly clear what is happening to me: are you saying that each time you "activate" the RL scene, the colors get set slightly differently, even though it should be sending the same color (hue/saturation and level) values? (That's what the logs make it look like.) If so, you can you leave RL out of the picture and see if the same thing happens when you just repeatedly run the "Set Color" command from the device detail page yourself?
It may also be interesting to see what the device reports. Do the hue and sturation values always report something close to what you send with the "Set Color" command, or do they also drift away?
Correct, running the same scene changes the actual colour on the lamp each time it is run.
I have gone into the device and have tried some things. Turning the light on and off doesn’t seem to change it. Setting a colour seemed to work ok but I did end up with setting a colour of purple and getting azure. I have not been able to reproduce so it may have been finger trouble as I got use to how the options worked.
I have now saved the same new scene on both the CocoHue room lighting version and the Matter room lighting version. I disable one and then activate the other. Cocohue version consistently displays the scene correctly and Matter consistently drifts.
On the matter setup.
I have noted that on some occasions a light will not turn on and the next time it turns on it is then the wrong colour, but not all lights that are wrong have not turned on before hand,. Once it becomes the wrong colour it then seems to remain that way until I change it by the hue app it then remains the new colour through off/on as if it was just getting an on and no set colour command.
One light, that I had been testing on, went back to the colour Azure I had seen when testing previously, some 10 minutes & a number of different RL activations later, it then remained at that colour until I changed the colour in the hue app (Yellow), It then remained at Yellow as if it was just receiving an on for a couple of on/off cycles before it reverted back to Azure and would always display Azure. I can get this to repeat . I then set the bulb to red in the device settings and did a couple of off/on cycles and it went back to Azure. This is the light that I set purple and it turned Azure when testing in device settings.
On all other occasions when a light drifted it seems to go to the centre of the colour wheel and once it has drifted it then seemed to stay like that despite RL reactivations again like it is just receiving an on.
Changing one that has not drifted works (to Blue)as expected in that a RL activation resets the light to the expected colour.
So are there any ideas on where the fault is or what can be done to correct it?
I'd imagine it's a problem with the color space conversion somewhere.
I wondered if there had been any changes in this area such that it is worth trying again?
I don't see anything in the driver that should be causing this. The "Set Color" command just sends the specified hue, saturation, and level values with optional transition time (e.g., as opposed to looking at any currently reported values and sending a difference, which would be an easy explanation for slow drift).
Because of that, my first guess would be that this is just an oddity with the device firmware, outside the control of the hub. Have you checked for any updates (or have you re-tested since doing any; Hue might do them for you automatically by default, and in this case, it might really be the Bridge firmware), or do you have any other Matter RGBW bulbs you could try the same thing on?
I parked it a year ago and then tried again this morning. I worked through room by room, cloning the room lighting and changing the lightbulbs from CocoHue enabled to via the matter link and then testing. I didn't hit the problem I had encountered previously. Things were going very well until I hit one particular room when I noticed the room lighting stopped turning off and the colours had changed again. This is different to the previous issue. I looked at the clone and found that the colours were different in the clone and as I had done a small change after the clone I went back to the original. To cut a long story short if I do the small change beforehand (remove disable and re-enable deactivation) then it clones and the room turns off but the colours are still off. If I try to change the colours by recapturing it says all the lights are off and manually changing the colours seem to have variable results. I will continue to investigate.
So far it looks like I have a consistent issue which is different to11 months ago. I have room lighting different per mode on all rooms and different colours on each light.
Every clone I have done has changed the room lighting to be the same scene for each period replacing the different scenes before the clone. This happened to be the scene when I was testing this morning hence why I didn't notice.
If I try to recapture a period's lighting then it turns off the RL activation switch (current) for each light and if the switch is then re-enabled it shows the previous settings for that light.
If I manually change the colours then the light comes on at the different colour but Room Lighting doesn't switch off.
If I try to recapture then it turns off the RL activation switch (current) for each light and if the switch is then re-enabled it shows the original settings for that light, not the changed ones that are still on in the room.
Later I will try to avoid the clone step and set up a new RL from scratch and see what that does.
Set up a RL from scratch and then alternated the bulbs between the CoCoHue and Matter Bridge versions.
Matter Bridge versions do not recapture the scene whilst CocHue versions do.
Matter Bridge versions are always turned off when first introduced and then default to the original settings not the current colour of the bulb . Whilst CocoHue versions are always on defaulted to the current colour.
So I created an RM app that
Step 1 was to set a RED scene.
Step2 The App ran and captured the current setting on 3 bulbs (2 via Matter and 1 via CoCoHue) tit then turned all bulbs green for 5 seconds then white for 5 seconds and then restored the bulbs to the original captured colours. The matter bulbs do not restore and turn off. The CocoHue bulb restored and remained on.
So I believe I probably have a capture issue with bulbs connected via the Matter Hub. That makes the issue thenwider than RL.
Any ideas on how to now progress investigating further?
I wouldn't say this is a "capture" issue if your devices are reporting the wrong state, but I suppose that isn't clear to me from the above. To narrow things down, you need to look at the current values for the desired attributes under "Current States" on the device detail page for each device if that's not already where you're looking. If those are wrong (say, the color is wrong or the switch says it's off when the light is on), then the capture is going to happen wrong, but that's really an issue with the device (or driver or something related to that); an app that captures the current state of the device can't know any better than the device reports.
With that out of the way, I think it would be clearer where any potential problems are. For any particular device, if the "Current State" values are wrong, you might want to check various things, including whether a "Refresh" helps, whether there are any errors in Logs, whether any state changes at all (is Matter in general or the particular bridge device they are connected to, assuming that's how you're getting them to Hubitat, not working?), etc. Similarly, you can test the commands on the device detail page, like "On" or "Off" or "Set Color," to see if those work as expected, again leaving any apps (rules, groups/scenes, RL, etc.) out of the picture.
So the devices are reporting different states the one connected through Matter is shown as off and doesn't change when the light changes colour, whilst the one reported through Cocohue is shown as on and does change Hue, Level and Saturation as the colour alters.
If I do a refresh on the Matter device then it shows the same as CocoHue and the switch is on.
Setting the colour on the Matter device via the colour map parameter changes the colour but does not show as the current settings until the device is refreshed.
Cocohue works as expected changing the colour map does not need a refresh to show the updated settings.
I also have one native Matter devices (a star projector) I included that in my RM app above and that worked as expected. Commissioned in HomeKit and a device setup in Hubitat via the pairing code.
The bulbs that are not working are all Hue connected to a Hue Hub and then to Hubitat through a Generic Matter Bridge and shown as Child Devices. They are also shown in HomeKit as well, although not used.
So where I have ended up is that I can now setup room lighting if I refresh the lights immediately prior to the capture.
However I am finding that the in RL lights are not reacting to the switch off (and I think sometimes the switch on) unless the lights are refreshed prior to the lights being switched off. They do react to the activate and turn off commands in the app. The log showed the turn off command but no bulbs being attempted.
Lights outside of RL that switch off using a set switch off command work ok. I do have my RL set to transition between scenes.
I don’t know if the issue is then generic matter bridge not doing a refresh or an issue with the hue bridge which is a Philips Hue device v2 (not the latest pro) set to update automatically and at version 1.74.1974142030.
