Schlage locks going offline/online

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.

1 Like

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. :slight_smile:

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.