The only changes to that driver were the implementation of the refresh command, this alone would not effect normal behavior.
If someone can give me a specific example of a specific room lighting rule not working with a specific device/driver combination I can look into that.
I sent you details and a video of the advanced driver misbehaving at Possible bug: Advanced Zigbee RGBW Bulb driver no longer going "on" after SetColorTemperature - #12 by jlv (my issue is reproducable without RL).
2 Likes
Tell me how and I will send you a RL rule? It's either a driver issue or a RL issue but I didn't see any mention of Bruce making any changes to RL. Another easy way to check if it's the driver would be to send me the unmodified driver to try on .134. Or it's something else that was changed between .125 and .134 that is affecting quite a few of us but I have no idea how to even try and troubleshoot that.
It seems that if you send a white temp and level or colour and level rather than a "ON" you get the issue.
Currently on my RM rules I just have put a ON before the colour or temperature command and that fixes the issue. Basically the driver is not updating the ON settings when the device is turned on via a level.
This obviously can't be done in RL
1 Like
Thank you @BorrisTheCat !
I just looked at the events using .125 and it shows the RL rule sending a command-setColorTemperature and the the driver then is sending a switch on. When I looked at the events last night using .134 I saw the command-setColorTemperarture but no corresponding entry where the driver sends a switch on command.
Now I know that I can work around the issue, if needed, by recreating the RL rule in RM. I will wait for @mike.maxwell before going to all of the trouble of doing that.
ok, thanks for the video, i see what its doing, or rather not doing...
4 Likes
Wondering if the advanced Zigbee driver will be changed to work like it did before?
If not, I'll start the arduous task of rewriting the affected Room Lighting in Rule Machine so I can upgrade the firmware on the hub. Thanks
Please look at advanced zigbee ct bulb driver because i had to change to the generic because it seems to be doing the same thing as the rgbw
thats the plan
the other advanced drivers will be changed to follow
3 Likes
Thanks @mike.maxwell
I installed .138 and the drivers aren't fixed yet. Rolled back. Waiting for next release.
The release notes will include a list of updates, save you some time:
You can set the Release Notes section to "Watching" so you get notified when new release notes are posted...
4 Likes
Thanks @danabw .
I did read the release notes but have at times seen things fixed/changed but not make it into the notes. I figured since I was sitting on my a$$ doing nothing I would check.
2 Likes
LOL...been there, done that. 
1 Like
Yepp, still not good...
Hi, I'm keeping an eye on this thread because I have the behavior reported on many bulbs.
@mike.maxwell
Do you have any estimate of when this issue will be resolved?
I was told in release 2.3.9
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
