Both Evening and Morning Rule Machine Apps are NOT finishing the "wait for" events. I have logging info turned on for Morning Lights, but that log show no commands at sunrise, Devices also confirm that no commands were sent from the app.
I have tried a rule line for turning actual switches "off" and dimmers (whether in-wall or plug style or LED driver style) to set to "0". Also tried treating everything as a switch because all the devices do have an "OFF" button on their device page.
Neither way has worked.
I just turned on logging this morning, but thought someone might see my fatal flaw from the existing data (screenshots of rule and device logs) rather than waiting another day and seeing all my lights on still when I'm up at night to go to the bathroom. UGH.
Thanks.
Not sure what's going on - it's always best to show logs filtered to the device and app (you may have but it's not too clear)
I do think that these rules are going to be problematic in general as the waits will be sequential (someone will correct me if I'm wrong). For instance your 'Morning Lights' triggers at 5 AM. You've a wait til sunrise followed by a wait til 8AM. When Sunrise occurs after 8AM it'll do the Sunrise actions then it's going to wait until 8AM the following day It'll trigger again at 5AM cancelling the previous wait, but the actions for 8AM will never occur.
Thanks
The app was working up to one week ago. Not sure what changed.
Sunrise here will never be after 8 AM. We’re past the solstice and it’s getting earlier every day.
Nothing jumping out as incorrect then. Hopefully the logs will show some information when it fails.
1 Like
What hub and firmware is this happening on?
C-7 running
2.4.0.146 I made that update this morning hoping it would solve everything. lol.
It weird because it was working before. Even the first "wait for" event at SUNSET when the group of dimmers reduce to 20-is working. But nothing past that.
The 9pm cue used to work rock solid, but now, no.
Devices are showing NO commands from the app. The log is showing no command from the app.
The devices all work fine from the Dashboard.
ideas?
I'll definitely put this in my test blender and see what happens, but in the meantime you could potentially work around the issue by disabling the WAIT FOR EVENT steps and add a DELAY 03:00:00 to subsequent action blocks. Not pretty, but might get you back on track for the time being.
Unfortunately cannot replicate (yet). Suggest you go into rule and click DONE just to make sure it's properly initialized, check all of its Logging options to enable, and then share Logs (tomorrow) with only that rule's entries filtered.
I'd be looking for it to generate entries like:
OK.
Do I need to do anything with this "required expression"? I cant find support for that question.
Thanks.
Nope, R.E. is just a means of governing whether a Rule's triggers will be evaluated. But if you wanna learn more on that topic...
obviously you can break up to 5 or so separeate rules with ease...
2 Likes
So, yesterday, I put in some 'test wait times' that were one minute apart to watch the steps happen. The when trying to edit the first 'wait until sunset' line, the edit would not take. It kept resetting to 12:30pm everytime I would click 'done'. I finally deleted the line, then re-entered a 'wait' line. THEN it finally entered properly.
Anyhow, the test worked fine. Then I put back the original 'wait' times based on sunset and following benchmark cues at 9pm, 11pm and lights out at 11:30pm. All worked fine overnight.
Strange.
So in the future, I guess, try removing the "wait until" line from the Rule and then re-adding it.
1 Like
On occasion I've had a rule act strangely and have deleted and recreated it exactly and then it worked fine. I have to assume somewhere along the line it got corrupted but not bad enough to break it. At least it doesn't happen too often!
1 Like
So, I think I solved my dilemma.
I bought several of these LED controllers on AliExpress. They work great BUT…they will only turn off when ‘dimmed to zero’
A simple Off command along with other switches doesn’t reliably shut them off. I’ve cluster them all with their own dim to zero rule line.
I think that’s solved it.
1 Like
