SmartThings to Home Assistant

1. Why Migrate from SmartThings

SmartThings has been a popular entry point for smart home automation, but several factors are pushing users toward Home Assistant:

Cloud Dependency

SmartThings requires Samsung's cloud for almost everything, including automations that seem like they should run locally. When Samsung's servers go down (which has happened multiple times), your entire smart home stops working. Even "local execution" in SmartThings is limited to a small subset of device handlers.

Edge Driver Transition

Samsung has been migrating from Groovy-based device handlers to Edge drivers. While Edge drivers run locally on the hub, the transition has broken many custom integrations that the community relied on. Some niche devices that had Groovy handlers never received Edge driver equivalents.

Limited Automation Power

SmartThings Routines are improving but still limited compared to Home Assistant automations. HA offers conditional logic, templates, scripts, timers, input helpers, and a full YAML automation engine that can handle complex multi-step scenarios that SmartThings simply cannot express.

Home Assistant Advantages

• True local processing: Automations run on your hardware, no cloud required
• 2,800+ integrations: Vastly more device support than SmartThings
• Advanced automations: Templates, conditionals, scripts, and blueprints
• Privacy: Your data stays on your local network
• Community: Massive community with HACS add-on ecosystem
• No subscription required: Full functionality without recurring costs (Nabu Casa subscription is optional for remote access)

2. Pre-Migration Checklist

Before touching any devices, complete this inventory so you know exactly what you're working with.

Inventory Your Devices

Open the SmartThings app and create a spreadsheet with every device:

• Device name and location/room
• Protocol: Zigbee, Z-Wave, WiFi, or cloud-only
• Make and model (check device details in ST app)
• Critical vs. nice-to-have (prioritize locks, lights, thermostats)

Document Your Automations

Screenshot or write down every SmartThings Routine and Scene. Note the trigger, conditions, and actions. You'll recreate these in Home Assistant later. Pay attention to timing-based automations, multi-device sequences, and any Routines that depend on SmartThings-specific features like Smart Home Monitor.

Check Protocol Compatibility

• Zigbee devices: Almost all will work with ZHA or Zigbee2MQTT. Check the Zigbee Device Compatibility Repository for your specific models.
• Z-Wave devices: All Z-Wave and Z-Wave Plus devices are compatible. Check the Z-Wave JS device database for your models.
• WiFi devices: Most will have native HA integrations or can be used through other means.

Hardware Shopping List

3. Step 1: Install Home Assistant

Set up your Home Assistant hardware before migrating any devices. This ensures you have a working target system.

Home Assistant Green (Recommended)

1. Connect Ethernet cable and USB-C power
2. Wait 5-10 minutes for initial boot
3. Navigate to http://homeassistant.local:8123 in your browser
4. Complete the onboarding wizard (create account, set location, configure timezone)

Raspberry Pi or VM

If using a Pi or virtual machine, download the appropriate image from home-assistant.io/installation and flash it to an SD card or disk. The onboarding process is the same once booted.

Essential First Steps

• Install the Samba share add-on (for easy config file access)
• Install the File editor add-on (for YAML editing in the browser)
• Set up backups (Settings → System → Backups)
• Consider Nabu Casa subscription ($7.50/month) for easy remote access, or set up your own reverse proxy later

4. Step 2: Set Up Zigbee and Z-Wave

Zigbee: ZHA vs Zigbee2MQTT

You have two options for Zigbee in Home Assistant:

• ZHA (Zigbee Home Automation): Built into HA core. Easiest setup. Good for most users. Plug in the SkyConnect and HA auto-detects it.
• Zigbee2MQTT: Runs as a separate add-on. More advanced, supports more devices, offers device-level configuration. Requires MQTT broker (Mosquitto add-on).

Setting Up ZHA

1. Plug in the SkyConnect USB coordinator
2. HA should auto-discover it. Go to Settings → Devices & Services
3. Click Configure on the discovered Zigbee device
4. Select the serial port and confirm

Z-Wave JS

If you have Z-Wave devices:

1. Plug in your Z-Wave USB controller
2. Install the Z-Wave JS add-on from the add-on store
3. Configure it to use your Z-Wave USB device
4. The Z-Wave JS integration will appear in Devices & Services

5. Step 3: Migrate Zigbee Devices

