How can I debug this? I had two different lights not turn off last night.
I see the app run, and create a log for the anti-on action, so the app tried to turn each of them off.
I see the devices each have an event asking for off.
But, the device did not generate a log, and did not turn off.
What other debug options are available?
The only thing somewhat strange is the burst of battery events from two ring water sensors coming in around that time. But would that stop the hub from sending out?
Can you post the actual rule? Thanks!
I don’t see anything off there but I use rule machine for most of my automations. Maybe someone else can offer more. Sorry.
Thanks for looking.
Did you do something earlier like update the Hubitat firmware?
Nope, I have not updated in a couple weeks. Running 2.4.0.145. But I've had this problem intermittently for years. Just paying more attention to it this time. But, I definitely did not reboot between when those lights came on and when they were supposed to turn off. But, again, evidenced by the anti-on in the logs. The rule ran. And, the event got (just sent?) to the devices. But the devices did nothing / didn't receive the event...
I have had trouble for a couple weeks with a similar rule. On at sunset, off at sunrise.
I noticed the logs said the rule fired but the switch didn't actually turn on. I didn't notice the lights stay on late, but they consistently wouldn't turn on at sunset.
Just updated from 2.4.0.146 to 148 hopefully it magically fixes everything
After the update to 2.4.0 I started having issues with a wait command in one rule only. The rule would fire based on the triggers, the first wait command worked fine, then the second wait command would happen, but the rule would not turn off the light. In the logs it showed the rule stepping through as it should. It showed the second wait command executing and waiting 3 seconds but it would not send the command after that to turn off the light. It would work about 20% of the time and fail the other 80%. This is after it working 100% of the time with no issue in all the earlier platform versions.
i was on version .147 and updated to .148 and it did not fix the issue. I cloned the rule and changed the second "wait for event" to a "wait for expression" with a 3 second duration and to this point it has worked 100% of the time for the past three nights. I have other rules written very similar and it did not affect them at all.
I don't know what happened with this new UI platform update but it has caused people some issues with some rules that worked fine before hand. I was lucky mine was a relatively simple fix if the fix holds true. I understand there is going to be hiccups and bugs with changes like this so I am not complaining. It is the price that is paid for the chance to move forward.
This is not really something new. The same behavior (nothing happens after wait statement) was observed with previous platforms as well.
I never had an issue with any of mine on any of the several versions of the previous platform level. Not saying it didn't exist. Just saying I didn't have the issue.
Download the Hubitat app
