You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First thank you for this nice port of the software, it works almost flawlessly for me.
However, sometimes the esphome restarts (once a day or something, due to unknown reasons) and the HAVC is turned off (due to the default off setting in the code).
Do you know if there is a possibility to read out the current value exposed by home assistant?, as you do not want to default the HAVC to cooling (as restarting the system will consequently turn on the unit.)
The text was updated successfully, but these errors were encountered:
The problem is actually the other way around, in #30 the status is the one provided by home assistant, while it is supposed to be off. However, in my case, when it reboots it is powered off, while it should be powered on (it should get the state from the hassio instance).
I will mess around with the code soon to see if i can implement this, defaulting to off seems in most cases a safe consideration.
It's not really reliable to try to get/save power status from HASS or any external source. It may cause weird behaviour where AC's will spontaneously turn on while they in fact should be off. I think the default of power off is the best.
You could probably create a sync automation which checks whether the state from HA mismatches the one in the unit, and then apply the requested mode by setting the mode if it does.
First thank you for this nice port of the software, it works almost flawlessly for me.
However, sometimes the esphome restarts (once a day or something, due to unknown reasons) and the HAVC is turned off (due to the default off setting in the code).
Do you know if there is a possibility to read out the current value exposed by home assistant?, as you do not want to default the HAVC to cooling (as restarting the system will consequently turn on the unit.)
The text was updated successfully, but these errors were encountered: