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”
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
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.
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.
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.
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.
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.
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).
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.