Short Answer: The Fee Is for the API Connection, Not the SmartThings App

Under Samsung's announced plan, a Home Assistant household that keeps using the SmartThings integration—its software connector to Samsung—should expect to need the $4.99-per-month Personal Plan starting with the October 2026 transition. Home Assistant now places that warning directly on its SmartThings page. Samsung says free access to its API, the online link used by outside software, continues through the third quarter of 2026 and calls October its target; it also says more transition details are still coming.

The normal SmartThings app is different. Samsung says SmartThings app users and people using Works with SmartThings partner devices are not affected by this API change. In plain English, you can keep controlling devices in the SmartThings app without automatically owing $4.99. The fee matters when another system—here, Home Assistant—uses Samsung's developer API to read and control SmartThings devices.

Do not react by removing SmartThings today. First sort every device into one of three groups: already local, movable to local control, or still dependent on SmartThings cloud. Local control means the ordinary command stays inside your home instead of needing a company server. That turns a frustrating subscription decision into a safe, room-by-room migration.

Tara's recommendation: build the local replacement in parallel, test it, then retire the old path. Home Assistant receives SmartThings updates through Samsung's cloud; deleting that connection first does not make the underlying devices local.

What Actually Changes in October 2026

Samsung announced the new API plans on June 23, 2026. The company describes the $4.99 monthly tier as a Personal Plan for non-commercial individual developers. Its examples include API access to Samsung televisions, refrigerators, device state and control, device health, and the wider mix of Wi-Fi, Zigbee, Z-Wave, Thread, and Matter products represented in SmartThings.

Zigbee and Z-Wave are the low-power radio systems used by many hub-connected sensors, switches, and locks. Thread is another low-power home network used by many Matter devices. Matter is the shared smart-home standard that can let one compatible device join more than one platform.

Home Assistant's official documentation makes the consequence unusually direct: free SmartThings API access is being phased out, and users will need the paid Personal Plan to continue using the integration. Home Assistant also suggests migrating suitable Zigbee and Z-Wave devices to local integrations as an alternative.

Two details are still unsettled. Samsung calls October 2026 a target rather than publishing a day-by-day cutoff schedule, and says it will provide more migration information. Also, paying for the API does not guarantee that every function visible in the SmartThings app appears in Home Assistant. Home Assistant already warns that some capabilities are app-only or are not exposed by Samsung's API.

What Can Move Locally—and What May Not

This table separates the five questions that usually get mixed together: official Home Assistant support, whether control stays in the house, whether Samsung's cloud is still required, whether Matter or Apple Home can share the result, and what can go wrong during the move.

Device or path Official Home Assistant support Local control and cloud dependency Matter and HomeKit path Migration action and caveat
Samsung washer, dryer, refrigerator, air conditioner, or other SmartThings-only appliance The SmartThings integration lists many appliance capabilities, but says not every SmartThings feature is exposed. Home Assistant receives these updates through Samsung's cloud and needs API access. The SmartThings app can remain available without the Home Assistant connection. Do not assume a SmartThings appliance is a Matter device. HomeKit Bridge can share a control with Apple Home only after that control works in Home Assistant. Leave it in SmartThings while testing. If no local integration exists, choose the paid API, app-only use, or loss of the Home Assistant feature.
Philips Hue Bridge v2 with Hue bulbs and accessories Official Hue integration; the square v2 bridge is discovered on the network and sends updates directly inside the home. Local Home Assistant control through the Hue Bridge. The Hue cloud is not required for ordinary local control. Home Assistant can share Hue controls with Apple Home through HomeKit Bridge. Hue's Matter bridge is optional; Home Assistant notes that the native Hue connection keeps richer features. Add the Hue integration without resetting bulbs. Keep the bridge, names, rooms, and reliable lighting network in place.
Shelly 2PM Gen3 and other supported Shelly Wi-Fi devices Official Shelly integration supports all Shelly generations and communicates directly with devices. Local; Shelly Cloud is not required. Current generations communicate directly with Home Assistant inside the home. HomeKit Bridge can share the Home Assistant controls with Apple Home. Matter depends on the exact Shelly model and its software version, not the SmartThings listing. Add the native Shelly integration while the device stays installed. For mains wiring, use a qualified electrician; this migration does not require rewiring a working relay.
Samsung Tizen TV on the same normal home network Official Samsung Smart TV integration supports direct control for compatible models when the TV and Home Assistant are on the same subnet. In a normal home, that means neither one should be on guest Wi-Fi or another isolated network. Basic Home Assistant media control stays on the home network. SmartThings-only television features may not have a local replacement. HomeKit Bridge can share the Home Assistant media controls with Apple Home. A TV appearing in SmartThings does not make it a Matter accessory. Add the native TV connection and compare controls before removing the SmartThings version. Keep whichever path supplies the features your household actually uses.
An actual Matter device already paired to SmartThings Home Assistant officially supports Matter; SmartThings officially documents sharing a Matter device with another service. After you add the device, Home Assistant's Matter control stays inside the home. Remote app and voice features can still add cloud dependencies. In SmartThings, open the Matter device, choose Share with other services, and use the newly generated code in Home Assistant. That is Matter multi-admin. Share before resetting. The option applies only to Matter devices, can have controller limits, and may not expose vendor-specific extras.
Zigbee sensor, plug, bulb, or switch on a SmartThings/Aeotec hub ZHA, Home Assistant's built-in Zigbee connection, supports a local Zigbee network. Connect ZBT-2 is a current official radio example and must be dedicated to Zigbee or Thread, not both. Local after the device joins Home Assistant's Zigbee network. No SmartThings cloud is needed for that device. Zigbee is not Matter or HomeKit. Home Assistant can later share selected controls with Apple Home through HomeKit Bridge. Record the model, factory-reset it using the manufacturer's instructions, then add it to ZHA. A device on another Zigbee network normally needs that reset.
Z-Wave lock, sensor, switch, or plug on SmartThings Official Z-Wave JS connection; Connect ZWA-2 is Home Assistant's current official 800-series adapter example. Local after inclusion in Home Assistant's Z-Wave network. No SmartThings cloud is needed for that device. Z-Wave is not Matter or HomeKit. Home Assistant can share suitable controls with Apple Home after they work locally. Remove the device from its old Z-Wave network, then add it to Home Assistant. If it has a security number (DSK) or QR code, save it first. Move locks and access devices only with a tested physical fallback.

A Safe Room-by-Room Migration Plan

The best transition is deliberately boring. Keep both systems available, move one device class at a time, and give each automation—an automatic rule such as “motion turns on the light”—only one owner.

1. Make an inventory before changing anything

List each device's brand, model, room, SmartThings name, and current job. Note whether it connects through a Hue Bridge, Wi-Fi, Matter, Zigbee, Z-Wave, or a Samsung account. Screenshot important SmartThings routines and write down which voice commands family members actually use. If the protocol is unclear, look up the exact model instead of guessing from the app icon.

Mark safety-related devices separately: door locks, garage doors, alarms, smoke or carbon-monoxide systems, thermostats, powered valves, and leak shutoffs. Confirm manual control and a physical key, switch, or other fallback before touching any of them.

2. Prepare Home Assistant and the right radios

Create a fresh Home Assistant backup. For Zigbee, use one supported radio, also called a coordinator, and one Zigbee connection in Home Assistant. Connect ZBT-2 is a current official option, but it can run either Zigbee or Thread at one time. For Z-Wave, Home Assistant recommends compatible 800-series adapters and lists Connect ZWA-2 as its official example. Place radios as their documentation recommends and finish basic setup before removing devices from SmartThings.

If you already use Home Assistant for Matter-over-Thread, do not repurpose its only Thread radio for Zigbee. A separate dedicated radio—or an existing compatible Thread border router, the device that joins Thread to your normal home network—is the cleaner path.

3. Add native local integrations first

Start with devices that do not need a reset. Add the Philips Hue Bridge through Home Assistant's official Hue connection. Let Home Assistant discover supported Shelly devices. Add a compatible Samsung TV through the official Samsung Smart TV connection. Compare names and controls with SmartThings for several days.

This is the lowest-risk win because the old path still works while the new local one is tested. When two copies of the same device appear, rename them clearly—such as “Living Room TV local” and “Living Room TV SmartThings”—until the final cutover.

4. Share Matter devices instead of resetting them

For a device that is genuinely Matter-certified and already in SmartThings, try multi-admin first. SmartThings says to open the device, select the menu, choose Share with other services, and generate a fresh setup code. In the Home Assistant companion app, add a Matter device that is already in use and enter or scan that new code.

This lets SmartThings and Home Assistant remain separate Matter controllers for the same device. It does not convert an older SmartThings Zigbee or Z-Wave device into Matter, and it does not guarantee that vendor-only scenes, energy details, or special buttons appear everywhere.

5. Move Zigbee devices one room at a time

Zigbee devices belong to one Zigbee network at a time. A SmartThings Zigbee sensor cannot simply be discovered by ZHA while it is still joined to the SmartThings hub. Follow the device maker's reset instructions, place ZHA in pairing mode, and confirm the device reports correctly in Home Assistant.

Start with a low-risk room. Move powered Zigbee plugs, bulbs, and wired switches thoughtfully because many repeat the Zigbee signal for nearby battery sensors. Do not remove every signal-repeating device from the old SmartThings network before the remaining sensors are ready to move.

6. Remove Z-Wave devices from SmartThings, then add them to Home Assistant

A Z-Wave device will not join the new Home Assistant network while it still believes it belongs to the old one. Use SmartThings removal when it is working, or use Home Assistant's exclusion step to remove it from the old network. Then use inclusion to add it to Home Assistant. Follow the device maker's secure-pairing directions without moving the installed Home Assistant adapter. If the device has a security number (DSK) or QR label, have it available.

Do a plug or non-critical sensor first. Leave locks, garage access, alarm interfaces, and heating or air-conditioning control until the process is familiar and someone can test the physical fallback immediately.

7. Rebuild automations, voice access, and dashboards

Re-create one routine in Home Assistant, test it, then disable the SmartThings version. If both systems respond to the same motion or button event, lights can flicker, notifications can duplicate, and troubleshooting becomes guesswork.

For Apple households, Home Assistant's official HomeKit Bridge shares selected controls locally with Apple Home; Siri and remote access may still use Apple services. Google Home and Alexa connections are useful family surfaces too, but remote voice and account linking generally bring cloud services back into the path. Keep the actual automation in one place even when several apps can control it.

8. Decide what to do with cloud-only holdouts

After the easy devices are local, review what remains in the SmartThings connection. A Samsung appliance may justify $4.99 per month if its Home Assistant controls drive useful energy or cycle-completion automations. A cloud-reported appliance status should never be the home's only safety layer. The same appliance may not justify the fee if the family only checks it in the SmartThings app twice a month.

Your choices are legitimate and simple:

  • Pay for API access and keep those SmartThings controls in Home Assistant.
  • Use the free SmartThings app only for the appliances that have no good local path.
  • Give up the cloud-only Home Assistant features and keep the rest of the home local.

Only remove the Home Assistant SmartThings integration after that list is empty or every remaining loss is understood.

Local, Cloud, Matter, and HomeKit Are Different Paths

Local control means Home Assistant can send the ordinary command inside your home. Hue through its bridge, Shelly through its native integration, ZHA, Z-Wave JS, Matter, and compatible Samsung TV control can all provide local paths. Internet access may still be needed for initial setup, device software updates, remote notifications, or optional accounts.

SmartThings API control is a cloud path. Even if the physical device uses Zigbee or Z-Wave to talk locally to a SmartThings hub, Home Assistant's official SmartThings integration talks through Samsung's API. The radio between the device and hub does not make the Home Assistant connection local.

Matter multi-admin lets an actual Matter device belong to more than one controller. It is the cleanest way to keep a device in SmartThings while adding local Matter control in Home Assistant, but it does not apply to every product displayed in SmartThings.

HomeKit Bridge is Home Assistant's path for showing its device controls in Apple Home. It can make a local Zigbee or Z-Wave device available to Siri after Home Assistant owns it. That sharing does not turn the device itself into Matter, and it does not restore SmartThings-only features.

What Not to Do

  • Do not buy radios before identifying protocols. A Zigbee radio cannot take over Z-Wave devices, and Connect ZBT-2 cannot run Zigbee and Thread simultaneously.
  • Do not assume every SmartThings device is Matter. Multi-admin works for actual Matter devices, not for an older device merely shown in the SmartThings app.
  • Do not reset a whole house at once. You need the old setup available to compare names, routines, device behavior, and family expectations.
  • Do not move safety and access devices first. Preserve keys, manual switches, manufacturer apps, and professional monitoring requirements.
  • Do not count “visible in Home Assistant” as complete. Test state updates, commands, automations, restart recovery, and an internet outage where local operation matters.

The Practical Recommendation

If SmartThings mainly holds ordinary Zigbee, Z-Wave, Hue, Shelly, Matter, and television devices, use the remaining free period to move those devices to documented local paths. That lowers the number of cloud dependencies and leaves the October decision focused on the few things that genuinely need Samsung's API.

If the value of your setup is Samsung appliances, do not pretend every feature has a local replacement. Keep SmartThings, test the app-only option, and price the Personal Plan against the automations you would lose. A mixed system—local Home Assistant for the house, SmartThings app for a refrigerator or washer—is often more sensible than either paying out of habit or deleting useful features in anger.

The goal is not a dramatic “SmartThings versus Home Assistant” weekend. It is a supported home where each device has a known owner, critical controls have a fallback, and the cloud bill is attached only to features that earn it.

FAQ

Will Home Assistant users have to pay $4.99 a month for SmartThings?

Under Samsung's announced plan and Home Assistant's current documentation, keeping the SmartThings API integration after the October 2026 transition will require Samsung's $4.99-per-month Personal Plan. Samsung calls October its target and says more transition details are coming.

Can I keep using the SmartThings app without paying the API fee?

Yes. Samsung says ordinary SmartThings app users and Works with SmartThings partner-device users are not affected. The fee concerns API access used by outside connections such as Home Assistant's SmartThings integration.

Can Home Assistant import SmartThings Zigbee and Z-Wave devices without re-pairing?

Generally no. A Zigbee device normally needs a factory reset before joining Home Assistant's Zigbee network. A Z-Wave device must be excluded from its old network and then included in Home Assistant's Z-Wave network.

Can a Matter device stay in SmartThings and also join Home Assistant?

Often yes. SmartThings documents a multi-admin sharing flow that creates a fresh setup code for another Matter controller. The option applies only to actual Matter devices, and the device and controller must support the needed Matter features.

What should I do with Samsung appliances that only work through SmartThings?

Keep them in SmartThings while you test what Home Assistant can control. If there is no suitable local connection, choose between paying for API access, using the SmartThings app without those controls in Home Assistant, or giving up those cloud-only features.