Happy new year @bravenel and all.
Still having a problem when hub reboots if a mode is being set by switch after upgradeing. Let me elaborate:
I have two modes, Home and Night (from the days of Smartthings); Night triggers at sunset and Home triggers at sunrise. When we go to bed, we say good night to Alexa, who then turns on a virtual switch to change the mode to asleep (if the switch is switched off during the night the mode goes back to night). In the morning at sunrise, the hub changes back to home whether it was in sleeping or night. This morning when I updated and when the hub rebooted, it switched from asleep to night, when it should have stayed in sleep and waited for sunrise to switch to home.
Perhaps a way to disable the restore hub on reboot would be a good pathway out of this?
Did you update to 2.3.4.128?
Yes. The behaviour I am describing was after I updated to 2.3.4.128.
Thanks,
Zuhair.
I had the original issue with .127 when hub rebooted while we were home it set mode to away. I just updated to .128 and rebooted....I was not home at the time and the hub was "away" when it rebooted it switched the hub to "morning" it's never done that before.
After .128 the hub rebooted and the mode was fine
Went to bed at about 10:00, at midnight the mode changed back to Evening "by update"
Not good to deal with after just 2 hours of sleep
I just rebooted again and it is consistent. Set my mode back to Morning.
Something is really goofy with my modes. This is in my logs:
The hub is telling me it's in "Day" mode. My Room Lighting apps thinks it's "Morning" mode.
What mode was your hub in when you rebooted it? And was that mode set from the Times table in Mode Manager, or by some other mechanism? Please post a screenshot of the Times table from Mode Manager.
I was remote and hub was in Away mode. I remotely rebooted hub and it switched to morning mode when it rebooted.
Away mode would have been set by presence in the Mode Manager.
Thanks. That will be fixed in the next release.
Mine did the same thing.
How about the issue I saw with my post above, here:
You can see in the logs the hub thought it was in Day and Morning mode at the same time.
Please show the RL setup page.
It's as if it missed the mode change when you changed it to Day mode, after Mode Manager erroneously set it to Morning. Yet, it shows Day mode for the condition.
It logs mode changes...
In my case, it went to Sleep mode at 9:55pm as part of my good night routine, at midnight it went to Evening Mode by Update, no reboot was performed
@bravenel
Something still a little wonky (version 129) even though it appears to be working correctly.
The logs after rebooting show the status in the app name incorrect. However, the logs entries show the correct current status and the apps themselves do.
I noticed this before the update as well but thought there might just be a lag or caching issue in the name. However, now, both HSM and Mode Manager appear to show in the log names one mode ahead of what I am.
Logs
App Name status shows Night for mode and Armed Night for HSM. Before I updated, they were showing Early Morning and Disarmed (Even when I was away at work earlier today). I assumed that was just a caching issue with the names as that was the first entry after update and reboot. However, I have not yet encountered the conditions for Night mode since I have updated.
Those names in the log headers are not updated, but reflect the name of the app at the first time it logged. If the app changed the mode on restart, it would log that, but the app name would not have been updated yet as that only happens when the app is open in the UI.
