Yale Assure Door Lock YRD226

  • Platform information: Windows 7 using Aeotec Z-stick Z-Wave Plus
    • Hardware: i7-3540M CPU 3.00GHz / RAM 8GB / x64 bit OS
    • OS: Microsoft Windows 7 using Aeotec Z-Stick Gen-5 Z-Wave Plus
    • Java Runtime Environment: jdk 1.8
    • openHAB version: openHAB 2.5.10 Release Build
  • Issue of the topic: It shows up on PaperUI as YRD256 Yale Assure Lock keyless, but I got YRD226 with keys. After adding it also shows detection of two nodes. Another issue is that I cannot control door lock using “lock” and “unlock” buttons.

Here is the example of button pressed is locked, but on the log file is showing “NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found”

Here are some portions of logs

2020-12-15 00:05:40.987 [INFO ] [ashboard.internal.HABotDashboardTile] - Started HABot at /habot
2020-12-15 00:05:41.030 [INFO ] [internal.ModuleHandlerFactoryStarter] - WebPushNotificationModuleHandlerFactory started by ModuleHandlerFactoryStarter
2020-12-15 00:05:42.848 [INFO ] [etvisu.internal.servlet.CometVisuApp] - Started CometVisu UI at /cometvisu serving …/…/…/CometVisu/src/
2020-12-15 00:05:43.304 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-12-15 00:05:43.679 [INFO ] [ebuilder.internal.HomeBuilderServlet] - Started Home Builder at /homebuilder
2020-12-15 00:05:50.352 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-12-15 00:05:50.353 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-12-15 00:09:14.213 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:09:14.222 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:70397ed4:node7’ to inbox.
2020-12-15 00:09:14.224 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:12:40.071 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:12:42.804 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:12:51.123 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:12:54.152 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:12:54.959 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:12:55.744 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:12:56.369 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:14:38.388 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:14:39.576 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:14:40.515 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:14:41.149 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:14:41.820 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:14:42.805 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:24:08.465 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:24:08.466 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:70397ed4:node7’ to inbox.
2020-12-15 00:24:08.467 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:24:08.467 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:70397ed4:node10’ to inbox.
2020-12-15 00:24:08.469 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:70397ed4:node13’ to inbox.
2020-12-15 00:25:02.606 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:25:02.608 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:29:50.405 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:29:53.175 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:29:54.065 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:29:54.648 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 13: Command class COMMAND_CLASS_DOOR_LOCK not found
2020-12-15 00:31:40.474 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:31:40.476 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:34:30.210 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2020-12-15 00:34:35.839 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-12-15 00:34:35.839 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-12-15 00:34:38.947 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:033f2153:node13’ to inbox.
2020-12-15 00:37:13.223 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:37:13.223 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:033f2153:node7’ to inbox.
2020-12-15 00:37:13.224 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:37:13.225 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:033f2153:node10’ to inbox.
2020-12-15 00:39:45.495 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:39:45.497 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-12-15 00:41:25.094 [WARN ] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2020-12-15 00:42:08.573 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2020-12-15 00:42:08.574 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2020-12-15 00:58:03.531 [INFO ] [ashboard.internal.HABotDashboardTile] - Stopped HABot
2020-12-15 00:58:03.615 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI

There is no YRD226 in the database, please add it from your xml file or post it here with a product image and a pdf manual.

1 Like

I do not know, the link what you provide didn’t sign me up.

Here is the code

YRD226 BDNK3004411

Here are the links of particular version of that one

That does not help.

We need the xml from your /userdata/zwave folder, a product image and the manual.
You only have provided the manual.

If you already registered to the database you need to send an email to get edit rights, after that you will be able to add the device yourself.
This is all stated in the link I provided.

Actually they need to open a ticket there asking for rights. That is in the guide in bold text. Perhaps we should use that horrible blink tag.

Email worked for years, I think it still works

Likely but not the stated path. Tickets can be more scalable in the future if others are given approval permissions.

Does this really matter?

Yale tend to use the same module in all, or at least many of their devices. They all (as far as I know) work the same, so if it is just that the device is not recognised correctly, then I wouldn’t worry.

Probably the device is not included securely, in which case the device will not support the secure functions.

1 Like

Thank you for your help and reply.

Regarding registration to OpenSmartHouse, registration is not working on my side.
When I want to register, it says that email is in use. When I want to forgot password, it says it cannot be reset because of unregistered email. I emailed OpenSmartHouse to resolve my issues.

Regarding xml file, here are attachments to the following link https://we.tl/t-WyXN7x4iHP
Please download that from there. I did this because, community.openhab.org website doesn’t allow new users to attach files.

Thank you

Sorry, I never ever download files from unknown sources.
I am pretty sure you should be able to insert the xml as plain text and format it properly as code.

```
code
```
1 Like

Here is a XML file of z-wave controller

<node>
  <homeId>0xd794a3ef</homeId>
  <nodeId>1</nodeId>
  <version>4</version>
  <manufacturer>0x86</manufacturer>
  <deviceId>0x5a</deviceId>
  <deviceType>0x101</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>false</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>1000</sleepDelay>
  <associationGroups class="concurrent-hash-map"/>
  <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_PC_CONTROLLER</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>0</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>0</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__BASIC>
          </entry>
        </supportedCommandClasses>
      </endPoint>
    </entry>
  </endpoints>
  <nodeNeighbors/>
