Here is the documentation for the module in my lock. Any idea how to get this added into openhab?
I think I figured out my issue digging deeper. My old gen 5 aeotec stick doesn’t support s2 security, I have an 800 series on order to try tomorrow.
There are more potential issues.
First the Zwave JS browser is the database for the Zwave-js application, not OH ZW. Review this to add your device to the OH ZW DB.
Second the OH ZW binding does not support S2 anyway. It falls back to S0 security which should also be supported by the device (per ZW specs).
Third the new 800 chip stick should work, but might need a tweak first, unless you are on OH5M1.
You might want to consider using the Zwave-js application with OH, but all your devices generally need to be on one or the other. I’d recommend using the HA configs or generic MQTT things for now, but there is a beta websocket app being developed for OH5. With zwave-js the three issues above will not be issues.
It looks like it is actually in the openhab zwave database too: org.openhab.binding.zwave/doc/yale/yrd4xxzw2_0_0.md at main · openhab/org.openhab.binding.zwave · GitHub
Ok, so what message are you getting? What information is partly discovered? There are possible issues. The device type:id is different or the inclusion ran out of time. Because of the security I think you need to factory reset to try again. On the controller UI change the wake timeout to 20. Also use debug logging on the next try. Need more info if something else.
I took your earlier suggestion and setup zwavejsui just now with the new 800 series stick and have the lock added. I’ll slowly start migrating things.
1 Like