I skimmed through the device you created and it looks good. I approved the change, so now it’s a matter of waiting for it to show up in the next build.
Awesome, thanks. I haven’t updated my binding to the 2.5 snapshot version yet so I need to start looking in to that next.
Sure thing. Just ask if you have any questions. The next version should be available in a few days.
Finally got around to getting the zwave binding updated to the 2.5 snapshot version. Got the new lock included and discovered in Paper UI just fine. I haven’t tested all the parameters and channels yet but basic functionality seems to be working great. Thanks again for all the help!
Does the new version report the lock states when manually operated? The BE469 requires the alarm_raw channel to figure this out. It’s also used to determine who’s code was used to lock/unlock. I suggest you remove the other alarm Channels and add this. Also, I expect all of your config params with a -1 value will not work or throw an error. The manual has negatives, but has to be an error. We’re talking bytes… no such thing as a negative byte.
Yes, the lock reports the state when manually operated. I was suspect of the -1’s as well but without any good documentation I didn’t know what else to put. What would you suggest, 255?
The endpoints are really just a SWAG on my part. I couldn’t find any documentation on how they should be configured so I copied them from the previous version of the lock where relevant. I’m no expert with this but I don’t see an alarm_raw in the nodeXML that was generated for the device. I do see the other four alarm types that were created though but can’t really see what usefulness they provide.
Take a look at the BE469. The parameters are very similar, if not identical, and have 0 and 1.
Remove the other Channels from the NOTIFICATION command class, and add alarm_raw, just like the BE469. I’m not sure you will have permissions though, so try and let me know. If you can’t do it, I’ll take care of it.
It’s great that Schlage finally realized that they needed to report the lock state! 
Ok, thanks Scott. I updated the parameters that had a -1 to match the BE469 model. I couldn’t figure out a way to remove the Channels though. The interface has the option to add or edit but not delete, am I missing something? Also, I added the alarm_raw Channel as you suggested but as soon as it updated it displays that the Channel is deprecated. Alarm (raw) [deprecated]
Yes… the permisions 
. I mentioned this may not be possible for you… I’ve removed them. Once you see what comes in with alarm_raw, you may find a use for breaking out one or more of them again. Easily put back.
There is a Deprecated checkbox on the edit page used to signify a duplicated Channel. You must have accidently ticked it. Gone now!
Cool, thanks for your help!
1 Like
So grabbed one of these and installed it. I can’t get it to register from the database to save my life. Seeing that several say these locks have to be nearly touching the zwave stick, I removed it and tried that. Also loaded zwave pc controller trying to remove the nodes (it somehow in my attempts got node 8-11 created) Still can’t get them removed. Anyways, it sits and doesn’t get any manufacturer information
I keep seeing this in the console:
17:12:08.473 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery could not resolve to a thingType! Manufacturer data not known.
Running a rather current binding version:
openhab> bundle:list |grep -i wave
283 x Active x 80 x 2.5.6.202005180339 x openHAB Add-ons :: Bundles :: ZWave Binding
Do you have the exact model number or link for your lock? The new ZP models being sold have some minor variations (i.e. 468ZP vs 469ZP) and may also need to be added to the zwave database.
Did you try inclusion via the new include/exclude button inside the lock or via keypad? I’ve used both, but keypad is more reliable for me.
For the removal part. If you run into a partial include and need to exclude the lock to start over again, you don’t need PC controller to remove the node. You can exclude from habmin and punch in the exclusion code on the keypad. At least that’s what worked for me.
I only did it with the button inside battery cover (from looking at the instructions). I didn’t even these could do that on the keypad. How did you do that? I’d give that a try. This one is model BE469ZP
When you exclude in habmin, where did you get the exclude code? I didn’t know you could do that via the keypad. Maybe that will make the difference. It keeps adding but increments up the nodes and how I have a gap. I kept trying that button from the manual to enroll.
Yeah, the documentation can be a bit confusing. To enroll or unenroll from keypad, the process is the same. Use these instructions:
The 6 digit programming code is on a sticker in your manual OR on a sticker inside the lock (you can unscrew the knob side of the lock to get to it)
To exclude from habmin, go to things -> your zwave controller -> tools -> advanced settings -> exclude devices and the run the process above from your lock
1 Like
I tried it from the keypad and put it a few inches away from the zwave stick and tried it again. I just keep burning my node increments 
So not sure but definitely doesn’t seem to pull from the database. shows but doesn’t grab or see mfg id or anything
20:53:38.184 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery could not resolve to a thingType! Manufacturer data not known.
20:53:38.186 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.
20:53:47.382 [INFO ] [ig.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:d3ebf740:node14' to inbox.
20:53:47.382 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID 'zwave:device:d3ebf740:node14' has been added.
20:53:48.398 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! Manufacturer data not known.
20:55:04.947 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery could not resolve to a thingType! Manufacturer data not known.
20:55:04.949 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.
20:55:04.957 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 14: Device discovery could not resolve to a thingType! Manufacturer data not known.
20:55:17.994 [INFO ] [ig.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:d3ebf740:node15' to inbox.
20:55:17.995 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID 'zwave:device:d3ebf740:node15' has been added.
20:55:19.001 [WARN ] [zwave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! Manufacturer data not known.
The node xml is below… could I manually modify that to maybe get the channels to populate? Not sure why it won’t show.
/var/lib/openhab2/zwave# cat network_cd0a2e40__node_13.xml
<node>
<homeId>0xcd0a2e40</homeId>
<nodeId>13</nodeId>
<version>4</version>
<manufacturer>0x7fffffff</manufacturer>
<deviceId>0x7fffffff</deviceId>
<deviceType>0x7fffffff</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_SECURITY</commandClass>
<commandClass>COMMAND_CLASS_SECURITY_2</commandClass>
<commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
<commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
<commandClass>COMMAND_CLASS_TIME</commandClass>
<commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map"/>
<endpoints class="concurrent-hash-map">
<entry>
<int>0</int>
<endPoint>
Don’t worry about this. After 232, the nodes will wrap back around to 1 and fill in the gaps where there are no devices.
Just to confirm, you are performing the inclusion through OH and not directly with an unplugged Aeon Zstick?
In your controller Thing settings, what do you have for Z-Wave Network Settings> Secure Inclusion Mode? This is best set to Entry Control Devices. Set the zwave binding to DEBUG and tail your openhab.log file during inclusion and while waiting for the device to initialize. Sometimes it helps to restart OH. Have you tried excluding and then hard resetting the lock? After secure inclusion, just wait with it in the Inbox.
Just to confirm, you are performing the inclusion through OH and not directly with an unplugged Aeon Zstick?
Yup the gen5 stick has been plugged in and all done via OH.
Just set inclusion mode to Entry Control Devices. It was set to not use security.
Will see if that works. I’ll pull it off and try it again closer to the stick.
That will make a big difference!
After enabling security, try the inclusion where is installed. Newer devices are much better at secure inclusion from a distance. You may be surprised.
Oh yes, this is a great point too. I have this working and here’s the controller config in Habmin.
I also agree you can fairly safely ignore the old “include from inches away advice.” Yes, I used to do this in the early days of zwave, but I’ve been able to safely include where installed for most devices for several years now, even for locks.
Well I’ll be! Sure enough … tried to do an inclusion after changing the Secure Inclusion Mode… worked fine. Thanks for helping me out! I was going crazy… That might have been the last thing I would have checked too. I left it installed, pretty far away from the controller and was discovered fine. I did worry that it wouldn’t update the status of the lock based on manual locking as some of the older ones were reported. But seems fine. So I have 3 channels - Door Lock, Alarm(raw) and Battery Level.
Any luck adding access codes or changing them without setting it via the REST API? I don’t see much documented there but looked like it was possible to do in HABmin?