-
-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better Thermostat UI is not working after Core-Update #1275
Comments
I also have Problems after the recent Update to HA Core 2024.2. I have the following log entries after the update: 2024-02-08 08:57:43.601 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from better_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please create a bug report at https://github.com/KartoffelToby/better_thermostat/issues 2024-02-08 08:57:57.863 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.better_thermostat.climate.BetterThermostat'>) implements HVACMode(s): heat, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/KartoffelToby/better_thermostat/issues Maybe it can help |
Mit BT 1.5.0-beta5 funktioniert es jetzt zum Teil. |
Bei mir funktioniert alles wie gewohnt mit dem neusten Core Update. Ich habe die neuste Beta installiert 1.5.0 beta 5 Ich habe nur diesen "Bug" #1274 ist aber nicht wirklich ein Bug. |
isibizi , sind bei Dir gruppierte Thermostate? Bei mir funktionieren nur die gruppierten nicht. Hier ein Auszug aus dem Protokoll, die gruppierten sind erst gar nicht dabei: Logger: custom_components.better_thermostat.utils.controlling better_thermostat Heizung Flur: ERROR controlling: climate.heizung_im_flur |
Ja, habe im Wohnzimmer eine Gruppe, das funktioniert ohne Probleme. Mach mal ein Update auf die neuste Beta, da sind einige Bugs behoben worden. |
Ist schon BT 1.5.0-beta5.. |
Dann würde ich mal empfehlen BT vollständig zu löschen und mit der 1.5.0 alles neu zu konfigurieren. Mit der 1.4 hatte ich eine ganze menge probleme, vor allem mit dem gruppen thermostat, diese wurden beim update nicht behoben, erst als ich alles neu konfiguriert habe, funktionierte es wieder. |
Erledigt, keine Besserung.. |
I'm also affected unfortunately. It seems that Tuya integration is involved.
|
There changed alot again in version 2024.2 i looking for the issue |
Thank you super much! |
Vielen Dank! |
Same problem - upgraded HA to 2024.2 and Better Thermostat devices became unavailable. Am attaching a BT diagnostic log I made when attempting to reload the integration, in case that is useful.
|
Tuya Integration too.. |
Yes, the two TVRs and the temperature sensors I use with better thermostat are Tuya, running through the official Tuya integration (not HACS). That has always been fine with Better Thermostat before. But the Tuya integration itself has been unreliable for some people and was changed in 2024:2 so as to improve authentication with Tuya (it’s a cloud based integration). All the Tuya devices and entities in Home Assistant were unchanged. So I don’t see why Better Thermostat would be affected. But just in case, I deleted and recreated one of my Better Thermostat devices. But it was still unavailable. I wonder if the Tuya change is a coincidence. It might be helpful if others can report whether Better Thermostat is working for them in HA 2024:2 or not, and whether the TRV they are using is Tuya or not. |
I have two TRVs running in the same situation with the same errors described from RLB7777. |
I have 6 moes trvs via tuya all stop working on 2024.2. |
Hello again, |
Good day. I have a Sonoff temperature sensor (SNZB-02), have upgraded to 2024.2.1, and BT is working for me. In my installation if the Sonoff temperature sensor is offline BT will remain unavailable. Also, in my installation, once the Sonoff temperature sensor comes back online BT will become available. I do have Tuya devices, but they are not utilized in my BT setup.
|
Just an update on this. As a work around, I created some scenes in SmartLife to turn the TRV “on”and “off” depending on the temperature of separate Tuya sensor. I then noticed that Better Thermostat had started working again. Great… I also have a SmartLife scene that runs every night that sets all TRVs to “Auto” so if anyone fiddles with them manually, they reset overnight. I noticed this morning that as soon as the TRVs switched to “Auto”, Better Thermostat stopped working again. So it looks to me as if the problem is very specifically about the ability of Better Thermostat to see or control a Tuya TRV which is set to “Auto”. Obviously, there’s a simple workaround (don’t set the TRV to Auto!). I’ll need to experiment for a few more days to be sure this is the issue, but feedback from others would be helpful. |
Ich habe auch trotz Installation der Beta keinen Erfolg. BT läuft nicht. Auch ein komplettes Neu Installieren der Integration hat nicht geholfen. Ich würde ja die interne Thermostatintegration nutzen, jedoch kann ich hier keine Externen Temperatursensoren verwenden. |
Macht doch ein downgrade des Cores bis ein Update kommt. Ihr seid doch nicht gezwungen auf dem neusten Stand zu sein. |
Das habe ich bereits probiert, jedoch klappt das auch nicht. Ich bekomme BT gar nicht mehr ans Laufen. |
Isn't marking this bug closed a bit misleading? Users should have a clear alternative between : updating HA core and have to switch to a beta version of BT (thus unstable), or prefer staying on stable channel for BT (1.4.0 as for now) and refrain from updating HA core. |
Unfortunately, the issue still persist with me despite updating everything, including installing 1.5.0-beta7 of Better Thermostat. |
Same in my case |
Could you please re-open this issue? |
Hallo,
nach einem Update CORE 2024.2.0 sind die Better Thermostate nicht mehr verfügbar. Momentan ist BT 1.4.0 installiert.
Wie kann das Problem gelöst werden?
Vielen Dank!
The text was updated successfully, but these errors were encountered: