BT devices not available after restarting HA #1322
Comments
|
I’ve got this too. Using BT with Tuya valves. Any restart of HA (update, power cycle etc) results in the BT instances becoming unavailable even though the Tuya valves still work within the Tuya integration. The workaround noted by @soeoeb works for me - I manually reconfigure each BT instance making a small change to the sensitivity threshold, and it comes back on line. Weirdly, reloading BT doesn’t help. It needs to be reconfigured and there needs to be an actual change to the configuration, however small. Nor does hitting configure and then saving without a change help. |
|
Facing the same issue, but not only on BT, also on versatile_thermostat. Probably something changed recently in climate or loading in core? |
|
Same Situation here with my two Tuya valves (SALCAR TRV801W). The Rademacher Valves are working. |
|
for me the same, also with BT Version 1.5.0 |
|
For me it's the same. I can solve the problem temporarily, if I reconfigure the component with a new value, e.g. increase "the outdoor temperature when the thermostat turns off" and it keeps available until the temperature sensor is unavailable for a short time or until a reboot. |
|
This could also be useful to look at. I kicked out all the window switches in the BT that where not working anymore. After this, they work again, just without the window detection. After the debugging, I hope I can switch them back ;-) #1333 |
|
i had too many problems with 1.5.0 also with 1.5.1
i went back to 1.4.0 , then recreated all devices => all problems gone |
|
I had the same problem with my Bosch BTH-RA thermostats. I saw that in Z2M under Details the system mode for my devices was not set. After I clicked on one of the available options, my devices were available again in BT. |
Thanks for the tip, that's exactly it, BT hasn't been working for days (since I noticed it). Now it works again. Nevertheless, I will test and set up the “Advanced Heating Control” blueprint soon. A BT has already failed one or two times, the first time it was due to an unavailable external sensor because there was no connection and now I think after the update to HA 24.5.x or a restart. |
|
for its not working like this, so thats maybe only a workaround for some devices! |
|
Workaround for my Tuya devices TRV SALCAR TRV801W)
Hardware Raspberry PI 4 I have inserted some lines of code to the module /homeassistant/custom_components/better_thermostat/utils/controlling.py after line 213. Now the Tuya TRV are active again even after a restart of HA. Background: The devices return an error when the HVAC mode is set to HEAT. Therefore, the workaround for this case is to set the HVAC mode to HEAT_COOL. |
|
@UweTo looks good. Is it possible to write down some of the code before and after your workaround! If i go to line 213, there is still the "_logger.debug" -line! So with some additional lines i have a better overview:) |
|
workaround with additional lines: |
|
Update of my workaround: The HVAC mode is now only changed for devices that are provided via the Tuya integration. The workaround is inserted after line 214. Works for me with 2 valves that are provided via the Tuya integration. The other of my valves are provided via the Rademacher integration and continue to work as before. |
I did exactly the same thing, back to 1.4.0 and after restarting everything works as before. |
|
I have the same issue, but think another root cause. After the restart of HA some BTs are not available, but some are working: The ZHA devices themselves are all fine. When I restart the BT component, it workes fine: In the log file I see this error (Click).Here is the full log: Let me know when you need more log out put to better understand the issue. |
|
Pls try the 1.7.0 Beta 1 |
|
I have The Same Problem. Also with 1.7.0 Beta 1. After restart ha all my Bt Thermostats From Tuya are Not available . |
With the beta right now they work stable (need to knock on wood). Sorry to reply back so late. I did not find this thread beside the others I am active in. What also helped to dramatically increase the stability of my zigbee network was to replace the USB 2.0 hub with a long USB 2.0 extension cable @lexi1970. After that fix only the reboot issue was left which seems to be solved in my case. |
|
hello they are Tuya thermostats without Zigbee. only my temperature sensors are zigbee2mqtt |
|
Hello, here #1322 (comment) I have described a workaround that works for my Tuya valves.
|
|
That would be nice if you could post the code |
Here is the code that must be in this directory: /homeassistant/custom_components/better_thermostat/model_fixes/WiFi Smart Thermostat.py WiFi Smart Thermostat is the name of the adapter model. You can find the name via Integrations->Tuya->Click on one of the Tuya thermostats. Then you will see this: On my test system Raspberry PI the name to use is “WiFi Smart Thermostat”, on my production system based on X64 it is “1q1grefcvygxzc7w”. The Quirks file on my Raspberry is therefore called WiFI Smart Thermostat.py, on my X64 system 1q1grefcvygxzc7w.py. |
|
Oh je. Das klingt kompliziert. oh dear, that sounds complicated |
|
Nö, ist einfach 😄.Bei Fragen gerne melden.Habe es auch mit Version 1.6.1 problemlos am laufen.Am 20.11.2024 um 17:24 schrieb lexi1970 ***@***.***>:
Oh je. Das klingt kompliziert.
oh dear, that sounds complicated
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Ich habe aufgehört den externen Wetterdienst zu verwenden, das macht auch immer wieder Probleme. Ich hätte das oben gestern nicht schreiben dürfen. Heute morgen war ein Fenstersensor im Schlafzimmer weg. Ergo Schlafzimmer kalt da TRV aus. Im gesamten Haus waren die Heizungen zu kalt obwohl BT lief. Der Offset Parameter in den TRVs war wieder extrem groß (-54), ich denke die TRVs können mit solchen Werten nicht umgehen. |
|
So viele deutsche hier. Klasse. Englisch ist immer ein Problem. Ich weiß nicht genau wo ich den Code einfügen soll. Oben gibts du einen anderen Pfad an als im Kommentar 1322 und auch wo genau im Code. |
|
Mode "heat_cool" on devices without mode "heat" is still not considered in v1.7.0b1, issues still open, will look into it |
|
Will be looking for an active tester for a proper fix (BT automatically falling back to heat_cool, if heat mode is not supported by the TRV) - Let me know if anyone is still following along and willing to help. Fix in PR #1533 available and waiting for testing/feedback (this is based on v1.7.0b1). |
Bugfix - Support devices only having mode heat_cool instead of heat (#1322)
folfy
added
bug
|
Should be fixed in v1.7.0b2 - Please test, and if not working, provide logs. diagnostic data debug log |
|
Should be working acc. to #1531 and didn't receive any further feedback indicating issues here, so closing this |
Model name of your Devices: ME167 Wireless Smart Radiator Thermostat (tuya)
Output from Home Assistant Developer Tools state e.g.:
State of climate.bt_test: unavailable
{ { "home_assistant": { "installation_type": "Home Assistant OS", "version": "2024.3.1", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.12.2", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "6.6.20-haos", "supervisor": "2024.03.0", "host_os": "Home Assistant OS 12.1", "docker_version": "24.0.7", "chassis": "embedded", "run_as_root": true }, "custom_components": { "better_thermostat": { "version": "1.4.0", "requirements": [] }, "hacs": { "version": "1.34.0", "requirements": [ "aiogithubapi>=22.10.1" ] }, "homee": { "version": "2.9.2", "requirements": [ "pymee==1.11.1", "websockets==11.0.1" ] }, "localtuya": { "version": "5.2.1", "requirements": [] }, "em6": { "version": "1.0.0", "requirements": [] } }, "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 Test", "temperature_sensor": "sensor.temperatursensor_1_temperatur", "off_temperature": 20, "humidity_sensor": "sensor.temperatursensor_1_luftfeuchtigkeit", "window_sensors": "binary_sensor.kontaktsensor_tur", "tolerance": 1.0, "outdoor_sensor": null, "weather": null, "cooler": null, "window_off_delay": 0, "window_off_delay_after": 1, "model": "p3dbf6qs" }, "thermostat": { "climate.seb_s_heizung": { "name": "Seb's Heizung", "state": "heat_cool", "attributes": { "hvac_modes": [ "off", "heat_cool", "heat_cool", "heat" ], "min_temp": 5.0, "max_temp": 35.0, "target_temp_step": 1.0, "preset_modes": [ "off" ], "current_temperature": 18.0, "temperature": 33.5, "preset_mode": null, "friendly_name": "Seb's Heizung", "supported_features": 17 }, "bt_config": { "calibration": "target_temp_based", "calibration_mode": "heating_power_calibration", "protect_overheating": false, "no_off_system_mode": true, "heat_auto_swapped": true, "child_lock": false, "homaticip": false }, "bt_adapter": "tuya", "bt_integration": "tuya", "model": "p3dbf6qs" } }, "external_temperature_sensor": { "entity_id": "sensor.temperatursensor_1_temperatur", "state": "18.6", "attributes": { "state_class": "measurement", "unit_of_measurement": "\u00b0C", "device_class": "temperature", "friendly_name": "Temperatursensor 1 Temperatur" }, "last_changed": "2024-03-21T13:45:00.793079+00:00", "last_updated": "2024-03-21T13:45:00.793079+00:00", "context": { "id": "01HSGM41KSNJF5JNS0Y9MAXW0K", "parent_id": null, "user_id": null } }, "window_sensor": { "entity_id": "binary_sensor.kontaktsensor_tur", "state": "off", "attributes": { "device_class": "door", "friendly_name": "Kontaktsensor 1 T\u00fcr" }, "last_changed": "2024-03-21T13:56:46.520191+00:00", "last_updated": "2024-03-21T13:56:46.520191+00:00", "context": { "id": "01HSGMSJSR8PECRZGTJR3ZPMFM", "parent_id": null, "user_id": null } } } } }Description
Every time I restart HA or reboot the system, my BT devices stop working (reporting "not available"). The real thermostats keep working just fine. After "making my devices stop working" I am getting a error message in HA system protocols:
In some cases I was able to "fix" the devices by reconfiguring the integration entry and changing values like tolerance on p. 1 or auto heat swap / alternative off mode on p. 2 of the config form, restarting HA and then repeat the reconfiguration process:
But most of the times, the only way to "fix" BT was to completely delete all integration entities, remove the HACCS integration, reinstalling BT and reconfiguring devices (restarting HA after every step). Why my workaround worked some time and why it didn't any other time is beyond me.
Steps to Reproduce
Expected behavior:
For my set up BT devices to remain available.
Actual behavior:
BT devices not responding.
Versions
HA versions:
Core: 2024.3.1
Supervisor: 2024.03.0
Operating System: 12.1
Frontend: 20240307.0
BT version:
Better Thermostat Firmware: 1.4.0
Additional Information
Don't know if that's of any help but this is the output of HA dev tools regarding the entity state when the entity is available:
State of climate.bt_test
When trying to investigate what's happening I stumbled upon two reoccurring errors in the HA protocol that happen when BT devices are working/available.
The text was updated successfully, but these errors were encountered: