Open gmdfalk opened 2 months ago
I have the same Problem, haven't checked my thermostat and it shows unavailable even though it is available in Z2M. I checked the data and it failed at 9th of may, when I updated to 2024.5.0. As there where many changes in MQTT and since then every version corrected values in MQTT (same timings not working correctly) I haven't updated further more until they fix the MQTT timing.
Could that be correlated?
The firmware version of my Sonoff TRVZB is 1.1.5
You need to disable the weekly_schedule sensor for your TRV and it fixes the behaviour I've tried talking to both the z2m and homeassistant people and neither of them accept responsibility for fixing this
You need to disable the weekly_schedule sensor for your TRV and it fixes the behaviour I've tried talking to both the z2m and homeassistant people and neither of them accept responsibility for fixing this
I have disabled the weekly_schedule sensor, afterwards I fully restarted my HA computer. The thermostat is still unavailable. How can I make it available again? Disabling the sensor isn't enough it seems.
You need to disable the weekly_schedule sensor for your TRV and it fixes the behaviour I've tried talking to both the z2m and homeassistant people and neither of them accept responsibility for fixing this
I have the same problem. Where do I disable the weekly_schedule?
You need to disable the weekly_schedule sensor for your TRV and it fixes the behaviour I've tried talking to both the z2m and homeassistant people and neither of them accept responsibility for fixing this
I have the same problem. Where do I disable the weekly_schedule?
Settings => Integrations, etc. => Entities Search for weekly and you will find it.
You need to disable the weekly_schedule sensor for your TRV and it fixes the behaviour I've tried talking to both the z2m and homeassistant people and neither of them accept responsibility for fixing this
I have the same problem. Where do I disable the weekly_schedule?
But for me that didn't changed anything, I've even reconfigured BetterThermostat nothing changes. New start, whatever I do, the TRV stays unavailable in BT. In Z2M it is online and can be controlled without a problem. So I hope for you, that it helps in your case. On my system it didn't change anything.
You need to disable the weekly_schedule sensor for your TRV and it fixes the behaviour I've tried talking to both the z2m and homeassistant people and neither of them accept responsibility for fixing this
I have the same problem. Where do I disable the weekly_schedule?
Settings => Integrations, etc. => Entities Search for weekly and you will find it.
Well that's what I did before asking here and I couldn't find anything. Maybe my TRVs don't have it? I got the Bosch TRV II.
You need to disable the weekly_schedule sensor for your TRV and it fixes the behaviour I've tried talking to both the z2m and homeassistant people and neither of them accept responsibility for fixing this
I have the same problem. Where do I disable the weekly_schedule?
Settings => Integrations, etc. => Entities Search for weekly and you will find it.
Well that's what I did before asking here and I couldn't find anything. Maybe my TRVs don't have it? I got the Bosch TRV II.
I am having exact the same problems. Also with Bosch TRV 2.
So, today I played a bit with my Sonoff TRVZB. They are running firmware 1.1.5. BT is version 1.6.0.
Basically whatever you do in HA through BT is not reflected to the valves. And viceversa, if you change something on the valve, it reflects in the HA UI, but after a few seconds the valve goes to OF.
Disabling the Scheduler does not work to fix the issue. I do not see any way to log what is the issue.
The valve works ok through MQTT. Issues appear only when using BT controls.
Prerequisites
Sonoff TRZVB (https://www.zigbee2mqtt.io/devices/TRVZB.html#sonoff-trvzb), Firmare 1.1.5
Description
BT stopped working for me a few weeks ago. Around that time i updated BT to 1.5.1 and HA Core 2024.5.x. So either of those updates might have caused this. Downgrading to BT 1.5.0 works for me to restore functionality, although the error still appears. I've reset the
_local_temperature_calibration
entity to 0, no idea how they ended up with values out of range.These are the BT error logs i see in the system logs:
I also get the warning reporter here: https://github.com/KartoffelToby/better_thermostat/issues/1347
Versions
BT 1.5.1 Core 2024.5.4 Operating System 12.3