Closed stowers95120 closed 1 year ago
I have the same problem here:
The window is closed and the target temp is set to 21°C. I open the window and as expected the target temp goes to 5°C. After closing the window, the target temp does not go back to 21°C, but to 30°C. When I then set the target back to 21°C via the Better Termostat UI card, everything is working fine again (until I open the window again).
Unfortunately I'm new to Home Assistant, so I'm not much help yet, but I'm reading up on HA development and checked out the Better Thermostat code. Hopefully in the future I can contribute a little bit more than just tell you what's not working ;)
I got almost the same problem. Got the Bosch Thermostat II. When opening the window it switches off. When closing sometimes it does not switch on or it switches on but changes the temperature. Today for example it did it one time. Before opening the window it was set to 21°C, it switched off an then on to 24°C.
We would need logs to see what happens.
But what I'm thinking, opening the window means the external sensor changes temperature, so yes after closing the window the TRV target temperature is different from before, to heat up again to the BT target temperature?
Now it switched from 21 to 22 without the window. How do I get the logs? Im new to Home Assistant. In the log section of Home Assistant is no entry for the Thermostat or the Entity at this time. I set the target for the room back to 21, the target for the TRV is still 22 but that is ok. My problem is that Better Thermostat changes its Target Temperature for the room.
Maybe I misunderstand the Better Thermostat UI then. I get that after opening the window and the temperature at the external thermometer dropping sufficiently a boost makes sense to heat the room back up. I would have expected the setpoint of the actual TRV going to 30°C but the target temp at the Better Thermostat UI staying at the target temp I set. Is the target temp (big center number) in the UI not only changed by the user and/or schedules (which I haven't set yet)?
I tested and can confirm that this does not happen when I just open the window and close it again before the room temperature drops significantly.
I'll try to get some log output for you and I'll also test if the target temp goes down again after a while. So far I always manually changed it back to 21°C after closing the window without giving it more than maybe 30 minutes.
I'll try to get some log output for you and I'll also test if the target temp goes down again after a while. So far I always manually changed it back to 21°C after closing the window without giving it more than maybe 30 minutes.
I dont think it goes down after some time. In my case it stayed at 24°C for over 10 hours and the I switched it back to 21°C. So I had it two times after I closed the window. The first it stayed of, the second it increased the temperature. And a third time it increased the temperature without a change on the window sensor.
Today - without opening or closing the window - it set the target to 21°C but did not switch to heat.
Maybe it has something to do with #791 or #785. Don't know.
I got this in my log: 2023-01-05 07:44:42.303 WARNING (MainThread) [custom_components.better_thermostat.utils.bridge] better_thermostat Heizung Wohnzimmer: intigration: bosch_shc isn't native supported, feel free to open an issue, fallback adapter generic
I have not been able to reproduce the problem in the last few days. There was a HA CoreUpdate to 2023.1.1 so maybe that took care of the issue? Not sure if that's possible.
Today - without opening or closing the window - it set the target to 21°C but did not switch to heat.
Maybe it has something to do with #791 or #785. Don't know.
I got this in my log: 2023-01-05 07:44:42.303 WARNING (MainThread) [custom_components.better_thermostat.utils.bridge] better_thermostat Heizung Wohnzimmer: intigration: bosch_shc isn't native supported, feel free to open an issue, fallback adapter generic
Here both are set to off. That's why there is no heating.
Here both are set to off. That's why there is no heating.
That is right. Thanks for confirming. It is the setting from Better Thermostat. It set them off. Switching them on manually Better Thermostat sets them off aganin.
2 hours after my post HACS showed the update to version 1.0.0. So I updated an it worked like a charme. Till yesterday. Yesterday - without doing somethine by myself - Better Thermostat changed the target temperature from my setting, 21°, to 24.5 to 30 to 23... and so on.
Over the night, it switched at 2200 to the target 18° it set the TRV to 23° and the valve to 15% - 0% - 15% - 0% - 15% and so on to keep the temperature at 20°.
Better Thermostat is really a nice concept but here it is buggy as hell.
Prerequisites
Description
I had configured my thermostat (Honeywell T9-T10) with a window sensor. When the window was opened, the integration correctly set the heating to off mode. When the window was subsequently closed, heating was returned to on mode. However, an incorrect set point temperature was set. Before opening the window, the set point ws 68 degrees F, but after the window close, it was incorrectly set to 74 degrees F.
Steps to Reproduce
Expected behavior:
Actual behavior:
Versions
Additional Information