I got SmartThings to run the script to fix the issue. I was also told that I had to delete the custom DTH and unpair/pair the lock again with the standard device handler. Is that true or can I still use the RBoy custom handler? And do I need to delete and recreate it?
There is no need to delete any handlers. Please do NOT exclude your lock or you will need to have the script run again.
Running the script with either the stock device handler or the Universal Enhanced Z-Wave lock device handler installed is okay. In either case the notifications will start working after the script has been run successfully.
Itâs okay to switch device handlers manually from the IDE after the script is run but do NOT exclude the lock after the script has been run otherwise you will lose the notifications and the script will need to run again.
After they ran the script, i still was not getting notifications. Their email said to delete the custom DTH, then exclude and rejoin the lock using the standard z-wave lock handler.
That would indicate that it didnât run âsuccessfullyâ. When executed correctly and received by the lock youâll see it start sending push notifications instantly without having to do anything from your end (as you can read from the experiences below).
A few things to note about how this works:
- The script that I worked with Tier-2 to create and then test sends an association command which tells the lock to send unsolicited notifications to the hub (ie push notifications). This command is the workaround for the auto encapsulation issue which has been fixed in the upcoming 0.31.x firmware.
- It doesnât matter what DTH youâre using (the command is DTH independent) just as long as the command reaches the lock. If the wrong lock ID/hub ID is used in the script or the mesh loses the command or the lock is unreachable then the command would need to be sent again. As soon as the lock receives the command it will immediately start reporting notifications. This has been tested and confirmed with the stock DTH and the Enhanced DTH and the results are instant when executed properly and received by the lock.
- When the lock is excluded, it resets itâs association with the hub and the lock will not longer send push notifications until it receives a new association command (i.e. the script is run again). Again this is specific only to FE599/BE359 due to the way they associate with the hub for sending push notifications.
Feel free to switch your DTH, get notifications working and then switch back to your original/custom DTH if that works for you. Just keep in mind that you will need to ask support to run the script again every time you exclude and re-pair the lock.
So I have 2 locks on 2 separate hubs. They were able to get one to work and this is the message I received after several days on the other one:
Thank you for being positive and patience with us.
Upon checking the account, we see that the lock has a custom device handler on the lock. You will need to exclude the lock and delete the custom device handler, then add the lock back with the standard device handler.
I thought for sure I was on the right path when the tech got one to work. I will keep asking, but it is very frustrating.
1 Like
So even after reading this extensive thread about all of the problems, out of desperation bought LUM just as a gamble for an FE599NX. Well unfortunately I have now blown $240 on a lock that will not work for what I need. Basically, user access notifications. Just for reference, I just bought the FE599NX and a new ST V3 and thought hey, maybe its all worked out. NOPE! No good. Do I jump into endless communications with all parties or take my lumps and just buy something that doesnât take a year to get working? It is actually for an install on a businessâ door. The door has no way to add a deadbolt. I have a Schlage Sense on my home front door and it works flawlessly. This is sad.
I was up until 2 am trying to figure this out. You are 100% correct, very frustrating. And I just started with these products.