Hey, so it seems that scene activators aren’t working as they were prior to 2.3.0.113.
Previous behavior.: Scene activator on, gets turned on again it activates all devices in the scene.
Current behavior: Scene activator on, gets turned on again. Some things will turn on, but most will not. If it is turned off first then turned on everything will turn on.
Just curious if this is intended, or a bug? I can script around this issue if it is intended, but that’s a crap ton of rules to update, so thought I’d check beforehand. Reproduced on a c5 and a c7 hub.
Thanks!
-N
Please show the Scene screenshot, and turn on logging for the Scene.
1 Like
Sure thing. Upon a littler deeper digging, I have scene activators inside of scene activators, the embedded scene activators don't seem to be working. The scene says it's on, but it's not, the log does not show it being activated. In the screenshot "Downstairs - Energize" is a scene for hue lights specifically. In this scene even though it says it's "on" it is not engaging this scene activator. If I go into the device page and manually turn it on, it activates.
If the embedded Scene activator reports that it is on at the time the encompassing Scene is activated, it won't be command on (since it appears to already be on). If, on the other hand, irrespective of its state if you hit On on its device page, it will activate the Scene. That's what you should look at, the state of the embedded Scene's activator at the time you activate Downstairs White Lights Scene Controller.
It's confusing that you show a Scene called Downstairs White Lights Scene Controller and a device called White Lights. I have no idea what that means or what's what.
Sorry, that's just a virtual I created to share out to Alexa/homebridge, etc. It follows the main switch, which I've attached.
None of this addresses the issue of the state of the activator for the embedded Scene at the time of activation.
BTW, a Virtual Switch device has a built-in auto-off feature, and you could lose most of that rule by using it. But at that point, what do you really need the rule for? Why not just turn on the Scene activator itself? Further to that point, Scene Activators are strange, and can be turned on multiple times, each of which would activate the Scene. There is no need to manage its on/off state. Clearly, this might be the cause of your problem with an embedded Scene. If it were me, I wouldn't embed one Scene in another, but just activate two Scenes if that's what you want to happen.
The auto-off is 5 seconds at most on a virtual, which wasn't long enough for it to register in homebridge and or Alexa. I use it for other signaling, at any rate the auto-off was too short. I was embedding as it prevented me from trying to capture the state of the hue bulbs in multiple other scenes, so this was the easier way to do it. It was working up until this latest release. I was just trying to clarify if it is working as intended, and before it wasn't and or it was changed to this. It seems that the current iteration is working as intended. So... I'll need to update the rules accordingly.
The scene here is decidedly short on purpose as I made it for testing, with a light linked to a couple 3rd party hubs I have.
Also if a scene activator turns off, it takes the lights it has set with it, I know this can be disabled in the scene, but I want this behavior for other rules. The virtual is passed to homekit and Alexa, and returned to "off" state quickly so it can be verified it was turned on by the digital assistants, and then be ready to be activated again fairly quickly.
None of this has changed, IF you're on the latest build. Also, I can see where there should be a slight change to the way it works. It shouldn't check the current state of a switch if Optimize on/off is not selected. I will put that change in for an upcoming release.
But, there is still an overriding issue about a device not being in its captured state for the Scene to activate it. So, that's still what you need to determine to use embedded Scene activators. Like I said, I would not do it this way. It's so easy to find a way not to embed Scenes, and if its giving you a problem, then that's the ultimate answer about it.
2 Likes
Here is a typical motion/mode/scene rule from RM for me that I have setup. of note, this rule has ceased to function correctly.
Lights used to activate no matter what on any motion in the room, no motion after 20:00 (the mzone timeout) it would dim the bar lights down, wait 5:01 then turn off. now it's currently skipping the dimming part altogether (maybe embedded scenes/groups?), and not waiting the m-zone timeout, it seems to jump right to the 5:01 delay right after the motion sensors themselves stop reporting motion. I'll need to a dig a bit more on this one as I'm not sure which part is not working correctly, but I'm leaning toward the zone, as I'll see it reporting as active on the device page, but it jumps to turning them off.
No worries, thanks for your time on this btw, and yes I'm on the latest build .113
