-
Notifications
You must be signed in to change notification settings - Fork 6
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
HKT - convert temperatures at sub-zero temperatures #52
Comments
The temperatures are stored as binary and there seems to be an issue with negative numbers. Let me quote from another discussion on the openhab community: "_Here’s a clue - 4096 happens to be a magic number in binary = 0001000000000000 I’d be fairly confident that you can make your own correction here with something as simple as |
Please providde a debug log with sch a "wrong" value based oin v1.0.0 (https://forum.iobroker.net/topic/61351/livisi-innogy-smarthome-adapter-1-0-0-breaking) |
Why is a debug log needed? The solution is already in jhassler's contribution (if myvalue > 300 then myvalue = myvalue - 409.6_). I can confirm that, the values count down 0.2; 0.1; 0.0; 409.5 (-0.1); 409.4 (-0.2);... Could you remove this formula internally in the code? A Thanks very much! Greetings |
Honestly, because I say so. I'm the developer which currently tries to maintain this adapter without even having the hardware. So if you want my support, then please deliver what I ask for. Thank you. And because I'm nice I also tell you the reason: All information above do not contain a detailed information which state is affected, which Capability and which Channel and I will not start to guess. So I would not even know where to do any change. The debug log will show me which data come in in which field and when you then tell me what the actual valueof the timepoint of the log is, I can make changes based on the data I see. So in the end it is your decision. Decide what you want. |
Here is the interesting part of the debug log. Regards 2023-02-06 16:11:47.215 - debug: innogy-smarthome.0 (21455) state innogy-smarthome.0.Aussen.HT_Aussen.Temperatur-(Heizkörper)-1.Temperature changed: 0.9 (ack = true) |
If the temperature of the HKT goes into the minus range, then no negative values are displayed, but temperatures above 400 degrees. I believe that it is not a BUG in the adapter, but the innogy API really delivers these values. I had already seen this on a smartphone app (mySmarthome) and wrote it to the developer. It converts these values so that correct temperature values in the nagative range result from the incorrect values of the API. Is it possible to program this for this adapter too, so that the values are correctly displayed in the ioBroker?
The text was updated successfully, but these errors were encountered: