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
Room Setpoint is 0 #46
Comments
Thank you for the report. It is indeed caused by #44, combined with the fact that the gateway apparently forwards |
This behavior is specific for Room Setpoint. From gateway.asm:
I agree that it should acknowledge the received value from the thermostat, however you cannot require that users upgrade to new (not yet exising) gateway firmware after updating a library, for functionality that used to work before. I think it is safe to always ignore 0 from both directions, since 0 also indicates no remote override is to be applied. Also, shouldn't any fix be duplicated to |
Thanks for the additional info. I wanted to be sure I understood the behavior before preparing a fix, and with this information I do. |
@PierreAronnax I have prepared a fix, but I am unable to test as my boiler supports the message ID. Would you be willing to help out with that? |
More than happy to help. I run Home Assistant on a Synology NAS in a Docker Container. Please tell me what to do. |
As long as you have access to the files in the container we should be able to test. |
I have updated both files and can confirm it is working for me with Home Assistant 2022.11.2 and firmware 5.5 :) Also, Schelte has released version 5.6 that has also fixed this problem (tested that this morning, downgraded and reproduced the issue first for this test) |
After updating Home Assistant to 2022.11.2 the Room Setpoint on the thermostat side is now 0
Likely due to #44
Log from Opentherm Monitor:
After updating at 11:00 (and downgrading again later).
The text was updated successfully, but these errors were encountered: