I'm having ongoing issues with room lighting not showing the correct state (Active/Not Active). As you can see, I have the indicator to show if all set per table, and the lights are all set per the table, but the room lighting app is not showing active (even after clicking update or done) and does not turn off per the settings. I was having this issue with the previous version of the app, so I recreated it from scratch thinking that it became corrupt somehow, but the new version also does not work. This behavior is happening with multiple room lighting apps, some of which have the indicator set to "any is on." Any thoughts on what may be the issue here?
Here are my logs showing in the few most recent lines that after I activate the kitchen lights (with Activate button on app) it immediately changes to Not Active:
I had issue with inconsistent Activator status regarding what was on or off.
I tried many of the options suggested by the peeps but in the end I bailed and went back to Groups and Scenes.
I was using it mostly to group bulbs with the odd simple motion on/off scenario.
It's all back on WebCore running fine with the Group.
I have the ceiling lights set up with a preset off so that if the lights are turned on manually, they get turned off when the other lights are turned off, so there is a reason for it to be included in the room lighting app and it is within what is expected to be normal operation of the app. As I mentioned, this is happening with multiple of my room lighting apps, and if you do a search for this same type of issue you will see multiple other reports of this happening, as is mentioned by the first commenter on my post. Here is another app that I rebuilt yesterday from scratch. It only includes one light, and yet the active/inactive status of the app is still continues to malfunction. I have tried many different solutions over the past few months, the last being rebuilding the apps from scratch, and still the issue continues, so the only conclusion that I can think of is that there is a fundamental issue with the way the apps are programmed (a bug) that is causing this to happen. I have multiple hubs across 2 locations, and they all experience this same issue with room lighting apps.
In response to the above supposition, I have removed the “unused” light from the app as shown below, and yet as you can see in the logs, shortly after activating the room lights, it changes back to not active even though all lights are set per the table.
What is the state of the activator device? Is it tracking what the app log says? Could you include it in the logs filter, so we can see both app and activator together.
Sure. It sets to “someOn”. Here are the logs with both. I turned off the kitchen lights using the “turn off” button in the app… the last entry in the logs.
Based on my testing, it appears that the indicator function will not indicate the Scene is Set if there is a device with no activation settings. I guess it's looking for those settings to match the device state, but they can't possibly match since there are not settings. And, as you point out, this happens when there is a device set in one mode/time-period but not another. The (faulty) logic in Room Lights fails to take into account the device not even counting in some mode/period.
Prefect I have noticed the indicator state not updating correctly on one of my groups this whole summer but never dug into it. Hopefully this will fix that also. I do have some seasonal devices in the group so I uncheck the activations in the summer and that's when I started seeing the issue. I swear it used to work correctly at some point.
Based on the code, it could not have worked before.
Actually, there are unusual circumstances over time that could possibly make it work sometimes. Each device for each mode/period has a flag as to whether or not it is set (that is, set to the settings). The test for the indicator is straight forward -- see if any device (for that mode/period) is not set. That was all of the logic. Devices for a particular mode/period that have no settings at all would never get that flag set, so would drag against any outcome that all were set per the table.
