Odd things with 2.5.1.142 and 2.5.1.143

@gopher.ny
When my C8 booted on 2.5.1.142 the SystemStart event did not happen. @thebearmay's Hub Information Driver found the Hub Uptime Variable reset to 0.

Later when the C8 booted on 2.2.1.143 the SystemStart event did not happen and the Hub Information Driver's Hub Uptime Variable did not reset to 0.

I track these two events to trigger a Hub Boot rule that delays some of my hub's CPU intensive rules if the Hub Load is high, checks to see if the hub was down for a while and missed running some housekeeping rules and does a few things with the Hub Variables.

Will this be corrected in a future release?

I'm not seeing the same, if my logs are adequate:

The Hub Events shows the SystemStart events, but the Live and Past Logs do not. If the events don't show up in those logs then RM can't use them as triggers.
Is there a setting that could have turned off the system logging?

ahh..

OK, I didn't check those logs.

This shouldn't be the case. Apps, including RM, would subscribe to the hub or location event, not scrape data from log text. (So the real question is indeed whether they show up where @csteele indicated.) Can you verify on the App Status page for a problematic app that the subscription is still in tact, or that hitting "Done" doesn't fix it?

The subscriptions are valid. Will try a reboot with Rebuild.


The events show up in Hub Events but not in the Live or Past Logs

This sounds like another case of this app not reporting correctly, just like your other bug report the other day.

Are you sure the event isn't happening, or just that it isn't being seen correctly by the app?

I love that app, but sometimes things change in Hubitat firmware and can unintentionally break things.

The reboot with database rebuild did the trick. Somehow the database was corrupted. Now the rule sees both the SystemStart and Uptime variable.

EDIT: need to remember the reboot with database rebuild when things aren't right. :confused:

What kind of a rule was it? Could be that a subscription got borked...

RM, all of my rules are RM.
Not sure. The rule had the triggers, but I didn't think of looking at subscriptions in the app detail. Hopefully, I will remember that next time.....

Hopefully, it won't happen again. :laughing:

I just do this after every hub update as a general rule