SmartThings opens local app control to Android and iOS

Samsung now describes local SmartThings app control as available on Android and iOS. Its October 5, 2026, US announcement says a phone can communicate directly with a supported hub on the same Wi-Fi network during an internet interruption. On October 12, Samsung began rolling out hub firmware 0.62.13 to five dedicated hubs, including the SmartThings Hub v2 and v3, to fix bugs in Matter device firmware updates and intermittent local connections between the app and the hub. It paused the rollout on October 13 after a rare crash on "a handful of Hubs." The replacement, 0.62.14, started on October 15 with the crash fixed, and Samsung's status page marked its rollout completed on October 20.

Samsung lists SmartThings Station, V2, V3 and V4 hubs, plus hub-enabled Samsung Smart TVs and Family Hub refrigerators. The app store listings now describe the phone side. iOS version 1.7.52, released October 14, and the Android listing updated October 12 both describe faster control of hub-connected devices when the phone and hub share a Wi-Fi network. Neither store note mentions internet outages or calls its build a minimum requirement, and Samsung has not published a country-by-country schedule for the app feature or a list of commands that work offline. Treat the feature as a reason to update and test the local devices you use, rather than a guarantee that your entire home works without internet access.

Firmware 0.62.14 replaces the paused 0.62.13

Firmware 0.62.7 prepared the same-network app path for five dedicated hubs: the Samsung SmartThings Hub 2015 (Hub v2) and Hub 2018 (Hub v3), the Aeotec Smart Home Hub, the Aeotec Smart Home Hub 2 and the ThingsOne Smart Home Hub. Both follow-ups target the same five hubs, and their shared status page entry covers the Americas, Europe, the Middle East and Africa, and Asia Pacific:

Samsung lists only the crash fix for 0.62.14 and moved its 0.62.13 status page entry to the new version, so treat 0.62.14 as 0.62.13 plus that fix. A hub that installed 0.62.13 before the pause already has the listed fixes, but Samsung has not said whether those hubs also received 0.62.14. It has not described the crash or the hubs it hit, and its notes do not say which Matter update failures or local connection problems the fixes address. The status page says the update "has been released" to the five hub models and marked the rollout completed on October 20, but it does not say whether every hub has installed it or how a hub still on an older version catches up. If Matter firmware updates through SmartThings have been failing, or the app has been losing its local connection to the hub, open the hub's Information screen in the SmartThings app and check for 0.62.13 or 0.62.14 before resetting the hub or re-adding devices. If it still shows 0.62.7 or older, ask SmartThings support about the update first. Hubs enrolled in the beta channel received the Matter and local connection fixes in 0.62.12 on September 24 and the Z-Wave fix in 0.62.13 on October 1. On October 15, Samsung said it would release 0.62.14 to beta hubs that day and had seen no crashes among beta testers, so a beta hub on 0.62.13 or 0.62.14 already has all three fixes.

The October announcement names a broader set of controllers, but Samsung does not assign 0.62.7, 0.62.13 or 0.62.14 to Station, TVs or refrigerators. Do not use the dedicated-hub version numbers as their update requirement.

Local app access is not local everything

The useful change is reaching the hub from the phone. SmartThings already lets eligible rules run locally, but every device feature and service involved must support local execution; other rules run in the cloud. A direct app connection does not remove those dependencies.

On one of the five dedicated hubs, confirm that its firmware reads 0.62.13 or later, since both 0.62.13 and 0.62.14 carry the fix for intermittent local connections. Then install the current SmartThings app and try a noncritical light or plug with the internet connection temporarily unavailable while leaving the router and hub powered. This checks the actual control path in your home. Matterhome has not tested the update, and Samsung's same-network requirement does not promise remote access during an outage.

The same October announcement adds Matter 1.6 support and names energy meters, closures such as specialized doors and gates, irrigation devices, and soil sensors. It does not identify exact accessory models for those categories.

Thread migration still needs separate confirmation

Firmware 0.62.7 also prepares supported hubs with existing Zigbee or Matter-over-Thread devices to join another Thread network. The release notes still mark it as waiting on an app update, but Samsung's October 9 and October 15 revisions left that same mark on local app access, which Samsung now calls available, so the footnote no longer settles the question. What matters is that none of Samsung's current sources, including the October 5 announcement and both store notes, says the app can now move a hub to another Thread network. Treat migration as unavailable until Samsung documents it.

SmartThings warns that changing the network's radio channel can require some Zigbee devices to be added again. If your Matter-over-Thread devices are stable, leave the network alone. Anyone planning a migration should allow time to restore affected devices and routines once the app path is documented.

Updated October 21, 2026, after Samsung marked the 0.62.14 rollout completed on October 20. Originally published September 6 and previously updated September 16, October 7, October 11 and October 18. The October 11 update corrected the 0.62.7 rollout status: Samsung's status page marked it completed on September 16, not still in progress as this article had said.