When window sensor is unavailable > better thermostat shouldn’t be unavailable too, it should simply ignore the window function #728
Replies: 2 comments
-
Hmm, yes. Currently the unknown state is handled as "window open". Could you confirm with the log entries, if that's the case? Because then i would change it. |
Beta Was this translation helpful? Give feedback.
-
Yes of course! I'll share with you my data, but first of all thank you very much for your wonderful integration! SUGGESTIONWhen window sensor is unavailable, I think that better thermostat should handle the window as closed, so that better thermostat can heat normally (as if you didn't set any window sensor) Furthermore I think that in most cases, when a window sensor in unavailable (especially zigbee window sensors), it happens because the window has been closed for many hours, so that HA - not receiving inputs from that sensor for a lot of time - can think that the sensor is unavailable. From your last message I read that probably you are planning to code better thermostat in the opposite way: when a window sensor is unavailable, better thermostat handles it as "window open". Maybe it could be a good idea to add an additional option into the configuration of better thermostat - as you can see in the following image - in the last page of better thermostat configuration, so that every user can select / unselect the correct expected behaviour in their home: MY CONFIGURATIONI've configured a better thermostat integration named "riscaldamento bagno" (entity climate.riscaldamento_bagno_better_thermostat) In the following image you can see my configuration of "riscaldamento bagno" (climate.riscaldamento_bagno_better_thermostat) and as you can see I have set a window sensor "sensore finestra bagno" (entity "binary_sensor.sonoff_finestra_bagno_aperto_chiuso") PROBLEM: WHEN WINDOW SENSOR IN UNAVAILABLE > BETTER THERMOSTAT IS UNAVAILABLE TOOYesterday at 16:42 my window sensor became unavailable (in italian "non disponibile"), as you can see in the following image: In parallel, better thermostat entity named "riscaldamento bagno" ("climate.riscaldamento_bagno_better_thermostat") became (and is still) unavailable (in italian "non disponibile"), as you can see in the following image: And when I try to add to my UI a better thermostat card with "riscaldamento bagno" ("climate.riscaldamento_bagno_better_thermostat") it tells me that the entity is unavailable (in italian "non disponibile"), as you can see in the following image: Here I import the diagnostic of "riscaldamento bagno": config_entry-better_thermostat-86a7dac91b5409f135c5ca10bbb6b907.json.txt TEST -> I OPEN THE WINDOW > BOTH WINDOW SENSOR AND BETTER THERMOSTAT BECOME AVAILABLE AGAINNow I try to open and close my window, so that the window sensor becomes available again (open and closed). screen.record.mp4I tried to be as detailed as I can, since you're doing a wonderful job! Thank you for your work!! |
Beta Was this translation helpful? Give feedback.
-
I’m currently testing better thermostat and I’ve set a window sensor in better thermostat configuration (I use a sonoff zigbee sensor).
Unfortunately sometimes window sensors can be unavailable (for example when zigbee sensors don’t update for a lot of time, they may appear as unavailable in home assistant).
I’ve realized that when my zigbee window sensor is unavailable, better thermostat entity is unavailable too.
I think that, when the window sensor in unavailable, better thermostat
What do you think? According to me a single window sensor shouldn’t block all climate control!
Pd: better thermostat is wonderful and has an enormous potential! Great job!
Beta Was this translation helpful? Give feedback.
All reactions