I have removed three Yale Assure Z-Wave Plus touchscreen locks from ST and, after several tries, gotten them added to HE. (In case helpful for someone else: I found that removing all user lock codes before adding to HE and then adding the codes back via HE/Z-Wave, rather than manually at the device, helped resolve some issues.) HE assigned each of them the built-in Generic Z-Wave Lock driver, which I have generally found okay for my purposes.
One thing I have noticed in the HE logs, however, is that HE's built-in Generic Z-Wave Lock driver seems to want to fetch a lot of nonexistent lock codes: HE has been trying to fetch 50+ lock codes from one of my locks that has only three user codes, for example, and the driver seems to start fetching more lock codes whenever I try to add/remove a code. The lock seems to respond to a few of these fetch requests (always with "null" codes) and then seems to give up or something, as the driver's "fetch" loop appears to hang and stop (until I try to add/remove a lock code, and then the fetching loop starts again where it left off).
Is this normal behavior? I would think that looping secure requests like this would be not only unnecessary but also very burdensome on the Z-Wave network.
