Alfred DB2S lock sync issues

Built-In Apps and Drivers Built-in Drivers
1

Hi I have Alfred DB2S lock. Alfred z-wave Driver reports this version info:
Version Report - FirmwareVersion: 1.03, ProtocolVersion: 7.13, HardwareVersion: 3

Hubitat version: 2.5.1.183

Driver is unreliable when it comes to receiveing sync updates from the lock. Otherwise, I can use driver to lock/unlock Alfred.

In certain situation (at the moment I cannot identify actual steps to reproduce the problem), lock gets engaged, either by Auto-Lock or manually locking, but status, event, is not reported to the Hubitat. Hubitat thinks that lock is unlocked. When I check Alfred interface, both Lock and Alfred WIFI hub, they show correct lock status.

Any suggestion how to debug this problem? How to isolate if problem is in Alfred's Zwave or in driver?

Should I use Generic lock driver or Alfred lock driver?

I'd really like to use lock to arm/disarm HSM (one of the reasons I was looking for the smart lock), but with unreliable lock state reports to Hubitat this is impossible.

Thanks!

2

Can't really comment on the DB2S lock, but with the DB2 version, the built in Alfred Lock Driver works perfectly, I'm wondering if it might be a Z-Wave signal issue, I've seen many people here talk about Z-Wave signal for locks being very sketchy and often add a repeater near the door(s) to help have a reliable connection. Not sure if it has anything to do with the motor in the locks or what but you might want to try that, I have had reliable operation probably because near every door I have a Zooz switch and/or dimmer to relay a solid signal?