See my link above, the hub does a bad job of buffering packets required for FLiRS devices. This you have packet loss. You need atleast one buffering repeater.
1 Like
Thanks RBoy - more helpful than ST, However, I am somewhat novice here and do NOT understand what to do or where to start. I have over 100 smart devices, so I donāt know how to find what is the "trouble device or devices. Is there anyway you can dumb this down on how someone like me can figure this out or what you are saying and I can easily do to troubleshoot? Thanks in advance, BG
2 Likes
Exactly, that answer doesnāt add up. How come Iāve had this exact setup for 10 years and never ever had my lock go offline one single time, and now itās constantly going off line, and noting has changed on my network devices in a year. And itās happening to hundreds of people that didnāt have issues either. Not accepting that as the issue, itās obvious that the firmware changed something that is responsible.
2 Likes
Agreed. 6 years for me and now thisā¦
1 Like
Thanks @RBoy - definitely appreciate your expertise. I understand these old Schlage locks have some deficiencies with regards to Z-Wave, where a repeater is highly recommended.
But like others, my setup of ST Hub and lock worked for YEARS, WITHOUT a repeater. In my case, nothing substantial changed - no device changes, no new devices added to the network. Except, of course, Samsungās October firmware update to the ST Hub.
Iāll probably end up buying the damn repeater if it makes this problem go away - I donāt want to change the lock. Samsung should fix their firmware anyway.
1 Like
I have a Leviton Decora smart plug-in outlet that wasnāt controlling anything. The specs on Amazon say itās a Z-wave repeater. I moved it to an outlet about 4 feet from the lock. The hub is upstairs from the lock and Leviton outlet. I had removed the lock from SmartThings, moved the outlet then did a Z-wave repair. I then added the lock back to SmartThings. The lock still behaves the same way. Iād like to see what path the lock is taking to the hub but ide.smartthings.com no longer exists. Is there a new way to check the mesh network?
Looks like itās time to move over to Hubitat, especially if Smartthings is not going to fix the firmware, itās cheaper to make that move than replacing all the locks.
I am in the process of moving over to Home Assistant. I am not getting the feeling of them fixing this anytime soon, if ever. I have all my Zigbee items moved. Iām waiting on the Z-wave adapter and then will move those devices (which include the two Schlage locks).
1 Like
Hi @RBoy and @Itati. While I appreciate the assistance, this doesnāt resolve the issue.
I have 14 devices. Over the course of several days, Iāve set each one offline, with a Z-wave repair after each one, then waiting for several hours to see if the errors continue. I continued this until the only remaining devices are three FE599 locks. The offline/online errors continue.
I even tried various iterations, such as having one plugged-in repeater along with the FE599 locks, but nothing resolves the offline/online issues.
As we know, the problem started with firmware 54.13.
Is there a possibility the firmware will be fixed?
Or do we have to replace our FE599 locks?
Does Hubitat officially support Schlage locks? I bought a hubitat hub prior to ST moving to Edge, but never migrated. I bought it assuming there was support since itās zwave. But when I looked back into moving to Hubitat a few months ago, I started seeing indications in the Hubitat forum that there were known issues with Hubitat and Schlage. At the time, it looked like the platform evolved to not officially supporting Schlage. Maybe it was just an issue with the early versions(s) of the hubā¦ not sure. I would just recommend confirming Hubitat is working well with Schlage before jumping over. 
As a side note, I have had no offline issues with my Schlages and ST, but I did recently upgraded them to zwave plus. My issue was that my Schlages were not consistently reporting some updates to the ST hub. This has always been a random issue even before Edge, but I was looking to resolve it so I could have more reliable security related auotmations. Thatās when I discovered concerns that moving to my hubitat may not be a good idea. Upgrading the locks to zwave plus seems to have improved the reporting, but Iām not 100% sure if it has made it infallible. I havenāt had bandwidth to do a deeper audit.
Iāve been dealing with ST support and sending logs. Got this response last night:
Greetings from Smartthings!
Hi, John! This is Donna. We have received an update from Escalation Team regarding your concern. Please check their reply below;
āWeāve escalated the issue to our devs who will investigate the logs. Other users have reported this issue and the devs are working with the hub team to resolve. We will reach back out if there are any updates, or if any further information is needed. We apologize for the inconvenience and we thank the user for their patience while we investigate this.ā
Thanks.
Would this upcoming update address any of these issues? Aeotec Smart Home Hub/2018/2015 Model Hub Firmware Release Notes - 0.55.4
Weāre screwed. Here is the response from ST:
Greetings from Smartthings!
Hi, John! This is Donna. We have received an update from Escalation Team regarding your concern, apologies for the late reply. Please check their reply below;
"The SmartThings devs(developers) have investigated the recent issue with Schlage locks falling offline after the recent hub update and have provided the following information
This issue is related to a recent security patch from SciLabs (chipset manufacturer) that was deployed to resolve a security advisory. When looking at the hub logs we are seeing these locks are attempting to re-use a specific value used in secure communication. We believe that Schlage was relying on this loophole when writing their firmware for these older locks.
We are reaching out to Schlage to make them aware of this issue. However, the team has decided they will not roll back the SciLabs security patch as it creates a vulnerability for the SmartThings hubs.
Let the users know that we have investigated and determined the issue is related to how these Schlage locks implemented the secure transmission protocol on these devices.
We will not be able to provide a fix for this issue. For additional support, they will need to reach out to Schlage. In the meantime, the user will need to replace the lock with a different model or continue using the lock manually until Schlage addresses the issue."
Thanks.
5 Likes
Thanks for helping get to the bottom of it. It sounds a bit fishy to me, but plausible I guess. Maybe time to try to lean on schlage for a firmware update? Is it even possible to do with these locks?
Since this is affecting the offline status of the lock and not the functionality, maybe ST can put an exception in the offline monitoring module to exclude these locks from being marked offline, which wonāt compromise security - atleast the lock is usable should Schalge decide not to address this.
But yes you should contact Schlage for a proper fix or a new replacement module.
Iām not affected by this so I wonāt follow up, but maybe some of the affected users can contact Silicon Labs (the chipset manufacturer and developer of Z-Wave) and let them know of this, perhaps they can update their patch.
They are responsible for product interoperability and certification, the website states: āInteroperability between all Z-Wave products is the cornerstone of the brand.ā
For those in contact with the SmartThings dev team, maybe push them to contact Silicon Labs as well. Silicon Labs certified those locks as Z-Wave compliant and itās their patch that has rendered them non-compliant.
1 Like
Does anyone have a worthy replacement that (mechanically) works the same way as the Schlage FE599 (disengages an internal mechanism to lock/unlock the lever lock)?
This is one of the most useful components of the lock, and why I have stayed with them for so long: the battery life is extraordinary because it is not physically moving a deadbolt in or out, simply enabling the mechanical lever to open or not open the door.
Worth noting: older firmware SmartThings Connect Home hubs remain unaffected since their firmware has not updated. Getting those hubs online/registered? Thatās another problem that Iām still working through.
1 Like
Thanka for sharing this contact information! I fired off an email to certadmin@z-wavealliance.org and linked this thread. I would urge others to do the same to see if we can drum up enough support to get this fixed in a future patch. Like others, this lock has been rock solid for me. I could replace it but hoping to avoid having to do that!
@RBoy thought you might want to hear more re: my experience.
I bit the bullet and purchased the Aeotec Range Extender 7.
I removed the lock via z-wave exclusion, moved the hub about 9ā away, added the extender, and rebuilt the network.
Then, re-added the FE599 lock.
All seems good - the locks are no longer going online and offline! Yay!
BUT - none of the lock controls work. The lock correctly reports battery and locked/unlocked status. I canāt actually control the lock to unlock or lock it, and I canāt add or remove any codes.
Basically, useless, and now Iām poorer for having bought the range extender to create a āmeshā where there wasnāt one before. Adding the extender to create the mesh did not solve the problem.
Sad to see the update that the issue is a āsecurityā problem that Samsung or its chipset vendor wonāt fix. I have little faith that Schlage will fix the issue on what are now really old and no longer manufactured locks.
I did a quick search and I donāt see any lever locks like FE599 from any manufacturer. Everything is a dead bolt now.