Nothing. You have no control over it other than to unplug you hub.
Yep, same issue. Hub firmware update is causing my Schlage FE599NX locks to continuously go offline, then come back online a few minutes later.
My phone is receiving 100+ alert notifications throughout the day.
Hopefully a firmware fix is released soon, and not take several months.
I tried two Chat sessions with ST Support and got nowhere. They said to delete the locks, Delete the app from my phone and tablet. Reset my router and I said to stop there as itās 1200 miles away. I then called ST support and gave them the case ID from the chat. Found out that it meant nothing to them, start all over. Went through the entire story, including that the hub/Schlage locks in question are 1,200 miles away and I cannot remove the devices/re-add them. I cannot reset my router. She said itās beyond her and she would move it to Tier 2 support. She also said Iād receive an email confirming (new case ID). That didnāt happen. Over the weekend I received over 30 notifications and mentally chalked them up to this issue. Late yesterday I started to count the number of times they hadā¦ there was a reply from Tier 2 Support in the notifications. The instructions were, Delete the devices. Remove the app. Reset the routerā¦. I went back to look at it for this post and that notification is gone. Not sure what that means.
I have already removed the device twice, deleted the smartthings app rebooted the router, rebooted the hub, reloaded the app, added the lock back into smartthings and it did not fix anything. Itās obvious itās the latest firmware update causing the issue. The issue does not happen when I pair the lock to the Ring Hub. Itās only a smatthings firmware issue.
@RBoy Maddy, can you confirm if your āpaidā edge drivers have this issue? The migration ones have the issue for sure. Do you have access to higher level people at SmartThings. This is not a āone offā issue, there are thousands of alerts going off daily to hundreds of users.
Nothing to do with the driver. SmartThings has tweaked the firmware for managing device offline detection. The FE599 is very susceptible to packet loss/delayed and if a single packet is lost (or delayed) it can lead to the hub thinking the device is offline. You should report it to SmartThings support to investigate it. They had recently reverted these changes to make the offline detection less aggressive but itās possible they have re introduced those changes. @nayelyz @alissa.dornbos
Meanwhile your best defence is a strong mesh with minimal delays and packet loss. What that means is remove any dead devices and do a mesh repair and also add a few high quality buffering devices in your mesh
King of hard to mesh when the only device is the lock and hub. The hub is 15ft from the lock.
SmartThings/Samsung isnāt taking the tickets seriously when reported.
They are asking you to reboot, make sure you have good batteries, etc. (trivial stuff)
Thatās your issue. You donāt really have a mesh and the hub doesnāt buffer well. Add a few buffering devices. Itās called a mesh because thatās how it works best.
From this thread alone itās clear that several of us have already reported the issue to SmartThings support with little/no useful response. Thatās concerning. While I understand specific hardware may be more or less sensitive to packet loss, Iāve also been on this platform with this same Schlage FE599 lock for over a decade without issue.
Additionally, I have direct access to a different SmartThings mesh WiFi hub running firmware v52.21 linked to an identical Schlage FE599 lock that continues to run flawlessly, with even greater distance and less repeaters between lock and hub, further evidencing the firmware-introduced changes as the culprit.
If there is a way to revert the firmware on my multiple-impacted ST hubs, please do let us know back here. This has significant and direct impact to my business and it pains me to think of leaving the SmartThings ecosystem after a decade of time, but my business runs on automations and lock management. If those automations are wholesale broken, thatās a major business liability for me going forward.
A prior firmware update a few years back knocked out thermostat control for weeks. That was a challenge, but workarounds existed. This issue of losing access control of buildings hundreds of miles away is far more serious. Thatās particularly true when the specifics of the communications drops make even the fallback first party Smart Lock Guest Access tool too flakey and inconsistent to use for manual code management - the only consistent way to get these locks working is to continually push remote reboots to the hub, then quickly set a lock code before the hub times out, overflows its cache, or whatever else is happening with the local control disruption.
Thatās actually not true. The mesh is a feature, not a requirement of the protocol.
This is an age old problem. Thatās what LUM, RLA, LMAPI did best - handle mesh problems, delays, losses, timeouts, out of order etc. If you have a good strong mesh to begin with, which takes work to ensure you have the right components and brands, it will ease the pressure significantly. Some brands (like specific GE models, some Aeotec models etc) can create havoc with the mesh and make things worse. Check out the various FAQ to help on how to root out faulty components, add in a few good ones and itāll make a huge difference. You should not ever have to reboot the hub just to program a code.
If a recent firmware update made issues with offline status a problem then ST should also look into it. But AFAIK the last beta update has resolved that issue which was introduced during a previous beta update. Maybe the staff can comment on it.
How does one get oneās hub into the beta channel?
I believe if you signed up now ā¦ you would not begin until beta 55 is released.
This doesnāt have any meaning for me having no context for what the current beta is. Whatās the timeframe for these beta seeds to drop?
darn itā¦ I thought the 54.X on the thread would have indicated the current beta
so to provide context - the current beta is 54.X 
So to clarify, the $1m question is whether we are talking about weeks or months before the next beta seed? Historically, whatās the cadence look like?
ST does not provide timelines
Maybe this update will help your problem.
While Iām having the same issue of the lock going offline, my biggest problem is the app no longer will control the lock. I canāt lock or unlock anymore. The app will show the lock status change when the door is unlocked or locked with the buttons or codes. Is this related? Would the Aeotec Z-Wave range extender help?
I put an Aeotec Z-wave extender in. No improvement. Lock is 10ft from hub, z-wave extender is in the middle.