Closed Soukyuu closed 1 year ago
I got it "unstuck" by switching to Offset-based calibration, then back to Temperature-based.
I have the same problem.
Same here.
What is the heating_power value if you check on the developer_tools / states?
The values are different on all TRVs. Here are the values:
climate.wohnzimmer (faulty): 0.01 climate.kueche (faulty): 0.0098 climate.badezimmer (faulty): 0.0052
climate.flur (works): 0.0047 climate.buro (works): 0.0087
Okay, they look fine. Then we need some debug logs, otherwise it's hard to guess what's happening.
No problem. What type of logs do you need? How would I produce a log which contains only the necessary information?
Update: Tested activating night mode at 14:00 and the logs show this: 2023-02-08 14:00:00.946 ERROR (MainThread) [homeassistant.components.mqtt.climate] Invalid modes mode: auto
I'm confused. This is the integrations's config:
i have the same issue. I think it is because the TRV has no Auto mode ... my log shows me following message for all of my TRV:
TS0601 von _TZE200_hue3yfsn
2023-02-11 11:41:45.208 WARNING (MainThread) [homeassistant.components.zha.entity] climate.thermostat_badezimmer_zonnsmartthermostat: can't set 'auto' mode. Supported modes are: [<HVACMode.OFF: 'off'>, <HVACMode.HEAT: 'heat'>]
maybe the source code or something else must be adjusted to the specific mode of this TRV, that only hast OFF and HEAT and no AUTO mode
Think this is related to the main issues with TS0601, pls search for TS0601 in the issues
I'm not sure which issues you mean, but it seems that it's BT having a problem reading the local_temperature_offset of some thermostats. It displays fine in HA and zigbee2mqtt, but in bt logs it complains about a float value for int.
It only breaks when using the night time template or rather the set target temp service.
I now have a workaround automation which sets all local_temperature_offsets to 0 after night time schedule ends and so far, no more stuck thermostats.
I am still struggling with this issue. My Netatmo Thermostats often stay stuck at 7°C (off setting) after the night ends or when I return to the house. Both automations trigger the comfort temperature, but not every Netatmo thermostat reacts and switches to heating. The BT command works without issues.
With the Netatmo Thermostats the only option is "Target Temperature Based" not offset.
I have already tried a secondary automation that just activates heating mode or higher temperature on the Netatmo thermostats and then lets BT do the rest, but this doesnt seem to solve the issue.
Any idea what Automation I could use to unfreeze/activate the Thermostats so BT can engage heating everytime and not in like 60% of all occasions?
Prerequisites
Model of the device: SEA801-Zigbee/SEA802-Zigbee
Description
I have an automation that sets the night mode temperature to 18°C from 22:00 to 6:30. Occasionally the temperature gets stuck at the night temperature according to the TRV (16°C). the BT entry shows the correct daytime temperature (20°C) and no matter what I do on the BT side, the tempertature on the real TRV does not change. I attempted to activate diagnostic logs but can't find any better_thermostat entries beyond the message that the component has been loaded. Reloading the integration does nothing.
Steps to Reproduce
Expected behavior:
The temperature being restored and TRV heating the room
Actual behavior:
Sometimes the BT entity seems to be stuck at night temperature despite GUI showing day temperature
Versions
HA 2023.1.7, BT 1.0.0
Additional Information
The only way to get it working again is to recreate the BT integration instance.Does not seem to work, still stuck at 16°C despite re-creating.Here are the real and BT TRV entities and their history for the past 24h:
![image](https://user-images.githubusercontent.com/2095054/216288030-7e195910-5301-40ec-97ec-553d41f39001.png)