Leviton Z-Wave VRCZ1 switch

Hardware Home Automation
1

I have 1 z-wave device I seem to be unable to include in my network. I’ve tried to exclude it, I’ve reset the device, no luck. Debug traces below. From looking at the web, someone in the Home Assistant forums suggested this particular z-wave device is somehow “different”. No clue, but it doesn’t show up as unknown or anything. Suggestions appreciated. Thanks.

At time 09:35:15.067 in the log below I see an add node to network that appears to fail. I put this thru the log viewer but didn’t gain much more knowledge and I’m not quite sure how to include that image here.

2020-02-11 09:35:04.474 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Start zwave:serial_zstick:d1f10b47
2020-02-11 09:35:04.475 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
2020-02-11 09:35:04.475 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2020-02-11 09:35:04.476 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller start inclusion
2020-02-11 09:35:04.476 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:true.
2020-02-11 09:35:04.476 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 125 to queue - size 1
2020-02-11 09:35:04.477 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-02-11 09:35:04.477 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 AC DD 
2020-02-11 09:35:04.477 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 AC DD 
2020-02-11 09:35:04.478 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2020-02-11 09:35:04.478 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 125: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 172
2020-02-11 09:35:04.479 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2020-02-11 09:35:04.479 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-02-11 09:35:04.479 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-02-11 09:35:04.480 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 125: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 172
2020-02-11 09:35:04.480 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2020-02-11 09:35:04.480 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-11 09:35:04.480 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A AC 01 00 00 1F 
2020-02-11 09:35:04.481 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-02-11 09:35:04.481 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=172, payload=AC 01 00 00 
2020-02-11 09:35:04.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=172, payload=AC 01 00 00 
2020-02-11 09:35:04.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 125: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 172
2020-02-11 09:35:04.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2020-02-11 09:35:04.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 125: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 172
2020-02-11 09:35:04.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 125: (Callback 172)
2020-02-11 09:35:04.482 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2020-02-11 09:35:04.482 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 125: callback 172
2020-02-11 09:35:04.483 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=172, payload=AC 01 00 00 
2020-02-11 09:35:04.483 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Learn ready.
2020-02-11 09:35:04.483 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeSent, new event IncludeStart
2020-02-11 09:35:04.483 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 125: Transaction COMPLETED
2020-02-11 09:35:04.483 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 5ms
2020-02-11 09:35:04.484 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 125: Transaction completed
2020-02-11 09:35:04.484 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:125 DONE
2020-02-11 09:35:04.487 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-11 09:35:04.487 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-02-11 09:35:06.479 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery completed
2020-02-11 09:35:06.481 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 9: Device discovery resolved to thingType zwave:leviton_vri06_00_000
2020-02-11 09:35:06.483 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery completed
2020-02-11 09:35:06.484 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery resolved to thingType zwave:leviton_vrs15_00_000
2020-02-11 09:35:12.157 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A AC 02 00 00 1C 
2020-02-11 09:35:12.157 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=2, callback=172, payload=AC 02 00 00 
2020-02-11 09:35:12.158 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=2, callback=172, payload=AC 02 00 00 
2020-02-11 09:35:12.158 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-02-11 09:35:12.158 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 0
2020-02-11 09:35:12.158 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: null
2020-02-11 09:35:12.159 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=2, callback=172, payload=AC 02 00 00 
2020-02-11 09:35:12.159 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: New node found.
2020-02-11 09:35:12.159 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-11 09:35:12.159 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-02-11 09:35:15.065 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A AC 07 0B 00 12 
2020-02-11 09:35:15.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=7, callback=172, payload=AC 07 0B 00 
2020-02-11 09:35:15.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=7, callback=172, payload=AC 07 0B 00 
2020-02-11 09:35:15.066 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-02-11 09:35:15.067 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 0
2020-02-11 09:35:15.067 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: null
2020-02-11 09:35:15.067 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=7, callback=172, payload=AC 07 0B 00 
2020-02-11 09:35:15.067 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Failed.
2020-02-11 09:35:15.067 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeStart, new event IncludeFail
2020-02-11 09:35:15.068 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2020-02-11 09:35:15.068 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 126 to queue - size 1
2020-02-11 09:35:15.068 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-02-11 09:35:15.068 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 AD 18 
2020-02-11 09:35:15.068 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 AD 18 
2020-02-11 09:35:15.069 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2020-02-11 09:35:15.069 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 126: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 173
2020-02-11 09:35:15.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-11 09:35:15.070 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2020-02-11 09:35:15.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-02-11 09:35:15.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-02-11 09:35:15.070 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-02-11 09:35:15.071 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 126: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 173
2020-02-11 09:35:15.071 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2020-02-11 09:35:15.071 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-11 09:35:15.071 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-02-11 09:35:15.120 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A AD 06 0B 00 12 
2020-02-11 09:35:15.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=173, payload=AD 06 0B 00 
2020-02-11 09:35:15.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=173, payload=AD 06 0B 00 
2020-02-11 09:35:15.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 126: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 173
2020-02-11 09:35:15.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
2020-02-11 09:35:15.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 126: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 173
2020-02-11 09:35:15.121 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 126: (Callback 173)
2020-02-11 09:35:15.122 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
2020-02-11 09:35:15.122 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 126: callback 173
2020-02-11 09:35:15.122 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=173, payload=AD 06 0B 00 
2020-02-11 09:35:15.122 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Done.
2020-02-11 09:35:15.122 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovered
2020-02-11 09:35:15.123 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveInclusionEvent
2020-02-11 09:35:15.123 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeFail, new event IncludeDone
2020-02-11 09:35:15.123 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2020-02-11 09:35:15.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 127 to queue - size 1
2020-02-11 09:35:15.123 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-02-11 09:35:15.124 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller end exclusion
2020-02-11 09:35:15.124 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWaveController include done
2020-02-11 09:35:15.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 126: Advanced to DONE
2020-02-11 09:35:15.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 55ms
2020-02-11 09:35:15.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 126: Transaction completed
2020-02-11 09:35:15.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:126 DONE
2020-02-11 09:35:15.124 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-11 09:35:15.125 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-02-11 09:35:15.125 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 00 B5 
2020-02-11 09:35:15.125 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 00 B5 
2020-02-11 09:35:15.125 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2020-02-11 09:35:15.126 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 127: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2020-02-11 09:35:15.126 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2020-02-11 09:35:15.126 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-02-11 09:35:15.126 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2020-02-11 09:35:15.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 127: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2020-02-11 09:35:15.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2020-02-11 09:35:15.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-02-11 09:35:15.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2020-02-11 09:35:20.127 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 127: Timeout at state WAIT_REQUEST. 3 retries remaining.
2020-02-11 09:35:20.127 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 127: Transaction is current transaction, so clearing!!!!!
2020-02-11 09:35:20.127 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 127: Transaction CANCELLED
2020-02-11 09:35:20.127 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:127 CANCELLED
2020-02-11 09:35:20.128 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-02-11 09:36:04.474 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:d1f10b47
2020-02-11 09:36:04.474 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave inclusion process not running - nothing to do
2

