Since the update(s) there have been two recently and the problem persists.
Scene's are there, and the system acts like it's doing the actions, it 'seems' to be updating the device status with what it thinks has happened, but in fact none of the lights turn on... Any ideas?
Log:
dev:1192018-10-20 14:19:42.653 info Livingroom - Truss is at 14% [digital]
dev:1082018-10-20 14:19:42.633 info Bedroom - Light is at 30% [digital]
dev:1172018-10-20 14:19:42.611 info Outside - Bat signal is at 100% [digital]
dev:1152018-10-20 14:19:42.592 info Hall - Entry is at 20% [digital]
dev:1122018-10-20 14:19:42.566 info Hall - DownLo is at 15% [digital]
dev:1112018-10-20 14:19:42.525 info Hall - Upper is at 50% [digital]
dev:1102018-10-20 14:19:42.484 info Hall - Fan Light is at 20% [digital]
So the devices are reporting that they are on, but they aren't? Please try the same settings from the device pages. Also, what you showed above is from Logs. Please look at the device events from the device page, and see if these entries are there or not, at the same times.
Correct the system thinks they've been turned on, the devices report on in the software and set to the right setting, but the lights are acctually NOT on. From the device page I can control them all as per the scene settings no problem.
Yes the device data shows last activity at the time the scene is activated.
At the moment I only have two scenes, one 'seems to be working' the other IS working... but as soon as I set one device in the wroking scene, so it's setting ON rather than off (just that one change) and it no longer works... if I set it back to OFF, it works again.
I asked a very pointed and specific question, and I need a pointed and specific answer. Did the Events link from the device page show that the device turned on at the same time as what you showed from the Logs page? Could you show me one screenshot from the device Events page that corresponds in time to the Logs page you showed above? I'd like to see the whole sequence of events for one device. Only need one, any one will do.
What driver are you using for these lights? Scene sends a setLevel() command to the light. Lights are supposed to respond to setLevel(n) by turning on, if n is > 0. All of our built-in drivers do this (or should).
Also, you titled this thread "no longer working". Was this Scene working before 1.1.6?
Sorry to hijack the thread but I have a question, I recently created my first scene, very simple, 2 switches on and one dimmer in 5%, if I turn on only the dimmer the scene itself turns on too but no the switches, so I must turn off the scene then turn on the scene if I want to run the scene. Hope you understand what I mean. Are this behavior correct?
Thanks
I am experiencing a similar issue. This is with a scene that had been working before the most recent firmware update. The scene is supposed to turn off all upstairs lights and set my living room lights to 1%. The last 2 times I executed it, the upstairs lights turned off as expected but the living room lights did not change level at all. I just checked the event log for the living room lights, and they report being set to 1%, but when I executed the refresh command the level updated to 36%, which is what they were set to previously. Most of the dimmers involved are the older GE style.
A Scene as an Activator Switch that has the same name as the Scene. If you turn it on, that will turn on the Scene. If you turn it off, that will turn off all of the devices in the Scene. You can disable this turning off function if you want. Even if one of the devices is already on, if you turn on the Activator switch, the other devices will be set according to the Scene. Turning on or off any device that is in the Scene has nothing to do with the Scene. If you turn on the Scene Activator switch, even if it is already on, this will activate the Scene (unlike most switches, that do nothing when turned on if already on).
Could you please repeat this and show a screen shot of the Device page right after you activate the Scene? Also, if this is an old Scene (not Scene-1.2), you might remove it and re-create it. Scene-1.2 has all of the updated features in it.
Oh, what you are seeing is the Scene tracking characteristic of the Scene Activator switch. This is only shows whether or not the Scene is active (which it can be from you turning on its elements). This is normal behavior. If all of the devices that make up a Scene are in their captured state, that switch will be on (unless the Scene contains a button to push). At that point, turning on the activator switch would not do anything, as the Scene is already set.
Ok, I ask because the scene changes to ON only with the dimmer, if I turn ON any of the other 2 switches the scene stay in OFF. Captured state is 5%, ON and ON. Thanks.
Are the two switches On when you set the dimmer to 5%? If so, then this is correct. If either is off, and setting the dimmer to 5% makes that switch turn on, that would be a bug. Turning either switch on by itself should not turn on the switch. Only with both switches are on and the dimmer set at 5% should make the switch turn on.
The 2 switches are OFF when I turn ON the dimmer at 5% and the scene gets ON too (by itself). Thank you for your time resolving this.
By the way, I noticed this with Sharptools, I created a tile with the scene, when I turn ON only the dimmer the tile for the scene will change to ON, I have to turn the scene tile OFF then turn it ON to get the scene.
No, I need the device page for a single device, this is the Devices page. I want to see what the device itself shows for its state after you activate the Scene.
Not entirely accurate in my experience. Several brand dimmers I've used, GE for one, allow for dimmer level to be set without turning on. There is an advantage to this if you don't want the lights to first fire off at 100% and then back down to the level set... if it was set higher. Yes it worked before the 11.5 update, didn't change anything, then it didn't work after that. the 11.6 I hoped was the fix, but nope. Posted this on the scenes and groups guide thread initially. if you see it there, it's the same issue.
