-
Notifications
You must be signed in to change notification settings - Fork 25
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
[custom_components.aquarea.climate] [HEAT] Target temperature is not within expected range, this is suspicious #240
Comments
Hello, thanks for the report. Could you update to version 1.12.4 of this integration and report the log line again please? |
New Message: My Temperatures 26 °C low and 35 °C high are between in your Range 20…55 🤷♂️ |
Could you look at the mqtt topic |
Compensation curve, always will be -5+5 range |
Morning, another Message: Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht Logger: custom_components.aquarea.climate [HEAT] Target temperature is not within expected range, this is suspicious. 5.0 should be within [-5,5] Z1_Heat_Request_Temp is Zero, see screenprint before. |
I think ‘ZoneTemperatureMode’ Direct and Compensation should be swapped, right? if mode == ZoneTemperatureMode.COMPENSATION: |
Thanks for the details.
I'm a bit confused by several items:
Overall, I'm not sure I understand what happens but it seems the integration code thinks you are using direct mode (that would explain the first warnings you reported) and later thinks you are using compensation mode (which is true).
I'll try two things to improve the situation
|
yes, its right, the first Message [20/55] comes at the beginning. Later Message [-5/5]. I believe DIRECT and COMPENSATION are mixed up in your programme code? „your screenshot shows a target temp of 0 for Z1 (which means a shift of 0) but the warning shows 5. Are you trying to set the shift to +5 ?“
|
Thanks for the precision about Z2. I'm not sure to understand why direct and compensation would be mixed up. |
Before this patch, HA used to forgot temperature mode, sensor mode and other rarely changing parameters. It required a complicated dance at the start-up of the integration until we received the first MQTT messages giving us those values (especially to get the temperature boundaries). Now we simply store them locally and assume they haven't changed while HA was down. It should really help with #240
Version 1.13.0 should be better and should not display any warning anymore. Could you test it and let me know if you encounter any issue? |
No more Messages 👍. Thanks for your Work. |
1.41
I dont know is a Bug. I constantly get this message:
[custom_components.aquarea.climate] [HEAT] Target temperature is not within expected range, this is suspicious
Why?
The text was updated successfully, but these errors were encountered: