I have a C8 Pro in which I have a rule that turns on the hallway light when there's motion in the hallway. If it's late at night/early in the morning in glows yellow. This worked fine until the last update of the software and now I no longer get the yellow change. The new version I'm running is 2.3.9.166.
I am able to change the color via voice through my alexa device or manually. So it seems isolated to Rule Machine operation. Here's the action.
Thoughts anyone?
Turn on all logging for the rule, then look at the output of Logs, filtered to just this rule, to get a better idea of where to start troubleshooting. It is hard to know unless you know what the rule thinks it's doing when. Share them here if you are not sure.
See also:
Great point. In fact, after looking it over more it very well could be the "Time Between" condition. I'd know that by looking at that debug.
Okay, so I'm now getting an error on this device that seems to indicate it cannot read a write-only property. Again, this has been working for many months, so something seems to have changed.
What device (brand and model) is that, and what driver is it using? And can you break it if you try the "Set Color" command from the device detail page, too? The rule seems to unlikely to be causing this driver error.
It's a Wiz Matter compatible bulb. Setting color from the device page works fine. I just set it to yellow and it had no issue.
The key point here is that it's been working fine until recently. I also find it interesting that the Groovy error mentions it cannot read a write only property (method SetColor).
My thinking is that this error is coming from Matter and that you'd be able to reproduce the same problem if you try the "right" thing with the setColor() command yourself. I suppose it could also be setLevel() with the transition time in your rule (though that's not what the error suggests) -- but either is all the rule would be doing, working through the driver in the same way you can test yourself.
If you suspect a platform update caused a problem, you can confirm (or not) this suspicion by downgrading and seeing if the problem disappears:
And if it reappears when re-upgrading, that is even more of a clue.
Updates are often blamed for things that are just coincidental. This is the only way to rule that out. 
I reverted back to 2.3.9.164 and I am no longer getting that error. I'm sensitive to blaming an upgrade mistakenly and I wasn't keen on even saying that. Now that I've reverted back and see that error no longer occurs I feel a little better. I'll wait on upgrading next time.
Thanks for the information. I'm able to replicate this on 2.3.9.166 but not on a newer build, so I'm wondering if something got fixed in a later beta. Looking into that...
Also, your rule is a bit odd. You are setting color and level, then immediately setting a new level with no transition time. While likely not related to your problem, is there a reason you don't just set the level you want as part of "Set Color" instead of something else first?
I presume you have Wiz lights then? Are you able to reproduce setlevel not working in 2.3.9.166? If so, does it work in the beta version? Issue with setlevel has been raised by @manderson989 here Rule Machine Track Dimmer is not working in Version 2.3.9.166 - #9 by manderson989
It's been a while since I created that rule, but if my memory serves me correct, that bulb wasn't setting the value properly within that command, so I added the extra DIM command. This weekend I'll remove it to see if that is a correct statement.
I've started (very slowly) changing out my Zigbee bulbs with Matter bulbs. That one is a Wiz my other are GE's, but they are more responsive (noticeably) in turning on. I only have 3 right now, but I've been impressed so far.
No (well, yes, but not Matter...), just another Matter bulb. At this point, I don't have a reason to believe it is specific to Wiz and not Matter, but it also appears to have been fixed. There will likely be another 2.3.9 hotfix, and I suggest seeing what happens then.
(EDIT: and doesn't even seem to be a Matter-specific problem based on the other report--but it's being looked into regardless!)
It seems like the Wiz light in the other thread is a WiFi light rather than matter.
I have not been paying much attention to the other topic, but in this one, I was able to reproduce the same problem with another Matter bulb. In any case, I'm not able to do it on newer hub platform versions, so I still suggest seeing if this is resolved in the next update (or beta if you are currently enrolled in that).
Can you PM me the hub id? I'll check the engineering log, there probably are some clues there.
Just for the record, this is the bulb in that hallway.
6 posts were split to a new topic: Problem setting color with WiZ bulb in Rule Machine
Download the Hubitat app
