We’re excited to announce the release of Samsung SmartThings Hub firmware version 0.30.5. This release is a hotfix to version 0.30.3. Once downloaded, your Hub will briefly go offline as it reboots and applies the update; most customers will experience less than one minute of downtime. We will update the status page when the release is complete.
Hub Target:
Samsung SmartThings Hub 2015 (Hub v2)
Samsung SmartThings Hub 2018 (Hub v3)
Release Date: 12 May 2020 ~ 14 May 2020 Note that this release may be spread over a few days, so you may not see your Hub update the first day of the release period. We will post on this thread once all users should have received the update.
Release Notes:
Fixes
Change to Z-Wave functionality to accept all incoming Multi-Channel encapsulated messages regardless of the Destination Endpoint value, correcting issues communicating with certain devices.
Fix for a rare problem causing issues communicating with zigbee devices.
What it means: No LAN connection, Hub doesn’t have an IP address
What to do: This is likely an internet connection issue. If your Hub is connected via Wi-Fi, try changing the Wi-Fi network or connect the Hub directly to the router via Ethernet. Make sure your Ethernet cable is securely plugged into the back of the Hub and not loose. If the Ethernet cable is snug but the blue light keeps blinking, the cable may be defective. Swap it for another shielded model. This may also be caused by strict network security settings preventing the Hub from connecting.
Of course I did, mainly my network is perfect, with no issue and nothing has been changed.
Until minutes before everything was fine, after the update, it returned that way
Silent about the rare problem causing issues for zigbee. Interesting. Also saw that this was pushed to everyone, but upon completion of said update I checked my IDE.
Last Updated 2020-05-11 9:51 PM UTC
So are beta users opted out of regular firmware updates? Effectively negating this update and fix for people who need it?
Fix rare issue communicating with the Zigbee radio on the Hub V3 that could result in failures to communicate with all Zigbee devices even though the Zigbee radio is reported as functional in the IDE.
Where did you find that information? If it’s “Fix rare issue communicating with the Zigbee radio on the Hub V3 that could result in failures to communicate with all Zigbee devices even though the Zigbee radio is reported as functional in the IDE.” Why didn’t they just put the entire fix instead of being so vague?
The update that went to the full set of users is the same firmware that beta received yesterday. Because the two releases are bit-for-bit identical, your firmware did not update again.
Thank you for your reply on this. Appreciated. However I still have an issue where all of my zigbee devices have dropped off since 3.03. I have rebooted, kept the hub offline for 30, pulled the repeaters, done all of the steps that are provided.
I’ve spoken to customer service and they are going to push it up a level, saying that it’s possible they are going to send it back to tell me to just delete and re add the devices.
That is not what I should be doing as if this happens again then I would be out all that time, as I am now with trying to figure out what happened.
Wanted to mention that when pulling batteries out of the zigbee devices that the light’s turn green as if it has connected to the hub. Still showing offline since my hub was updated to 3.03.
This sounds right. I have a wifi hub (plume) and after I received a firmware update last Thursday my Zigbee devices slowly stopped being controllable and acting on events.
Fast forward to today… It’s affected my zwave now
I’ve been in communication with support and the engineers while they try to track it down
