You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the LG heat pump operates in auto (AI) mode there is the option to increase the target water temperature up to +5 degrees or decrease it up to -5 degrees,
so the correct display values should be from -5 to +5 with default 0,
as they are in the ThinkQ app (see screenshot from app)
But
In the control card of the integration, the values are wrong,
Scaling from +12 to +22 with default +17 instead of -5 to +5 with default the 0
The mechanism works thought, meaning if I change the value in the ThinkQ app from 0 to +1 then in the integration it changes from +17 to +18 (and vice-versa)
I am including the integration diagnostics from version 0.41.1
It would be fantastic to fix this, ruins the results of a very good integration
ps
this post may be considered as duplicate of post [](#819)
but in 819 there are confusing opinions, so it is a bit messy, and there are not any diagnostics
The text was updated successfully, but these errors were encountered:
When the LG heat pump operates in auto (AI) mode there is the option to increase the target water temperature up to +5 degrees or decrease it up to -5 degrees,
so the correct display values should be from -5 to +5 with default 0,
as they are in the ThinkQ app (see screenshot from app)
But
In the control card of the integration, the values are wrong,
Scaling from +12 to +22 with default +17 instead of -5 to +5 with default the 0
The mechanism works thought, meaning if I change the value in the ThinkQ app from 0 to +1 then in the integration it changes from +17 to +18 (and vice-versa)
I am including the integration diagnostics from version 0.41.1
It would be fantastic to fix this, ruins the results of a very good integration
Thank you
config_entry-smartthinq_sensors-01JGVS3F30B4FTSC56FCS2P26X.json
ps
this post may be considered as duplicate of post [](#819)
but in 819 there are confusing opinions, so it is a bit messy, and there are not any diagnostics
The text was updated successfully, but these errors were encountered: