better_thermostat
better_thermostat copied to clipboard
wrong actual temp
Prerequisites
- [ ] Sonoff TRVZB Heizung Wohnzimmer:
hvac_modes: off, auto, heat
min_temp: 4
max_temp: 35
target_temp_step: 0.5
current_temperature: 21.3
temperature: 22
hvac_action: idle
battery: 100
battery_low: null
child_lock: UNLOCK
closing_steps: 184
frost_protection_temperature: 7
idle_steps: 326
linkquality: 87
local_temperature: 21.3
local_temperature_calibration: -7
occupied_heating_setpoint: 22
open_window: OFF
running_state: idle
system_mode: heat
update:
installed_version: 4353
latest_version: 4353
state: idle
update_available: false
valve_closing_limit_voltage: 2631
valve_motor_running_voltage: 1624
valve_opening_limit_voltage: 1353
friendly_name: Heizung Wohnzimmer
supported_features: 1
Better_Wohnzimmer_Heizung:
hvac_modes: heat, off
min_temp: 4
max_temp: 35
target_temp_step: 0.5
current_temperature: 20.5
temperature: 22
hvac_action: heating
window_open: false
call_for_heat: true
last_change: 2024-01-06T18:50:59.871468
saved_temperature: null
humidity: 48.2
main_mode: heat
tolerance: 0
heating_power: 0.01
errors: []
batteries: {"sensor.thermometer_wohnzimmer_zb_temperature": {"battery": "100", "battery_id": "sensor.thermometer_wohnzimmer_zb_battery"}, "sensor.thermometer_wohnzimmer_zb_humidity": {"battery": "100", "battery_id": "sensor.thermometer_wohnzimmer_zb_battery"}, "binary_sensor.wohnzimmer_fensterlinks": {"battery": "off", "battery_id": "binary_sensor.fabian_wandthermostat_battery"}, "climate.heizung_wohnzimmer_zb": {"battery": "100", "battery_id": "sensor.heizung_wohnzimmer_zb_battery"}}
friendly_name: Better_Wohnzimmer_Heizung
supported_features: 1
wrong actual temp
It seems that the external temperature sensor is not being used correctly. The temperature value in the BT card is correct, but the value in the thermostat card is not correct and this is causing the heater to stop heating.
HA Core 2024.1.2
BT installed_version: 1.4.0
I've similar issues with my Sonoff TRVZB and I assume that this is not a BT bug. Please correct me if I'm wrong. Some other smart people found out that the temperature calibration of the TRVZB is not working as expected due to a firmware bug. Sonoff is currently working on a fix. See https://github.com/Koenkk/zigbee2mqtt/issues/19269#issuecomment-1839743498
I have something similar with two of my Hama branded Tuya TS0601. They randomly stop heating even though local_calibration
is set to -6, showing a local temperature of i.e. 21.4°C even though it's 18.8°C in the room.
It might be related to the temperature of the heating circuit, as one of the thermostats is like 2m away from the heater itself. Recently we had to increase the heater target temperature because the house is old and with -5°C outside, it has troubles keeping the temps up at night.
So I'm guessing even at -6 in local_calibration
, the thermostat itself thinks it's over 21°C. Trying temperature based calibration since that potentially goes up to 30°C...
I have something similar with two of my Hama branded Tuya TS0601. They randomly stop heating even though
local_calibration
is set to -6, showing a local temperature of i.e. 21.4°C even though it's 18.8°C in the room.
So I'm guessing even at -6 in
local_calibration
, the thermostat itself thinks it's over 21°C. Trying temperature based calibration since that potentially goes up to 30°C...
Use target temperature calibration. The -6 and the 1.5 to 2 degrees "deadzone" from Hama is often not enough for the calibration.
I have exactly the same problem with six TP-Link Tado Thermostats and self made esp8266 temperature sensors (ESPHome). The sensors are working as expected, showing the correct temperature. I've set the esp temp sensors as external sensors in my better thermostat settings. But the Better Thermostat is not using these external thermometers. It is showing and using the internal Thermostat Temperature Sensor.
I am having a similar issue with my Moes BRT-100-TRV devices. External temperature sensors are working as expected and are showing correctly in the current_temp of the Better Thermostat. However, the current_temp of the real TRV is not updating correctly and shows a different temperature. This means that Better Thermostats may show as Heating or Idle, where this is not actually the case on the real TRV. When reloading the Better Thermostat the temperature on the real TRV updates to the correct value given by the external sensor, but does not continue to update.
I have tried changing the sort of calibration from offset to target temperature based, as well as changing the calibration mode from AI to Normal, but neither has fixed the issue. The only thing which seems to correct it (briefly) is reloading Better Thermostat. Maybe a new feature where you can set how often the real TRV is updated would fix the issue? I have seen another post requesting this feature. At present the issue means the Better Thermostat does not work as intended.
I'm having a similar issue. It used to work fine, but recently one of my BT integrations has started to behave weird.
I have 2 TRVs (Tuya TS0601 via ZHA) and an external thermometer (SwitchBot Meter) in one BT integration. I'm using offset calibration. The external sensor is working fine. The target temperature on the TRV display looks fine. However the valves don't open/close as expected. They seem to be reacting to the internal thermometer, not the external one.
e.g. yesterday the external thermometer was showing 18.5C, and the target was 19.5C, when I noticed the valves didn't open. I had to increase the target temperature all the way up to 24C for them to open. Then when I lower it to 23C they shut off again (at that point, the external thermometer showed around 19C). I'm sure this used to work fine previously.
Also, I have 3 more BT integrations using the same TRVs and same external thermometers, although all of those are are hooked up to a single TRV, and all of those seem to be working fine.
I'll switch the batteries in the 2 problematic TRVs, just in case. Although they aren't reporting that they are low. And it would be really weird that both of them are drained at the same time. But maybe one is enough to mess with the whole integration
The problem as I see it is that the TRVZB offset is being capped at -2.5 perhaps in my case by ZHA , BT won't create a larger offset than 2.5 at least from what I can see in the logs.
If it weren't then I would be getting better results ?
Anyone know how to fix this limit - maybe I need to use Z2M ?