Home Assistant 2025.11.2 and latest-25315

[toggledbits]

I just tested mode sensitivity, which I also had done before the build, and it's working as expected. So that part is fine. The log shows "Day mode" rule is going to Reset state, so unless your action is in the Reset reaction, I wouldn't expect it to log the change you seem to anticipate. You haven't shown the rules or reactions, so I have no way of judging what it will do or whether what I can see it doing is right. Show your work, please! Also check your host time zone settings. Logs are Zulu (UTC), not ET, and that would account for a five hour difference in host time vs log time, normally (standard time).

http://your-reactor-ip:8111/diag/sun

Also look at the rule detail panel any time you are troubleshooting logic. Your log snippets don't show any actions being run at all for rule-kmfo3pz8, just the rule eval/update to Reset state. Logging of actions in HubitatController is currently unconditional, so if any action was being sent, it would be in the logs (regardless of log level).

[gwp1]

@toggledbits The host time is currently 12/4/2021, 10:41:24 AM offset -300 minutes from UTC, which lines up to log timestamps of 15:xx:xx.

This ruleset hasn't changed since MSR came online months ago so I'm loathe to point to that, esp since it's across multiple modes.

Searching the log for this ruleset shows it first appearing at that RESET! line.

I've rolled back to 21332 and retested. Mode day did not kick over as expected. Given this has worked flawlessly with this build I'm digging further. Right now it appears like the house never moved to mode night even though all the actions (lights off, announcement made, unlocked locks locked) happened.

How far back does MSR retain logs time-wise?

[toggledbits]

@gwp1 said in Modes not changing correctly since 21337:

How far back does MSR retain logs time-wise?

As far as your log rotation allows.

Can you go back to 21337 and show the result of the rule detail/status panel?

Also, make sure to check the case of all mode setting actions. Mode names are case-sensitive in Hubitat ( day =/= Day ), so if they don't match, the action won't work. When testing in conditions, make sure the test is case-insensitive (it is in the rule you've shown, so that's good).

[gwp1]

@toggledbits I just moved back to 21337 a moment ago. I cannot seem to get the house into mode night atm. Troubleshooting this as my thinking now is that the house, though doing all the actions (and I repeated that just now), doesn't actually going into mode night anymore.

[toggledbits]

Try "Night" (capital N)... case matters to Hubitat

[gwp1]

@toggledbits When it is time for the house to go into night there is an Alexa routine that flips a virtual switch. This is the sole trigger and the result is the running of a Reaction.

This has been unchanged.

At the end of the reaction is a :10 delay and the virtual switch flips back off again (for next time.) That's it. Nothing fancy. All of these steps are working except for the mode actually changing to night.

This has worked for MONTHS untouched. I'm literally watching it step thru here:

[gwp1]

@gwp1 Ok, this is very odd. I can change the mode in this reaction to any other mode but night and it works. Put it back to night as the outcome and nada.

[toggledbits]

This post is deleted!

[toggledbits]

@gwp1 Please show the entity detail for the "Mode" entity (Entities list).

Also, try setting "Night" from the Entities list actions. And grab logs for the action if it doesn't change.

[gwp1]

@toggledbits This is odd. Wouldn't I expect to see all the modes listed under x_hubitat_sys_mode.modes={"Day":1}?

Tried setting Night from the Entities list actions. Nada.

