Originally, I raised this thread:
Room Lighting App not issuing lighting command (used to work, now doesn't) - Why Hubitat Elevation / Ask Anything - Hubitat
I had thought that Room Lighting was failing to work but I re-ordered the devices in the Room Lighting app and constructed the rules in Rule Machine to treat the problem devices separately and I still get unwanted behaviour.
OK, so what's going on?
When I trip a motion sensor in my living room, while it's dim, the living room lights come on.
I have them come on in one of two states: when the TV is on or when it is off. The principle difference is that some table lamps are on when the TV is off (for extra light) and off when the TV is on (to prevent reflections on the screen).
The table lamps are Cree Zigbee bulbs and, knowing that they don't always play nicely with other Zigbee devices, I have them associated with the Extender of my Harmony Hub.
I use the rather excellent driver by @ogiewon to control the activities and automations.
Something strange happens in only one instance and I can't work out why...
I walk into the living room while it's dim and the lights come on, including the Cree bulbs commanded by the Harmony Hub.
I turn on the TV and the Rule Machine detects it and issues the command to change the Room Lighting. The same rule is supposed to tell the Harmony to turn off the Cree bulbs but they don't turn off. I can then run the rule actions through the web interface (or through another rule that issues the same commands) and the bulbs will then turn off as requested.
I can turn the TV off and the rule commands the lights back to the previous state and the Harmony Hub turns on the Cree bulbs as expected. If I turn the TV back on, it leaves the Cree bulbs on when they should turn off.
Screenshots below are as follows:
The Harmony Devices (I am using the two automations at the bottom of the list)...
The rule that doesn't run correctly when the TV turns on (and that I have to repeat through the web interface)...
The rule that runs correctly when the TV turns off...
Logs in timeline order for when I enter the room and the rules run. You can see what is being done. I don't pretend to understand most of what's going on here...
Logs in timeline order of when I trigger the rule through the web interface to correct what was left undone...
Can anyone help advise why, in only one specific instance, my automation isn't running?
I have changed nothing material since late last year when it was running absolutely fine.
I can't swear as to when this behaviour started, but it is recent (within the last 3-4 weeks).
Everything seems to be working individually and the two rules above are almost identical yet behave differently. It doesn't matter what time of day I trigger these rules, it's only ever associated with the TV turning on when the living room lights are already on.
I have raised this topic under Custom Apps and Drivers, but this may yet be the wrong place.
I'd like help narrowing down where this is going wrong so I can get a meaningful fix that will help others as well as sort out my own frustrations.
