Push Notifications for Schlage Lock Not Working (April 2019)

I am using the mobile app with Lock Manager for a Schlage lock on an iPhone XR. I recently realized that the Push Notifications were not longer working. I went through the posts here and removed my Contact Book and all the related instructions but that did not change anything. Any suggestions on how to get this working again?

Thanks

1 Like

There were changes to the platform and hub firmware last week which may be related to the issues youā€™re taking about.

The other option is to revert to the stock ST DTH and use the ST SmartLocks app or try a lock managment app that works with the stock ST DTH like (if you have access to RBoy Apps)

Greetings! New ST and RBoy apps user. I just installed LUM and the Enhanced Zwave Device Handler today. So I should have all the updated Device Handler firmware (04.03.06) for the new v3 25.x firmware. However, I cannot get any push notifications from door code entries. Under ā€œGeneral settingsā€ā€“> ā€œNotificationsā€ --> ā€œPlay notifications on these devicesā€ it says ā€œNone Availableā€ and Iā€™m not able to add anything. I also added a phone number under ā€œSend SMS notification toā€ but it doesnā€™t text me anything when the code is entered.

Programming codes is going smoothly with LUM. I also have a ZWave repeater installed between the hub and lock (Schlage FE599).

I appreciate any help!

Thanks

Welcome to ST.

You need a compatible Text to Speech audio notification device like a Sonos or Echo Speaks (Alexa) paired to your hub to announce the push notifications.

Check that you havenā€™t enabled the Disable all push notifications option in the Notifications page, because that option disables all notifications.

You need to check if the lock events are reaching the hub. The easiest way to do this to open your ST classic app ā†’ My Home ā†’ Click on your lock (FE599) ā†’ Click on the Recently tab. Now unlock your lock using your code. You should see an event pop up here saying that The door was unlocked by user xxx.
If you donā€™t see that event, then your lock events arenā€™t reaching the hub which is why you arenā€™t seeing any notifications being pushed. This indicates a mesh problem. Try moving your repeater closer to your lock, hub away from the lock, reboot the hub and then do a Z-Wave repair. Once the message shows up in the Recently tab you should start getting push/sms notifications

1 Like

Thank you for your quick reply and suggestions. I checked in the Recently tab and do not see unlock events popping up, so that may be the problem. The repeater is close to the lock, but so is the hub (one floor below). I tried spacing them as far as I can (given the hub is wired currently to the router), rebooting and doing a repair, but still no luck.

Iā€™ll have to either run it further away with an ethernet cable and try again, or figure out how to change the hub from Ethernet to Wifi without resetting the hub (havenā€™t been able to figure out how to do the latter easily).

Iā€™m having the same issue. Iā€™m not getting any response after doing all of the above.
I am using RBOY Enhanced Z-Wave DTH and Using Lock User Management App.

  • fw: 43.37
  • manufacturer: Schlage
  • networkSecurityLevel: ZWAVE_S0_LEGACY
    Is there any additional things I can do to try and resolve this? I would like to subscribe to the codeunlock notification that another app I have I can subscribe to for additional functionality.

Iā€™m using ZWave Plus GE EZSmart Outlet ZW1002 as the potential repeater. I say potential because I donā€™t know how to be sure if the outlet is actually being used as the repeater.
Any suggestions would be helpful.

This is normal for Z-Wave devices which donā€™t support S2 with the new hub firmware. If itā€™s shows Failed then you need to reset and re-pair the device.

Did you check if the event messages from your lock are reaching the hub?

You need to check if the lock events are reaching the hub. The easiest way to do this to open your ST classic app ā†’ My Home ā†’ Click on your lock ā†’ Click on the Recently tab. Now unlock your lock using your code. You should see an event pop up here saying that The door was unlocked by user xxx .
If you donā€™t see that event, then your lock events arenā€™t reaching the hub which is why you arenā€™t seeing any notifications being pushed. This indicates a mesh problem. Try moving your repeater closer to your lock, hub away from the lock, reboot the hub and then do a Z-Wave repair. Once the message shows up in the Recently tab you should start getting push/sms notifications

Assuming itā€™s running on mains power, open the device in the IDE ā†’ My Devices ā†’ Click on your outlet and look at the raw description. The zw should start with a Ls or a L and of course the device should be closer to the lock than the hub.
You can reboot the hub and do a z-wave repair and look at the hub event logs to ensure that no zwave failures are showing up for the GE device or the lock.

  • IDE ā†’ My Hubs ā†’ Hub Utilities ā†’ Reboot hub
  • IDE ā†’ My Hubs ā†’ Hub Utilities ā†’ Z-Wave Repair
  • IDE ā†’ My Hubs ā†’ List events (keep refreshing every minute until you see Z-Repair Wave finished and look for any errors before that message and after Z-Wave Repair started)

Ok. Still not working. No events coming back from the lock in the app. More detail about the layout
The lock and the outlet are about the same distance from the hub, about 20-30 feet. But close (6-7 feet) from each other. The outlet is visible on the hub and can be turned on/off. When manually changing the I have a Z-Wave switch and an outlet (1 foot from each other) between the outlet close to the lock and the hub.
Layout:

    hub --(15 feet)-- switch & outlet --(15 feet)-- outlet 
                                                  |
                                               (7-feet) - lock

Switch: GE Z-Wave Fan control:

Label Value
Data networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE
Raw Description zw:L type:1108 mfr:0063 prod:4944 model:3131 ver:5.22 zwv:4.54 lib:03 cc:5E,86,72,5A,85,59,73,26,27,70,56,2C,2B,7A role:05 ff:8400 ui:8400

Outlet near lock: GE Z-Wave+ Outlet: (both outlets in layout are same make/model)

