external sensor reverts back after setting #31
Comments
IsaacBreuer
changed the title
|
see here my log from esphome that current temperature get randomly set to different what the set_remote_temperature did |
|
Try forcing the math to be floats all the way through the conversion process by using decimal numbers instead of integers:
I have to admit I got lazy and just switched my US-based install to "degrees of Communism" instead of "degrees of Freedom" to avoid a bunch of the artifacting issues with temperature conversions. Wife acceptance factor was diminished, but she got used to it eventually. |
|
unfortunately forcing the decimal point in the conversion did not resolve
the issue, and for me to change my house to Communists setting as a no no
for WAF.
…On Fri, May 28, 2021 at 11:39 AM Geoff Davis ***@***.***> wrote:
Try forcing the math to be floats all the way through the conversion
process by using decimal numbers instead of integers:
- lambda: 'id(hp).set_remote_temperature((x-32.0) * 5.0/9.0);'
I have to admit I got lazy and just switched my US-based install to "*degrees
of Communism*" instead of "*degrees of Freedom*" to avoid a bunch of the
artifacting issues with temperature conversions. Wife acceptance factor was
diminished, but she got used to it eventually.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNS2YV64WP7AIGLWOSCJZ3TP62MVANCNFSM45WKJIIQ>
.
|
|
Changing the system to C did not solve it for me either.
i have also tried the following , exposing a HA sensor that is rounded to
.5 C just to rule out rounding when my sensor actually show 20.70 , and
was not resolved
…On Fri, May 28, 2021 at 1:36 PM Isaac Breuer ***@***.***> wrote:
unfortunately forcing the decimal point in the conversion did not resolve
the issue, and for me to change my house to Communists setting as a no no
for WAF.
On Fri, May 28, 2021 at 11:39 AM Geoff Davis ***@***.***>
wrote:
> Try forcing the math to be floats all the way through the conversion
> process by using decimal numbers instead of integers:
>
> - lambda: 'id(hp).set_remote_temperature((x-32.0) * 5.0/9.0);'
>
> I have to admit I got lazy and just switched my US-based install to "*degrees
> of Communism*" instead of "*degrees of Freedom*" to avoid a bunch of the
> artifacting issues with temperature conversions. Wife acceptance factor was
> diminished, but she got used to it eventually.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#31 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABNS2YV64WP7AIGLWOSCJZ3TP62MVANCNFSM45WKJIIQ>
> .
>
|
IsaacBreuer
changed the title
|
This could possibly be something to do with your heat pump model. From upstream issues (e.g. SwiCago/HeatPump#69, SwiCago/HeatPump#144) it sounds like there are two methods used by different models to set the remote temperature, and who knows if that covers everything? Either way, the relevant code is at https://github.com/SwiCago/HeatPump/blob/master/src/HeatPump.cpp#L248 if that helps. |
|
The function gets through successfully, but then after like 30 seconds
reverts back , so I added a automation in HA to update a attribute for that
particular sensor every 25 seconds, so far this work, but is just a
workaround
…On Fri, May 28, 2021, 5:45 PM sijk ***@***.***> wrote:
This could possibly be something to do with your heat pump model. From
upstream issues (e.g. SwiCago/HeatPump#69
<SwiCago/HeatPump#69>, SwiCago/HeatPump#144
<SwiCago/HeatPump#144>) it sounds like there are
two methods used by different models to set the remote temperature, and who
knows if that covers everything? Either way, the relevant code is at
https://github.com/SwiCago/HeatPump/blob/master/src/HeatPump.cpp#L248 if
that helps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNS2YURERXCKSDF5O2JLCTTQAFJFANCNFSM45WKJIIQ>
.
|
Can you share the automation you used to update the sensor? My attempts aren't updating the whole sensor. I'm having the same issue with my MVZ air handler. Reverts to onboard temp sensor after ~3 minutes. EDIT: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I followed the new instructions to use external temperature sensor, works great, but i believe it extremely important to add to instructions that if you are using a HA sensor and your HA is set to use Fahrenheit as mine is, you have to convert the ha value before passing it to HeatPump
as
instead of
however, even after conversation, I still ha r some issue, the current temperature reported, keeps switching back and forth from external to builtin, I suspect that the rounding may cuase it to get value that set it back, I am now sure though
The text was updated successfully, but these errors were encountered: