2.3.4.128 Mode Changed at Midnight, woke us up! Mode set "by Update"

[joeplayspiano]

Updated to 4.128 on C-7, on 1/2/22. Went to bed, activated "night" mode in which my motion sensors in the master bedroom are no longer a means to activate lights.

At midnight, our lights came on. After checking log files, I found this:

This has never happened before and I have not made any changes to my automations for triggering modes in over a year.

My Modes - Day, Evening, Night
Triggers -

• Day-Switch Turned off or TOD, whichever is first.
• Evening-TOD
• Night-When switch is turned on or 2:05am, whichever is first

Screenshots

Mode Manager:

Room Lighting:

I'm not sure what Mode set to Evening from Night by Update means, assuming it's due to the 4.128 update? I'm not concerned unless this happens again tonight, in which WAF will tick down a few points.

Thanks for any information you can provide.
Joe

[toy4rick]

This appears to be part of what was fixed in .128, Here is the main thread on the topic

2.3.4.127 - Mode Manager switching to incorrect mode on reboot

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 [image]

[joeplayspiano]

Thanks for the thread @toy4rick. I didn't have this problem in .127, and after updating to .128 I rebooted well before I went to bed (as did you) So this doesn't seem to be resolved?

[sburke781]

The fix, from what I saw related to mode changes due to a reboot, which, at least from the logs, this does not appear to be.

This might be something @bravenel and the team may need to look at.

[sburke781]

Actually the 128 notes do refer to update as well.....

Release 2.3.4 Available

Release 2.3.4.128 Available Changes from 2.3.4.127 Updated Apps webCoRE. Bug Fixes Faster loading for HomeKit app. Mode Manager: Fixed errors on initial install and for variable times, and setting wrong mode on reboot or Update from app. Thermostat Scheduler 2.0: Fixed error caused by logging.

And that was the comment @toy4rick linked... I should have read that first ..

[sburke781]

Looks like a fix is coming. Thanks HE Dev team.

[rlithgow1]

Known Issues in Release 2.3.5.152

See this: Release 2.3.5 Available - #23 by gopher.ny Barring unforeseen issues, we plan this to be the final 2.3.5 release. The following issues have been identified in Release 2.3.5.153; we expect these to be resolved in the next release: Rule 5.1: Sets invalid value for Set Variable to Current Date (invalid for Dashboard). Delay per mode throws error for variable delay. Repeat n times sometimes fails to repeat. Fails to set multiple thermostats for Set Thermostat Scheduler. Erroneously s…

[joeplayspiano]

Updated to .129 - Thanks all.