I have a few Sengled Zigbee Bulbs using the Sengled Element Classic driver that are part of my “Evening Lights” scene. This scene turns them on and sets their level. I have 2 RL rules that turns on this scene: one that is based on Mode change to Evening when we are at home and another that is based on Time Period when Mode is Away or Vacation.
I’m seeing a weird behavior with these bulbs when they are turned on via one of the RL rules. According to the Events page, it simply calls setLevel without turning on the bulb even though I do NOT have pre-staging enabled. However, when I activate the Scene via the scene page, it is also turning on the bulb in addition to setLevel. I’m guessing this is why the bulbs aren’t turning on through RL.
Any ideas why there is a difference in behavior when called via RL vs direct activation through the Scene page? I did just turn on “Enable discrete on for activation” on the scene page and I’ll see if it makes a difference tomorrow evening.
Oh another observation. I have another RL rule that turns on & sets the level on other Sengled bulbs in the guest rooms directly instead of through a scene (restricted to activate only if my “Guest” virtual switch is ON). That works fine as it does both turning on and setting the level. I suppose if I can’t get my Evening lights rule to work this way, I could just create the Scene as a RL rule, create an activator device, and then turn on the activator device in my Time Period based RL when Mode is Away/Vacation.
For what it's worth, I don't think you are alone in this. I posted a similar issue with Sengled bulbs not turning on, but in my case it appeared to be setting the level to 0% even though I was only sending the "on" command. Also, I am not using RL or scenes but the behavior is similar and quite recent.
That’s unfortunate. I just bought so many of these Sengled light bulbs for all my table & floor lamps since I prefer those for evening lights vs overhead lights around the house Did you find a work around for your issue?
I was using the Generic Zigbee Dimmer driver and I changed it to the Segnled Element Classic one. I haven't had an opportunity to see if this has solved the issue, but based on a limited test (1 day), I did see that the logs were not showing the setLevel 0% line and the all 3 bulbs came on/off that one day. We were traveling for the holiday, so I will be watching this over the next week.
Thanks! I’m already using that driver so maybe my issue is Scenes & RL-specific. It seems like it since it works fine when Activate Scene through the scene page, but not when activated through the RL
Try writing rules in rule machine that will accomplish the same thing and see if that works. I have a lot of Sengled bulbs. I had an issue where that the level was set wrong not allowing them to work. After I got that corrected my rules in rule machine work just fine with the bulbs.
One quick thought. Since you are using the Sengled Element Classic driver and I was using the Generic Zigbee Dimmer driver and were having a similar issue, I wonder if changing the driver did the trick for me. Not the actual driver, but the save, configure, save dance that you have to do when changing drivers. It may be worthwhile for you to change to a different driver (either Generic Zibgee Dimmer or the Sengled Element Classic (Legacy), do the "save, configure, save" and then switch back to the Sengled Element Classic (do the "save, configure, save" again)? Maybe something changed in one of the updates and this may set it back - seems a long shot, but may be worth it.
I actually was able to get around my issue by setting this on my "Scene". It should not have been necessary because I have pre-staging on my bulbs disabled, but this seems to work.
I know the question everyone is going to have is "Why are you creating a Scene and then executing it in Room Lighting when RL creates a Scene for you?" I have two RL rule (one based on Time Periods when the Mode is Away or Vacation and another based on Mode changes when we are Home) and I did not want to have to maintain the scenes in two different places.
Did you find a work around for your issue?