Zigbee migration is straightforward but requires patience. Work through devices one at a time.

Migration Order

Start with mains-powered devices (plugs, switches, bulbs) before battery-powered devices (sensors, buttons). Mains-powered Zigbee devices act as routers in the mesh network. Having them connected first gives battery devices a stronger mesh to join.

For Each Zigbee Device

1. Remove from SmartThings: Open the ST app, go to the device, and select "Remove Device." Wait for confirmation.
2. Put device in pairing mode: Most Zigbee devices: hold the button for 5-10 seconds until the LED flashes rapidly. Check the device manual for exact instructions.
3. Pair with Home Assistant: In HA, go to Settings → Devices & Services → ZHA → Add Device. HA will scan for pairing devices.
4. Name and assign to area: Give the device a meaningful name and assign it to the correct room/area in HA.
5. Test: Verify the device responds to commands and reports status correctly.

Tips for Smooth Zigbee Migration

• Move 3-5 devices at a time, not all at once. Let the mesh stabilize between batches.
• If a device won't pair, try a factory reset (usually a long-press sequence specific to the device).
• Keep the SmartThings hub powered on during migration so remaining devices continue working.
• Zigbee channels: ZHA defaults to channel 15. If you experience interference, try channels 20 or 25.

6. Step 4: Migrate Z-Wave Devices

Z-Wave migration is the most time-consuming part of this process. Unlike Zigbee, Z-Wave devices must be formally "excluded" from one controller before they can be "included" on another.

The Exclusion/Inclusion Process

1. Put the old SmartThings hub in exclusion mode: In the ST app, go to Add Device → Scan Nearby. The hub enters a general exclusion mode.
2. Trigger exclusion on the device: Press the device's inclusion/exclusion button (varies by device). The ST app should confirm the device was removed.
3. Include on Home Assistant: In the Z-Wave JS UI, click "Include Node." Select the security level (S2 Authenticated is recommended for locks and most devices). Trigger the inclusion button on the device.
4. Complete S2 security pairing: If the device supports S2, you may need to enter a PIN or scan a DSK code from the device or its documentation.

Device-Specific Notes

Z-Wave Locks (Schlage, Yale, Kwikset)

• Locks are the most finicky devices to migrate. Keep the lock within 3 feet of the Z-Wave controller during pairing.
• S2 security is required for locks. Have the DSK (Device Specific Key) ready. It's usually on a card included with the lock or on a sticker inside the battery compartment.
• If pairing fails, factory reset the lock (consult the manual) and try again.
• After pairing, test lock/unlock and PIN code management before moving to the next device.

Z-Wave Switches and Dimmers

• These are usually straightforward. Exclude from ST, include on HA.
• Some switches have specific button sequences for exclusion/inclusion. Check the manual.
• Multi-tap features (double-tap, triple-tap) may need configuration in Z-Wave JS after pairing.

Z-Wave Sensors

• Battery-powered sensors may need to be woken up during pairing (press the inclusion button).
• After pairing, sensor reporting intervals may need adjustment in Z-Wave JS device configuration.

7. Step 5: Rebuild Automations

This is where Home Assistant really shines compared to SmartThings. HA automations are more powerful, more flexible, and run locally.

SmartThings Routines to HA Automations

For each SmartThings Routine, create an equivalent HA automation. The structure maps roughly like this:

• ST "If" section → HA trigger
• ST "Only when" section → HA condition
• ST "Then" section → HA action

Common Migration Examples

"Turn on lights at sunset" becomes:

automation:
  - alias: "Lights on at sunset"
    trigger:
      - platform: sun
        event: sunset
        offset: "-00:15:00"
    action:
      - service: light.turn_on
        target:
          entity_id: light.living_room
        data:
          brightness_pct: 80

"Lock door at night" becomes:

automation:
  - alias: "Lock all doors at 10 PM"
    trigger:
      - platform: time
        at: "22:00:00"
    action:
      - service: lock.lock
        target:
          entity_id:
            - lock.front_door
            - lock.back_door

"Turn off everything when I leave" becomes:

