One UI 9 broke SmartThings? Fix the layer, not the devices

If you are searching “samsung one ui 9 update broke smartthings devices how to fix” because half the house just went Offline, do not start by deleting devices. Start by finding the failed layer. As of August 25, 2026, direct One UI 9 causation belongs in the “Investigating” bucket, not the “Confirmed” bucket. The timing may be real. The diagnosis still needs proof.

The safe recovery order is phone/app first, hub firmware second, radio or device pairing last. That order matters because re-pairing a house full of Zigbee, Matter, and Z-Wave devices is the smart-home equivalent of pulling every breaker because one lamp flickered.

The short status check before you fix anything

One UI 9 is real, but that does not mean every SmartThings failure in August 2026 is a One UI 9 failure. Samsung’s One UI page and PhoneArena’s rollout tracking put stable One UI 9 first on the Galaxy Z Fold8 Ultra, Z Fold8, and Z Flip8, with a wider rollout expected from September 2026 rather than already completed across the Galaxy lineup by August 25, 2026.[1][2]

So the first split is simple: if you are not using one of those early One UI 9 devices, your SmartThings problem may still be update-adjacent, but it is less likely to be caused by stable One UI 9 itself. It could be a SmartThings app version problem, a hub firmware regression, a radio mesh issue that happened to surface after a reboot, or a device-driver mismatch.

Samsung has documented this pattern before. After the T OS (Android 13) upgrade, Samsung HK said SmartThings could crash below app version 1.7.69 and the fix was to update the SmartThings app.[3] That is useful precedent, not proof that One UI 9 is breaking devices. It tells you that after a phone OS upgrade, the app layer is a legitimate place to check before blaming the hub or re-pairing sensors.

There is also a separate “the app looks different” thread to keep in its lane. SamMobile showed an early One UI 9-styled SmartThings redesign on August 4, 2026, with a floating five-tab bar, new widget types, and a Routines split into Discover and My Routines, but that redesign was still unreleased as of August 25, 2026.[4] A leaked interface is context for confusion, not a fix target.

If the SmartThings app or phone layer failed

This is the least destructive branch, so take it seriously even if the timing feels too convenient. An app-layer failure usually has one of these tells: SmartThings crashes, device tiles will not load, widgets are empty, location or Nearby Devices prompts changed, or another household member can still control devices from a different phone.

• Update SmartThings from the Galaxy Store or Google Play, then reopen it before changing devices.
• Force stop SmartThings and clear the app cache. Do not clear app data until you have confirmed your Samsung account and home membership are intact.
• Check Android permissions that updates often disturb: Location, Nearby Devices, Notifications, and background battery access.
• Test the same home from another Galaxy phone, a tablet, or SmartThings web. If the other client works, the hub and devices are not the first suspects.
• If the app still fails, reinstall SmartThings. Reinstalling the app is not the same as deleting devices from your SmartThings home.

For basic app setup and version-check habits, the same app-layer discipline applies whether the phone is new or old; the steps in Set up SmartThings on Galaxy A27 5G are still useful when the app itself is the thing misbehaving.

If the hub says Disconnected, look at the LED before you touch the plug

This is the part that saves hubs at 11 p.m.: a SmartThings hub that is flashing or showing solid magenta can be in the middle of a firmware update, and Samsung says it may show as Disconnected during that state. Samsung’s instruction is not subtle: do not unplug or reboot the hub during the magenta firmware-update state.[5]

If the LED indicates an update, wait. If the hub is Disconnected and the LED does not indicate a firmware update, then move to a controlled power and network check: confirm the router is online, confirm the hub’s Ethernet or Wi-Fi connection, then power-cycle the hub only after you have ruled out the update state.

A hub reset is not a prettier reboot. It is the last-resort move after narrower layers have failed. Resetting too early can turn one bad firmware state or one bad radio route into a full re-onboarding project.

If many Zigbee devices went Offline after the June 2026 hub firmware

The strongest dated SmartThings evidence in 2026 is not a confirmed One UI 9 phone bug. It is hub-side. SmartThings hub firmware 0.61.6 rolled out June 15–26, 2026, and changed the Zigbee device-health algorithm so online and offline status is derived from each device’s reporting intervals. In that release thread, users reported losing clusters of Zigbee devices after installation, including reports of 8 to 27 Zigbee devices going offline.[6]

That does not prove every Offline Zigbee device is healthy. It does mean the first question is whether the hub started judging device health differently, not whether every sensor died at once. A new health algorithm can expose weak reporting, sleepy battery devices, bad repeaters, or routing problems that were already marginal.

1. Confirm the hub is not updating. If the hub LED is in the firmware-update state, wait.
2. Power-cycle the hub only after the update state is ruled out.
3. Power-cycle mains-powered Zigbee repeaters such as plugs or in-wall switches before touching sleepy battery sensors.
4. For a battery device that remains Offline, Samsung’s recovery ladder includes removing the battery for 30 seconds before reinstalling it.[7]
5. Check placement. Samsung identifies router proximity and interference as possible causes of offline readings, and notes that Wi-Fi channels 1, 6, and 11 overlap the SmartThings Zigbee band.[7]
6. Only delete and re-add a device after the hub, repeaters, battery reset, and interference checks have failed.

If the Offline wave followed a power cut rather than a phone update, use the same radio-order discipline in Smart devices won’t reconnect after outage? Fix the layer. The important overlap is the order: stabilize the hub, stabilize repeaters, then touch endpoints.

If Matter bridged devices became Generic Switches or lost temperature

A different 2026 failure pattern hit Matter bridge users. In April 2026, around hub firmware 0.60.12-era reports, bridged Matter devices were re-identified as Generic Switches and the temperature capability disappeared. In the documented community thread, one fix was switching the device driver to a Matter Sensor driver.[8]

This is a driver and capability problem, not a reason to re-pair every Matter device. If a temperature sensor suddenly looks like a switch, inspect the device type and driver first. Rebuilding the bridge should come after the driver path fails, not before.

If only Z-Wave devices stopped responding

Z-Wave deserves its own branch because the recovery rules are different. In January 2026, SmartThings community users reported hubs losing Z-Wave control overnight, with Z-Wave repair not restoring control in the reported case cluster; Samsung support requested hub logs. The unclear user-reported “95 Update” wording in that thread should not be treated as a confirmed fix timeline.[9]

If the hub is online, the app works, Zigbee devices behave, and Z-Wave devices alone are stuck, then Z-Wave repair is appropriate. If repair does not restore control, collect hub logs or contact support before tearing down the network. Re-pairing can be valid, but for Z-Wave devices Samsung’s recovery ladder includes exclusion before re-pairing where required.[7]

This is where many clean-looking fixes create ugly leftovers. A factory-reset Z-Wave device that was not properly excluded can leave a ghost or stale entry behind. If the device must be removed, exclude it first, then add it back.

The dated decision tree

“One UI 9 broke SmartThings” is a useful search phrase because it preserves the timing. It is a weak diagnosis because the fix changes completely depending on the layer. As of August 25, 2026, direct One UI 9 causation remains unconfirmed, while several nearby SmartThings app, hub firmware, Matter, Zigbee, and Z-Wave fixes are specific enough to act on without re-pairing the whole home.

References

1. One UI — Samsung US
2. One UI 9 release date, features, news, compatible phones — PhoneArena
3. After T OS upgrade, SmartThings app does not work properly. How do I resolve it? — Samsung HK
4. Massive Samsung SmartThings update: One UI 9 early look — SamMobile — August 4, 2026
5. Hub disconnected from SmartThings — Samsung US Support
6. Hub Firmware and Edge Driver Release Notes - 0.61.6 — SmartThings Community — June 2026
7. SmartThings devices are showing offline — Samsung US Support
8. Issues with Bridged Devices April 2026 — SmartThings Community — April 2026
9. SmartThings Hub stopped connecting to Z-Wave devices — SmartThings Community — January 2026