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
#35
I have the same problem, when I go from auto to off or from auto to heat, when I go back to auto the thermostat always goes to period 1.
To go back to the right period I have to physically act on the thermostat by switching first to manual and then to automatic.
The Beok thermostat is on "1234567" and the climate of HA schedule=2
Am I doing something wrong or there is no solution.
Thanks
--EDIT--:
I did some tests.
The problem occurs only on days 6 and 7 (Saturday and Sunday) even if the loop_mode (schedule) is set to 2.
I tried to edit line 31 of "init.py" by setting DEFAUL_SCHEDULE=2, but the result does not change.
It seems that every time a command is sent from HA, "schedule"=0 is also transmitted.
Of course from the BEOK everything works normally if I use the buttons on the terostat or if I use the app.
--EDIT--:
This is the log of floureon debug
#35
I have the same problem, when I go from auto to off or from auto to heat, when I go back to auto the thermostat always goes to period 1.
To go back to the right period I have to physically act on the thermostat by switching first to manual and then to automatic.
The Beok thermostat is on "1234567" and the climate of HA schedule=2
Am I doing something wrong or there is no solution.
Thanks
--EDIT--:
I did some tests.
The problem occurs only on days 6 and 7 (Saturday and Sunday) even if the loop_mode (schedule) is set to 2.
I tried to edit line 31 of "init.py" by setting DEFAUL_SCHEDULE=2, but the result does not change.
It seems that every time a command is sent from HA, "schedule"=0 is also transmitted.
Of course from the BEOK everything works normally if I use the buttons on the terostat or if I use the app.
--EDIT--:
This is the log of floureon debug
The auto_mode and the loop_mode value 3 is an error?
The text was updated successfully, but these errors were encountered: