I just looked, I didn't think about the data base culling shrinking the history here too. Last time I actually looked at mine, it went back to April when I turned on my hub for the first time. It's not that way now....
I have it turned on almost all the rules, definitely on for the ones I shared the examples for. Take a look at the Screenshot that I had shared in my message (Shades - Downstairs Blinds....), you will Events are being logged but last logged event from that rule is 07/20
What’s interesting is that both of us have the event logs pointing to July 20th as the last activity date for respective rules. If the firmware upgrade was the root cause, what are the chances that we both upgraded on the same date - 19th or 20th itself and just us having broken rules!!
I also have a odd Mode manager issue going on. One of my modes doesn’t change all of sudden (I have a post going on for it as well). Are you seeing any issues with modes?
My rule ran at sunrise despite having both settings, so the issue is elsewhere. I'll keep digging.
2 Likes
Looks like simple automation issue is with negative time offsets. Removing offset or setting it to a positive number reliably triggered the event for me while setting it to a negative number reliably did nothing. We'll fix that, but for the time being please remove the negative time offset.
3 Likes
One of the rules that was misfiring for me was in 'simple automation' with a -ve offset, so glad to know RCA is and a fix on it's way. Thanks for your work on this.
What about 'Motion Lighting App' & 'RM' rules. Any insight why some of those may not be working and why events are not being logged despite the logging to be enabled?
I am also seeing odd behavior in the mode manager, could that be related with the same issue?
I'll look into those today.
My rules don't have the offset but still have problems.
So far, the rules that don't work consistently, work when logging is turned on. Something about forcing them to make a log entry is causing them to work correctly.
I found another issue with another rule, that is selectively firing for some devices and not for others.
I have a rule that turns off everything on our upper floor in the morning. Started noticing that some fans are not turning off (all controlled by GE Smart Fan switches). Here are my settings:
Rule
Rule has been firing consistently
But this device no longer getting controlled since 09/11
Here is the settings for the Group that this Switch is part of and is controlled by the rule
Here is another example of another fan that stopped getting events in Aug.
But then here is one of Lutron lights, which is part of the same rule & group, and works just fine. For example the rule turned this light off at 8am, as intended.
So I wonder if one of the firmware updates, broke something with these GE Switches in this case?
I think I am seeing the same time. As I go thru settings of these devices & test then, I am also manually triggering these. And that seem to jump start them and again start getting triggered by rule(s). I have to test more to confirm that it is a confirm behavior though.
Another issue that I discovered is that none of my fan controls are working via rules. I can still control them directly from their respective device page but they don't get triggered via rules anymore. Looks like switch status polling is also not work (for example, if I turn the switch on manually, the device in habitat is not seeing its state change). These are GE Smart Fan controls. Very frustrating, it all used to work until sometime ago.
@gopher.ny did you get a chance to look into these issues? TIA
I think this may be related to hub's time jumps. If at some point the hub thinks it is 2036, it will schedule the next rule trigger into 2036. A save causes it to recalculate next trigger time using current (correct) time.
Now that there's a clear problem definition, I just need to come up with a solution...
1 Like
Related thread:
Never put your hub in the DeLorean.
9 Likes
@gopher.ny Don't want to continue to pester but any update? I continue to see issues - old & new. Is hub gone bad (I only have had it for 4 months). I just created a new rule (motion rule) and it continues to fail every now & then on & off. Sometimes the rule works and sometime it doesn't. Here is the new rule that I created:
Here are the rule logs:
Device (LED Strip) Logs:
Motion Sensor Logs
These logs aren't really useful. What you label as "rule logs" are device logs.
Please turn on logging in the Motion Lighting app, and show those logs when it fails.
So tonight I noticed things all over the place not working. When I went into one of the rules, even though I have all logging turned on, no events showed up in the log and in fact, no new events have been added to the device log for months.
When I Look at the main logs, I see a lot of these:
dev:892020-09-23 11:34:00.494 pm errorjava.lang.RuntimeException: java.sql.SQLException: Connections could not be acquired from the underlying database! (parse)
app:3332020-09-23 11:34:00.478 pm errorjava.lang.RuntimeException: java.sql.SQLException: Connections could not be acquired from the underlying database! (motionHandler)
app:6832020-09-23 10:59:00.511 pm errorjava.lang.RuntimeException: java.sql.SQLException: Connections could not be acquired from the underlying database! on line 7069 (allHandlerT)
dev:892020-09-23 10:40:37.753 pm errorjava.lang.RuntimeException: java.sql.SQLException: Connections could not be acquired from the underlying database! (heartbeat)
dev:762020-09-23 10:40:37.704 pm errorjava.lang.RuntimeException: java.sql.SQLException: Connections could not be acquired from the underlying database! (parse)
Here are some screen shots for context...
This looks ripe for a hub reboot. If that does not cure the issue, next step is soft reset. Here's a "best practice" approach to it:
- Take a backup, and download it locally (just in case).
- Perform a soft reset in the Diagnostics Tool. DO NOT DO A FULL RESET - that will clear radios.
- Restore from the latest backup (one you've just taken). If you don't see backups listed immediately after soft reset (we saw it happened a few times), reboot the hub, and it will pick them up.
Time jumps will be addressed in 2.2.4 firmware update. There's no built in battery, but huge jumps into either future or past will be detected. Hub time might still be off until proper time sync, but not by years.
