BT is being turned off by TRV #1223
Comments
|
I have the same problem here with 1.4.0 - thought I was imagining it first. I see a similar event in my log:
I have Hive TRVs which do not support any other HVAC mode other than Heat. So they are are always on Heat mode. It also seems that my BT thermostat is changing/syncing the target temperature to that of the actual TRV too - e.g. 5C when BT sets it to off (seems similar/same as #1224 and others?) I can maybe work around this bug by just setting the target temp on the real TRV in an automation and bypass BT. This is what I'm testing now. Strange thing is that I have 4 Hive TRVs setup with BT and this problem only seems to happen on one of them, that I've noticed anyway. |
|
Same Problem here. |
|
Same/similar here with TuYa TS0601 TRV:s. Somehow BT instances keep turning off and TRV:s not wanting to obey even the ones that show heating. Started withing last 2-3 days or so. Added recently more TRV:s and instances of BT. Does not affect all TRV:s despite them being the same model. Downgraded to 1.3 but problem persists. This is what I have on dashboard This is what is actually set to TRV (and gets just set again if I manually alter) |
|
I too am experiencing this. I have about 8 trvs started seeing this in the last few days. I've removed BT from one for them all together to see of the underlying TRV still turns off. |
|
So it's been a few days since I completely removed the BT thermostat that was turning itself on/off and changing the temperature on its own, so I thought I would provide an update. I am now just talking directly to my TRV via an automation to essentially provide a grouped setup for one room (one physical actuator and one Hive TRV). It now seems to be working properly and I notice that the room is now finally heating much better than before as the TRV is actually turning on and staying on, when needed. Note: I found that I still had issues with the TRV behavior before I restarted HA. Once the BT thermostat was fully removed and HA restarted the TRV has been fine. I also migrated one other BT thermostat to use an automation that is part of another room that can be grouped - that also seems to be working too. I previously didn't use this one in a BT grouped setup and had them separate. I have also been thinking some more about why was it that only one BT thermostat had this strange problem and the only thing I can think of is that this TRV was originally part of a BT grouped setup with my physical actuator thermostat. However, the BT grouped logic never worked properly from the outset and did strange things, so I just deleted it and recreated it as regular single BT thermostat. I wonder if there is some hidden/stored configuration data for that TRV value (e.g. unique ID) that caused BT to continue to do weird things with it? Not sure of the BT internals, but it's just an idea as I can't think of any other reason, as my other TRVs which used BT seem to work OK - it's very strange why it only seemed to affect that one TRV. |
|
|
|
I was wondering how BT distinguishes between inputs set by the user on the TRV and changes of the TRV made on its own. BT seems to take over some of the TRV changes, probably to have the option to set a new temperature. I run several TS0601 (_TZE200_hue3yfsn) and have two of them currently controlled via BT. I do not use the childlock function and use the AI mode with target temperature setting. BT target is set to lets say 20°C. For heating BT set the target of the TRV then to 30°C which is perfectly all right. If I then manually move the temperature control on the TRV, BT suddenly switched to a BT target temperature of 29,5°C. This might be the wanted behaviour of BT as this allows to control the BT target temperature of BT via the TRV. So my question is, how does BT distiguish TRV target temperature changes, as the might be induced by BT itself, by the user on the TRV or even by the TRV itself due to some internal function? If the manual input via the TRV is not needed, maybe the BT childlock function helps to block any input from the TRV, independent if it is a manual or a TRV generated change? |
I have used the naked trv for 3 days and it has not deviated from what I set it to. I have today reintroduced a NEW BT wrapper trv, so we'll see if I see the odd behaviour again |
Actually I think that nothing should be able to change the BT Settings. At least there should be an option to prevent such behaviour. When I set BT to 20 degrees, it should stay at 20 degrees whatever happens. But it happens very often, that sudenly the BT is at 28 degrees or something like that.
In my special case, when I enable child lock, not even BT is able to change the TRV settings. But this is probably because of a problem with the TRV. |
|
Similar problems with BT and 1 of my Hive TRVs. My only workaround is an automation to set the TRV's setpoint to the thermostat's target temperature whenever the TRV's setpoint drops to 5C |
|
I have nearly he same issue with my Thermostat from Homematic. If the Thermostat is Idle, after a while it will be set to off. The main problem is than that i must set it to on and than i can set temperature (via Homeassistant) or if i set it to a temperature with my wallcontroll than it ignores the set temperature cause it was set to off. I just want to have it that OFF is disabled and it just leave at a temperature which i set it to |
|
I have got the same issue. The actual BT target temperature (19°C) remains constant and in order to reach it the TRV aims for a higher temperature (24°C). And for some reason BT defines the new BT target temperature to be the local/internal TRV target temperature. Version: 1.4.0 and 1.4.0-beta5.
|
|
I probably do have the same issue - heating is turned off randomly and completly and never gets activated again.
Version: 1.6.0 |
|
Nearly one year later still the same problem. I didn't even touch the thermostat "Heizung Balkonfenster". Actually, I wonder how it is possible that BT is being controlled by the real thermostats. For me, BT should control the physical thermostats. Only this way, never the other way. Why is there no way to disable this messy functionality? |
|
This post ist not only to keep this bug report alive: this morning it happened again, as it does nearly every day. What ever reason some people might have to be able to change BT status by manually changing anything at there physical TRVs: I dont't need this. |
|
Same. Happens every single day. Given the amount of issues on this project I don't think this will see any fix soon, so it's best to find alternatives for BT. |
|
im sad to hear about such a way to search for the next integration instead of trying to improve existing ones. |
|
The title of this issue says it: it is not, that BT is changing the settings of a TRV. The problem is, that a TRV is able to switch off BT. The message being shown then in the logs is: "BT Bathroom turned off triggered by state of TRV Bathroom changed to Heat". So BT was turned off by a TRV, not the other way. As I mentioned already a couple of times, I would like to have an option to prevent this kind of behavior. I really don't need the functionality that a TRV changes any of the BT settings which I made in Home Assistant. BT should always keep all settings. It should keep the target temperature, the on/off state and all other things which I configured using Home Assistant. |
|
The bug still hasn't been fixed. After opening and closing a window, BT turns off with a strange explanation. Of course the TRV changes to heat because the window was closed and BT enables both TRVs again. So far so good. However, the fact, that BT ist turning on the TRVs always results in BT turning off and so turning off the TRVs. That doesn't make sense at all! BT on -> both TRVs on -> opening Window -> BT turns off both TRVS -> closing Window -> BT turns TRVs on again -> because (at least one) TRV was turned on, BT turns off with the explanation below and so turns off both TRVs.
|
|
For the reason I just didn't want to create a new issue and that I thought that old issues won't be ignored, I just tried to keep this issue alive. However, I just realized this thread: #1568 Maybe this thread can be closed then? |
|
@code-chicken Do you also use the 5C instead of off option? If so, then yeah, your issue probably is #1195, like based on all the descriptions here I'm 95% certain this (switching BT to off on the next TRV status update) is just a side-effect of that issue. Would need at least the "debug log" from you/someone here, to make 100% sure this rly is the same problem though (see description in the first comment of #1568), before closing. Thanks for looking up stuff, I'm gradually trying to triage all the issues atm, but as you see it's a big backlog still. Sometimes issues sound very similar but might have different causes, so that's why I usually try to get logs from someone before closing an issue as duplicate. |
First thank you for answering! 👍 Yes, I am using 5C instead of off option. With my TRVs, "off" just means off. So not using any more battery-power 😆 but it doesn't mean closing the valves. Actually I didn't think this information would be important. Just tell me how I can produce the right logs for you and I will do so. |
Yeah, then it's probably a side effect of the known issue.
debug log |
|
Okay, here is the log from this morning. At 5:50, an automation switches on BT. This is not part of the log. At 07:44:12 I opened a window to let in some fresh air. In this room, BT is controlling two TRVs: Heizung_Schreibtisch and Heizung_Balkonfenster. Hope this helps. |
|
@code-chicken Yup, and then at the same time as you close the window BT went into off mode according to the logbook, or was that after? If so, then yes, thanks a lot, this can be closed as duplicate. |
|
@folfy Actually I am a bit confused now. In HA I got the message "BT Wohnzimmer turned off triggered by state of Heizung Schreibtisch changed to Heat" already at 07:54:38. So this already happened about a minute before I closed the window.
|
|
@code-chicken Thx, yeah, that also makes sense with my previous analysis in #1195 - When the status/temperature update from one of the associated TRVs is received, the control loop is running again, and that's actually when having 5°C set at the TRV automatically leads to BT switching to off mode. |
{ "home_assistant": { "installation_type": "Home Assistant Supervised", "version": "2023.12.4", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.11.6", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "6.5.6-arch2-1", "supervisor": "2023.12.0", "host_os": "Arch Linux", "docker_version": "24.0.6", "chassis": "vm", "run_as_root": true }, "custom_components": { "waste_collection_schedule": { "version": "1.44.0", "requirements": [ "icalendar", "recurring_ical_events", "icalevents", "bs4", "lxml" ] }, "battery_sim": { "version": "1.0", "requirements": [] }, "eufy_security": { "version": "8.0.0", "requirements": [ "websocket-client==1.4.2", "aiortsp==1.3.7" ] }, "google_home": { "version": "1.11.0", "requirements": [ "glocaltokens==0.7.0" ] }, "grad_vol": { "version": "1.0.0", "requirements": [] }, "google_fit": { "version": "v3.0.0", "requirements": [ "oauth2client==4.1.3", "google-api-python-client==2.82.0" ] }, "hacs": { "version": "1.33.0", "requirements": [ "aiogithubapi>=22.10.1" ] }, "epex_spot": { "version": "2.2.0", "requirements": [ "bs4" ] }, "better_thermostat": { "version": "1.4.0", "requirements": [] }, "asterisk": { "version": "1.0.3", "requirements": [ "asterisk-ami==0.1.6" ] }, "chime_tts": { "version": "v0.10.2", "requirements": [ "pydub" ] }, "blitzortung": { "version": "1.0.1", "requirements": [ "paho-mqtt>=1.5.0" ] }, "webrtc": { "version": "v3.5.0", "requirements": [] }, "alarmo": { "version": "v1.9.13", "requirements": [] }, "unifigateway": { "version": "0.3.3", "requirements": [ "pyunifi==2.21" ] }, "nordpool": { "version": "0.0.14", "requirements": [ "nordpool>=0.2", "backoff" ] } }, "integration_manifest": { "domain": "better_thermostat", "name": "Better Thermostat", "after_dependencies": [ "climate" ], "codeowners": [ "@kartoffeltoby" ], "config_flow": true, "dependencies": [ "climate", "recorder" ], "documentation": "https://github.com/KartoffelToby/better_thermostat", "iot_class": "local_push", "issue_tracker": "https://github.com/KartoffelToby/better_thermostat/issues", "requirements": [], "version": "1.4.0", "is_built_in": false }, "data": { "info": { "name": "BT Bathroom", "temperature_sensor": "sensor.gw1000a_v1_7_5_temperature_4", "off_temperature": 20, "tolerance": 0.0, "humidity_sensor": "sensor.gw1000a_v1_7_5_humidity_4", "outdoor_sensor": "sensor.gw1000a_v1_7_5_outdoor_temperature", "window_sensors": null, "weather": null, "cooler": null, "window_off_delay": 0, "window_off_delay_after": 0, "model": "TV02-Zigbee" }, "thermostat": { "climate.trv_bathroom": { "name": "TRV Bathroom", "state": "heat", "attributes": { "hvac_modes": [ "off", "heat" ], "min_temp": 5.0, "max_temp": 30.0, "target_temp_step": 0.5, "preset_modes": [ "none", "auto", "manual", "holiday" ], "current_temperature": 15.1, "temperature": 5.0, "preset_mode": "manual", "friendly_name": "TRV Bathroom", "supported_features": 17 }, "bt_config": { "calibration": "local_calibration_based", "calibration_mode": "heating_power_calibration", "protect_overheating": false, "no_off_system_mode": true, "heat_auto_swapped": false, "child_lock": true, "homaticip": false }, "bt_adapter": "mqtt", "bt_integration": "mqtt", "model": "TV02-Zigbee" } }, "external_temperature_sensor": { "entity_id": "sensor.gw1000a_v1_7_5_temperature_4", "state": "18.1", "attributes": { "state_class": "measurement", "unit_of_measurement": "\u00b0C", "device_class": "temperature", "friendly_name": "GW1000A_Pro Temperature 4" }, "last_changed": "2023-12-31T18:08:18.274426+00:00", "last_updated": "2023-12-31T18:08:18.274426+00:00", "context": { "id": "01HK0GZXV2MKVK5TKQ4S1WSV4M", "parent_id": null, "user_id": null } }, "window_sensor": "-" } }Description
Better Thermostat keeps turning off again and again. The reason is given by the message "BT Bathroom turned off triggered by state of TRV Bathroom changed to Heat"
Steps to Reproduce
Expected behavior:
Whatever the TRV is doing, Better Thermostat should stay in the state which has been set by the user.
Actual behavior:
In my case, after a few minutes (something between 10 and 30) it turns off. The reason is given by the message "BT Bathroom turned off triggered by state of TRV Bathroom changed to Heat"
Versions
BT Version: 1.4.0, HA Version: 2023.12.4
Additional Information
Seems to be similar to #1201 where the TRV changes to "Auto"
The text was updated successfully, but these errors were encountered: