@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.
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.
I kinda thought that when I was seeing early morning in the name. However, it hasn't been "Night" since the update (still). That is what was puzzling me. When I updated, the name stated Early Morning. It was in the evening mode. So, when it booted after the update, it should have been "evening". However, it read "Night" from somewhere on reboot. I don't care as long as it is working properly. I just thought you might find it interesting that it is not reading the actual current status when it reboots...... and wondering if that isn't somehow related to the previous issues you have been chasing. (apologies if it seems I was complaining. I was just trying to give data in case it is useful)
Again, it appears to be flowing correctly. So, no issues that I have seen as yet.
Also, I just noticed this flag. I don't recall seeing that before (not sure if it was there and I just ignored it ) Is that new? Any chance that might have caused the issues of Modes being set to home while away on reboot in a couple of the previous comments?
) Is that new? Any chance that might have caused the issues of Modes being set to home while away on reboot in a couple of the previous comments?
