better_thermostat
better_thermostat copied to clipboard
Problem: Beter Thermostat "Not available"
Hello, I have the problem that after the setup I have thermostats at different intervals, thermostats that are displayed as not accessible. Although I have set them up correctly and they are working. The original thermostat is accessible, but the Better thermostat is not.
I believe thats the same issue as mine here: #1299
I believe thats the same issue as mine here: #1299
Yes, you're right. At least that's how it looks. For me, it's such a change, from being reachable and then not reachable again.
Same Here.
I've had the same problem for 2 days, at first everything was running normally and suddenly 2 heating controllers are no longer recognized. Does anyone already have a solution?
I have the same problem. After upgrading to HA 2024.3.0 BT unavailable. :(
2024-03-07 15:28:54.948 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 2024-03-07 15:28:54.979 DEBUG (MainThread) [custom_components.better_thermostat.utils.bridge] better_thermostat TRV Bedroom: uses adapter mqtt for trv climate.sonoff_trv_bedroom 2024-03-07 15:28:54.997 INFO (MainThread) [custom_components.better_thermostat.climate] better_thermostat TRV Bedroom: Waiting for entity to be ready... 2024-03-07 15:28:54.999 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'hvac_action' when rendering '{{states.climate.trv_bedroom.attributes.hvac_action}}' 2024-03-07 15:28:55.000 INFO (MainThread) [custom_components.better_thermostat.climate] better_thermostat TRV Bedroom: Starting version 1.4.0. Waiting for entity to be ready... 2024-03-07 15:28:55.000 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/config/custom_components/better_thermostat/climate.py", line 563, in startup if self.hass.states.get(self.weather_entity).state in ( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'state' 2024-03-07 15:28:55.056 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'hvac_action' when rendering '{{states.climate.trv_bedroom.attributes.hvac_action}}'
Do you have a solution or how do you deal with this? Because as long as Better is unavailable, the rooms remain cold.
My only solution is to adjust the TRV entity itself, so the rooms are unautomated like before home automation. It's freezing cold here at night. Can we rollback the home assistant core or use the 1.5 beta for compatibility?
If you recreating the BT objects with the same name resolves the problem. It works for me.
I think I've got the same problem. Better Thermostat became unavailable whereas the climate heating entity is well functional.
I try to remove and recreate a better thermostat entity but without getting a functional one...
Ich hatte
Habt ihr eine Lösung oder wie geht ihr damit um? Denn solange Better nicht verfügbar ist, bleiben die Räume kalt.
Hatte genau das gleiche Problem. Habe nun auf Version 1.4.0 umgestellt, jetzt geht alles wieder. Mit der Beta-Version habe ich einen Raum nicht mehr hinbekommen, weder mit Neueinrichten, noch mit anderem Namen oder anderen Geräten.
Viele Glück
stromas
I have the same problem right now. I am moving my old RaspPi HA to a microPC and cannot take the entire heating system with me because the devices show exactly this error "not available". Completely fresh system with BT 1.4.0, HA Core 2024.2.5 and HA OS 11.5
Sorun devam ediyor ayrıca güneş simgesi neden aktif oldu değiştirme nasıl oluyor
Is there any solution for this? I have exactly the same issue...