Kwikset. I have those in my residence. I’ll be changing the Schlage lock in my vacation cottage next spring.
1 Like
Scratch that - the lock is still going on and off line despite the new Z-wave repeater.
1 Like
I removed the Schlage from Smartthings and linked it to a ring alarm and no longer have any offline issues. Then basically created the same routines in Alexa as I had in Smartthings.
That’s completely logical since this is a Samsung firmware issue. I can also confirm the locks work perfectly with Home Assistant. No drops. No flipping status. Just work.
If this was truly caused by a patch from the supplier of Z-wave chips, Silicon Labs, then it’s possible that as other hub manufacturers apply this patch you’ll see the same problem.
Conversely, if other hub manufacturers have applied this patch without causing problems, then it’s something Samsung did.
This requires a push from those in the user community to get Samsung to work with Silicon Labs and Schlage to find a solution. I don’t have a Schlage lock so it won’t be me but someone needs to be relentless in pushing Samsung to act collaboratively to solve this.
Maybe we could start with something more basic: how does one even reach support beyond the initial Samsung support team that replies from an unreply-able email?
I work with a lot of different companies, but rarely one as unreachable as Samsung.
Send a message from within the app. They reply there.
I’ve replied to Smartthings and begged them to also contact Sci Labs in addition to Schlage. I requested they try to figure out a resolution between the three entities so we all don’t have to spend hundreds of dollars each to replace the locks. I will now reach out to Sci Labs with the info listed above. I would think the more people that contact all three the better our chances of a resolution.
1 Like
So is it SiLabs and not SciLabs like ST said?
1 Like
I searched around the SiLabs site and can’t find a way to contact them but I did find this from May of 23:
1 Like
It’s Silicon Labs, and their website is silabs.com
Also, note that their release notes for the Z-Wave SDK states this: “Backwards-Compatible: Z-Wave certification mandates backward-compatibility. The first Z-Wave devices on the market, more than ten years old, still perform as intended in networks with the latest Z-Wave technologies.”
I don’t have a Schlage lock, but if I did I would be pushing Samsung hard to resolve this.
3 Likes
The latest release of firmware for the hub is being released now version 55.4 is the new one it replaces 54.14
1 Like
That’s not the correct SDK. v.7 SDK series specifically targeted for 700 and 800 series chipsets. As far as I know, all the ST hubs are still using 500 series chipsets.
It’s probably the SDK 6.85.02 that did it:
6.85.02 GA 1-MAR-2024 Active
6.84.00 GA 21-JAN-2021 Monitored
6.82.01 GA 13-APR-2020 Obsolete
Based on timing (not to mention the huge gap inbetween releases), and the release notes I suspect it’s related to this:
https://nvd.nist.gov/vuln/detail/CVE-2022-24611
If so, then I’d expect neither SiLabs or ST to budge this (nor should they, tbh). If this indeed the case, the right company to speak to is Schlage (and tbf they’re probably going to just tell you to buy a new lock).
I’ve had some Kwikset locks with 500 series chipsets suddenly begin dropping out of ST this year. I went through all sorts of fix attempts. I can’t help but wonder if this is related… As of now they are working good enough. But I switched over to HA, and got an 800LR controller so a drastic change I doubt most will be willing to even consider in here…
1 Like
Kwikset locks are known to have issues with their chips after a few years.
For security reasons, they should have allowed monitoring only. No active changes to the locks. And constantly going offline then online is not a valid solution. As it stands, I will use my door bell camera to see who enters and leaves and use the combo lock as a dumb lock. Or I will switch to an alternate system that still allows the lock to work (especially logging the users coming in). Either way, they are not improving security, they are lowering it and simply transferring culpability to the lock owner. Sounds like the future of “smart things” will be getting dumber by the decades.
2 Likes
Switching platforms to ring. It seems that no one in Samsung does know how to revert to the October 21 firmware update or simply they want to take out the locks from smart things to make you buy new ones from a sponsored brand. Usually is the latter one. They did it with wemo.
2 Likes
Schlage FE599: works great on Alexa/Ring, works great on HomeAssistant, doesn’t work at all on SmartThings subsequent to the 54.13 firmware update. Pretty clear where the problem lies here, particularly since my SmartThings Connect Home hub running on the older firmware continues to hum along with the same Schlage FE599 locks just perfectly.
I bought both a SmartThings Connect Home and Connect Home Pro hub that I’m working to try and get online this week to replace the firmware-upgraded v2 hub, but if I can’t get those onboarded because Samsung’s decided to blacklist devices running an older firmware version, I’ll circle back here with a rundown of how others here can migrating over to Home Assistant, which is proving far better supported and versatile than anything I’ve seen in the post-Groovy SmartThings world.
2 Likes
Should those platforms implement the security fix that ST did, they could also have issues.
2 Likes