Closed philrich closed 7 months ago
could you use the Telnet Console and 'call thermostat mode manual' with logging enabled so we can see any error messages and what Tx is being sent.
Something gone wrong when adding the changes for #1398. Please check if the fix from https://github.com/MichaelDvP/EMS-ESP32/releases/tag/latest works.
If not, please send the complete telegram 0x2B9 (read 10 2b9
in terminal or in web log all and wait for the telegram).
Something gone wrong when adding the changes for #1398. Please check if the fix from https://github.com/MichaelDvP/EMS-ESP32/releases/tag/latest works.
This seems to work. Manual mode is working again. Thanks.
I also noticed that I now have a entity select.thermostat_hc1_control which is set to RC310, but on the devices screen it says "RC200/CW100". I can select RC200 in the entity select box but it stays at RC310. It doesnt seem to have anything to do with this problem but looks incorrect.
Thanks for the feedback, i'll make a PR.
The control entitiy is to set the control to a external roomthermostat as remote control. Setting RC310 means "this thermostat" , the other settings different types of remote. I think the RC200 can not act as master for remotes. You can use the customization to remove the unused setting.
PROBLEM DESCRIPTION
After Firmware Update from 3.6.2 to 3.6.3 th climate.hc1 Entity in Homeassistant went to Unavailable state (it was set to manual heating before). In MQTTExplorer there was no
hc1.mode
inthermostat_data
). After switching to auto mode on the thermostat the climate entity appeared in homeassistant (andhc1.mode
inthermostat_data
). But it is not possible to switch to manual mode anymore. If i try to switch to manual mode (heat) it goes to off. I also tried to switch on manual mode via telnet but same problem.REQUESTED INFORMATION
TO REPRODUCE
Update Firmware from Version 3.6.2 to 3.6.3.
EXPECTED BEHAVIOUR
Switching thermostat to manual should be possible. If thermostat is already in manual mode, climate entity should not be unavailable.
ADDITIONAL CONTEXT
Downgrading to 3.6.2 fixes the behavior.