</node>

Here is a xml file for Yale Door Lock

<node>
  <homeId>0xd794a3ef</homeId>
  <nodeId>13</nodeId>
  <version>4</version>
  <manufacturer>0x129</manufacturer>
  <deviceId>0x600</deviceId>
  <deviceType>0x8002</deviceType>
  <listening>false</listening>
  <frequentlyListening>true</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>1000</sleepDelay>
  <nodeInformationFrame>
    <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
    <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
    <commandClass>COMMAND_CLASS_SECURITY</commandClass>
    <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
    <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
    <commandClass>COMMAND_CLASS_VERSION</commandClass>
  </nodeInformationFrame>
  <associationGroups class="concurrent-hash-map"/>
  <endpoints class="concurrent-hash-map">
    <entry>
      <int>0</int>
      <endPoint>
        <deviceClass>
          <basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
          <genericDeviceClass>GENERIC_TYPE_ENTRY_CONTROL</genericDeviceClass>
          <specificDeviceClass>SPECIFIC_TYPE_SECURE_KEYPAD_DOOR_LOCK</specificDeviceClass>
        </deviceClass>
        <endpointId>0</endpointId>
        <secureCommandClasses/>
        <supportedCommandClasses class="concurrent-hash-map">
          <entry>
            <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
            <COMMAND__CLASS__DEVICE__RESET__LOCALLY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__DEVICE__RESET__LOCALLY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
            <COMMAND__CLASS__MANUFACTURER__SPECIFIC>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <initSerialNumber>false</initSerialNumber>
              <deviceManufacturer>297</deviceManufacturer>
              <deviceType>32770</deviceType>
              <deviceId>1536</deviceId>
            </COMMAND__CLASS__MANUFACTURER__SPECIFIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_VERSION</commandClass>
            <COMMAND__CLASS__VERSION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <libraryType>LIB_SLAVE_ENHANCED</libraryType>
              <protocolVersion>4.24</protocolVersion>
              <applicationVersion>1.78</applicationVersion>
              <hardwareVersion>255</hardwareVersion>
            </COMMAND__CLASS__VERSION>
          </entry>
          <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_POWERLEVEL</commandClass>
            <COMMAND__CLASS__POWERLEVEL>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <powerLevel>0</powerLevel>
              <powerTimeout>0</powerTimeout>
            </COMMAND__CLASS__POWERLEVEL>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_SECURITY</commandClass>
            <COMMAND__CLASS__SECURITY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__SECURITY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BASIC</commandClass>
            <COMMAND__CLASS__BASIC>
              <version>0</version>
              <instances>0</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__BASIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
            <COMMAND__CLASS__ZWAVEPLUS__INFO>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <zwPlusVersion>1</zwPlusVersion>
              <zwPlusRole>ROLE_TYPE_SLAVE_SLEEPING_LISTENING</zwPlusRole>
              <zwPlusNodeType>NODE_TYPE_ZWAVEPLUS_NODE</zwPlusNodeType>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__ZWAVEPLUS__INFO>
          </entry>
        </supportedCommandClasses>
      </endPoint>
    </entry>
  </endpoints>
  <nodeNeighbors/>
  <lastReceived>2020-12-15 06:04:28.776 UTC</lastReceived>
</node>

Thx, this is the final proof:

<manufacturer>0x129</manufacturer>
<deviceId>0x600</deviceId>
<deviceType>0x8002</deviceType>
<applicationVersion>1.78</applicationVersion>

Your device is already defined as YRD256 and there is no way to distinguish between your device and the device in the database.

As already mentioned you need to live with that. Is there a function or parameter missing?

1 Like

Here, YRD256 is keyless, YRD226 comes with key.

I am not sure about function, I don’t know.

Yes, it is identified as YRD256, which is not right model.
You mentioned that, because it is not in database, it found what is in database.

How can I resolve that issue?

Is that manufacturer problem? or is software identification problem?

Likely they use the exact same electronics with just physical, non-electronic differences. If so, there is no issue to resolve.

It won’t really be possible to resolve this - the ID is allocated to the other models. As I said, my understanding is that Yale use the same module for multiple devices.

I can really only reiterate what I said earlier - if your device is not securely included, then it will not support the lock. This is not a database issue - you need to ensure the device is securely included to make it work.

2 Likes

Would you mind to send a link to documentation how to add securily?

Take a look at the binding documentation -:

The important thing to note is that the secure inclusion must happen within 15 seconds of the device first being included into the network. If it fails, you MUST reset the device and start again. You also MUST perform the inclusion using the binding - not by removing the stick and taking it to the device (I’m not sure what stick you have, and don’t know if you’re doing this, but it will never work this way).

1 Like

Thank you, I will take a look.

I excluded and included my Yale (YRD110) and it shows “online”, but does not recognize that the door is locked/unlocked.

In the past, Yale locks didn’t update the lock_door channel. I’m not sure if that’s still the case, but you can use the alarm_raw channel with a rule to identify the state.

Here’s the rule I use, which works for both Yale and Schlage locks.