Novelan Heatpump Binding doesn't reply useful values for state, extended_state and massflow

Add-ons Bindings
21

1) Where in your configuration are the strings Wärmepumpe läuft and Heizbetrieb defined?

Never mind. I found it in code.

If the heatpump is returning a value of 2 in byte 118 and a value less than 0 in byte 95, you will get a 0 value:

        if (heatpumpValues[118] == 2) {
            long value = heatpumpValues[95];
            if (value < 0) {
                value = 0;
            }
22

Wow, thanks for taking your time analysing the code. Awesome.
What does that mean for my measurements? I really don’t know what byte 118 and byte 95 is. It is nearly impossible tha the massflow is 0.

23

That’s what the new binding I provided is supposed to help us determine. You need to install it and capture new logs.

24

Hi namraccr,

sorry for the huge delays. I got the house full of sick kids the last couple of weeks and no time for debugging. Tried it out now by uninstalling official heatpump binding and installing your .jar file. I switched on debug logging. openhablog attached. I couldn’t see any further details yet. openhab.log (11.1 KB)
Thanks in advance for looking into it.

25

and another one with log level set to TRACE:

openhab_trace.log (5.8 KB)

26

Excellent. In short, everything is working correctly for the values received.

Details… The value for Massflow comes from byte 155, for which your heatpump is reporting a value of 0.

The value for state comes from combining a state string with a time value.

The state string keys off of byte 117, for which your heatpump is reporting a value of 0, which translates to Wärmepumpe läuft.

The time value keys off of byte 120, for which your heatpump is reporting a value of 0, which translates to 00:00:00.

If you are getting different values for these attributes via the native Novelan system/software, it may be that you are using a version that is out of step with the expectations the binding is using (e.g. your Novelan is newer/older).

27

I have the same problem. I have a new alpha innotec heat pump and always get Heatpump running: 00:00:00

Here is my value set

Values read from heatpump: [1103102016] [1103102016] [0] [0] [0] [4] [1167609600] [1167609600] [0] [0] [319] [281] [282] [50] [622] [-15] [2] [543] [540] [30] [-500] [750] [0] [0] [0] [0] [0] [0] [0] [1] [0] [1] [0] [1] [0] [0] [0] [0] [0] [1] [0] [1] [0] [1] [1] [0] [0] [1] [0] [0] [0] [0] [0] [0] [0] [0] [5866607] [157] [0] [0] [191234] [59228] [0] [5866607] [5711184] [15409] [0] [6330] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [82] [1] [0] [86] [51] [46] [56] [51] [46] [49] [0] [0] [0] [170919223] [-256] [170919423] [170919169] [1541686882] [1541688564] [1541673766] [1541673741] [1537422680] [712] [796] [798] [799] [710] [5] [9] [9] [9] [9] [9] [1550049045] [1550101663] [1550127272] [1550186278] [1550233684] [0] [0] [0] [0] [0] [0] [0] [0] [1] [1] [0] [1] [0] [0] [0] [0] [0] [0] [1550269751] [1] [0] [0] [0] [0] [0] [4492] [0] [0] [3] [0] [0] [0] [0] [0] [0] [92943] [3181] [0] [96169] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [826] [1] [0] [21] [50] [75] [80] [1820] [570] [0] [351] [549] [0] [0] [0] [0] [320] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [0] [1932] [-54] [306] [0] [0] [1920] [0] [0] [0] [0] [0] [0] [0] [600] [0] [0] [0] [0] [244] [295] [62] [1030] [0] [826] [0] [6] [4819] [0]

28

HI All,

the same for me after a software update in my alpha innotec. Anyone able to fix that?

Br

Christian