[latest-21337]2021-12-04T16:45:03.111Z <Rule:5:Rule.js:793> Rule#rule-kphozuch Upstairs bulb requesting eval; entity-changed from Entity#hubitat>55
[latest-21337]2021-12-04T16:45:03.112Z <Rule:5:Rule.js:793> Rule#rule-komaz8fr Upstairs motion requesting eval; entity-changed from Entity#hubitat>55
[latest-21337]2021-12-04T16:45:03.113Z <Rule:5:Rule.js:1005> Rule#rule-kphozuch (Upstairs bulb) evaluate() acquiring mutex
[latest-21337]2021-12-04T16:45:03.114Z <Rule:5:Rule.js:1005> Rule#rule-komaz8fr (Upstairs motion) evaluate() acquiring mutex
[latest-21337]2021-12-04T16:45:03.120Z <Rule:5:Rule.js:1009> Rule#rule-kphozuch._evaluate() mutex acquired, evaluating
[latest-21337]2021-12-04T16:45:03.121Z <Rule:5:Rule.js:1013> Rule#rule-kphozuch update rate is 0/min limit 60/min
[latest-21337]2021-12-04T16:45:03.122Z <Rule:5:Rule.js:936> Rule#rule-kphozuch evaluateExpressions() with 0 expressions
[latest-21337]2021-12-04T16:45:03.124Z <Rule:5:Rule.js:1033> Rule#rule-kphozuch._evaluate() trigger state now false (was false)
[latest-21337]2021-12-04T16:45:03.125Z <Rule:5:Rule.js:1035> Rule#rule-kphozuch._evaluate() constraints state true
[latest-21337]2021-12-04T16:45:03.127Z <Rule:5:Rule.js:1044> Rule#rule-kphozuch rule state now false, changed no
[latest-21337]2021-12-04T16:45:03.131Z <Rule:5:Rule.js:1009> Rule#rule-komaz8fr._evaluate() mutex acquired, evaluating
[latest-21337]2021-12-04T16:45:03.133Z <Rule:5:Rule.js:1013> Rule#rule-komaz8fr update rate is 0/min limit 60/min
[latest-21337]2021-12-04T16:45:03.134Z <Rule:5:Rule.js:936> Rule#rule-komaz8fr evaluateExpressions() with 0 expressions
[latest-21337]2021-12-04T16:45:03.136Z <Rule:5:Rule.js:1033> Rule#rule-komaz8fr._evaluate() trigger state now false (was false)
[latest-21337]2021-12-04T16:45:03.137Z <Rule:5:Rule.js:1035> Rule#rule-komaz8fr._evaluate() constraints state true
[latest-21337]2021-12-04T16:45:03.139Z <Rule:5:Rule.js:1044> Rule#rule-komaz8fr rule state now false, changed no
[latest-21337]2021-12-04T16:45:46.427Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; entity-changed from Entity#hubitat>51
[latest-21337]2021-12-04T16:45:46.429Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex
[latest-21337]2021-12-04T16:45:46.431Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating
[latest-21337]2021-12-04T16:45:46.432Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 2/min limit 60/min
[latest-21337]2021-12-04T16:45:46.433Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions
[latest-21337]2021-12-04T16:45:46.436Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false)
[latest-21337]2021-12-04T16:45:46.437Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true
[latest-21337]2021-12-04T16:45:46.439Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no
[latest-21337]2021-12-04T16:45:46.673Z <HubitatController:null> HubitatController#hubitat final action path for x_hubitat_sys_mode.set on Entity#hubitat>sys_mode: http://192.168.1.214/apps/api/14/modes/Night

[toggledbits]

According to the entity, the only mode that exists on the hub is Day. Log in to your hub and check the Modes screen. If that agrees, something happened to your hub (firmware upgrade to latest new version recently?).

[gwp1]

@toggledbits

Latest release to 2.3.0.115 on Hubitat. Rolling back to .113 to see what happens.

[gwp1]

@gwp1 Rolled back to .113, saw this:

When the restore was done it was in Evening because that's where it was when the release was deployed and backup taken.

Did a Tools > Restart on MSR to ensure everything was synced and now I see this again:

[toggledbits]

Are you on their latest firmware?

[gwp1]

@toggledbits Well I was until apparently an hour ago lol Seems there's .116 out now. Also, rolling back apparently doesn't restore the old firmware to .113 like I thought it would. I'm still on .115. Guess I'll fail forward to .116.

[gwp1]

@gwp1 On Hubitat's latest, .116. No change.

Following my Rule#1 of troubleshooting, "what changed?" I rolled back MSR to 21332 (because I'd just updated to 21337) just in case and now I see this:

Things are behaving as they should. Using the Entities menu I triggered mode night and it flipped over (only to flip back to day as it should because it's day time - but I watched it three times visibly flip to the correct mode.)

[toggledbits]

Yup, and I think I see the issue... stay tuned...

[toggledbits]

OK. 21338

[gwp1]

@toggledbits Yep - all good! Thanks Patrick, I'll mark this as solved. Appreciate it.

[toggledbits]

Thanks for doing the footwork, being the hands and eyes! Sorry for the trouble. Onward!