I do not see that device listed in our database.

Here is the database guide of you wish to add it.
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

Otherwise we need the xml file generated by OH in the userdata/zwave folder and a link to the user guide.

3

But doesn’t OH need to see the device as a thing, even if it is unknown before it can be added to the device database?

4

Yes… you’ll need to add the Thing from the Inbox before the device will be interrogated and the xml will be created. Or does it get interrogated in the Inbox?

1 Like
5

No - that’s not correct. The interview is not dependant on the device being a thing - the protocol and OH parts of the binding are pretty much separate.

The XML file should be generated even it it’s not a thing.

2 Likes
6

Well, I’ll check when I’m home and see if there is an XML. But given it doesn’t show after I attempt to include… Do we think adding it to the database will fix not getting an unknown thing when attempting to include it?

7

If you update to a snapshot binding including the changes, yes.

8

Sorry, but in userdata/zwave there are only 3 xml files, one for the controller and 2 for 2 other switches. The switch I attempted to add is not there. So, something else is going on… Any additional debug I can capture?

9

The log you provided shows that the inclusion failed - I’m afraid it’s not possible to tell why, but the controller did not include the device into the network. All I can suggest is to try this again - until the controller includes the device, the binding can’t do anything.

10

Factory reset the device first. I recall some devices that would not include until I did that first.

11

Pilot error. I now have an XML file. This switch of course has a slightly different way of putting into inclusion mode than their VRI06 and VRS15 switches. I’ll work on getting info to database. Thank you all for the help! Next time I read the instructions closer.

1 Like
12

I’ve got a fresh install of 4.3.2 via Openhabian on an RPi4. Aeon ZW090 Z-stick. Yes, an old controller, from 2017. I have a stable Z-wave mesh network with about 18 devices. I recently tried expanding by including the VRCZ1, a 1-button zone dimming controller. Because my Z-stick is so old, network inclusion doesn’t seem to work. I have to remove the controller from the USB port and exclude/include in low power, off-line. So, I don’t have OH logs of the inclusion process, yet.

I tried excluding and including several times. The feedback from the controller LED convinces me that the exclusion and inclusion is successful, however the thing appears in my Inbox as,

Z-Wave Node 044 (001D:0D01:0215:0.2)

Either the device is not in the database or the device initialization is not complete. We know the former is not true. The device is in the database. The device initialization is not complete.

  • This device has not been fully discovered by the binding. There are a few possible reasons for this -:
    • The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like “Z-Wave node 1 (0082:6015:020D::2.0)”). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
    • The device initialisation is not complete. Once the device is included into the network, the binding must interrogate it to find out what type of device it is. One part of this process is to get the manufacturer information required to identify the device, and until this is done, the device will remain unknown. For mains powered devices, this will occur quickly, however for battery devices the device must be woken up a number of times to allow the discovery phase to complete. This must be performed with the device close to the controller.