Label Value
Data * MSR: 0063-4952-3133
ā€” * manufacturer: Jasco Products
ā€” * networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE}
Raw Description zw:L type:1001 mfr:0000 prod:0000 model:0000 ver:5.24 zwv:4.38 lib:03 cc:5E,56,86,72,5A,85,59,73,25,27,70,2C,2B,7A role:05 ff:8700 ui:8700

Iā€™m going to try physically rebooting the hub and repairing the z-wave network.

  • Result: This did not work.

Any suggestions?

Thatā€™s the crux, if no events are coming then the mesh is losing it somewhere.

Iā€™m noticed that youā€™re using the older GE/Jasco Z-Wave switche. These tend become problematic. STā€™s engineers have noticed issues with overheating and weā€™ve seen other issues in our labs (I wrote about it on a Z-Wave repeater topic).

I would recommend either switching to the newer GE Z-Wave Plus switches or resetting the switches (use the air gap if itā€™s there otherwise cut the mains for a few seconds). Then reboot the hub and do a Z-Wave repair. Worst case you may need to exclude the older Z-Wave switch from your network, do a Z-Wave repair.

I still canā€™t get this to work. Iā€™ve moved the ST hub further away, put the Aeotec ZWave Plus powered repeater closer to the lock. Iā€™ve tried the reboot and repair Z Wave network. I still canā€™t get any activity notices in the Recently tab. Is it something with the lock that it is not reporting events? I find it hard to believe that the hub is not receiving these notifications, either through the repeater or directly after following all these steps. Not a single notification. If these notifications donā€™t work, I donā€™t have much use for the LUM app since I got it specifically for the notifications.

Any other suggestions?

Thank you!

Try to reset your lock, exclude and re pair. Otherwise contact Schlage for a replacement, it could be a bad module.

I tried those suggestions including factory reset, exclude, repair. Still doesnā€™t work.

I also obtained a second new FE599 lock and set it up but still no keypad unlock notifications at all. So, unlikely a ā€œbad moduleā€.

The Schlage firmware is listing 43.37 on ST. Is it something with this current fw?

Any other ideas?

Open the IDE -> My Hubs -> Utilities -> Click Send hub logs

Tagging @Kianoosh_Karami

Only ST can help figure this out

If youā€™re using a custom DTH delete it and try then. Sometimes when using a custom DTH since it runs in the cloud it adds a delay which can cause the pairing to fail due to timing issues.
If it pairs without any custom DTH, you can the add custom DTH back afterwards.

@RBoy Thanks for pinging me.

@RB03, Would you please reproduce the issue and do ā€œSend Hub Logsā€ and I will take a look at the logs and can provide more details as to what is going?

1 Like

Hello @Kianoosh_Karami -

I just sent the hub logs. When I enter the keypad code, there is no report of the unlock to the hub. I appreciate your help.

@RBoy - I am using the RBoy Universal ZWave Lock with Alarms device handler - are you saying I should delete that? I did try deleting it once already and reverted back to the default ZWave lock DTH but it didnā€™t help.

Thanks

Hey @RB03, My bad, I forgot to ask you to let me know the timestamp that you reproduced the problem. Can you do the following?

  1. Reproduce the problem
  2. Jot down the timestamp (With timezone please)
  3. Send logs
  4. Message me?

Thanks

Hi @Kianoosh_Karami, sure thing, but the problem is that nothing is happening in the logs/events when I enter the keypad code so itā€™s hard to ā€œreproduce the problemā€. The problem occurs every time I enter a keypad code because nothing happens. The @RBoy Lock User Management SmartApp is supposed to notify me when someone uses the keypad code. But maybe you can decipher things in the send logs that I canā€™t see. Today 5/2/19, the keyad was accessed several times between 1330 and 1530 US Eastern Time if you can look in that time period.

Unfortunately I am not near my lock anymore to enter the keypad code and it may be a couple weeks until I will be there again. This is all the more reason I am hoping to get the unlock notifications to work - so I get notified when someone uses their designated keypad code. If you can please excuse the delay, I will contact you again when I am able to further test the lock again.

Thank you!

Yeah, I have the ability to look at our internal hub and radio logs, so I can try to understand what the issue is.

Feel free to ping me with the info I asked for anytime you get a chance to reproduce the problem.

Thanks again

Iā€™ve been following this thread to try to find a solution because I am having a similar problem. I also have a Schlage lock and use the LUM app and DTH from RBoy. Everything worked fine until about 2 weeks ago when I stopped receiving notifications from the lock. Iā€™ve updated, repaired, rebooted and still nothing. I can change codes and lock/unlock, but no notifications from the lock. Funny thing is I get notifications from the Door sensor. I thought that maybe the lock had some damage from salt air so I bought a new one and installed it yesterday. Now Iā€™m really frustrated because that didnā€™t help at all. I have the same setup at another unit less than 1/4 mile away and it is still working perfectly. So I thought maybe it is now a problem that I want notifications from both hubs to come to the same phone number. I changed the phone number and still nothing. I did notice that the locks are identified differently ā€¦one is ā€˜Schlage FE369 Z-Wave Lockā€™ on the problem device and the functioning one is identified as ā€˜Z-Wave Lockā€™. Do you think that could be a problem? I have never changed the nameā€¦it must autofill somehow. Any advice? I also sent an email to SmartThings.

ST has been rolling out a firmware update to the hubs over the last month or so and a change in that firmware is causing the missing notifications issue.

We had released a patch for it back in Feb. If youā€™re using the custom ā€œEnhanced Universal Z-Wave Lockā€ DTH, please update to the latest version and it should fix your issue:

If your lock is using the stock ā€œZ-Wave Lockā€ DTH, then the patch for it already rolled into the firmware update and hence nothing to be done for those locks.