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
WPU 5G: Status values that are 0 and "float" (divide by 100) can be some small number instead of 0.
The correspoding statusvalue is 0x0000 datatype 0x92 (2 byte, divide by 100). 0000 is cast to float and divided by 100 and some floating point rounding error occurs.
Solution: round / limit floats to 2 decimal places. Other datatype 0x92 values are rounded to 2 decimal places.
(See screenshots)
Also in MQTT:
"CV pressure (Bar)":2.26,"Compressor current (A)":3.62,"Current e-element (A)":0.000489009,
Expected behaviour
0 is displayed as 0 or 0.00
Screenshots
Device information
Firmware version 2.4.4-beta6
Hardware revision non-cve 2
Type/model number Itho WPU 5G v37
This is a very minor issue. It's just my OCD. I might fix it sometime.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
![image](https://user-images.githubusercontent.com/6316468/212532078-7317e10f-d8a4-4ed7-90ee-5b635ba1f367.png)
Zero not zero:
WPU 5G: Status values that are 0 and "float" (divide by 100) can be some small number instead of 0.
The correspoding statusvalue is
0x0000
datatype0x92
(2 byte, divide by 100).0000
is cast to float and divided by 100 and some floating point rounding error occurs.Solution: round / limit floats to 2 decimal places. Other datatype
0x92
values are rounded to 2 decimal places.(See screenshots)
Also in MQTT:
Expected behaviour
0 is displayed as 0 or 0.00
Screenshots
![image](https://user-images.githubusercontent.com/6316468/212531892-b48b54bb-8a5f-40e1-9766-698c9e9e3685.png)
Device information
This is a very minor issue. It's just my OCD. I might fix it sometime.
The text was updated successfully, but these errors were encountered: