Qubino Flush 2 relays ZMNHBD incorrect kWh values

Hi

I have two Qubino Flush 2 relays, and both report wrong kWh values (the values are clearly too high, e.g. one switch reports 50 kWh after one week on an output with no load…).

Does anybody else have that issue?

I tried reading the values with Domoticz and Home Assistant, and all show the same but wrong values.

Well, I have similar problem - both channels show -214748364.8 which is the minimum value for 32-bit integer, so definitely wrong value. I haven’t dig into this yet, but I am going to look into this issue soon.

Most likely this is an issue with the device, not with OH, the binding or the configuration. The first thing to check will be what values are reported by the device.

Thanks! In my case the values are positive and are increasing - just way too fast. Where can I see the values that are reported by the device? Is it possible to see the data sent by the device?

Googling reveals users of other host systems griping about kWh values from these devices as well. Seems to be a device firmware deficiency.

Change logging level to DEBUG for this binding and you’ll see all the commands with responses in the log.

Would you mind pointing me to these discussions?

Does anybody know how I can see the raw data sent from the relays? That would help in the discussions with the Qubino team.

That would be really bad if it was a firmware issue. It is not possible to update the firmware and the devices need to be sent to Qubino…

i have 16 qubino din dimmers

i also see non plausible kwh values… did not dig into it yet

also on watt reporting there are single spikes that report eg 40.000 watts for one second just to switch back to some normal value like 20 watts. those bogus messages however kill my grafana charts and i need to filter to 95 percentile

Really? Okay …
https://www.domoticz.com/forum/viewtopic.php?t=22928

https://groups.google.com/forum/#!topic/openzwave/fp9CPwFHQq8

indeed after checking the values in grafana I see clearly wrong values in kwh

the chart 1 shows a low watt light source with about 5 watts for 2 weeks
chart 2 shows a that kwh raises by approx 10kwh in 2 weeks which is totally unplausible

seems almost like it could by wrong by factor 10 …
edit: after checking all 16 dimmers I would guess that factor 10 seems plausible
maybe the device reports kwh differently than zwave standard and therfore the binding interprets this this way?

Below is the log (it is actually much longer but from what I can tell with my limited knowledge of z-wave it is the relevant part:

2019-02-04 21:26:39.461 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message     = 01 18 00 04 00 09 12 60 0D 02 01 32 02 21 24 00 00 07 09 00 01 00 00 07 09 A2
2019-02-04 21:26:39.468 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 12 60 0D 02 01 32 02 21 24 00 00 07 09 00 01 00 00 07 09
2019-02-04 21:26:39.472 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 12 60 0D 02 01 32 02 21 24 00 00 07 09 00 01 00 00 07 09
2019-02-04 21:26:39.474 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-02-04 21:26:39.476 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Application Command Request (ALIVE:DONE)
2019-02-04 21:26:39.478 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false
2019-02-04 21:26:39.480 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-02-04 21:26:39.482 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Incoming command class COMMAND_CLASS_METER, endpoint 2
2019-02-04 21:26:39.484 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: SECURITY not supported
2019-02-04 21:26:39.486 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 9: Received COMMAND_CLASS_METER V3 METER_REPORT
2019-02-04 21:26:39.489 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 9: Meter: Type=Electric(1), Scale=kWh(0), Value=180.1
2019-02-04 21:26:39.491 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveMeterValueEvent
2019-02-04 21:26:39.493 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 2, command class = COMMAND_CLASS_METER, value = 180.1
2019-02-04 21:26:39.497 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:6bd38490:node9:meter_kwh2 to 180.1 [DecimalType]
2019-02-04 21:26:39.501 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Commands processed 1.
2019-02-04 21:26:39.504 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@b0d28a.
2019-02-04 21:26:39.508 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@b0d28a.
2019-02-04 21:26:39.511 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: notifyTransactionResponse TID:201 DONE
2019-02-04 21:26:39.514 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-02-04 21:26:39.517 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2019-02-04 21:26:39.520 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-02-04 21:26:39.523 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-02-04 21:26:39.525 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-02-04 21:26:44.592 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 09 07 60 0D 01 00 25 03 00 B2
2019-02-04 21:26:44.597 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 07 60 0D 01 00 25 03 00
2019-02-04 21:26:44.600 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=9, callback=0, payload=00 09 07 60 0D 01 00 25 03 00
2019-02-04 21:26:44.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-02-04 21:26:44.603 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Application Command Request (ALIVE:DONE)
2019-02-04 21:26:44.605 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: resetResendCount initComplete=true isDead=false
2019-02-04 21:26:44.607 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2019-02-04 21:26:44.609 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 1
2019-02-04 21:26:44.610 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 9: SECURITY not supported
2019-02-04 21:26:44.612 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 9: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2019-02-04 21:26:44.614 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 9: Switch Binary report, value = 0
2019-02-04 21:26:44.616 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2019-02-04 21:26:44.618 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_SWITCH_BINARY, value = 0
2019-02-04 21:26:44.621 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:6bd38490:node9:switch_binary1 to OFF [OnOffType]
2019-02-04 21:26:44.627 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Commands processed 1.
2019-02-04 21:26:44.632 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 9: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@c8d0a0.
2019-02-04 21:26:44.634 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

I assume that
payload=00 09 12 60 0D 02 01 32 02 21 24 00 00 07 09 00 01 00 00 07 09
is the actual message? Does anybody know the format and how to extract the value?

@rossko57: thanks for the link. It is about low wattages though. This does not apply in my case, I have all kinds of loads. One of it is a 240W lamp and on one relay one output is not connected. But maybe the author of the thread is wrong and it is not linked to low wattage loads and it is a general issue.

The idea with the graphis good. I’ll try to create one too.

Three links.

Thanks.

Below is a graph that clearly shows that something is wrong. The kWh counter increases even if the lamp is off and not consuming any power.

Is Openhab reporting the correct value/parameter and is this a device issue?

I was about to buy one of these but I think ill wait! given the power metering issues.

The Qubino support mentioned that there is a new firmware that supposedly fixes the issue. I could send the devices to them for the update. That is a lot of effort though, they are mounted in the wall…

Same problem here with zmnhbd. Could you Fix it with the new firmware?

It is better now. I doubt that it is very accurate, but it is cerainly better.

1 Like

Thank you, better is good. So you know the new firmware version? Mine is 5.0.

zwave_version 5.1

That is what it shows. I assume this is the version?