Qubino ZMNHBD showing very high temperature

Add-ons Bindings
1

I’ve connected a 1 wire temperature sensor to my Qubino ZMNHBD, but the temperature readings are way to high. (Somtimes over 200 degrees celsius) This is how I’ve configured the binding: { zwave=“22:command=sensor_multilevel,sensor_type=1” }

I’ve also enabled the zwave trace log, this is the output:

2016-08-29 21:22:23.296 [DEBUG] [eController$ZWaveReceiveThread:1530]- Receive Message = 01 0C 00 04 00 16 06 31 05 01 22 07 99 6E 
2016-08-29 21:22:23.315 [DEBUG] [o.b.z.i.protocol.SerialMessage:243 ]- Assembled message buffer = 01 0C 00 04 00 16 06 31 05 01 22 07 99 6E 
2016-08-29 21:22:23.317 [DEBUG] [b.z.i.protocol.ZWaveController:1195]- Process Message = 01 0C 00 04 00 16 06 31 05 01 22 07 99 6E 
2016-08-29 21:22:23.322 [DEBUG] [b.z.i.protocol.ZWaveController:194 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 16 06 31 05 01 22 07 99 
2016-08-29 21:22:23.324 [TRACE] [b.z.i.protocol.ZWaveController:215 ]- Incoming Message type = REQUEST
2016-08-29 21:22:23.326 [TRACE] [ApplicationCommandMessageClass:32  ]- Handle Message Application Command Request
2016-08-29 21:22:23.328 [DEBUG] [ApplicationCommandMessageClass:40  ]- NODE 22: Application Command Request (ALIVE:DONE)
2016-08-29 21:22:23.330 [DEBUG] [ApplicationCommandMessageClass:58  ]- NODE 22: Incoming command class SENSOR_MULTILEVEL
2016-08-29 21:22:23.332 [TRACE] [ApplicationCommandMessageClass:82  ]- NODE 22: Found Command Class SENSOR_MULTILEVEL, passing to handleApplicationCommandRequest
2016-08-29 21:22:23.334 [DEBUG] [veMultiLevelSensorCommandClass:95  ]- NODE 22: Received Sensor Multi Level Request
2016-08-29 21:22:23.336 [DEBUG] [veMultiLevelSensorCommandClass:130 ]- NODE 22: Sensor Multi Level REPORT received
2016-08-29 21:22:23.337 [DEBUG] [veMultiLevelSensorCommandClass:145 ]- NODE 22: Sensor Type = Temperature(1), Scale = 0
2016-08-29 21:22:23.340 [DEBUG] [veMultiLevelSensorCommandClass:154 ]- NODE 22: Sensor Value = 194.5

What could be the problem?

2

I guess the temperature probably should be 19.45 degrees? Does that sound correct?

I don’t see anything wrong with the code - according to the zwave doc I have, the packet is only providing 1 decimal place, so it’s coming in at 194.5 rather than 19.45. Now it’s possible that this is an updated version of the command class and there’s another bit hidden somewhere, but I think that’s unlikely as there are already 3 bits for precision.

So, based on this, I would say it’s a bug in the device.

I’ve just received some connectors so plan to add some temp sensors to my Qubino devices in the coming days - I’ll see what they show.

One question - is the value always around the 200C mark, or is it normally ok, but occasionally wrong?

3

I’ve got another DS18B20 1-wire temperature sensor (directly connected via cable) and this sensor is currently showing 25 degrees. The value from the z wave sensor is always very high. (over 180)

Edit: Regarding the device specs it sends a SENSOR_MULTILEVEL_V7 command.

4

I would suspect that the sensor is probably broken - if another sensor nearby is reading 25 deg, then it’s not just a scaling issue (which I don’t really think it is anyway). Do you have another sensor to try?

5

You can define an offset value with one parameter (according to the manual). I don’t think this could be the problem, but maybe you check if there isn’t some kind of “+160°” offset?

6

The offset parameter has a maximum of +/- 10 degrees and is set to the default value 32536. I’ve connected the temperature sensor to an ZMNHDD dimmer and there I get the right temperature, so the problem is the switch.

Is this maybe a firmware problem? My switch has the application version 1.2. (The dimmer has 1.1) Is there a way to downgrade or upgrade the firmware with OpenHAB?

7

No - there’s no support for firmware upgrades at the moment.

8

Is there any third party software to update the firmware? I only found firmware downloads and a tool for Aeotec devices.

9

I’m not personally aware of one…