Here is the log of when I inserted the Z-Stick in the USB port and restarted RPi:

2025-01-23 15:52:07.167 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2025-01-23 15:52:07.169 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2025-01-23 15:52:16.085 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 44: Device discovery could not resolve to a thingType! 001D:0D01:0215::0.2

I do have a device XML file in userdata/zwave.

<node>
  <homeId>0xd1a61e37</homeId>
  <nodeId>44</nodeId>
  <version>3</version>
  <manufacturer>0x1d</manufacturer>
  <deviceId>0x215</deviceId>
  <deviceType>0xd01</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>500</sleepDelay>
  <nodeInformationFrame>
    <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
    <commandClass>COMMAND_CLASS_HAIL</commandClass>
    <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
    <commandClass>COMMAND_CLASS_VERSION</commandClass>
    <commandClass>COMMAND_CLASS_NODE_NAMING</commandClass>
    <commandClass>COMMAND_CLASS_MANUFACTURER_PROPRIETARY</commandClass>
    <commandClass>COMMAND_CLASS_MARK</commandClass>
  </nodeInformationFrame>
  <associationGroups class="concurrent-hash-map">
    <entry>
      <int>1</int>
      <associationGroup>
        <index>1</index>
        <maxNodes>0</maxNodes>
        <associations/>
      </associationGroup>
    </entry>
  </associationGroups>
  <endpoints class="concurrent-hash-map">
    <entry>
      <int>0</int>
      <endPoint>
        <deviceClass>
          <basicDeviceClass>BASIC_TYPE_STATIC_CONTROLLER</basicDeviceClass>
          <genericDeviceClass>GENERIC_TYPE_STATIC_CONTROLLER</genericDeviceClass>
          <specificDeviceClass>SPECIFIC_TYPE_NOT_USED</specificDeviceClass>
        </deviceClass>
        <endpointId>0</endpointId>
        <secureCommandClasses/>
        <supportedCommandClasses class="concurrent-hash-map">
          <entry>
            <commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
            <COMMAND__CLASS__NO__OPERATION>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__NO__OPERATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BASIC</commandClass>
            <COMMAND__CLASS__BASIC>
              <version>0</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__BASIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
            <COMMAND__CLASS__MANUFACTURER__SPECIFIC>
              <version>0</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <initSerialNumber>false</initSerialNumber>
              <deviceManufacturer>29</deviceManufacturer>
              <deviceType>3329</deviceType>
              <deviceId>533</deviceId>
            </COMMAND__CLASS__MANUFACTURER__SPECIFIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_NODE_NAMING</commandClass>
            <COMMAND__CLASS__NODE__NAMING>
              <version>0</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <name></name>
              <location></location>
            </COMMAND__CLASS__NODE__NAMING>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_HAIL</commandClass>
            <COMMAND__CLASS__HAIL>
              <version>0</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
            </COMMAND__CLASS__HAIL>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
            <COMMAND__CLASS__ASSOCIATION>
              <version>0</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <maxGroups>1</maxGroups>
            </COMMAND__CLASS__ASSOCIATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_VERSION</commandClass>
            <COMMAND__CLASS__VERSION>
              <version>0</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <libraryType>LIB_CONTROLLER_STATIC</libraryType>
              <protocolVersion>2.21</protocolVersion>
              <applicationVersion>0.2</applicationVersion>
            </COMMAND__CLASS__VERSION>
          </entry>
        </supportedCommandClasses>
      </endPoint>
    </entry>
  </endpoints>
  <nodeNeighbors/>
  <lastReceived>2025-01-23 20:57:12.271 UTC</lastReceived>

Not sure what to try next. Thanks for any help.

13

Are you sure? I see: OpenSmartHouse Z-Wave Device Database - but that has Type 0D02:0224 which doesn’t match above. I believe you need an exact match for the binding to find it. Maybe I missed your device.

1 Like
14

I added these TYPE:ID to the ZW DB. However, they need to be approved and merged into the binding (The ZW DB is in the jar file).

One option (besides waiting), if you are willing is to use this procedure and this file (folder levitron)
vrcz1_0_0.xml (3.6 KB)

to overwrite the current file with the additional info.
Could also try to simply edit your current zwave jar with this line (If you have an app to edit a jar).
<property name="manufacturerRef">0D01:0215,0D02:0224</property>

15

Ah, well if the Type ID must match, then you are correct @jswim788. I guess I need to request a login to OpenSmartHouse and upload the XML.

Except…I get “Page not found” when attempting to register. :slightly_frowning_face:

16

Thanks, @apella12. I’m in no rush with this, so, I can wait for approval.

17

Take a look at this post Opensmarthouse Database Registration Down - Off-Topic - openHAB Community. Might be a good idea to register and get write access if you are looking to expand your network.