m_venice
The driver was pushed to Rboys subscribers and I turned on the new option with repeaters within 6’ of the FE599s. Still waking me up with multiple online/offline notifications - day and night.
If it’s happening with the new driver I’m suspecting packet loss or communication issues with the lock. Other have reported that it’s fixed the issue as it’s increased the communication frequency with the lock so the platform should never make it offline.
I would suggest changing your lock batteries, doing a zwave repair and if it still doesn’t fix the issue then look a the logs to see if the lock is responding to the driver, if it isn’t then is a lock / mesh issue.
@Pejorative it’s the older model SmartThings Connect Home model that continues to work just fine with Schlage FE599 locks, since the firmware was never updated beyond v1.2.00.3040 (which is before the problematic firmware release).
A comparison of the different Samsungs hubs is still available off the Canadian Samsung site, which unlike those of us in the USA, are not busy closing down useful websites. You can find plenty of those older Connect Home hubs off eBay or other sites. Note that I didn’t have any luck getting a SmartThings Connect Home Pro model working, just the standard model.
It goes without saying that there’s undoubtedly dozens of other security fixes in each subsequent Samsung firmware release so it’s not awesome to continue leveraging hardware that’s no longer receiving security updates, but given I’m still building out my HomeAssistant workflows, it’s enough to get me by until I can wholesale swap out my entire Samsung ecosystem.
Purchased the app/driver. Hopeful to fix my issues with my fe599 that was previously working flawlessly. Enabled driver, but maybe I’m missing something.
You say theres an option in the setting page? What option and where?
Also some people say they can get connection after forcing a reboot? How can I force it?
I would be ok with an added step to get a reliable connection when I need access.
A firmware update to resolve this issue is now in beta.
Try to sign up for the beta but it states the opportunity isnt available
I have a SmartThings hub in beta on firmware v56.6 that seems to be free of the on/offline problem for past week or so. Aeotec hub still on v55.5 and going on/offlne still.
I confirm that this appears to be fixed now. I am on firmware version 56.9 and there are no more offline/online issues.
Seems fixed at both my houses (both in USA). Super glad they got to this…
I have the Aeotec Hub (FW version 000.057.00014) and still experiencing two Schlage Connect Zwave Plus locks go offline. I have a third Schlage non-plus zwave version that does not have this issue. I was always consistently able to put the lock back online when physically locking/unlocking it. I’ve enrolled my hub firmware enrollment to “beta” as I read that the beta firmware has fixed this issue. Is there a way to force update the hub? I would like to verify that the issue has been solved on beta as the issue is still persistent with the public firmware.
That firmware has long since gone into production. What you’re experiencing is likely Wave packet loss issues. Have you tried adding some repeaters and doing a Zwave repair?
I also have started to see this issue with this same lock. V3 hub with FW 000.057.00014.
I have 3 of the locks and they all started going offline within the last few days. I have several ZWave Repeaters and doing a repair does not seem to help. They will randomly reconnect but usually within a couple hours show offline again.