OCT 9 UPDATE: A follow up release (62.13) will be deployed, addressing several issues from the 62.7 release. Parts of the release notes below have been updated to reflect this second 62.X release while keeping the previous content for visibility.
OCT 15 UPDATE: We observed a rare crash in a handful of Hubs upon rolling out 0.62.13 to Production, at which time we we paused the rollout of 62.13. We will be releasing 0.62.14 starting today which fixes this crash.
We will begin rolling out Samsung SmartThings Hub firmware version 0.62.7 starting on September 8, 2026. This will be a phased rollout, so that we can keep a close eye on any issues that arise, so your hub may not be updated immediately. 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)
Aeotec Smart Home Hub
Aeotec Smart Home Hub 2
ThingsOne Smart Home Hub
62.7 Release Period: Sept 8, 2026 - Sept 16, 2026 62.13 Release Period: Oct 12, 2026 - Paused on Oct 13, 2026 62.14 Release Period: Oct 15, 2026 - Oct 20,2026
Note that this release will be spread out over the course of a week, so you may not see your Hub update on the first day of the release period. This release period is an estimate, so the rate of hubs updated and final completion date may vary slightly within the timeframe. Please check the status page for more up to date information on this release.
Release Notes
Hub Release
The SmartThings app can now communicate directly with SmartThings Hubs when the app and Hub are connected to the same local network, even when the Hub is offline.*
Improved device state synchronization after extended Hub offline periods, ensuring all device states are accurately reflected in the App upon reconnection.
Included firmware updates for SiHAS PMM-300Z2 and PMM-300Z3 power meters which will be applied automatically if the hub has automatic updates enabled.
Enable hubs with Zigbee and/or Thread-based Matter devices to join a different Thread network.*
Note: There is a risk that some Zigbee devices may need to be re-added if the network is on a different channel.
When performing Offline Diagnostics of Thread devices, certain rare network conditions can now be automatically recovered.*
Added the ability to detect Tag In/Out events with the following SmartThings Hub models newly in SmartThings Find*:
Aeotec Smart Home Hub 2
ThingsOne Smart Home Hub
[New in 62.13]
Bug fixes for Matter OTA updates
Intermittent local connectivity issues between the app and the Hub
Fix a regression where Z-Wave Network Repair would occasionally fail
Edge Drivers
Added a set of device preferences to IKEA BILRESA Scroll Wheel to allow finer, more precise control when adjusting light brightness or color temperature.
Added ability to control Zigbee and Matter window coverings with the scroll wheels.*
* dependent on an upcoming SmartThings app version
So if my SmartThings Thread/Zigbee network is on channel 20 and my Google/Apple/OpenThread thread network is on channel 11 you want me to disconnect my 77 zigbee devices and reconnect them?
This is an incredible oversite by a programmer somewhere. I would not take the risk of trying to unify SmartThings thread with another thread until this is resolved.
I think this is more likely an issue with the devices than the smartthings firmware. When I changed the channel on my hub previously most zigbee devices came back on the new channel. For those that didn’t it was mostly the tuya ones and they either needed a power cycle by removing batteries or in some cases putting into pairing mode without deleting device from smartthings, this caused them to reappear as the original device and maintained routines etc. Your mileage may vary however…
Intrigued to know what this really means when the problem at this moment arises when the other network has no interface to respond with the OTP code that ST asks for.
The SmartThings app can now communicate directly with SmartThings Hubs when the app and Hub are connected to the same local network, even when the Hub is offline.*
Anyone know if this behaviour will be the standard when SmartThings app and hub are on same lan, or does this only happen as a fallback when internet isn’t available?
I think it simply means they will allow you to attempt to join a ST hub to another Thread network even if it already has Zigbee/Thread devices. Currently the ST hub has to be empty.
So more users will be able to discover it doesn’t work in the circumstances you describe.
It’s very interesting that the SmartThings Hub supports Galaxy Find Network through its BLE antenna. In particular, it is expected that these functions can be linked with modes and routines app to more effectively utilize them for presences detection via SmartThings Find.
I hope so, I’ve always seen the cloud dependency of the app for local devices a red flag for a smart home platform and makes the app slower even to turn on a light. Even Google Home claims to have local control through the app now, although I haven’t tested it.
At least, with offline control, the Aeotec hub 2 claiming “local control and automations” will no longer be false advertising and SmartThings will be easier to recommend.
The SmartThings app can now communicate directly with SmartThings Hubs when the app and Hub are connected to the same local network, even when the Hub is offline.*
Wooooooooaaa! Finally! This is huge and extremely pong overdue! Any chance there will be a webgui aswell if we try accessing via ip adress? Its about time this happened!
“local control and automations” was correct for most of my routines and Ikea dimmers/buttons since the rollout of Edge.
That said, direct communication between the SmartThings app and SmartThings hub is ‘huge’.
Yeah, relying on local routines was what most of us had to do to workaround the lack of local control, but that’s not what is called local control, that’s a local automation.
“Local control” and “local-first communication” as Aeotec advertises has a very specific meaning in the context of a smart home platform and it was being used in a misleading way so people would think SmartThings offered local control and were local-first like other platforms like Apple Home, Home Assistant, Hubitat, IKEA Home Smart, Aqara Home (well, this one is not local-first but certain hubs support local control), etc.
Finally, this will solve enabling/disabling my virtual SmartThings Home Security setup when the internet is offline without having to use zwave button remotes.
I’m also thinking that perhaps a remote VPN connection to a SmartThings hub network that’s behind the VPN might connect locally, hummmm…(thinking…when I’m away and the hub is offline perhaps…)
I’m really curious if they will use some proprietary communication protocol between the app and hub, or ‘hopefully’ they might use some open standard communication protocol that could be exposed to other manufactures and devices on the local network. (I’m dreaming…)
It’s about time! I was seriously considering jumping ship as this is the only major SmartHome provider that didn’t support direct network communication between the hub and app when on the same network. Kind of a no-brainer. I hope it works as advertised since we are in hurricane season and internet can be wiped out for days.
