-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Wrong Uptime compressor pool #2109
Comments
we have expected a value of 0xFFFFFFFF for invaliid/not set value, but possible that Bosch uses 0xFFFFFF00. |
or we make a special case for DeviceValueType::TIME (which is now an unsigned 4-byte int) to mark it invalid if its > 0xFF000000 ? |
We have all UINT24, UIN32, and TIME stored as 32 bit uint value and check for all notset values. The times for ems (3byte) and ems+(4byte) are all marked as TIME. But ems+ 4byte values are in seconds (shows with DIV60), so a 24bit limit is too low (half a year). |
Tomorrow I´ll be back home and check |
Perfekt. The pool compressor time does not show up anymore in the list of entities. |
I close this now as it is 3.7.0-dev. 48 |
DESCRIPTION
Pool Compressor uptime is wrong. But this is not a problem of EMS-ESP.
I saw some problems in the issues/discussion around the interpretation of 4 byte values.
The information sent from the boiler is:
002+12:18:17.249 N 15: [emsesp] boiler(0x08) -W-> me(0x0B), UBAInformation(0x0495), data: 00 0E 59 CA 00 01 0A D6 00 0D 4E F4 FF FF FF 00 00 00 00 00 0
FF FF FF 00
calculates to those ~49000 days, see screenshot.Assuming it´s a signed 4 byte integer, it will calculate to -256 (two´s complement). This is also nonsens as an uptime can´t be negative in my opinion.
Maybe a solution is to show other than 0 only in case if the value of the signed 4 byte integer is positive?
Or if compressor pool starts is >0? Or if a PMxx is installed?
Or other ideas?
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
http://<IP>/api/system
TO REPRODUCE
n/a
EXPECTED BEHAVIOUR
Show something that is logical if the information sent from the boiler makes no sense.
SCREENSHOTS
ADDITIONAL CONTEXT
n/a
(Please remember to close the issue when it has been addressed)
The text was updated successfully, but these errors were encountered: