Over the last couple of days, I’ve been having issues again with my Zigbee devices going offline and coming back online. This is after 20 days of no problems since moving from the Station back to the V3. These issues have been happening ever since my Station updated to version 58.10 on 9/29/2025.
Surely, after 48 days, engineering should have some idea of what they messed up in that firmware upgrade! If they’re not going to properly test firmware updates before pushing them to our hubs, there needs to be a way to opt out of these updates until we choose to upgrade—or at least after the update has been out for a while.
This time of year, people rely on SmartThings to control their heating and other vital functions. It doesn’t seem like we’re asking for much—just a simple switch in SmartThings to opt out of firmware updates.
The engineering team mentioned that there are some changes in the firmware version 59.5 or higher that should help with the issue you’re experiencing in the V3 Hub. The current one is 59.6
Would you be willing to enroll your hub in the Beta group to receive this firmware version and see if the issue is resolved?
There are two options to do this:
You agree and since we already know your Hub ID, the engineering team will add you manually. The difference is that if you choose this one, once the Beta version 60 is rolled out, you will be removed from the Beta Group automatically.
You go to https://my.smartthings.com/advanced/hubs and change the value of “Hub Firmware Enrollment” from “Public” to “Beta”. This will add you to the Beta Group and won’t remove you until you decide to unenroll and change it back to “Public”
I’m willing to try anything at this point — it’s very frustrating. If I do this and it completely blows everything up, is there any way to roll back to version 58.10, or am I stuck on the beta version until the next production release rolls out?
In Option 2 under Hub Firmware Enrollment, why can’t there be an option for None? That would prevent this entire scenario. I could leave it set to None until I actually wanted to update the firmware.
Please bring this up with engineering — this is a desperately needed feature, and it’s available on every other platform I’ve used.
Let me know if I’m permanently stuck on beta or if there’s a path back. Once I have that information, I can decide what to do next.
Hi, @mlchelp
The team mentioned you would be removed and go back to the latest Customer/Production version, which is 58.X in this case. So, do you agree?
Ok, thank you for the feedback I shared your comment with them.
Please also let engineering know that whatever they’ve been doing with Zigbee over the past 8 to 12 months is causing all of the Zigbee devices to burn through batteries much faster than before.
My motion and leak detectors used to last 1.5 to 2 years on a single battery. Now, on average, they need to be replaced every 3 to 6 months — sometimes even sooner.
Something clearly changed, and it’s having a significant impact on usability and maintenance.
I’m on the beta software now, and so far, so good. The reason not everyone is seeing this issue is because most users only have a handful of devices. For them, the available memory and CPU—despite all the new Thread and Matter features being enabled—are sufficient.
However, for power users with 100 to 200+ devices, the CPU and RAM just aren’t enough, especially with all the added Thread and Matter services. These hubs are severely underpowered, particularly the Station. I saw major improvements after switching back from the Station to the V3.
No one at Samsung seems to know—or is willing to say—what the CPU or RAM specs are for the Station. I haven’t looked into the V4 yet, but I’d bet it’s also underpowered. They likely design them this way to keep costs low.
That said, I’d gladly pay $400 to $500 for an upgraded, high-performance SmartThings hub, given that I manage over 200 devices.
Thanks for the information. When the Station first came out, no one at Samsung seemed to know what the CPU, memory, or flash specs were. I asked the support people here and even called Samsung directly. They only disclosed that the processor was an MCIMX6Y1DVM05AB and said they would not publicly disclose the memory or flash.
I highly doubt it has 512MB of RAM or 4GB of flash! My V3 can run circles around the Station. I would have never purchased it or done the hub replace from the V3 to the Station if I had known that. Now that I’ve switched back to the V3, I realize how much quicker it is.
My Station is going on eBay!
Do you have confirmation on the V4 specs?
Hi - I am having the same issues, for weeks my hub keeps connecting and reconnecting over night and it also usually happens some time during the early evening but I am not notified that it does; I just know it doesn’t because of my bulbs won’t turn on from the motion sensor. That lets me know that I have to go un-plug/re-plug in the hub and then it will work until it happens again. This is a daily occurence.
I also have the V3 Hub and my current firmware is the 58.10. Can I get on this list for the beta firmware as well? My hub has been working flawlessly since I bought it and this is a daily issue that is trying me mad.
That is easy to do. In the Adavanced Web App go the the Hub section, tap on your hub and look for Hub Firmware Enrollment and change it to Beta. Your hub should get the next release of the Beta Firmware when it gets pushed out.
