Zwave Thing configuration with snapshot 1361

            <commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
            <COMMAND__CLASS__CONFIGURATION>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <configParameters>
                <entry>
                  <int>1</int>
                  <configurationParameter>
                    <index>1</index>
                    <size>1</size>
                    <value>0</value>
                    <readOnly>false</readOnly>
                    <writeOnly>false</writeOnly>
                  </configurationParameter>
                </entry>
                <entry>
                  <int>2</int>
                  <configurationParameter>
                    <index>2</index>
                    <size>2</size>
                    <value>0</value>
                    <readOnly>false</readOnly>
                    <writeOnly>false</writeOnly>
                  </configurationParameter>
                </entry>
                <entry>
                  <int>3</int>
                  <configurationParameter>
                    <index>3</index>
                    <size>1</size>
                    <value>1</value>
                    <readOnly>false</readOnly>
                    <writeOnly>false</writeOnly>
                  </configurationParameter>
                </entry>
                <entry>
                  <int>4</int>
                  <configurationParameter>
                    <index>4</index>
                    <size>1</size>
                    <value>1</value>
                    <readOnly>false</readOnly>
                    <writeOnly>false</writeOnly>
                  </configurationParameter>
                </entry>
              </configParameters>

Sorry, but please can you say what is this trying to show, and what is it a copy of exactly?

This is a section of: /srv/openhab2-userdata/zwave/network_d57e8418__node_2.xml

Node 2 being the NZW39 in my system.

I’m assuming it is the section that 4 of the configuration parameters that show up in habmin:


Which goes on to list a total of 12 sections (6,6,6,7,8,9 not shown in this screen shot)

I’m trying to grok how someone got these based on what is shown in the inovelli github NZW39.xml.

As I said before, the Inovelli data might be wrong. Maybe there’s a manual somewhere with more parameters, or maybe the database is wrong.

Based on the fact that these entries are in the XML you pasted, it seems most likely that they do exist or they would not be in the XML. If you want to confirm this, then check the debug logs to see if there are responses to these parameters.

When I change the Dimming Step and save it in habmin reports in the log:

2018-09-15 12:42:23.362 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_1_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]


But, habmin shows pending… and there is never a second entry in the log.
(and when you say debug log, I assume it’s a something other than the openhab.log and events.log?)

It’s the same log, but you need to enable debug logging in the console (log:set debug org.openhab.binding.zwave).

Changed dimming step to 2 and got this (filtered the log on “NODE 2”:


2018-09-15 13:40:39.326 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 16 EA 

2018-09-15 13:40:44.914 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 16 EA 

2018-09-15 13:40:53.527 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 16 EA 

2018-09-15 13:40:59.125 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 16 EA 

2018-09-15 13:41:00.873 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Configuration update received

2018-09-15 13:41:00.878 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Configuration update set config_1_1 to 2

2018-09-15 13:41:00.880 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 2: Creating new message for application command CONFIGURATION_SET

2018-09-15 13:41:00.883 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported

2018-09-15 13:41:00.885 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured

2018-09-15 13:41:00.888 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue

2018-09-15 13:41:00.894 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 2: Creating new message for application command CONFIGURATIONCMD_GET

2018-09-15 13:41:00.897 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported

2018-09-15 13:41:00.899 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured

2018-09-15 13:41:00.902 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue

2018-09-15 13:41:01.691 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 16 EA 

2018-09-15 13:41:05.773 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0C 00 13 02 05 70 04 01 01 02 25 D6 62 

2018-09-15 13:41:05.804 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: sentData successfully placed on stack.

2018-09-15 13:41:05.809 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 1010: Transaction not completed

2018-09-15 13:41:05.836 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 214, Status = Transmission complete and ACK received(0)

2018-09-15 13:41:05.838 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false

2018-09-15 13:41:05.843 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Response processed after 64ms

2018-09-15 13:41:05.845 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 1010: Transaction completed

2018-09-15 13:41:05.848 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: notifyTransactionResponse TID:1010 DONE

2018-09-15 13:41:05.850 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2018-09-15 13:41:05.861 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0A 00 13 02 03 70 05 01 25 D7 61 

2018-09-15 13:41:05.889 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: sentData successfully placed on stack.

2018-09-15 13:41:05.893 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 1011: Transaction not completed

2018-09-15 13:41:05.921 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 215, Status = Transmission complete and ACK received(0)

2018-09-15 13:41:05.924 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false

2018-09-15 13:41:05.928 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 1011: Transaction not completed

2018-09-15 13:41:05.938 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)

