Getting started with SmartThings (Oct 2026): hubs, Edge drivers, Australian considerations

Discuss the Samsung Smartthings HUB and ecosystem
Post Reply
User avatar
ZerOne
Site Admin
Posts: 216
Joined: Sun Dec 13, 2020 8:21 am

SmartThings is Samsung's smart home platform. It is the most "consumer-friendly" of the platforms we cover on this forum: you use the SmartThings app with a Samsung account, add devices, and build routines. For hobbyists the interesting part is the hub, which can run device integrations locally using Edge drivers.

Compiled from SmartThings developer documentation and Aeotec's published specs as at October 2026. Anything marked "third party" is not from an official source - please verify before buying. Corrections welcome.

1. How it fits together
  • SmartThings represents every device through its Capabilities model (switch, temperature, motion and so on).
  • Edge drivers translate between that capability model and a device's own protocol (Zigbee, Z-Wave, Matter or LAN). They are written in Lua and run on the hub, so commands to Hub Connected devices execute locally. Libraries are provided for Matter, Zigbee and Z-Wave, and Edge supports TCP/TLS/UDP sockets (including multicast), which is what makes LAN integrations possible.
  • Edge replaced the old Groovy-based Device Handlers; the old "Groovy IDE" style of custom code is gone, and anything you read on the web that mentions Device Handlers or SmartApps in Groovy is out of date.
  • The app, your Samsung account, and the cloud still sit in the path for many features (routines, remote access, voice assistants). I would love to hear from anyone who has measured exactly what keeps working with the internet unplugged.
2. Hub hardware (and the Australian catch)

The Aeotec Smart Home Hub (3rd generation, model family GP-AEOHUBV3) is the current standalone SmartThings hub that Aeotec documents. Per Aeotec's technical specifications page:
  • Radios: Z-Wave Plus, Zigbee, Thread, Matter, Wi-Fi (a/b/g/n/ac) plus 10/100 Ethernet
  • 528 MHz ARM Cortex-A7, 256 MB RAM
  • Needs the SmartThings app (Android 10+ or iOS 12+)
  • Z-Wave frequency is region-locked: EU/UK model 868.4 MHz, US 908.4 MHz, and AU/NZ model GP-AEOHUBV3AN at 921.4 MHz
In Australia that means: check the model code ends in AN before you pay. A US or EU hub will not talk to ANZ-frequency Z-Wave devices. (Third party: one Australian smart home site reported in August 2026 that the ANZ hub was sold through a single importer, with an Amazon AU listing being a parallel import outside Aeotec's warranty, and stock often out. Treat that as a pointer, not gospel - stock and prices change.)

Zigbee and Thread/Matter are on 2.4 GHz and are not region-locked in the same way.

3. Edge drivers: what you need to know
  • Most users never write a driver. Official drivers are delivered by SmartThings; community drivers are delivered through driver channels that you enrol your hub in using an invitation link.
  • Drivers in a channel are locked to a specific version. A newer version published later does not change what is installed on your hub until you install it again.
  • SmartThings' own caution: third-party Edge drivers are not maintained or reviewed by SmartThings, so support comes from the driver's developer.
  • SmartThings' public driver source lives at SmartThingsCommunity/SmartThingsEdgeDrivers. The docs also describe an Edge Device Builder for bringing a device to the platform without writing code.
A practical walkthrough for installing a community driver and switching a device over is in the project thread in this forum.

4. First things to do
  1. Set up the app and hub, and make sure the hub firmware is up to date.
  2. Add Zigbee/Z-Wave/Matter devices through the app (Add device > Scan nearby). Put Z-Wave devices into pairing mode when the app asks.
  3. Build a couple of routines to get a feel for the automation model.
  4. Only then look at community Edge drivers for devices that the stock driver handles poorly.
5. Strengths and limitations (my view)
  • Strengths: easy onboarding, good mobile app, Zigbee + Z-Wave + Thread/Matter radios in one hub, local execution for Edge-driver devices, large "works with" device list.
  • Limitations: much less low-level control than HA/openHAB/Domoticz; you depend on a Samsung account; automation depth is limited compared with a script-based system; and for ANZ you have to be careful about hub variants and stock.
6. Links
Question: which SmartThings hub are you using in Australia and where did you get it? And if you have moved some devices to Home Assistant or openHAB, what pushed you over (or kept you on SmartThings)?
Top
Post Reply

Return to “Smartthings Hub Discussion”