This is a classic "If it ain't broke, don't fix it" moment, but I want to check if I am missing anything before I revert back.
I'm slowly working towards migrating all my non-Z-wave Plus devices to Plus devices. My Kwikset 910 Deadbolt was a non-Plus unit so I bought a Plus PCB module off ebay. Including the new unit and exluding the old unit was super easy. On the Plus PCB, the HE hub will send the lock/unlock commands, however ANY manual interaction with the lock is not updated back to HE without hitting the Refresh button within the UI. My non-Plus PCB would report it status back within 5-10 seconds if it was manually locked/unlocked. I also noticed that the LastLockEvent appears to be missing from the new Plus PCB module. This and LastCodeUsed were two variables that I would use as triggers.
The lock was seen as a Schlage upon inclusion and I changed it to use the Generic Lock drivers. I did the Configure button thing shortly after inclusion too. To me it seems like the newer Plus PCB is defective in not reporting its status where the non-Plus module did. Before I start to revert back to my non-Plus PCB module, I was curious if there is anything I'm missing or need to do?
I have 4 wired switches about 3 feet away, so I don't think it's a beaming issue.
Partial pairing could be a possibility? Is there a way to tell that? I didn't remove the lock off the door when I paired the non-Plus PCB nor the Plus PCB. I was running Vera before HE and the lock was near the end of the devices I migrated over.
Zwave plus barrier devices go into whisper mode where the transmit power drops to next to nothing to prevent the pairing to be picked up by a snooper. Bringing the lock close to the hub or hub to the lock for this helps a lot. You might be able to see something from the zwave details community app or maybe the zwave settings page. A close pairing would be the first thing I try though.
Kwikset 910 should use the Generic ZWave Lock driver and be fully functional. (Always pairs as the Schalge FE599/BE588 and needs to be changed to work.) The plus version of the lock uses the 500 chip so it should be paired S0.
The Generic Zwave Lock driver. Both the Plus and non-Plus are/were setup the same but behave differently.
The non-Plus would report its status back after any manual or keypad updates, along with the LastCodeName variable.
The Plus does not report anything unless you force a refresh, and there is NO LastCodeName variable.
Yes - The Plus version is paired as S0. It is also directly connected to the Hub.
I'm going to exclude and include the lock again this weekend, but have the hub and lock a few feet apart from each other. I'm curious if there are any other 910 lock users here with a z-wave Plus PCB module that are getting status updates and the LastCodeName variable.
I have 3 of these locks and they are problematic in signal/RTT numbers.
There are Aeotec 6 repeaters nearby but they never use them.
I have a piston running on my network to refresh a few items including all 3 of these locks as they don't update.
I really want to try the ZB modules but I can't find 3 new ones anywhere.
Just an update to this thread. I excluded and included with the lock approximately 8 inches above the hub and fixed all the rules, variables, apps, etc.. The lock was still missing the lastCodeName variable. And it still would not update its status. Excluded the Z-wave Plus module and went back to the original Z-wave module and everything is back. And lickety split too. Within a second or two of manually unlocking the lock, the hub was updated.
Moral of this thread. If it ain't broke, don't fix it. Lucky for me, the ebay seller refunded me.