2018-09-15 13:41:05.939 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false

2018-09-15 13:41:05.942 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_CONFIGURATION, endpoint 0

2018-09-15 13:41:05.943 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported

2018-09-15 13:41:05.945 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT

2018-09-15 13:41:05.947 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 2: Node configuration report, parameter = 1, value = 2, size = 1

2018-09-15 13:41:05.948 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent

2018-09-15 13:41:05.950 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@1f7033

2018-09-15 13:41:05.952 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Update CONFIGURATION 1/1 to 2

2018-09-15 13:41:05.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.

2018-09-15 13:41:05.956 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@e30b7c.

2018-09-15 13:41:05.958 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@e30b7c.

2018-09-15 13:41:05.960 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: notifyTransactionResponse TID:1011 DONE

2018-09-15 13:41:05.962 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

Sorry, but can you provide the log without the grep node 2 please? This filters out all the received data. It does look like this is supported ok though, which is no surprise I guess since it was in the manufacturers list.

I would also suggest to try some of the parameters that are not in the Inovelli list - parameter 1 is confirmed as being there - I think what you’re trying to establish is if the others are there (or not just param 1 and 2 that they have stated are supported).

As I explained earlier, the OZW XML is missing information that the ST DTH contains (you can find them on the Inovelli website. I see one for the NZW36, but it only has the two configuration parameters found in the OZW XML.

Same as the NZW39, there are duplicate entries in the db for the NZW36 (Inovelli, Willis). Both are missing configuration parameters, and the Willis is missing an association group.

I’m trying to get to the point where I know what to ask for to get the info required to enter into the OpenHAB database.

All my questions are me trying to figure out what goes where.

Is there an example of a document that shows what a fully described device would look like?

BTW, what is “ST DTH”, it’s probably obvious and I’ll do a forehead slap when I find out. :flushed:

SmartThings (:face_vomiting:) Device Type Handler

To ask Inovelli? When I asked them to provide the configuration parameters for the NZW39, they pointed me to the OZW XMLs. I responded that the info I needed was not there, they sent me the link again :roll_eyes:.

There is a database full of examples - every one is different…

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

Information on the database is here -:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

It’s the SmartThings device type handler.

Yeah, I know those links. But, what I was asking for was a document, from a manufacturer I guess, that was the source for what I’d type in to create one of those by hand.

Maybe I’m making this harder than it is. Maybe what I’m looking for is what is referred to in the Database Guide page as reference material. I’m thinking the docs that are needed here are similar to the Aeotec engineering docs, for example: https://aeotec.freshdesk.com/helpdesk/attachments/6052990315
That have pages upon pages like this:

@5iver I suspect Inovelli may only be a rebranding house and have little knowledge about the guts of what they make…I could be wrong. When I did a failure analysis of a NZW39, fixed it, and sent them a failure report (I was a engineer in a destructive test lab in a past life…) they completely ignored it.

You will find similar info in other user manuals. An Aeotec HEM was one of my first devices, and their documentation spoiled me. The Linear docs are pretty good too, as in complete. From what I’ve seen, this information is rarely provided and usually needs to be reverse engineered. That’s one of the reasons Chris’ db is so handy, and not just for OH users.

Then you already have an example :confused:. Every manufacturer provides the data in a different format - normally it’s in the manual, sometimes it’s in a technical or engineering manual, sometimes it’s in an XML format, and sometimes it just doesn’t exist.

If you are looking for a nice manual like the Aeotec one, for Innovelli, then I don’t think you will find one unfortunately.

@chris @5iver

SO, I got a reply from Innovelli:

For the NZW36 the configuration parameters shown in the XML (Parameter #1 & #2) are all that exist. On the newest version of the NZW36 there also exists:

Association group 2 (Basic_Set) which can hold 5 members. I will fix that for the open-zwave repository.

The device can also send a central scene report when you press the button 2x.

For the NZW39 the same is true. It has parameter 1 & 2 as listed in the XML file. On the newer versions of it there is also: 

Association group 2 (Basic_Set) which can hold 5 members. I will fix that for the open-zwave repository. 

The device can also send a central scene report when you press the button 2x.

This certainly doesn’t match with what is shown for the NZW39’s I have. So, I went to one and changed parameter 4: Invert Switch 3: LED Indicator. I chose them since the action should be easily visible.

But, there was no change in the behavior of the plug.

When I hit save in Habmin after changing them I get this in the log:

2018-09-18 08:49:39.359 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:16500637f6a:node3' has been updated.

2018-09-18 08:49:39.372 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_3_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

Am I right in thinking the [vent.ConfigStatusInfoEvent] message is from OH code saying it sent the config message to the device and a confirmation is being expected?

I turned on the zwave debug and tried again:

2018-09-18 09:01:32.036 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-09-18 09:01:34.216 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Configuration update received

2018-09-18 09:01:34.224 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Configuration update set config_3_1 to 1

2018-09-18 09:01:34.229 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 3: Creating new message for application command CONFIGURATION_SET

2018-09-18 09:01:34.234 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported

2018-09-18 09:01:34.239 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured

2018-09-18 09:01:34.244 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Adding to device queue

2018-09-18 09:01:34.249 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-09-18 09:01:34.253 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 13 03 05 70 04 03 01 01 25 56 E2 

2018-09-18 09:01:34.257 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 0C 00 13 03 05 70 04 03 01 01 25 56 E2 

2018-09-18 09:01:34.260 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT

2018-09-18 09:01:34.263 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06

2018-09-18 09:01:34.263 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 2170: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 86

2018-09-18 09:01:34.266 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-09-18 09:01:34.268 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-09-18 09:01:34.268 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 3: Creating new message for application command CONFIGURATIONCMD_GET

2018-09-18 09:01:34.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 2170: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 86

2018-09-18 09:01:34.271 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported

2018-09-18 09:01:34.275 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 

2018-09-18 09:01:34.275 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Command Class COMMAND_CLASS_CONFIGURATION is NOT required to be secured

2018-09-18 09:01:34.272 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK

2018-09-18 09:01:34.279 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-09-18 09:01:34.279 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Adding to device queue

2018-09-18 09:01:34.281 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-09-18 09:01:34.283 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2018-09-18 09:01:34.286 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2018-09-18 09:01:34.290 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-09-18 09:01:34.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 2170: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 86

2018-09-18 09:01:34.294 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-09-18 09:01:34.297 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 2170: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 86

2018-09-18 09:01:34.300 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-09-18 09:01:34.301 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: sentData successfully placed on stack.

2018-09-18 09:01:34.304 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 2170: Advanced to WAIT_REQUEST

==> /var/log/openhab2/events.log <==

2018-09-18 09:01:34.304 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:16500637f6a:node3' has been updated.

==> /var/log/openhab2/openhab.log <==

2018-09-18 09:01:34.307 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 2170: Transaction not completed

2018-09-18 09:01:34.309 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-09-18 09:01:34.312 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

==> /var/log/openhab2/events.log <==

2018-09-18 09:01:34.313 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_3_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

==> /var/log/openhab2/openhab.log <==

2018-09-18 09:01:34.366 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 56 00 00 0A B7 

2018-09-18 09:01:34.368 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=86, payload=56 00 00 0A 

2018-09-18 09:01:34.371 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=86, payload=56 00 00 0A 

2018-09-18 09:01:34.373 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 2170: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 86

2018-09-18 09:01:34.375 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-09-18 09:01:34.378 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 2170: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 86

2018-09-18 09:01:34.380 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 2170: (Callback 86)

2018-09-18 09:01:34.383 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!

2018-09-18 09:01:34.385 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 2170: callback 86

2018-09-18 09:01:34.388 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=86, payload=56 00 00 0A 

2018-09-18 09:01:34.391 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 86, Status = Transmission complete and ACK received(0)

2018-09-18 09:01:34.393 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false

2018-09-18 09:01:34.395 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 2170: Transaction COMPLETED

2018-09-18 09:01:34.398 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Response processed after 134ms

2018-09-18 09:01:34.400 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 2170: Transaction completed

2018-09-18 09:01:34.403 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: notifyTransactionResponse TID:2170 DONE

2018-09-18 09:01:34.405 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2018-09-18 09:01:34.408 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-09-18 09:01:34.410 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-09-18 09:01:34.413 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 03 03 70 05 03 25 57 E2 

2018-09-18 09:01:34.416 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 0A 00 13 03 03 70 05 03 25 57 E2 

2018-09-18 09:01:34.418 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT

2018-09-18 09:01:34.420 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06

2018-09-18 09:01:34.421 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 2171: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 87

2018-09-18 09:01:34.422 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-09-18 09:01:34.424 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-09-18 09:01:34.427 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 2171: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 87

2018-09-18 09:01:34.430 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK

2018-09-18 09:01:34.431 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 

2018-09-18 09:01:34.433 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-09-18 09:01:34.435 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-09-18 09:01:34.435 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2018-09-18 09:01:34.438 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-09-18 09:01:34.440 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 2171: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 87

2018-09-18 09:01:34.441 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-09-18 09:01:34.443 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 2171: [WAIT_RESPONSE] priority=Config, requiresResponse=true, callback: 87

2018-09-18 09:01:34.445 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01 

2018-09-18 09:01:34.447 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: sentData successfully placed on stack.

2018-09-18 09:01:34.449 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 2171: Advanced to WAIT_REQUEST

2018-09-18 09:01:34.451 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 2171: Transaction not completed

2018-09-18 09:01:34.452 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-09-18 09:01:34.454 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2018-09-18 09:01:34.554 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 57 00 00 0D B1 

2018-09-18 09:01:34.556 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=SendData[19], type=Request[0], dest=0, callback=87, payload=57 00 00 0D 

2018-09-18 09:01:34.558 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=87, payload=57 00 00 0D 

2018-09-18 09:01:34.560 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 2171: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 87

2018-09-18 09:01:34.562 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-09-18 09:01:34.564 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 2171: [WAIT_REQUEST] priority=Config, requiresResponse=true, callback: 87

2018-09-18 09:01:34.565 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 2171: (Callback 87)

2018-09-18 09:01:34.567 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!

2018-09-18 09:01:34.569 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 2171: callback 87

2018-09-18 09:01:34.572 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 03 05 70 06 03 01 01 83 

2018-09-18 09:01:34.572 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=87, payload=57 00 00 0D 

2018-09-18 09:01:34.574 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 87, Status = Transmission complete and ACK received(0)

2018-09-18 09:01:34.574 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=3, callback=0, payload=00 03 05 70 06 03 01 01 

2018-09-18 09:01:34.576 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false

2018-09-18 09:01:34.578 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 2171: Advanced to WAIT_DATA

2018-09-18 09:01:34.580 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: TID 2171: Transaction not completed

2018-09-18 09:01:34.582 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=3, callback=0, payload=00 03 05 70 06 03 01 01 

2018-09-18 09:01:34.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2018-09-18 09:01:34.586 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Application Command Request (ALIVE:DONE)

2018-09-18 09:01:34.588 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: resetResendCount initComplete=true isDead=false

2018-09-18 09:01:34.589 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Incoming command class COMMAND_CLASS_CONFIGURATION, endpoint 0

2018-09-18 09:01:34.591 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: SECURITY not supported

2018-09-18 09:01:34.592 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT

2018-09-18 09:01:34.594 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 3: Node configuration report, parameter = 3, value = 1, size = 1

2018-09-18 09:01:34.596 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent

2018-09-18 09:01:34.597 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@e6b1ee

2018-09-18 09:01:34.599 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Update CONFIGURATION 3/1 to 1

2018-09-18 09:01:34.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Commands processed 1.

2018-09-18 09:01:34.603 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@104ce28.

2018-09-18 09:01:34.605 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@104ce28.

2018-09-18 09:01:34.606 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 3: notifyTransactionResponse TID:2171 DONE

2018-09-18 09:01:34.608 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2018-09-18 09:01:34.610 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1

2018-09-18 09:01:34.611 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-09-18 09:01:34.612 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-09-18 09:01:34.614 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-09-18 09:01:45.554 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 0B 0E 32 02 21 44 00 00 01 B9 00 1F 00 00 01 B9 A0 

2018-09-18 09:01:45.560 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=11, callback=0, payload=00 0B 0E 32 02 21 44 00 00 01 B9 00 1F 00 00 01 B9 

2018-09-18 09:01:45.564 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=11, callback=0, payload=00 0B 0E 32 02 21 44 00 00 01 B9 00 1F 00 00 01 B9 

2018-09-18 09:01:45.566 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2018-09-18 09:01:45.568 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Application Command Request (ALIVE:PING)

2018-09-18 09:01:45.571 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: Incoming command class COMMAND_CLASS_METER, endpoint 0

2018-09-18 09:01:45.573 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: SECURITY not supported

2018-09-18 09:01:45.575 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 11: Received COMMAND_CLASS_METER V3 METER_REPORT

2018-09-18 09:01:45.578 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 11: Meter: Type=Electric(1), Scale=kWh(0), Value=4.41

2018-09-18 09:01:45.581 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveMeterValueEvent

2018-09-18 09:01:45.583 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_METER, value = 4.41

2018-09-18 09:01:45.586 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:16500637f6a:node11:meter_kwh to 4.41 [DecimalType]

2018-09-18 09:01:45.589 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Commands processed 1.

2018-09-18 09:01:45.592 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 11: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@489fa9.

2018-09-18 09:01:45.594 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-09-18 09:01:45.596 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2018-09-18 09:01:45.599 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-09-18 09:01:45.601 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-09-18 09:01:45.699 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 0B 0E 32 02 21 44 00 00 01 B9 00 1F 00 00 01 B9 A0 

2018-09-18 09:01:45.705 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=11, callback=0, payload=00 0B 0E 32 02 21 44 00 00 01 B9 00 1F 00 00 01 B9 

2018-09-18 09:01:45.708 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=11, callback=0, payload=00 0B 0E 32 02 21 44 00 00 01 B9 00 1F 00 00 01 B9 

Though I don’t know what to look for in the log to see if the change was accepted by the device, it does not appear to chage the behavior. (for example, set the led to always on)
BTW, is there a way to send specific commands to a device by hand? For example on my ISY944 there was a dialog that would allow me to specific the command code and payload to a device. I guess I’m asking if I can send or probe a zwave device from the OH console?

2018-09-18 09:01:34.592 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Received COMMAND_CLASS_CONFIGURATION V1 CONFIGURATIONCMD_REPORT

2018-09-18 09:01:34.594 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 3: Node configuration report, parameter = 3, value = 1, size = 1

2018-09-18 09:01:34.596 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent

2018-09-18 09:01:34.597 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@e6b1ee

2018-09-18 09:01:34.599 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Update CONFIGURATION 3/1 to 1

These lines show that parameter 3 was read from the device, and is currently set to 1, which is what you had set it to. It’s possible the device might need to be power cycled for the configuration change to take affect.

No, this is not available in OH. You can change configuration parameters by adding a channel for them in the device db. You can also send the command “REFRESH” to an item to poll the device and refresh the item’s state.

I guess it’s also possible that the configuration exists in software, but maybe doesn’t do anything? Sometime manufacturers use the same software/hardware for multiple devices as it makes it easier (ie cheaper!) for them to certify devices, but different versions may not have the same physical form, and (for example) may have different LEDs etc, or no power monitoring…

Just another possibility…

Power cycle of the device doesn’t seem to change the behavior.

Since Inovelli seems sure the only parameters are those in their xml file, I’m guessing Chris is correct in that the firmware in the device can respond to the query, but doesn’t know how to actually change the parameter.

Interestingly, the thing that started my query on this was that after update to snapshot #1361, it appeared that local activation of the switch didn’t update the state in paperui (or habpanel). (at the same time a Haozee plug was also not updating the voltage)

After running for 24 hours the Haozee started updating the voltage again.

And I, now notice that the Inovelli plugs are now updating in paperui/habpanel as well. (This could have been the case for a couple days and I just noticed it…)

Any clues as to why things would “heal” like that?

And, a side question: since I’m running the snapshot, does it make sense to update the snapshot ever day or so?

That seems odd for a small network of mains powered devices. Every time you restart the binding, start discovery, save items… there’s probably something else… it will take some time for the devices to partially reinitialize, and this may limit some functionality, or slow down responses. With 121 devices in my network, it takes a few hours for things to settle down. 24 hours sounds like an issue, but there is also a nightly heal process that runs at 2am by default. This heal will help sort out the mesh, which could be a bit of a mess, depending on how you initially included the devices, It will take several heals to get the mesh completely sorted. My guess is either initialization finally completed, or the heal sorted something out, but that’s conjecture without looking at some debug logs,