Not getting temperature from ZMNHAD / ZMNHEA1 (qubino)

@sihui Thanks for the information.

Is that a recent change? Could it have been updated some time after I had originally included the devices?

Rather than excluding and including the devices on the Z-Wave network, would deleting the relevant Things and re-discovering them be adequate?

UPDATE: I’ve just taken a look at the database entry for ZMNHDD on Chris’ site. As far as I can tell there is no SENSOR_MULTILEVEL capability for Endpoint 2 (only for Endpoint 0).

Acccording to the docs it should be endpoint 4:

End point 4:
Group 1: Lifeline group, 0 nodes allowed.
Group 2: multilevel sensor report (triggered at change of
temperature sensor) up to 16 nodes

As I don’t have this device and can’t test it I am not able to make the database changes, sorry.

The change was accepted (however, it is already declarded as deprecated which I don’t understand).
I just deleted the thing and added it again. However, there is still no change in the thing. It doesn’t seem to use the latest thing configuration from the database. Does somebody know what I missed?

Have a look here: https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide
You register for an account, make the change and request the approval. That’s pretty much it :slight_smile:

During your last database change you’ve added/edited the sensor_mulitlevel channel for endpoint 0.
Is that really what you want?

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/210

Not quite. It took me a little while to work out what’s up here. I think the sensor_temperature channel in endpoint 0 was always there.

No channels were added - but a new command class has been added to endpoint 1, and in the config for that command class the channel has been added (Which won’t do anything).

I’ll remove this as it’s presumably wrong?

@sihui
I added it to Endpoint 2 in the editor. Not sure why it appears to be a change on Endpoint 0. That wasn’t my intention. It wasn’t clear what I needed to add to the ‘Configuration’ field though.

As above - you added a new command class (not channel) to endpoint 1 as seen below -:

This is not the same as adding a channel and will not do anything. I think it’s wrong, and we should delete this and add the command class AND the channel to endpoint 2.

@chris
Yes that was what I was trying to do. Did I need to add the Command Class and then add some XML in the ‘Configuration’ field?

There’s no XML required. You add the command class, then inside that in the main screen is another + button that allows you to add a channel.

Please check that you’re adding to endpoint 2 - not the second endpoint (which is endpoint 1 since endpoints are numbered from 0). My guess is that you went to the second endpoint and added the class there, missing the fact that this is actually number 1.

1 Like

@chris
This is what I’m seeing in my log:

2020-01-25 11:51:18.586 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 2

2020-01-25 11:51:18.587 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: SECURITY not supported

2020-01-25 11:51:18.589 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 29: Received COMMAND_CLASS_SENSOR_MULTILEVEL V7 SENSOR_MULTILEVEL_REPORT

2020-01-25 11:51:18.591 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 29: Sensor Type = Temperature(1), Scale = 0

2020-01-25 11:51:18.593 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 29: Sensor Value = 25.3

2020-01-25 11:51:18.595 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 29: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2020-01-25 11:51:18.597 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 29: Got a value event from Z-Wave network, endpoint=2, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=25.3

2020-01-25 11:51:18.600 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 29: Commands processed 1.

2020-01-25 11:51:18.602 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 29: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@101e6cd.

2020-01-25 11:51:22.603 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 29: Application Command Request (ALIVE:DONE)

2020-01-25 11:51:22.605 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: resetResendCount initComplete=true isDead=false

2020-01-25 11:51:22.607 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: Decapsulating COMMAND_CLASS_MULTI_CHANNEL

2020-01-25 11:51:22.610 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 2

2020-01-25 11:51:22.617 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: SECURITY not supported

2020-01-25 11:51:22.619 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 29: Received COMMAND_CLASS_SENSOR_MULTILEVEL V7 SENSOR_MULTILEVEL_REPORT

2020-01-25 11:51:22.620 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 29: Sensor Type = Temperature(1), Scale = 0

2020-01-25 11:51:22.621 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 29: Sensor Value = 25.8

2020-01-25 11:51:22.623 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 29: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2020-01-25 11:51:22.625 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 29: Got a value event from Z-Wave network, endpoint=2, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=25.8

2020-01-25 11:51:22.627 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 29: Commands processed 1.

2020-01-25 11:51:22.628 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 29: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@b1ce4e.

The report comes in on endpoint=2.
Are you saying that is Endpoint 1 as far as the database is concerned?

No - I’m saying that it’s endpoint 2 in the database, but you added the CC to endpoint 1. My point is there is also an endpoint 0, so if you didn’t check the numbering, and just counted to the second endpoint, then this is endpoint 1 - not 2.




@chris
If I added it to Endpoint 1 that was a typo - my apologies. Yes, I was aware that the numbering started at 0.

@chris
I also need to make a similar change for a Qubino ZMNHND device.
This sends unsolicited temperature reports on Endpoint 1 though (rather than Endpoint 2), for which there isn’t an entry for in the database.

2020-01-25 12:09:15.115 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 1

2020-01-25 12:09:15.116 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: SECURITY not supported