automation:
  - alias: "Away mode"
    trigger:
      - platform: state
        entity_id: group.family
        to: "not_home"
        for: "00:10:00"
    action:
      - service: light.turn_off
        target:
          entity_id: all
      - service: climate.set_hvac_mode
        target:
          entity_id: climate.thermostat
        data:
          hvac_mode: "away"
      - service: lock.lock
        target:
          entity_id: all

HA Features SmartThings Doesn't Have

• Templates: Dynamic values in automations (e.g., "set brightness to 50% during day, 20% at night")
• Input helpers: Virtual switches, dropdowns, and sliders for manual override control
• Scripts: Reusable action sequences callable from multiple automations
• Blueprints: Pre-built automation templates from the community
• Conditional actions: If/else logic within a single automation

8. Step 6: Migrate WiFi Devices

WiFi devices are the easiest to migrate because they don't need to be re-paired with a radio. They just need a new integration in Home Assistant.

Common WiFi Devices

• TP-Link Kasa: Auto-discovered by HA. See our TP-Link Kasa guide.
• Philips Hue (via bridge): Add the Hue integration in HA. See our Philips Hue guide.
• Ecobee thermostat: Add via HomeKit Controller integration. See our Ecobee guide.
• Ring cameras: Add the Ring integration. See our Ring guide.
• Sonos speakers: Auto-discovered by HA. See our Sonos guide.

Devices That May Not Transfer

Some WiFi devices connect to SmartThings via a cloud-to-cloud integration. These typically have their own app and can be added to HA directly using their native integration. Check the Home Assistant integrations list for your specific device.

9. What You Cannot Migrate

A few things are SmartThings-exclusive and have no direct equivalent in Home Assistant:

• ADT security panels: The SmartThings ADT Home Security Starter Kit uses a proprietary connection that only works with the SmartThings hub. These cannot be migrated.
• Samsung appliances (cloud-to-cloud): Samsung refrigerators, washers, and ovens that connect via SmartThings cloud may not have HA integrations. Check the integrations list.
• SmartThings-exclusive automations: Smart Home Monitor alerts and some Samsung ecosystem automations have no HA equivalent. Rebuild them using HA's more powerful automation engine.
• SmartThings Find (device tracking): Samsung's device tracking network is not available in HA. Use HA's built-in device tracker with companion app or router integration instead.

10. Parallel Operation Period

We strongly recommend running both SmartThings and Home Assistant simultaneously for at least 2 weeks before fully cutting over.

How to Run in Parallel

• Keep the SmartThings hub powered on for remaining devices
• Optionally add the SmartThings integration in Home Assistant to control ST devices from HA during transition
• Move devices in batches (room by room or protocol by protocol)
• Leave critical devices (locks, security cameras, thermostat) on SmartThings until the rest is proven stable

What to Watch For

• Zigbee mesh stability: New mesh networks take 24-48 hours to fully optimize routing. Don't judge reliability until the mesh settles.
• Automation reliability: Test every automation manually before relying on it
• Battery sensor accuracy: Some battery sensors report inaccurate levels for the first few days after pairing
• Z-Wave device responsiveness: Z-Wave mesh builds route tables gradually. Devices may be slow for the first day.

11. Post-Migration Cleanup

Once everything is stable on Home Assistant and you've run in parallel for at least 2 weeks:

Final Steps

1. Factory reset the SmartThings hub: Hold the reset button for 15 seconds. This removes all device associations and account data.
2. Cancel any SmartThings-related subscriptions: If you were paying for SmartThings premium features or connected services.
3. Remove the SmartThings integration from HA (if you added it for parallel operation).
4. Update your network: Assign static IPs or DHCP reservations for all WiFi smart home devices.
5. Create a full HA backup: Now that everything is configured, create a complete system backup.

Optional: Sell or Repurpose the SmartThings Hub

After factory reset, SmartThings hubs can be sold or given away. The Aeotec Smart Home Hub (rebranded SmartThings) still has an active market. Alternatively, keep it as a spare in case you ever need a temporary Zigbee/Z-Wave bridge for testing.

12. Sources

This guide was compiled from official documentation and community resources:

• Home Assistant Installation Guide
• Home Assistant ZHA Integration
• Home Assistant Z-Wave JS Integration
• Zigbee Device Compatibility Repository
• Z-Wave JS Device Database

Last verified: 2026-03-20 against Home Assistant 2026.1. If you find outdated information, let us know.