The last day or so I've had two App rules miss actions:
R-M Missing a simple turn lights off at 10:30 PM. I opened the App and pressed "Done" now the pending rules show correctly.
Thermostat Scheduler:
I have two that are both the same logic.
One thermostat is Z-Wave (and has been working)
The 2nd thermostat is Zigbee and missed the morning change today. Have done nothing but look at the events, logs and details of this instance of the app. Currently the schedule shows the pending actions correct for this evening and tomorrow morning.
How do I troubleshoot.
BTW
There has been no changes to my HE hub in the past week or so**. I was considering posting in Getting Started that I was bored because every had been working so well.
** Actually there was one change, one of my 6 dimmer modules which had been using the "Leviton Fan Controller" driver , did not report (based on the dashboard) so I change it to "Generic Zwave dimmer"
I have had the same issue. On of my lights scheduled to go on at 4:50 am and off at sunrise -15, turned on two days ago but didn't turn off. Then today it didn't turn on at 4:50 am. Shows in the log that it recognized the time but didn't fire. I have brought it up with support as it was working before.
Based on what you showed in the logs, it appears that the rule is running when it should but the light is not responding to the command being sent. What type of device is this?
Look at the same logs the @JohnRob posted. The app events show his rule firing both true and false as expected. But his device doesn't respond. That suggests it's a device issue, not a rule issue. Same question about the device type.
I hadn't collected enough information to respond but since @pcgirl has asked I will tell you what I found so far.
Devices: Linear WD500Z-1
Thought that it might be the devices, unlikely as they work fine manually (from the dashboard or device page)
My rule is shown in my previous post. The rule posted was after it started to not go off at the prescribed time.
This rule originally worked for some time, maybe weeks.
Not too many days ago I found it wouldn't go off.
Two days ago I deleted the rule and recreated it. The newly recreated rule works.
What I found
I had captured the rule "details" (?) both before it was deleted and after it was recreated.
In the below screenshot are two different rule details side by side. The left side is from when the lights were not going off, the right is after I recreated the rule.
It seems some OFF information is missing from the rule that did not shut off the light. But exists in the recreated rule.
I had gone through a few updates but cannot say if the data loss(?) was related to the updates.
At this point I am assuming there was a data loss in the rule details, however I really have no evidence of that, just a logical deduction.
So my lights worked as expected this morning. Not sure why it didn't work the other days. I didn't change anything. I just let it be because it had worked before. Here is the log that shows the light not coming on at 4:50am on Dec. 18 but turning off at sunrise -15. It recognizes the time but doesn't do anything. But it all worked today.
Thanks for showing that, and figuring it out! That is very bizarre, I haven't seen any setting get lost like this before. Will have to scratch our heads about this one!!
Thinking back, one of the recent updates hung somewhere in the install cycle. I did what every computer owner would do, removed power, waited ~ 30 seconds and restored power.
Could this possibly have corrupted the above rule (my post not pcgirl's) ?
If the root cause is due to an abrupt loss of power, I think next time an update hangs (if there is one) I would restore the backup I make just prior to updating, the reapply the update.
Can you verify this would remove the possibility of corrupt data due to the power loss?
That's a good plan. Also, another thing to try is to just return to the portal, and see if the download won't start over. I've experienced stuck downloads too, but haven't had to pull power to get them going again. Did you try refreshing that page, or hitting back in your browser? It happens so infrequently that I don't remember which of those three steps works to get it started again -- I'd try the link in the portal first.
My issue is/was different than yours. Once the RM stopped executing the [false] actions they never returned. The first thing I tested when the failure started happening was the ability to control the light(s) from devices and or dashboard (aka manually). My devices always worked manually and with minimal delay. Do you feel the devices are "solid" with regards to communications?
I know you said you didn't change anything, however might have you looked at the rule and pressed "DONE" when you finished looking? It may have recreated the same internal instructions correcting some issue in how HE interprets the rule. I'm out on a limb here, not really knowing the HE RM internal details but hazarding a guess.
Still having some issues with RM rules. Even though the rule is saying TRUE nothing happens. Even though it worked the day before. For instance my undercabinet lights are set to go on in the mornings at 4:50am. For days they will work and then all of a sudden they don't turn on. Rule shows TRUE but the lights aren't on. It is sporadic so it is hard to tell what is causing the issue. Is it the zwave receptacle? Is it something in RM that isn't firing? Is it the hub? Not sure.
Look at the app events for the rule on the app status page. If it says the rule is "now True" then you know that the rule did its thing. If the rule did its thing, but the light didn't turn on, that implies the light didn't respond.
Yes, sometimes it says TRUE and it says that it turned the light ON but it isn't on. Other times it recognizes the time as TRUE but doesn't do anything. Doesn't happen consistently either. Some weeks everything is working great then I come downstairs and the lights aren't on in the morning. But most everything works. Just some weird things happening occasionally. Where they were working and then not.
Do you have another device that is near the hub and has proved to be reliable? If so you might temporarily add it to your Rule that is giving you issues. It might show if the problem is in the devices or the hub.
If you haven't already recreated the rule, I would suggest you delete the current rule and create a new one exactly the same.
