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.
Is it included securely? Check the properties to make sure it was securely included - if not, exclude it, and re-include it until it shows it is securely included.
Where would I find these properties in OH3?
They are displayed in the thing information / configuration page. You need to click on the properties line to expand them.
Under “Information”, “Thing Properties”, “zwave_secure” is set to “false”. Is that what needs to be “true”?
Keep deleting the thing and exclude/include the zwave until it shows “true”?
Correct - if the device is not securely included, then you will not be able to operate the lock, or read back the lock state. A lock requires the use of security to protect your home.
1 Like
Awesome, thank you!!
1 Like