2020-01-25 12:09:15.118 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 32: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT

2020-01-25 12:09:15.119 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Type = Temperature(1), Scale = 0

2020-01-25 12:09:15.120 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Value = 24.9

2020-01-25 12:09:15.121 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2020-01-25 12:09:15.124 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got a value event from Z-Wave network, endpoint=1, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=24.9

2020-01-25 12:09:15.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Commands processed 1.

2020-01-25 12:09:15.128 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@632530.

2020-01-25 12:09:19.119 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Application Command Request (ALIVE:DONE)

2020-01-25 12:09:19.120 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: resetResendCount initComplete=true isDead=false

2020-01-25 12:09:19.122 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: Decapsulating COMMAND_CLASS_MULTI_CHANNEL

2020-01-25 12:09:19.123 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 1

2020-01-25 12:09:19.125 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: SECURITY not supported

2020-01-25 12:09:19.127 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 32: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT

2020-01-25 12:09:19.128 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Type = Temperature(1), Scale = 0

2020-01-25 12:09:19.130 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Value = 24.4

2020-01-25 12:09:19.131 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2020-01-25 12:09:19.132 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got a value event from Z-Wave network, endpoint=1, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=24.4

2020-01-25 12:09:19.133 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Commands processed 1.

2020-01-25 12:09:19.135 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1a3871b.

I will make that change now.

@chris
I added the temperature sensor to endpoint 1.

I wasn’t sure whether to add it as a V0 or V7. Strangely, not only do polled reports come in on a different endpoint to unsolicited reports, they are also marked as a different version; see below:

Polled report (V7, endpoint 0)

2020-01-25 12:46:11.593 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 32: Received COMMAND_CLASS_SENSOR_MULTILEVEL V7 SENSOR_MULTILEVEL_REPORT

2020-01-25 12:46:11.594 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Type = Temperature(1), Scale = 0

2020-01-25 12:46:11.595 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Value = 22.1

2020-01-25 12:46:11.597 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2020-01-25 12:46:11.598 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=22.1

2020-01-25 12:46:11.599 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Updating channel state zwave:device:1139f694:node32:sensor_temperature to 22.1 °C [QuantityType]

2020-01-25 12:46:11.607 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Commands processed 1.

2020-01-25 12:46:11.609 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@58eb8.

2020-01-25 12:46:11.611 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@58eb8.

2020-01-25 12:46:11.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: notifyTransactionResponse TID:2560 DONE

2020-01-25 12:46:11.618 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

Unsolicited report (V0, endpoint 1):

2020-01-25 12:47:42.351 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 1

2020-01-25 12:47:42.352 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 32: SECURITY not supported

2020-01-25 12:47:42.354 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 32: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT

2020-01-25 12:47:42.355 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Type = Temperature(1), Scale = 0

2020-01-25 12:47:42.356 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 32: Sensor Value = 23.5

2020-01-25 12:47:42.357 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2020-01-25 12:47:42.359 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Got a value event from Z-Wave network, endpoint=1, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=23.5

2020-01-25 12:47:42.360 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Commands processed 1.

2020-01-25 12:47:42.361 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 32: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1ed306e.

This is just due to the way the database is configured. If you add a new channel, then this will stop (so long as you use this channel).

That’s just an issue with binding logging.

Initial database contribution a year ago for endpoint one was v7, so I left it in for endpoint two.

1 Like

@sihui
Thanks for making the changes. I wasn’t sure what the next step is for me to test this. Chris indicated in his post (below) that I would only need to delete the Thing and re-discover it. I’ve done this but the unsolicited temperature updates from endpoint 2 are not getting updated in the linked Item still.

Should there now be another temperature channel for me to link to, or does ‘sensor_temperature’ effectively now get shared by both endpoints 0 and 2?
Or am I being too hasty - does the database need to build first? Still working out the mechanics of all this!

No ‘Updating channel’ message in the log

2020-01-25 15:40:09.187 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 2

2020-01-25 15:40:09.189 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 29: SECURITY not supported

2020-01-25 15:40:09.191 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 29: Received COMMAND_CLASS_SENSOR_MULTILEVEL V7 SENSOR_MULTILEVEL_REPORT

2020-01-25 15:40:09.192 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 29: Sensor Type = Temperature(1), Scale = 0

2020-01-25 15:40:09.195 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 29: Sensor Value = 24.9

2020-01-25 15:40:09.197 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 29: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2020-01-25 15:40:09.199 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 29: Got a value event from Z-Wave network, endpoint=2, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=24.9

2020-01-25 15:40:09.201 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 29: Commands processed 1.

2020-01-25 15:40:09.203 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 29: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@115471c.

Yes, but you don’t needed to exclude it. All this does is ensures that OH reads the new database.

The binding has not been updated - I will do this tonight, and if you update your system tomorrow it should then have the updated definitions.

Exactly :+1:

I’m currently running the stabil version of OH (2.5.1) with the 2.5.1 z-wave binding. Do I have to switch the whole OH to snapshot-version in order to “update the system”? :-/