SmartThings Devices Still Showing Offline After the 0.62.7 Hub Update? Here’s the Actual Fix (2026)

Where to Start

• What Does the 0.62.7 Update Actually Change?
• Why Are Devices Still Showing Offline After the Fix?
• Which Hub Models Got This Update, and When?
• How Do You Fix a SmartThings Device Stuck Offline?
• Should You Switch Thread Networks on This Firmware?

What Does the 0.62.7 Update Actually Change?

SmartThings Hub firmware 0.62.7 targets one specific problem: the app not accurately reflecting a device’s real status after the hub comes back online from an outage. According to the official release notes on the SmartThings Community, the app can now talk directly to the hub over the local network even while the hub itself is offline from the cloud, and device-state syncing after a reconnect is meant to be far more accurate.

The same update adds Thread network flexibility (a hub can now join a different Thread network instead of being locked to the one it started on), expanded offline diagnostics for Thread devices, and wider Tag In/Out detection for locating Galaxy SmartTags. None of that is cosmetic — it’s a genuine attempt to fix a years-old complaint about hubs lying about device status.

Rollout started September 8, 2026, and ran as a staggered release through roughly September 16, with each hub taking under a minute of downtime to apply it.

Why Are Devices Still Showing Offline After the Fix?

Because the fix addresses status reporting after a reconnect — not every reason a device can go dark in the first place. Multiple posts on the same release-notes thread describe devices that still show offline days after 0.62.7 landed, with the app’s offline troubleshooter reporting that the hub itself can’t be reached, which then pushes you toward deleting and re-adding the device.

When I compared the reports on that thread, the common factor wasn’t Wi-Fi-connected gear. It was Zigbee and Thread devices specifically — the same radios this update touches. A firmware change that alters how the hub tracks device state on those protocols can, for a subset of devices, end up in a worse spot than before if the device’s cached state gets out of sync during the update window itself.

This part trips people up: seeing “offline” right after an update feels like the update broke something. Sometimes it did the opposite — it revealed a device that was already flaky and just hadn’t been reported accurately until now.

You’ll notice this most on battery-powered Zigbee sensors — door sensors, motion sensors, water leak detectors — since they only check in with the hub on a schedule instead of staying constantly connected. A device that was quietly dropping check-ins for weeks can suddenly show “offline” the moment the hub starts reporting status more honestly.

Which Hub Models Got This Update, and When?

Five hub models received 0.62.7 in this rollout window, based on the official release notes.

If your hub is one of these five and you haven’t seen a brief reboot in that window, it may not have received 0.62.7 yet — check the version number in the app before assuming this guide applies to you.

How Do You Fix a SmartThings Device Stuck Offline?

Confirm the firmware version first. Open the SmartThings app, go to your hub’s device page, and check that it actually shows 0.62.7 before troubleshooting further — some of this is misdiagnosed on hubs that haven’t updated yet.

Power cycle the stuck device itself before touching the hub. Unplug it or pull the battery for about ten seconds, then reconnect. For Zigbee devices this alone resolves a surprising share of “offline” reports.

If that doesn’t bring it back, soft reset the hub. Leave the Ethernet cable connected, unplug the hub’s power, then press and hold the small reset button on the back with a paperclip while plugging the power back in. Release the button as soon as the LED starts flashing yellow — that’s a soft reset, and it clears a corrupted network state without deleting your devices or routines.

Still offline after both of those? Remove the device from the app and put the hub into pairing mode from Add Device, then follow that device’s specific pairing steps to re-add it. This is the step that actually resolves it for most of the “hub cannot be reached” reports.

Don’t factory-reset the whole hub as a first move. It solves the same problem a soft reset does, at the cost of rebuilding your entire device list from scratch.

Give the mesh a few minutes after any of these steps before deciding it hasn’t worked. Zigbee devices route through each other, and a sensor two hops away from the hub can take longer to reappear than one sitting right next to it.

Should You Switch Thread Networks on This Firmware?

Only if you have a specific reason to. The ability to move a hub to a different Thread network is new in 0.62.7, and it comes with a real cost that isn’t obvious from the changelog.

Zigbee and Thread share the same 2.4GHz radio hardware inside these hubs. On the official release-notes thread, one user described needing to re-add 77 Zigbee devices after a Thread network switch, because the new network operated on a different channel — channel 20 instead of 11 — and every Zigbee device on the old channel had to be paired again from scratch.

If your setup already works, leave the Thread network alone. The feature is genuinely useful if you’re consolidating multiple Thread border routers into one network, but it’s not something to try just because it’s newly available.

The Zigbee Re-Pairing Trap

Before switching Thread networks for any reason, check your current Zigbee channel in the app’s hub settings. If the destination network uses a different channel, assume every Zigbee device will need to be re-paired, not just Thread devices.

Don’t switch networks on a hub with more than a handful of Zigbee devices unless you’ve budgeted the time to re-pair all of them. There’s no bulk re-pair option — it’s one device at a time.

Back up your routines and automations before any hub-level change. A soft reset preserves them, but a full factory reset or a botched Thread migration doesn’t always.

Before You Touch the Reset Button

• ✅ Confirm the hub actually shows firmware 0.62.7 in the app first
• ✅ Power cycle the stuck device before touching the hub itself
• ✅ Use a soft reset (button + power, release at yellow LED), not a factory reset
• ✅ Remove and re-add only the specific device still showing offline
• ✅ Check your Zigbee channel before switching Thread networks

FAQ

Does installing 0.62.7 automatically fix a device that’s already stuck offline?

Not on its own. When I checked the release-notes thread, the update fixes how future offline periods get reported — it doesn’t retroactively repair a device that was already showing a stale status before you updated. Power cycling the device or re-adding it in the app is still the actual fix for those cases.

Will switching to a new Thread network break my existing Zigbee devices?

It can, if the new network runs on a different channel. Zigbee and Thread share the same radio, and a channel change on one affects the other. Check your current channel before switching, and expect to re-pair Zigbee devices individually if the channels don’t match.

How do I check whether my hub has actually received the 0.62.7 update?

Open the SmartThings app, tap your hub, and look at the device details page for the firmware version number. If it doesn’t show 0.62.7 yet, the staggered rollout may not have reached your hub, and none of this update’s fixes or side effects apply to you yet.

Sources

• SmartThings Community — Hub Firmware and Edge Driver Release Notes 0.62.7
• Geeky Gadgets — SmartThings Hub Update 0.62.7 Fixes Offline App Status Sync
• SmartThings Status

Fact-checked based on public sources as of September 27, 2026.