Add-On Restarts or otherwise reverts to temperature of 18 °C #1441
Comments
|
Can you please provide:
|
|
I'm facing a different but related issue in #1464 BT does not change the temp in the UI, but the logs show it randomly reads the target temp as 18°C. |
|
I'm facing a similar issue. BT randomly switches target temperature to 5°c. This is also reflected in the UI. But there are no indications that the integration restarted. The trigger for the first event that shows the new target temperature seems to be: "trigger_trv_change test". I have attached a log of the latest occurrence. |
|
This looks like an issue similar to #1387. The logs show the same |
|
That could be the case. I think the two issues are somewhat related but I'm still trying to figure out the root for the problem. |
|
@Asakash yeah, I also had a brief look at the source (obviously need to spend more time on it), but from what I can see — the So I guess the issue is one of two:
Will also dig a bit more |
|
@antstorm I totally did not see that it overwrites I will add some more debug logs and wait for the next occurence. |
|
@Asakash yes, I'm also now trying the child lock via BT. I had previously configured the child lock on my TRVs via their native software (Tado in my case), however that didn't help. Hopefully setting it in BT should prevent the change of the target temperature 🤞 |
|
@antstorm I just had the "error" happening again. I added some more logs. One in the function As the log shows, the 5.0°c originates in the new state of one of the TRVs. No idea where it comes from. Maybe some sort of overheat protection (as BT sets it to 31°c for a while as my radiators are a bit undersized at the moment). There is no option for something like this in the shelly TRVs but that could be the problem. But he rest is more or less as we suspected. Switching on child lock in the TRV software will not help as the only reason setting it in BT for the TRVs might solve our/my problem is, that the function to change BT target temp will not fire if child_lock is |
|
@Asakash yes, it does seem like the issue is originating from a TRV itself (or something else upstream of the BT) without the manual input. Assuming there's no way to distinguish between someone manually turning the TRV and TRVs firmware sending weird data, the only way to fix this is to ignore these inputs altogether. And that's what setting the I've got child lock set in both TRVs and BT and it seem to be behaving as expected so far. |
Prerequisites
Zigbee-Modell
RBSH-TRV0-ZB-EU
Zigbee-Hersteller
BOSCH
Beschreibung
Radiator thermostat II
Unterstützungsstatus
Unterstützt
IEEE-Addresse
0x18fc2600000c7cf8
Netzwerk-Adresse
0xB9F2 / 47602
Firmware-Datum
20220627
Firmware-Version
3.02.05
Hersteller
Bosch
Modell
BTH-RA
{ "home_assistant": { "installation_type": "Home Assistant OS", "version": "2024.10.4", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.12.4", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "6.6.54-haos", "supervisor": "2024.10.3", "host_os": "Home Assistant OS 13.2", "docker_version": "27.2.0", "chassis": "embedded", "run_as_root": true }, "custom_components": { "hacs": { "documentation": "https://hacs.xyz/docs/configuration/start", "version": "2.0.1", "requirements": [ "aiogithubapi>=22.10.1" ] }, "battery_notes": { "documentation": "https://andrew-codechimp.github.io/HA-Battery-Notes/", "version": "2.5.4", "requirements": [] }, "better_thermostat": { "documentation": "https://github.com/KartoffelToby/better_thermostat", "version": "1.6.1", "requirements": [] } }, "integration_manifest": { "domain": "mqtt", "name": "MQTT", "codeowners": [ "emontnemery", "jbouwh", "bdraco" ], "config_flow": true, "dependencies": [ "file_upload", "http" ], "documentation": "https://www.home-assistant.io/integrations/mqtt", "iot_class": "local_push", "quality_scale": "platinum", "requirements": [ "paho-mqtt==1.6.1" ], "is_built_in": true }, "setup_times": { "null": { "setup": 1.5740981325507164e-05 }, "507735d44302723d0d76268418b845a2": { "wait_import_packages": -1.236915681976825, "wait_import_platforms": -0.35411177086643875, "config_entry_setup": 1.6155338000971824 } }, "data": { "connected": true, "mqtt_config": { "broker": "core-mosquitto", "port": 1883, "username": "**REDACTED**", "password": "**REDACTED**", "discovery": true }, }Description
The set temperature of the climate entity is randomly set to 18 °C. Logs suggest a bug of sorts that restarts the entity or add-on, which is set to 18 °C by default.
Steps to Reproduce
Expected behavior:
Temperature stays at set temperature.
Actual behavior:
Temperature is changed to 18 °C
Versions
"version": "2024.10.4"
BT: 1.6.1
Additional Information
The text was updated successfully, but these errors were encountered: