SmartThings hubs (the Aeotec generation and the older Samsung-branded models) communicate their state through a single multicolor LED. The same color can mean different things depending on whether it is solid, pulsing slowly, or pulsing fast. This reference lists every documented pattern and what it actually requires from you.
Green
Solid green: hub is online, all radios operational, cloud connection healthy. This is the normal state. No action needed.
Slowly pulsing green: hub is booting. Wait up to two minutes. If it does not transition to solid green within two minutes, the boot is stuck; see our SmartThings stuck boot recovery guide.
Quickly pulsing green: hub is in pairing mode for a Z-Wave or Zigbee device. This was triggered intentionally from the SmartThings app and will time out after a few minutes if no device is added.
Blue
Solid blue: this should not happen on a normal SmartThings hub. If you see it, the hub is in factory mode and waiting for first-time setup. Open the SmartThings app and complete the welcome flow.
Slowly pulsing blue: hub is waiting for Wi-Fi credentials. Only applies to Wi-Fi capable hubs. Open the SmartThings app to set the Wi-Fi network.
Quickly pulsing blue: Bluetooth pairing mode, used briefly during initial setup to communicate with your phone. Will not persist long.
Yellow
Solid yellow: firmware update in progress. Do not unplug. This can take up to fifteen minutes for major updates. Unplugging during a yellow state can brick the hub.
Slowly pulsing yellow: hub is connected to the local network but cannot reach the SmartThings cloud. The hub will continue to function for local-only automations but cloud features (voice control, remote access, third-party integrations) are offline. Check your internet connection. If your internet is healthy, check status.smartthings.com.
Quickly pulsing yellow: hub is downloading a firmware update. Will transition to solid yellow when the download completes and the install starts.
Magenta or purple
Solid magenta: hub is performing a Z-Wave network heal. This is initiated manually from the app. Lasts up to thirty minutes. Do not power-cycle during this time.
Slowly pulsing magenta: hub is stuck in startup, usually waiting on a service that failed to initialize. This is one of the most common stuck-boot symptoms. See the dedicated recovery guide.
Red
Solid red: critical fault. Either the Zigbee or Z-Wave radio has failed, or the hub’s main board has detected a temperature or voltage anomaly. Unplug, wait two minutes, plug back in. If red returns, the hub may need replacement.
Slowly pulsing red: Z-Wave or Zigbee radio is initializing after a soft recovery. Should transition within one minute. If it persists for more than five minutes, the radio failed to come up and you need a full power cycle.
Quickly pulsing red: hub is performing a factory reset. This is triggered by holding the reset button for thirty seconds. If you did not intentionally trigger this, unplug the hub immediately to prevent the reset from completing.
White
Solid white or off: hub is off, lost power, or has a power adapter issue. Try a different known-good 12V 2A adapter. If the LED stays off with a known-good adapter, the main board has failed.
Cycle through colors
If the LED cycles through several colors during boot, the hub is healthy and going through its normal startup sequence. The sequence usually goes: yellow (hardware init), green slow pulse (kernel boot), red brief flash (radio init), green slow pulse (service start), solid green (ready). The entire cycle takes about ninety seconds.
What to do when you see a pattern not in this list
Some pre-release firmware introduces patterns that are not documented. If you see something that does not match anything here, the safest first action is a thirty-second power cycle. If the pattern persists after power cycle, take a video of it and contact SmartThings support. They can usually correlate the pattern with internal firmware build identifiers.
How to read the LED through the hub’s plastic case
The LED on the Aeotec hubs is diffused through a frosted plastic ring on the front. In bright daylight the color can be hard to read. The cleanest way to confirm a color is to view it head-on in a dim room. The most commonly confused pairs are yellow vs green slow-pulse, and red vs magenta. If you cannot tell, use your phone camera; the camera sensor distinguishes the wavelengths more clearly than the human eye does.
LED brightness control
The SmartThings app lets you dim the LED to one of three brightness levels, including off. Going to Settings, then your hub, then LED Brightness. If you have the LED set to off and the hub is faulting, you will not see the diagnostic. Always turn LED back on temporarily when troubleshooting.
Building intuition for the patterns
After living with a SmartThings hub for a few months, you stop reading individual LED codes and start recognizing patterns. Pulsing green for thirty seconds after a known firmware update is normal. Pulsing green for two minutes is a stuck boot. A brief red flash when your spouse is heating leftovers is the microwave-Zigbee channel interaction, not a fault.
Take a video of your hub’s LED during a healthy boot once a year. Compare against current behavior if something feels off later. The first thing support asks for is exactly this kind of comparison data. For deeper boot-state issues, see our stuck boot recovery guide.
The LED dim setting and why it matters in diagnostics
SmartThings hubs let you dim the LED for ambient comfort. The lowest setting is barely visible. When troubleshooting, temporarily bump it to maximum brightness so you can read the color and pulse pattern clearly. Forget this step and you end up squinting at a 5% LED trying to tell green from yellow. The broader pattern of diagnostic affordances applies to most hubs as discussed in our Echo as Zigbee hub guide.
The state worth photographing
The first time you see an unfamiliar LED pattern, take a short video before troubleshooting. The video lets you compare to documentation later and is invaluable if you escalate to support. The same documentation principle saves time when migrating to a new hub, as covered in our Hue migration guide.
