AlCalzone

Hope that answers some of your questions. I'll let the bot create an import from the Z-Wave Alliance DB which can serve as a starting point. @zwave-js-bot import config 4028...

The locks aren't necessary really. We've only noticed that https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x0129/templates/yale_template.json has a few different definitions for the auto-relock that should be unified. This includes renaming the `manual_relock_time` template there and...

Not sure how this was supposed to be working before, but Z-Wave JS has never done any repeated polling nor has it been refreshing until a status has stabilized. What...

Similar, but not entirely the same --> https://github.com/zwave-js/node-zwave-js/issues/5028

You'll have to start with a fork and ideally a branch in that fork. You can then either edit the files in the branch and create a PR for that...

Interesting - we have this with a matching device ID under Wintop: https://devices.zwave-js.io/?jumpTo=0x0097:0x6131:0x4501:0.0

The Alarm (or rather Notification) CC is supported. Depending on which application you use, these reports may show up as events and not as values.

Looks like you haven't configured the device to recognize that tag yet. This is from the device manual:  You need to take the user code that is reported in...

@kars85 your issue is most likely a reception issue of some nodes. It starts at 9:14:39 (`2022-09-21T02:14:39.121Z`) with you locking Node 15. That command takes 10 seconds to be received,...

@jcam try to do the same first, then I can look at some logs