Possible mismatch between binary_sensor in HA and MSR
-
It may. I have similar behavior with other Template sensors being 0/null/off at boot.
As a defensive measure, I always make the condition to be sustained for at least 10 secs and/or avoid them being evaluated when ha has been restarted for the last 20 secs.
I rarely use ha templates, so my experience is anecdotal.
-
@therealdb that would rather force (in this case) all the heating off (or on), wouldn't it?
I like the idea of a 30 second delay though.
C
-
I don’t know if setting to null it’s better for reactor. @toggledbits here is the best source of truth.
-
OK. I can't prevent HA from starting up in an undefined state, and the effect that can have on the rules, but @therealdb is spot-on with an approach to dealing with that, since the corrected state usually comes pretty quickly after. Sometimes, you just have to debounce those switches a little.
Beyond that, there is definitely an opportunity for a race condition and I think I have a good general fix for that. The logs support that cause as well. Testing my updates now. Will likely do a build with the update tomorrow.
-
This is just a follow-up to link this conversation to the announcement for the build that addresses it, and expands generally on transient startup/outage states in HA integrations
-
Thanks, installed and working.
Although after the first restart there were some virtual switches in HA that were not being accurately reflected in MSR, but I restarted MSR again, and everything looks fine.
Thanks again for your help. Next time I'll upload the logs to start with!
C









