| Situation | Best Option |
|---|---|
| Regular update | **OTA** |
| OTA failed or system unstable | **Type-C Cable** |
| Device won’t start / “bricked” | **SD-Card** |
Hint: if your path is long for typing, copy it, and in CMD enter cd + do right click. This will insert Clipboard content into CMD window.
[](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/yfjimage.png) --- ### 6) Start the flashing script **Important:** **Do not** connect the SMHUB yet. The script need to be run first. Run: `flash.bat` By typing this command `flash.bat` and pressing **Enter** button. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/ncyimage.png) --- ### 7) Now connect the SMHUB When `flash.bat` is running, **connect SMHUB to the PC via USB-C** (Type-C port on the back of SMHUB, near Ethernet port) The script will detect the device and begin flashing automatically. You’ll see progress output in the CMD window. > If nothing happens for ~a while, try another USB port or USB-C cable, but **keep the script running** while you reconnect the cable. > > [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/CArimage.png) --- ### 8) Wait for “Flashing completed” (script finishes) - When the script completes, it will show a success message and return to the prompt or close. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/9NMimage.png) - You can now safely disconnect the SMHUB from the PC and power it normally (via its regular power supply), **or** leave USB-C connected if it provides power. --- ### **8-b) IF THE FLASHING PROCESS DOES NOT START** In some cases, removing the PoE add-on may help to start the flashing process successfully. If your device does not start flashing using either the Type-C or SD-Card method, please follow the steps below: 1. Open the enclosure (no screwdrivers are required, as the enclosure is screwless). 2. Physically disconnect the PoE add-on. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/xfhimage.png) 3. **To be even more secure, please remove 4G and Z-Wave addons if you have them installed.** 4. Start the flashing process again. Try to boot without the add-on first. Once the device flashes and boots successfully, you can reinstall the add-on. --- ### 9) First boot and LED cues (what “ready” looks like) **First start takes longer than subsequent boots.** This is normal. When the SMHUB starts up after flashing, the LEDs show you exactly what’s happening. Here’s what to watch step by step: 1. **Power ON indicator:** As soon as you plug in the SMHUB, the **small green LED near the buttons** (not the Ambilight LEDs) turns **ON**. → This simply means the device is receiving power. If you can't power your device - check [this](https://smlight.tech/support/manuals/books/smhub/page/troubleshooting#bkmrk-9.1-power-%26-boot) bug. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/Lhzimage.png) 2. **Blue chase effect (Ambilight):** Right after powering on, you’ll see a **moving blue light** (chase effect) running around the Ambilight LEDs. → This means the system is booting — please wait. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/smhub-rotating.gif) 3. **Blue effect stops:** When the **blue chase effect stops**, it means the **core system has finished booting** and **SSH access is available**. → From this point, advanced users can connect via SSH if needed. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/YAtimage.png) 1. **Green Ambilight turns on:** After the delay (1-2 min), all **green Ambilight LEDs will light up at once.** → This means that **Web UI and all apps are fully loaded** and ready to use. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/3wLimage.png) The green lights will stay on for about **1 minute**, then turn off automatically. > 💡 **In simple words:** > > - Blue moving lights = starting up > - Blue stops = system ready for SSH > - Green lights = Web interface ready to use --- ### 10) (Optional) Quick post-flash checks **Web UI:** - Open a browser and go to: `http://smhub.local/` (or your device’s IP). [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/WeYimage.png) **SSH (from Windows using built-in OpenSSH or PuTTY):** - Hostname: `smhub.local` (or your device’s IP) - Username: `smlight` - Password: `smlight` --- ## Troubleshooting ### A) The script doesn’t detect my device - **Most likely cause:** Device connected **before** `flash.bat`. **Fix:** Close the script, **unplug** SMHUB, re-run steps 4–7 exactly: admin CMD → `flash.bat` → **then** connect SMHUB. - Try a different USB port or another **data-capable** USB-C cable. ### B) Driver didn’t install or Windows blocked it - Re-run `driver\smhub-driver.exe` as admin. - Approve any Windows prompts. - Reboot Windows if the installer requests it, then try again. ### C) “Access denied” or “cannot open port” - You’re likely not in an **Administrator** CMD. Close CMD, re-open **as Administrator**, repeat from step 5. ### D) Flashing stops or errors out mid-way - Leave the CMD window open; wait a bit to ensure it’s not still working. - If it clearly failed, **unplug** SMHUB, close the CMD, reopen **admin** CMD, start `flash.bat` again, and **only then** plug SMHUB back in. ### E) SSH/Web UI doesn’t come up after flashing - Give the device more time on the first boot. - Watch the LEDs: - **Blue ambilight LED stopped running** → SSH should be ready. - **All ambilight greens lit** → Web UI should be ready. - If still nothing, power-cycle the SMHUB and check your network/DHCP (try accessing by IP, not by hostname). # Update/Restore using SD-Card 👉 **Download the firmware ZIP** from your usual link (latest): SD-CARD RESTORE FIRMWARE: **prod**: [os\_v0.9.9](https://updates.smlight.tech/firmware/smhub/os/smhub_os_v0.9.9.zip) , **dev**: [os\_v1.0.0.dev3](https://updates.smlight.tech/firmware/smhub/os/smhub_os_v1.0.0.dev3.zip) (previous: [os\_v0.3.11](https://updates.smlight.tech/firmware/smhub/os/smhub_os_v0.3.11.zip) | [os\_v0.3.10](https://updates.smlight.tech/firmware/smhub/os/smhub_os_v0.3.10.zip) | [os\_v0.3.7](https://updates.smlight.tech/firmware/smhub/os/smhub_os_v0.3.7.zip)) and save the ZIP file to your computer (e.g., `Downloads`). You’ll need: - A **microSD card** (8–64 GB is ideal) + **microSD–to–SD** adapter if your PC needs it - A Windows PC - A way to read/write the microSD card (built-in reader or USB adapter) ### ⚙️ What You’ll Do 1. Download the ZIP file with the firmware 2. Format microSD to **FAT32** 3. Copy **three files** from the archive folder ROM onto the **root** of the card 4. Insert the card into the SMHUB (**click** fully) 5. Power on → **wait ~4 minutes** (silent) 6. Power off → **remove the card** 7. Power on → watch LED cues → open **smhub.loca** --- ## 1) Get the firmware and unzip it 1. Click the firmware link above and **download the ZIP** to your computer (e.g., Downloads). *\[screenshot: browser download\]* 2. **Right-click** the ZIP → **Extract All…** → choose a simple folder (e.g., `C:\SMHUB\firmware\`). Inside the unzipped folder, you’ll see these **three files** in the **rom** folder. You’ll copy them to the SD card: - `emmc.img` - `fip.bin` - `partition_gpt.xml` --- ## 2) Format the microSD card to **FAT32** > This erases the card completely. Back up anything important first. 1. Insert the **microSD** (or SD adapter with the microSD inside) into your PC. 2. Open **This PC** (Windows Explorer). 3. **Right-click** the SD card drive (e.g., “SDHC (E:)”). 4. Click **Format…**. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/select-format.jpg) 5. In the **Format** window: - **File system:** choose **FAT32** - **Allocation unit size:** leave **Default or 16kb** - **Volume label:** optional (e.g., `SMHUB`) - **Quick Format:** **checked** (recommended) [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/format-settings.jpg) 6. Click **Start**, then **OK/Yes** to confirm. 7. Wait for the **Format Complete** message → click **OK** and **Close**. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/format-completed.jpg) > **Tip:** If your SD card is larger than 32 GB and FAT32 isn’t shown, try another (smaller) card. (Advanced users: a third-party FAT32 formatter also works.). > **Check the lock switch:** If you’re using a full-size SD adapter, make sure the **tiny switch on its side is not set to “LOCK.”** If locked, Windows won’t let you copy files. --- ## 3) Copy the **three files** to the **root** of the SD card 1. Open the folder you unzipped earlier. 2. **Select these three files:** `emmc.img`, `fip.bin`, `partition_gpt.xml` 3. **Copy** them (Ctrl+C). 4. Open your SD card drive in **This PC** and **Paste** (Ctrl+V). - The files must be in the **root** of the SD card (not inside any folder). [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/copying-to-sdcard.jpg) 5. When copying finishes, **right-click** the SD card drive → **Eject** → remove the card. --- ## 4) Insert the microSD card into the SMHUB - With the SMHUB **powered OFF**, insert the microSD into the slot. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/VTRimage.png) - **Push until you feel a “click.”** It must be fully seated. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/M5mimage.png) --- ## 5) Power ON and **wait ~4 minutes until completion** - Connect power to the SMHUB. - The device will automatically and silently flash itself from the SD card. - The blue LED (located near the IR transmitter) will begin blinking slowly (approximately once every 2 seconds), indicating that the flashing process has started. Please note that LED indications during SD-card flashing are available only starting from firmware **0.3.1-dev2 (24 Oct 2025)**. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/smhub-flashing-sd-card.gif) - Once the process is complete, the same blue LED will start blinking faster (about 3 times per second). This means the flashing was successful. You can now disconnect the device from power (fully disconnect it — do not simply reboot). There is no need to power it on again with the SD card inserted, as the flashing process would otherwise start again. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/smhub-flashing-sd-card-completed.gif) --- ## **5-b) IF THE FLASHING PROCESS DOES NOT START** In some cases, removing the PoE add-on may help to start the flashing process successfully. If your device does not start flashing using either the Type-C or SD-Card method, please follow the steps below: 1. Open the enclosure (no screwdrivers are required, as the enclosure is screwless). 2. Physically disconnect the PoE add-on. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/xfhimage.png) 3. **To be even more secure, please remove 4G and Z-Wave addons if you have them installed.** 4. Start the flashing process again. Try to boot without the add-on first. Once the device flashes and boots successfully, you can reinstall the add-on. --- ## 6) Power OFF and **remove the SD card** - After ~5 minutes, **power OFF** the SMHUB. - **Remove** the microSD card. > ⚠️ **Important:** If you **leave the SD card in** and power on, the SMHUB will **start flashing again**. Always **remove the card before** the next boot. --- ## 7) Power ON again and watch the LEDs (readiness) Boot the SMHUB **without** the SD card: **First start takes longer than subsequent boots.** This is normal. When the SMHUB starts up after flashing, the LEDs show you exactly what’s happening. Here’s what to watch step by step: 1. **Power ON indicator:** As soon as you plug in the SMHUB, the **small green LED near the buttons** (not the Ambilight LEDs) turns **ON**. → This simply means the device is receiving power. If you can't power your device - check [this](https://smlight.tech/support/manuals/books/smhub/page/troubleshooting#bkmrk-9.1-power-%26-boot) bug. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/Lhzimage.png) 2. **Blue chase effect (Ambilight):** Right after powering on, you’ll see a **moving blue light** (chase effect) running around the Ambilight LEDs. → This means the system is booting — please wait. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/smhub-rotating.gif) 3. **Blue effect stops:** When the **blue chase effect stops**, it means the **core system has finished booting** and **SSH access is available**. → From this point, advanced users can connect via SSH if needed. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/YAtimage.png) 1. **Green Ambilight turns on:** After a short delay, all **green Ambilight LEDs will light up at once.** → This means that **Web UI and all apps are fully loaded** and ready to use. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/3wLimage.png) The green lights will stay on for about **1 minute**, then turn off automatically. > 💡 **In simple words:** > > - Blue moving lights = starting up > - Blue stops = system ready for SSH > - Green lights = Web interface ready to use --- ### 8) (Optional) Quick post-flash checks **Web UI:** - Open a browser and go to: `http://smhub.local/` (or your device’s IP). [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/WeYimage.png) **SSH (from Windows using built-in OpenSSH or PuTTY):** - Hostname: `smhub.local` (or your device’s IP) - Username: `smlight` - Password: `smlight` --- ## Troubleshooting (quick) - **Nothing happens after power on?** Ensure the **three files** are on the **root** of the SD card, card is **FAT32**, and the card was **fully clicked in**. - **Flashing loops every time I power on?** You forgot to **remove the SD card**. Power off, **remove card**, then power on. - **Web UI not loading yet?** Wait for the **green Ambilight LEDs**. Blue stopped = SSH ready; Green on = Web UI ready. - **Card won’t format / no FAT32 option?** Try a **smaller card** (8–32 GB is easiest) or a different PC card reader. --- # SMHUB Early Adopter – Quick Start Guide The **SMHUB Early Adopter Version** is the first public release of our multi-radio smart hub. It’s designed for early buyers who want to explore the platform before the full release.| **\#** | **Date** | **Type** | **Version** | **Updates / Changes** |
| 17 | 28 Feb 2026 | smhub-os smhub-services openthread | 0.9.6dev0.2.11 0.3.0-1 | **smhub-services, smhub-web & SMHUB OS Released – Key Features:** - **Linux Kernel 6.18** (upgrade from vendor kernel 5.4.x) for better stability, performance, and hardware support - **Base for the pre-1.0.0 release candidate** (DEV channel, but recommended as a strong daily version) - **Factory Reset via hardware button** (hold the middle button for 10 seconds on SMHUB Essentials/Premium) - **User data backup & restore** support added - **New “Backups” page** in the Web UI for managing backups **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes) |
| 16 | 22 Jan 2026 | smhub-os smhub-services openthread | 0.3.11 0.2.8 0.2.1-2 | **smhub-services, smhub-web & SMHUB OS Released – Key Features:** - Fixed issue with `cron.daily` preventing daily package updates - Improved kernel options required for OTBR firewall functionality - Migrated autostart files to new structure for improved service handling - Added support for configuring the OTBR app directly - Improved logging and debugging output - Improved pairing flow for new Thread devices - Added support for firewall and NAT64 configuration 💡 **How to update:** **SMHUB-OS:** Settings -> Update and restore **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes) |
| 15 | 19 Jan 2026 | smhub-os smhub-services smhub-web | 0.3.10 0.2.7 0.2.23 | **smhub-services, smhub-web & SMHUB OS Released – Key Features:** - Added nftables (+ iptables compat) for Tailscale/firewall - Auto log truncation (daily / size limit) – to resolve freezes issue - Improved NanoMR4 EFR flashing (CC flash reset) - Zigbee2MQTT default logs set to info - Fixed rare boot into backup partition - Faster startup (deferred component loading) - Increased flasher load timeout - Updated GPIO mapping for kernel 6.18 - Updated Buildroot to 2025.11.x 💡 **How to update:** **SMHUB-OS:** Settings -> Update and restore **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes) |
| 13 | 26 Nov 2025 | smhub-os smhub-services smhub-web | 0.3.7 0.2.2 0.2.16 | **smhub-services, smhub-web & SMHUB OS Released – Key Features:** - **smhub-services v0.2.2** • Added support for reading **EEPROM v1 format** • Radio flashing endpoints updated to support model-based flashing • Updated **pysmlight v0.2.11** for Nano flashing • Corrected some default Zigbee2MQTT settings - **smhub-web v0.2.16** • Radio page now supports **Nano Mg24** flashing • Device **model displayed in sidebar** • Updated default Zigbee2MQTT settings • **App status** displayed on Apps settings page • Progress bar + changelog displayed for **OS updates** - **SMHUB OS v0.3.7** • Added hooks enabling **model-specific features** • **Nano boot LED indicators** enabled • Fixed duplicate services appearing after OTA restart 💡 **How to update:** **SMHUB-OS:** Settings -> Update and restore **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes) |
| 12 | 22 Nov 2025 | smhub-os smhub-services smhub-web | 0.3.6 0.2.1 0.2.15 | **smhub-services v0.2.0 & smhub-web v0.2.14 – Key Features** - **CC Radio Flashing:** Added full support for flashing TI CC radios (CC26xx) directly from the Web UI. - **Improved Radio Flashers:** Better progress bar behaviour and clearer error messages during flashing of CC and EFR32 radios. - **App Logs & Restart Buttons:** Iframe improvements and new App Logs + Restart controls added for supported apps. - **Run/Stop App Fixes:** Run/Stop buttons now work more reliably across all apps. - **Log Formatting Fix:** Resolved issue where logs were incorrectly rendered in Title Case. - **Backend Flashing Support (services):** Added *smlight-cc-flasher* and integrated flashing logic into the backend. - **Zigbee2MQTT Defaults Fix:** Corrected default settings in the Web UI configuration form. - **Node-RED Logs Fix:** Fixed Node-RED log handling so logs display properly. - **OS Base Image Updated:** OS v0.3.6 now uses Buildroot v2025.08.1 and includes correct paths for CC and Silabs flashers. 💡 **How to update:** **SMHUB-OS:** Settings -> Update and restore **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes) |
| 11 | 15 Nov 2025 | smhub-services smhub-web | 0.2.0 0.2.14 | **smhub-services v0.2.0 & smhub-web v0.2.14 – Key Features** - **EFR32 Firmware Flashing:** Built-in flasher for Silicon Labs radios, fully integrated into the UI. - **New Radio Page:** Central place to manage radios and perform flashing operations. - **Run/Stop App Controls:** Start or stop apps directly from the Apps page. - **OpenThread Support:** SMHUB can now be configured as an **OpenThread Border Router** via the UI (flashing + app installation + launch). 💡 **How to update:** **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes) |
| 10 | 09 Nov 2025 | smhub-os | 0.3.4 | **smhub-os Released – Key Features:** **🔹SMHUB OS v0.3.4** - Set the default **apps update channel** to *stable* - Fixed **OTA upgrade issue** affecting users on firmware v0.3.2/v0.3.3 (update to v0.3.4 now available and functional across all installations) - Fixed **UART communication** for baud rates above **115200** 💡 **How to update:** **SMHUB-OS:** Settings -> Update and restore **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-os-0.3.3%2C-smhu](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-os-0.3.3%2C-smhu) |
| 9 | 07 Nov 2025 | smhub-services smhub-web | 0.1.20 0.2.12 | **smhub-services, smhub-web Released – Key Features:** 🔹 **smhub-web v0.2.12** - Added Timezone Selector in *Settings → General* - LTE page fixes: corrected status display and connectivity info - Z-Wave JS page: now indicates if module is installed - App tiles: fixed version comparison bug on app overview page 🔹 **smhub-services v0.1.19** - Timezone management: added backend support for listing and setting timezone - EEPROM integration: added support to read product data from device EEPROM - App update stability: fixed bugs related to version comparison and update channel logic 💡 **How to update:** **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1.-1](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1.-1) |
| 8 | 03 Nov 2025 | smhub-os smhub-services smhub-web | 0.3.3 0.1.18 0.2.11 | **smhub-os, smhub-services, smhub-web Released – Key Features:** 🔹 **smhub-web v0.2.11-1** • New Ethernet settings page • New 4G/LTE management page 🔹 **smhub-services v0.1.18-1** • Added backend support for 4G/LTE • Added peripheral backend layer for future hardware features 🔹 **SMHUB OS v0.3.3** • Added timezone data to the base system *(frontend integration coming soon)* • Added 4G/LTE modem support 💡 **How to update:** **SMHUB-OS:** Settings -> Update and restore **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1.-1](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1.-1) |
| 7 | 28 Oct 2025 | smhub-os smhub-services smhub-web | 0.3.2 0.1.17 0.2.10 | **smhub-os, smhub-services, smhub-web Released – Key Features:** 🔹 **Wi-Fi setup in UI** – scan & connect to 2.4 GHz networks (5 GHz in testing mode – IPv6 works so far) 🔹 **USB Device/Host selector** – switch modes in Settings *(requires reboot)* 🔹 **USB device list** – view connected devices (up to 127 supported) 🔹 **Change device hostname** – directly from the Web UI 🔹 **WireGuard** – now supports hostnames + IPv4 and IPv6 🔹 **Improved recovery** – fixed Type-C / SD-Card flashing, added U-Boot realignment & auto-reinstall scripts 🔹 **Wi-Fi MAC fix** – persistent across reboots 🔹 Added **gpiod** utilities 🔹 **Blue LED** indicators during **Type-C / SD flashing** 💡 **How to update:** **SMHUB-OS:** Settings -> Update and restore **smhub-services/smhub-web:** Apps-> smhub-services/web or via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-2025-oct-28%3A](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-2025-oct-28%3A) |
| 6 | 24 Oct 2025 | smhub-service smhub-web | 0.1.16 0.2.9 | **smhub-services, smhub-web Released – Key Features:** - **💾 Wireguard client Settings in UI:** Configure SMHUB’s internal Wireguard client from the UI (Settings → Wireguard). - 🔄 Small, but helpful tweak - Reboot button at the left bottom corner of the UI :) **Important**: Please update via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-2025-oct-13%3A](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-2025-oct-13%3A) |
| 5 | 18 Oct 2025 | OS smhub-service smhub-web | 0.3.0 0.1.13 0.2.8 | **New SMHUB-OS, smhub-services, smhub-web Released – Key Features:** - 🧠 **MQTT Broker Settings:** Configure SMHUB’s internal MQTT broker directly from the UI (Settings → Mqtt) or link it to an external broker in bridge mode. - 💾 **Read-only RootFS:** The system partition is now read-only for higher reliability; all settings remain saved after OS updates. - ⚙️ **Improved Stability:** Fixed MQTT user saving, web upgrade errors, and refined translations and form handling. - 🪄 **Improved Resets:** Deleting the overlay restores system defaults instantly. Important: Please update via SSH (either Internal console or external SSH client - [manual is here](https://smlight.tech/support/manuals/books/smhub/page/access-smhub-via-external-ssh-client)) by executing these commands: **For more details and to update, follow this guide**: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-os-v0.2.2-%2B%C2%A0sm](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-os-v0.2.2-%2B%C2%A0sm) |
| 4 | 13 Oct 2025 | smhub-service smhub-web | 0.1.9 0.2.5 | **New SMHUB Services v0.1.9 & SMHUB Web v0.2.5 Released – Key Features:** - 🖥 **Web Console (Console Tab):** Run Linux commands directly from the Web UI — no SSH required. - ⚙️ **Improved Logs:** Fixed log visibility for Web and Z-Wave apps. - 🛠 **Fixed Service Installation Hang:** Updates now install reliably via Web UI. - 🚫 **401 Error Fix:** Prevented HEAD request spam in system logs. - 🔄 **Added `opkg update` Endpoint:** Enables smoother package refresh via backend. - 👤 Web terminal now logs in as `smlight` with color-enabled shell. **For more details and to update, follow this guide:** [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1). |
| 3 | 12 Oct 2025 | OS smhub-service smhub-web | 0.2.2 0.1.7-1 0.2.3-1 | **New SMHUB OS 0.2.2 Released – Key Features:** - **Full Kernel OTA Support:** Until now, only WebUI and backend (smhub-services, smhub-web) could be updated via OTA. Starting with version **0.2.2**, the **Linux kernel** is now also OTA-upgradable - no Type-C flashing needed. - **New Logs Tab:** Apps such as **Zigbee2MQTT** now have live log viewing directly in the Web UI. - **Improved System Boot:** Fixed Z-Wave JS startup issue. - **Dashboard Improvements:** Added explanatory notes for clarity. - **Settings Layout Update:** Disabled not-yet-available pages. - **Firmware Version Display:** Added version indicator to the bottom-left corner. - **Coming Soon:** Web console for running Linux commands from **Settings → Console**. **Update Sequence (Required):** 1️⃣ Update **OS to 0.2.1c** 2️⃣ Update **smhub-services** and **smhub-web** to latest versions 3️⃣ Then check **Settings → Update and Backup** to update **OS to 0.2.2** To update, follow this guide: [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-os-v0.2.2-%2B%C2%A0sm](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-os-v0.2.2-%2B%C2%A0sm) **IMPORTANT: if you updated via the UI button, and the UI hangs/freezes, please read the link above for the solution.** |
| 2 | 06 Oct 2025 | OS | 0.2.1c | **New SMHUB OS 0.2.1c Released - Key Features**: - **Kernel OTA Support**: Previously, only the WebUI, backend, and apps supported OTA updates - the kernel did not. Starting with version 0.2.1c, kernel updates now work as well. After this update, the entire system can be updated via OTA, with no need for USB flashing. - **LED Animation During Boot**: After powering on (in about 3–5 seconds), the LEDs display a blue chasing animation. When this animation stops, it indicates that the device is accessible via SSH. Shortly after, all green LEDs turn on, meaning that the Web UI is also accessible. - **Other Internal Improvements and Bug Fixes** To update, please follow this manual: [https://smlight.tech/support/manuals/books/smhub/page/smhub-early-adopter-quick-start-guide#bkmrk-updating-smhub-firmw](https://smlight.tech/support/manuals/books/smhub/page/smhub-early-adopter-quick-start-guide#bkmrk-updating-smhub-firmw) |
| 1 | 26 Sep 2025 | OS | 0.2.0 | Initial release |
| Action | Command / Button |
|---|---|
| Login username | `smlight` |
| Login password | `smlight` |
| Update packages | `sudo opkg update` |
| Upgrade packages | `sudo opkg upgrade` |
| Exit session | `exit` |
| Subsystem | Description |
|---|---|
| **smhub-os** | Core Linux system — provides the kernel, drivers, and low-level environment. |
| **smhub-services** | Backend layer handling configuration, networking, and communication between OS and the web interface. |
| **smhub-web** | Front-end web interface for interacting with the device, viewing system state, and adjusting settings. |
| Component | Version | Description |
|---|---|---|
| **smhub-os** | `0.2.2` | Updated kernel and file system with full OTA kernel flashing support. |
| **smhub-services** | `0.1.7-1` | Improved backend management of configuration and processes. |
| **smhub-web** | `0.2.3-1` | Updated UI with new dashboard and refined settings layout. |
On the first SMHUB models (with old firmware) the web interface will be on port **3000** To it access use: `http://smhub.local:3000`**If you have such a device, we strongly recommend that you immediately update it via USB according to [this guide](https://smlight.tech/support/manuals/books/smhub/page/smhub-early-adopter-quick-start-guide#bkmrk-updating-smhub-firmw)** Old firmware has critical issues that have been fixed in the new version!
- Open a browser and go to: - `http://smhub.local` (mDNS) - or the IP address assigned via DHCP. ### SSH Access - Connect from a terminal: `ssh smlight@smhub.local` - Default credentials are user: **smlight**, password: **smlight** - Use SSH for advanced configuration and Wi-Fi setup until the web Wi-Fi interface is fully implemented. ### USB-C Upstream Mode - If connected via the **USB-C upstream port**, SMHUB may appear as a network device to your host machine. - This allows direct connection without a router. --- ## 3.5 First Boot Behavior - The system automatically starts **Zigbee2MQTT** service. Other services like **Matterbridge** and **Node-RED** could be run manually afterwards. - Service LEDs and RGB LEDs will indicate boot sequence and status. - On first login, you should: 1. Change the default password (via web UI or SSH). 2. Configure your preferred network connection (Ethernet or Wi-Fi). 3. Update system software (see Section 4). --- ## 3.6 Safety Notes - Always use certified power supplies when running from USB-C. - If using the UPS module, only install **good quality18650 cells**. - Ensure proper ventilation - SMHUB is designed for continuous 24/7 operation. # 4. Software & System SMHUB is powered by a **Linux-based operating system** with an integrated **Node.js runtime** and a suite of **smart home applications**. This software foundation provides both **enterprise-grade stability** and **DIY flexibility**. --- ## 4.1 Operating System - **Base:** Lightweight Linux distribution optimized for embedded controllers. - **Runtime:** Node.js preinstalled for native execution of Node.js applications. - **Package Management:** Extendable via Linux packages and Python scripts. - **Update System:** - Secure firmware updates. - Individual application updates independent of OS. --- ## 4.2 Preinstalled Applications ### Zigbee2MQTT (Z2M) - **Preinstalled by default**. - Works with onboard CC26xx or EFR32XX Zigbee radios. - Publishes device data to MQTT. - Compatible with Home Assistant, OpenHAB, Node-RED, etc. - Local dashboard for Zigbee pairing and monitoring. ### Matterbridge - **Preinstalled by default**. - Bridges Zigbee/Thread devices into the Matter ecosystem. - Compatible with Google Home, Apple Home, Amazon Alexa, SmartThings. ### Node-RED - **Preinstalled by default**. - Visual, flow-based automation editor. - Includes libraries for MQTT, Z2M, and Matterbridge. - Accessible via web browser. ### Mosquitto MQTT Broker - **Preinstalled and running by default**. - Provides the MQTT backbone for Zigbee2MQTT, Node-RED, and Matterbridge. - Allows additional MQTT clients to integrate seamlessly with SMHUB. --- ## 4.3 System Services - **Networking** - Ethernet (default). - Wi-Fi 2.4 GHz and 5 GHz (AP and Client modes). - Bluetooth 5.0 with BLE. - **VPN Support** - WireGuard preinstalled. - Secure remote access tunnels. - **USB Passthrough** - Full passthrough of USB dongles to the host stack. - USB protection logic for safe host/device switching. --- ## 4.4 Built-In Visual System - **Ambilight System** - Runs continuously by default. - Uses 12 × WS2812B RGB LEDs for system visualization, notifications, or ambient effects. - User-configurable patterns and colors. - **Service LEDs** - Indicate power, network status, and radio activity. --- ## 4.5 Features in Development - **Buzzer Control** - System and user notifications. - **Audio Output (3.5 mm jack)** - System alerts, notifications, and future media playback. - **IR Transmitter & Receiver** - IR learning and replay for remote-controlled devices. - **Extended LED Controls** - Custom animations and media sync in Ambilight. --- ## 4.6 Developer Options - Full **SSH access**. - Node.js environment ready. - Support for Python scripting and Linux daemons. - Exposed GPIO, UART, I²C, and SPI for DIY hardware extensions. # 5. Network & Connectivity SMHUB provides robust and flexible networking options to ensure reliable operation in both **enterprise environments** and **home setups**. It can connect via **Ethernet, Wi-Fi (2.4/5 GHz), Bluetooth**, and optionally via **VPN tunnels and DDNS services** for secure remote access. --- ## 5.1 Ethernet - **Primary interface** for stable operation. - Supports **100Mb Ethernet** via onboard RJ-45 port. - Recommended for enterprise and multi-device deployments. - Provides lowest latency and highest reliability compared to wireless options. --- ## 5.2 Wi-Fi SMHUB includes **dual-band Wi-Fi** with both **2.4 GHz** and **5 GHz** support. - **2.4 GHz** - Longer range, higher wall penetration. - Ideal for IoT-heavy environments with many legacy devices. - **5 GHz** - Higher throughput. - Less interference in crowded environments. - Suitable for high-speed data transfers and local automations. **Operating Modes:** - **Client Mode** - SMHUB connects to an existing Wi-Fi network. - Configurable via CLI (`nmcli`) or SSH. - Web UI configuration will be available in upcoming updates. - **Access Point Mode (in development)** - SMHUB creates its own Wi-Fi network. - Default SSID: `SMHUB-XXXX` (last 4 MAC digits). - Default password: `smhub1234`. - Useful for first-time setup or when no LAN is available. --- ## 5.3 Bluetooth - **Bluetooth 5.0** with **BLE (Bluetooth Low Energy)** support. - Future updates will expand Bluetooth integration into the web interface. --- ## 5.4 VPN (WireGuard) SMHUB includes **WireGuard VPN** for secure tunneling. - Provides encrypted remote access to SMHUB and connected devices. - Suitable for enterprise remote deployments or secure home use. - Configuration available via CLI or SSH. - Can be combined with DDNS for access without a static IP. --- ## 5.5 USB Networking When connected via **USB-C upstream**, SMHUB can act as a **network device** to the host PC: - Appears as an Ethernet-over-USB adapter. - Provides direct access without needing an external router or switch. - Useful for initial setup, debugging, or portable use cases. # 6. Radios & Protocols SMHUB integrates multiple radios to support a **broad range of smart home and IoT protocols**, making it a true **multi-radio coordinator and Matter bridge**. --- ## 6.1 Zigbee - **Chipset:** TI CC26xx series. - **Port:** /dev/ttyS1 - **Baudrate**: 115200 - **RTS/CTS**: false - **Protocol:** Zigbee 3.0 and legacy devices. - **Software:** Zigbee2MQTT (Z2M). - **Integration:** - Pairs and manages Zigbee devices directly. - Publishes states/events via the preinstalled **Mosquitto MQTT broker**. - Compatible with Home Assistant, OpenHAB, Node-RED, and other MQTT platforms. - **Coordinator Mode:** Can operate as a standalone Zigbee coordinator, without additional servers. --- ## 6.2 Thread - **Chipset:** Silicon Labs EFR32MG series. - **Port:** /dev/ttyS2 - **Baudrate**: 115200 - **RTS/CTS**: false - **Protocol:** Thread 1.1/1.2. - **Integration:** - Acts as an **OpenThread Border Router (OTBR)**. - Works with **Matterbridge**, exposing Thread/Zigbee devices into Matter. - **Use Cases:** - Bridging Zigbee sensors to Matter. - Running mixed Zigbee + Thread networks. --- ## 6.3 Z-Wave - **Radio Module:** EFR32ZG23 expansion module. - **Port:** /dev/ttyS3 - **Baudrate**: 115200 - **RTS/CTS**: false - **Protocol:** Z-Wave 700/800 series, including **Z-Wave Long Range (LR)**. - **Software:** Managed via Z-Wave JS (installable). - **Integration:** - Local Z-Wave or Z-Wave LR networks. - Automation via Node-RED and MQTT. - **Hardware:** Dedicated LED and reset/flash pins for diagnostics and firmware updates. --- ## 6.4 4G/LTE (in development) - **Module:** SIM7672G LTE modem. - **Port:** /dev/ttyS4 - **Baudrate**: 115200 - **RTS/CTS**: false - **Capabilities:** - LTE Cat 1 connectivity. - Interfaces: USB, debug UART. - Antenna connectors for LTE and GNSS. - SIM slot with SIM detection. - **Status:** Hardware fully integrated, **software support is in active development**. - **Planned Functions:** - LTE fallback connectivity. - Remote site deployments without Ethernet/Wi-Fi. --- ## 6.5 Wi-Fi - **Bands:** Dual-band **2.4 GHz** and **5 GHz**. - **Modes:** Access Point (AP) and Client. - **Use Cases:** - 2.4 GHz: long range, high compatibility. - 5 GHz: higher bandwidth, reduced interference. - **Integration:** Used for device connectivity and as a network backbone when Ethernet is not available. --- ## 6.6 Bluetooth - **Version:** Bluetooth 5.0. - **Support:** Bluetooth Low Energy (BLE). --- ## 6.7 Multi-Radio Operation - Zigbee + Thread + Wi-Fi + Bluetooth operate simultaneously out of the box. - Z-Wave and 4G/LTE are available via expansion modules. - Hardware and firmware are designed to minimize interference and ensure stable concurrent radio operations. --- ## 6.8 Matter Bridge SMHUB can function as a **Matter bridge**, allowing non-Matter devices to join modern ecosystems: - Bridges Zigbee and Thread devices into Matter. - Compatible with Google Home, Apple Home, Amazon Alexa, SmartThings. - Entirely **local bridging** — no third-party cloud services required. # 7. User Interface The SMHUB web interface is the primary way to configure and manage the system. It provides access to dashboards, built-in applications, and detailed system settings. --- ## 7.1 Dashboard The **Dashboard** is the starting page of the interface and shows an overview of the hub: - **System Information** - Device model, firmware version, uptime. - CPU load, memory usage, and storage status. - **Network Status** - Ethernet/Wi-Fi interfaces with IP addresses. - VPN (WireGuard) status. - **Radio Status** - Zigbee, Thread, Z-Wave (if installed), Bluetooth. - Service LED indicators and Ambilight effects. - **Service Overview** - Running state of **Zigbee2MQTT, Matterbridge, Node-RED, Mosquitto MQTT broker**. - Quick buttons to start/stop services. --- ## 7.2 Zigbee2MQTT - Direct integration with the **Zigbee2MQTT frontend**. - Allows pairing, removing, and managing Zigbee devices. - Displays a network map, device states, and logs. - Zigbee devices are automatically published to the local **Mosquitto MQTT broker**. --- ## 7.3 Matterbridge - Provides direct access to the **Matterbridge frontend**. - Manages bridging between Zigbee/Thread devices and Matter ecosystems (Google Home, Apple Home, Alexa, SmartThings). - Allows configuration of bridge modes and Matter controllers. --- ## 7.4 Node-RED - Opens the **Node-RED frontend**, a visual automation editor. - Users can create and deploy flows combining Zigbee2MQTT, Matterbridge, MQTT, HTTP APIs, or custom integrations. - Pre-installed flows include templates for MQTT and device automation. --- ## 7.5 Apps The **Apps** section acts as a package manager for SMHUB applications. - **App Management** - Install, uninstall, or update applications. - Configure settings per application. - Start/stop applications with one click. - **Preinstalled Apps** - Zigbee2MQTT - Matterbridge - Node-RED - Mosquitto MQTT broker - **Additional Apps** - Future apps (e.g., Z-Wave JS, custom services) can be added here. - Apps can be distributed as packages and installed via this page. --- ## 7.6 Settings The **Settings** section contains all configuration options for SMHUB. It is divided into modules, each with tabs for **configuration, telemetry, and debug** where available. ### System - Hostname, time zone, system info. - User management (accounts, passwords). - Updates (firmware & app updates). - Backup & restore. - Factory reset. ### Network - Ethernet (DHCP/static). - Wi-Fi (2.4/5 GHz, AP/Client mode). - VPN (WireGuard). - DDNS configuration (DuckDNS, others). - USB-over-network. ### Radios - Zigbee: coordinator settings, pairing mode, diagnostics. - Thread: OTBR management, Matterbridge integration. - Z-Wave (if module installed): inclusion/exclusion, network management. - Bluetooth: enable/disable, scanning, BLE integrations. - 4G/LTE (in development): SIM/APN settings, LTE telemetry, GPS data. ### Audio & Buzzer - Volume control (3.5 mm output). - Enable/disable system notification sounds. - Buzzer toggle and test alerts. ### LEDs - Service LED control. - Ambilight modes (status, animations, user-defined patterns). ### IR - IR transmitter: configure/send commands. - IR receiver: learn remote commands and store them. ### Storage - SD card and eMMC info. - Format, mount/unmount. - Telemetry: usage stats. ### Security - User authentication settings. - SSH toggle. - VPN certificates and DDNS keys. - Firewall and remote access rules. # 8. Modules & Extensions SMHUB is designed to be modular. The **main board** provides essential radios, networking, and I/O, while additional **hardware modules** extend functionality for power resilience, connectivity, and advanced integrations. --- ## 8.1 USB Passthrough - **Purpose:** Enables SMHUB to act either as a **USB host** (powering connected peripherals) or as a **USB device** (connected to a PC or another host). - **Logic:** - Automatically decides whether to supply or draw power. - Prevents reverse powering through integrated FET switching. - **Use Cases:** - Attach Z-Wave or extra Zigbee dongles, printers, audio devices, storage etc. - Connect SMHUB to a PC for development/debugging. - Power downstream devices safely. --- ## 8.2 SD Card - **Slot:** Standard microSD slot on the main board. - **Purpose:** Expand storage for logs, app data, or backups. - **Integration:** - Mounted automatically by the Linux OS. - Users can format, mount/unmount, and monitor usage from the UI. - Support up to 2Tb volume. --- ## 8.3 PoE Module - **Standard:** IEEE 802.3af-compliant. - **Input:** Power delivered via Ethernet cable from a PoE-enabled switch or injector. - **Output:** Stable **5V regulated** supply to the hub. - **Protection:** Surge and ESD protection integrated. - **Monitoring:** “PoE Power Check” exposed in the system for telemetry. - **Use Case:** Ideal for enterprise deployments where powering over Ethernet is standard. --- ## 8.4 UPS Module - **Battery:** Supports **18650 Li-ion cells** (user-installed). - **Charger:** advanced circuit with overcharge/undervoltage protection. - **Conversion:** Step-up/step-down converters to maintain **5V, 3.3V, 1.8V** rails. - **Telemetry:** - Monitors voltage/current - Provides battery health and charge state in the UI. - **Inputs:** Can also accept **DC power** or **solar panels**, making SMHUB deployable off-grid. - **Use Case:** Ensures uninterrupted operation during outages. --- ## 8.5 4G/LTE Module - **Connectivity:** LTE Cat 1 with fallback modes. - **Interfaces:** - Main UART. - USB. - Debug UART. - **SIM Slot:** NanoSIM with detection circuitry. - **Antennas:** Dedicated connectors for LTE and GNSS. - **UI Integration:** - Settings → Radios → 4G/LTE. - SIM/APN configuration, LTE signal telemetry. - **Status:** Hardware available, **software support in development**. --- ## 8.6 DIY Pinouts & Interfaces For advanced users and developers, SMHUB exposes additional hardware interfaces: - **GPIO pins** for general use. - **UART, SPI, and I²C** buses. - **Custom module connectors** for prototyping or specialized hardware. - **Use Case:** Attach sensors, control boards, or experimental expansions not covered by official modules. --- ## 8.7 Integrated Peripherals While not separate modules, the following are considered part of SMHUB’s extension capabilities: - **IR Transmitter & Receiver** - Control TVs, AC units, and IR-based devices. - Capture IR codes for learning mode. - **Audio Output (3.5 mm)** - System alerts and future media/streaming support. - **Buzzer** - Local audible notifications. - **LED Systems** - **12 WS2812B RGB LEDs (Ambilight)** – running by default, user configurable. - **4 Service LEDs** – network, power, radio status. # 10. Glossary **Ambilight** – Integrated RGB LED ring used for status indication and visual effects. **Apps** – Modular software packages (e.g., Zigbee2MQTT, Node-RED) that can be installed/uninstalled independently on SMHUB. **BLE (Bluetooth Low Energy)** – Energy-efficient version of Bluetooth for sensors, tags, and small IoT devices. **DDNS (Dynamic DNS)** – A service that maps a dynamic IP to a permanent domain name for remote access. **Matter** – A connectivity standard that allows devices from different ecosystems (Google, Apple, Amazon, SmartThings) to interoperate. **Matterbridge** – An application that bridges Zigbee/Thread devices to the Matter ecosystem. **MQTT (Message Queuing Telemetry Transport)** – A lightweight messaging protocol used for IoT communications. SMHUB includes a built-in **Mosquitto MQTT broker**. **Node-RED** – A flow-based programming tool for IoT automation, preinstalled on SMHUB. **OTBR (OpenThread Border Router)** – Service that connects Thread devices to IP networks. **PoE (Power over Ethernet)** – A method of delivering power and data over the same Ethernet cable. **UPS (Uninterruptible Power Supply)** – Add-on module with 18650 cells providing backup power during outages. **WireGuard** – A modern VPN protocol, preinstalled on SMHUB for secure remote access. **Zigbee2MQTT (Z2M)** – Application that connects Zigbee devices to MQTT brokers, enabling integration with multiple smart home platforms. **Z-Wave JS** – An open-source software stack for managing Z-Wave devices. # Run Thread networks The following guide explains how to enable **Thread networking** on your **SMLIGHT SMHUB** device. This process involves updating the operating system, flashing Thread firmware to the radio module, and installing the OpenThread Border Router (OTBR) app. > ⚠️ **Note:** This is an *early-access feature*. Future (expected v0.3.5+ versions) of SMHUB-OS will make it fully automatic. > For now, please follow the steps carefully in the order below. #### A new complete manual is created here: [https://smlight.tech/support/manuals/books/smhub/page/using-smhub-as-thread-border-router-for-matter-devices](https://smlight.tech/support/manuals/books/smhub/page/using-smhub-as-thread-border-router-for-matter-devices) --- ##The first batch of SMHUBs with 4G add-ons did not include the screw with a ring, which was meant to be placed between the add-on and the main PCB. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/screw-4g-addon.jpg) For some users, this caused a short circuit that prevented the hub from turning on. To fix this, follow the steps below:
1. Remove the 4G add-on 2. Stick insulating tape to the SIM card slot or place a layer of paper between the PCB and the 4G add-on [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-10/sticker-sim-card-addon.jpg) 3. Install the 4G add-on --- This section lists common issues that may occur during the installation or operation of SMHUB and their solutions. --- ## Feedbacks from users - **Issue**: ... nothing on the webUI is loading. the Settings page stays completely blank, doesn't matter which setting I choose. **Resolution**: And I have to admit, the problem was not the hub, it was me - Firefox & AdBlock will break the UI, at least in my case. --- ## Device bricked with SMHUB-OS v2.xSome users experienced a *"soft bricked"* device after updating over any method (Type-C / SD-Card or through the web UI). This issue appeared because of U-Boot changes introduced in version **0.2.0**, when the Robust Auto-Update Controller ("**RAUC**") was introduced. Users who experienced that were able to recover their "bricked" device by flashing back **0.1.2** via Type-C (because it did not contain the new RAUC changes \[by the way, it is here [smhub-os-v0.1.2](https://updates.smlight.tech/firmware/smhub/os/smhub_os_v0.1.2.zip)\]) and then updating directly to a **0.3.x** version via Type-C. Below is a simple explanation of what happened and how it was fixed. When the device turns on, the very first piece of software that runs is called **U-Boot**. You can think of it like the **“starter”** or **boot manager** of the device. Before anything else loads, U-Boot reads some **settings** (called “environment variables”) from the internal storage (the MMC). These settings tell it *how to start the system*. At some point, **RAUC** (stands for "Robust Auto-Update Controller" - **the Linux update system on SMHUB**) accidentally **damaged/corrupted those settings**. When U-Boot tried to read them, it got confused and didn't know how to continue booting properly, and the device failed to boot - which looked like it was “bricked.” (for regular start, or for Type-C/SD-Card updates). **What Was Changed**: To prevent this from ever happening again, we made two fixes: 1. **Automatically reset U-Boot's settings** whenever they are detected as corrupted. In simple terms: If U-Boot sees that its configuration is broken, instead of crashing or getting stuck, it will throw away the bad settings and restore working default settings - before any damage happens. 2. We also corrected how RAUC marks a software update as “successful.” It will now only do that **after an update actually happens**, instead of doing it on **every boot**. The old behavior is likely what caused the corruption. **Simple Analogy:** - Imagine a PC that reads its BIOS settings when it powers on. - If the BIOS settings get corrupted, the PC might not start. - The fix is to detect the bad BIOS settings and **automatically reset to “factory defaults”** so the computer can continue to boot normally. This is exactly what we are doing here, but for an embedded device. **The good news**: starting from SMHUB-OS **v0.3.2**, the fix is now built-in. You can simply update and recover your device via Type-C / SD-Card. (See details below [https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1.-1](https://smlight.tech/support/manuals/books/smhub/page/smhub-os-release-notes#bkmrk-smhub-services-v0.1.-1)) **Your device is now**: **- More robust - Self-recovering - Protected** from this type of failure in the future
--- ## Zigbee2MQTT **z2m: Error: \[BACKUP\] Current backup file is not for EmberZNet stack.** > This means that you have previously run Z2M for Radio1 (CC26XX). > Unfortunately Z2M does not support restoring backups between CC and EFR Zigbee chips, so to run Z2M for EFR radio you will have to delete the backup, which means you will have to re-pair all Zigbee devices.Following the steps below means you will have to re-pair your Zigbee devices.
Hint: You can press the \[TAB\] key to autocomplete paths/file names.
1. Open console[](https://smlight.tech/support/manuals/uploads/images/gallery/2025-11/nCBimage.png) 2. Type: `cd /opt/zigbee2mqtt/data` 3. (optional) Type: `ls` to show filelist 4. Type `rm coordinator_backup.json` 5. (optional) Type: `ls` to show updated filelist 6. Go to "Apps" -> "Zigbee2MQTT" and press "Run" button [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-11/nndimage.png) 7. Now you can go to the Z2M interface, it will launch soon Screenshot with a list of commands: [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-11/tWLimage.png) ## SMHUB Nano Mg24 model ID and radio flashing not-accessible Model ID is not identifiable and Radio updates do not work properly. [](https://smlight.tech/support/manuals/uploads/images/gallery/2026-01/Fipimage.png) To fix this, please 1. Go to Console and execute this command: `sudo bash /usr/lib/eeprom/eeprom-lib.sh --model nanomg24 --hw 0.97 --force` (password for sudo is smlight). IMPORTANT: option --hw 0.97 relates to hardware revision. You can see it on the PCB. 2. Reboot and check. It should work 3. Please also update OS, smhub-services, and smhubos to the latest versions afterwards. 4. Please check that LOG level in Zigbee2MQTT settings is set to INFO or WARNING; the level DEBUG overspams the device. # Connecting Zigbee2MQTT on SMHUB to Home Assistant This guide explains how to connect any **SMHUB Series** device to **Home Assistant** using **Zigbee2MQTT**. --- ## Requirements - Any **SMHUB** model (Essential, Premium, Nano, etc.) - **Home Assistant** running in your network - Minimum SMHUB firmware: - `smhub-os` ≥ **0.3.7** - `smhub-services` ≥ **0.2.4** - `smhub-web` ≥ **0.2.18** > 💡 Tip: You can check and update these versions in the SMHUB web interface > > - smhub-os: under **Settings → Updates and Restore**. > - smhub-services and smhub-web: under **Apps** → **Refresh** → **Upgrade smhub-services** and **smhub-web**. > - z2m - please update like this: go to **Console** tab and type `**curl -fsSL https://updates.smlight.tech/z2m.sh | sudo sh**`, password is `**smlight**`) - this is one-off action, Zigbee23MQTT will be moved to release on 13 December 2025) --- ## Connection options You can use Zigbee2MQTT on SMHUB in **two ways**: - **Option 1 (simple):** Zigbee2MQTT connects directly to Home Assistant’s MQTT broker - **Option 2 (advanced):** Zigbee2MQTT uses SMHUB’s local MQTT broker, which is bridged to MQTT on Home Assistant --- ## **Option 1 – Direct Z2M connection to Home Assistant** ### What to do - Open **SMHUB Web UI** - Go to **Apps → Zigbee2MQTT** Configure the following: - **MQTT Broker URL** `mqtt://HOME_ASSISTANT_IP:1883` - **MQTT User / MQTT Password** Use your Home Assistant MQTT credentials (often the same as Home Assistant login) - In **Home Assistant Settings** → **Enable** - Enable **Experimental Events** [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/EfNimage.png) Then: - Click **Save** - Stop and start **Zigbee2MQTT** *(or simply reboot SMHUB)* ### Result - Zigbee2MQTT on SMHUB connects directly to MQTT on Home Assistant - Zigbee devices appear automatically in Home Assistant - Multiple SMHUBs can connect to the same Home Assistant --- ## **Option 2 – Local MQTT on SMHUB with bridge to Home Assistant's MQTT** ### What to do - Open **SMHUB Web UI** - Go to **Apps → Zigbee2MQTT** - Enable **Home Assistant Settings** - Click **Save** ****[](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/4Ijimage.png)**** Then configure MQTT bridge: - Go to **Settings → MQTT** Set the following: - **Allow External** → Enabled. This lets the remote broker send MQTT messages to SMHUB's broker. - **Allow Anonymous** → Enabled *(simplest option) - but be careful. You can tweak this by adding credentials and making the respective settings on the remote broker.* - **Enable Bridge Mode** → True Remote broker settings: - **Remote Address** `HOME_ASSISTANT_IP:1883` - **MQTT User / MQTT Password** Home Assistant MQTT credentials - **Bridge Topic** `` [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/6zOimage.png) Then: - Click **Save** - Reboot SMHUB *(recommended)* ### Result - SMHUB keeps its own MQTT broker - MQTT data is bridged to Home Assistant - Zigbee devices appear in Home Assistant - Multiple SMHUBs can connect to one Home Assistant --- ## Which option should I choose? - Choose **Option 1** if you want the simplest and fastest setup - Choose **Option 2** only if you need local MQTT on SMHUB # Using SMHUB as Thread Border Router for Matter devices This guide explains how to run an **OpenThread Border Router (OTBR)** on **SMHUB** and connect it to **Home Assistant** for **Matter-over-Thread** devices. --- ## Requirements ### Hardware - Any **SMHUB** model (Essential, Premium, Nano, etc.) ### Firmware & apps (tested on) - **smhub-os** ≥ **0.3.11** - **smhub-services** ≥ **0.2.8** - **smhub-web** ≥ **0.2.23** - **OpenThread app** ≥ **0.3.1-2** --- ## Important note about radios - **SMHUB Essential/Premium**: - Use **Radio 2 (EFR32MG21 / EFR32MG24)** for Thread - **CC26XX** is **not supported yet** for Thread *(support will be added later)* - **SMHUB NanoMg24** - Use Radio 1 (EFR32MG24) for Thead --- ## Prepare SMHUB for Thread ### Flash Thread firmware to the radio Do the following in the **SMHUB Web UI**: - Go to **Settings → Radio** - Select **Radio mode: Thread** - Select a **Thread firmware version** - Click **Update** [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/iKYimage.png) ✅ The radio is now prepared for Thread networks. --- ## Install and start OpenThread Border Router on SMHUB ### What to do - Go to **Apps** - Click **Refresh** - Install or upgrade **Openthread Border Router** - Latest version: **0.3.0-2** - Enable **Start on boot** - **Reboot** the SMHUB device or press **Stop**, wa,it until it stops, and then **Run** buttons. [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/xpCimage.png) After reboot or re-launching the app: - Go to **Apps → Openthread** - Verify that Status = **Running** [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/Mhkimage.png) --- ## Connect OpenThread Border Router to Home Assistant ### Add the integration in Home Assistant In **Home Assistant**: - Go to **Settings → Devices & Integrations** - Click **Add Integration** - Search for **OpenThread Border Router** In the connection dialog, enter: `tcp://SMHUB_IP:8081` Example: `tcp://192.168.1.69:8081` [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/3uAimage.png) - Confirm and wait for successful connection [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/NzRimage.png) --- ### Verify Thread integration - Home Assistant should automatically install the **Thread** integration - If it does not: - Go to **Settings → Devices & Integrations** - Manually add **Thread** (no settings required) [](https://smlight.tech/support/manuals/uploads/images/gallery/2025-12/mDRimage.png) --- ### Home Assistant SettingsAll the information below relates to setting up a Matter-over-Thread controller (in this particular case, Home Assistant) and is outside the scope of SMHUB functionality (i.e., this is a third-party configuration topic). Therefore, the instructions below may change over time, and we do not track or maintain updates.
#### Setting Up the Matter add-on and Integration While Thread is a physical network, to control Matter-over-Thread devices, users need to installa Matter server on Home Assistant. 1. Go to the Home Assistant interface and navigate to `Settings` > `Devices & Services`. 2. Click on `Add integration` and search for `Matter`. 3. Keep checkbox `Use the official Matter Server Supervisor add-on` and click `Submit`. 4. Wait untill installation of Matter Integration and Matter Server add-on is completed. 5. Head over to the Left panel within Home Assistant and Click `Settings` and choose `Add-ons`. Go to the Matter Server add-on. Start the Matter Server add-on. Here we would suggest as well to click both `Start on boot` and `Watchdog`. #### Set-up and configuring the Integrations 1. Thread Integration – click `Configure` and make sure you have `OpenThread Border Router` under `Preferred network` line, and it contains an icon with key+phone. [](https://smlight.tech/support/manuals/uploads/images/gallery/2026-01/ftZimage.png) 2. If not, do the following: - click three dots on the right to `OpenThread Border Router`, choose `Add to preferrede network`. - Under the preferred network now, click again three dots on the right to `OpenThread Border Router`, and choose `Use router for Android + iOS credentials`. #### Reboot your Home Assistant server 1. Once all Home Assistant components are installed, we reccomend to reboot your Home Assistant server. ## Result - SMHUB is running an **OpenThread Border Router** - Home Assistant is connected to it - Your system is ready for **Matter-over-Thread** devices --- ## Pairing Matter-over-Thread devices ### Pre-set up your phoneThis paragraph is an extended version of the official documentation Home Assistant: https://www.home-assistant.io/integrations/thread/#to-make-home-assistant-your-first-thread-network
1. Install `Home Assistant` App on your Android phone from the Play Store. At the time of this video, we were unable to pair a Matter-over-Thread device via iPhone. 2. Install `Google Home` app from the Play Store. It is recommended by `Home Assistant` developers and we were not able to pair our Thread devices without installed Google Home app. 3. Open `Home Assistant` app and sync it with your Home Assistant server. Your phone and Home Assistant server should be in the same Wi-Fi network. 4. In the app, go to `Settings` – `Companion app` -> Click `Troubleshooting` and click `Sync Thread Credentials`. 5. Wait until the message `Home Assistant and this device use the same network`. If you see another message, namely `Added network from Home Assistant to this device` – You need to click on `Sync Thread Credentials` again until you get that message about the same network. 6. If you are not getting my message `Home Assistant and this device use the same network` - try to reset your Google Play Services (remove all data, usually by App settings -> Erase data -> Clear All Data, but names depend on the smartphone model). ### Adding the Matter Device 1. With the Matter integration set up, grab your Matter device and Android smartphone. Make sure Bluetooth is enabled on your phone. 2. Open the Home Assistant app and navigate to `Settings` > `Devices & Services` -> `Devices` Tab. 3. Click the `+ ADD DEVICE` button at the bottom right part of the screen to add a device, choose `Add Matter device`. 4. Follow the on-screen instructions in the app. You'll likely need to scan a QR code located on your Eve Energy socket or enter the pairing code manually. We did it with QR-code scanning. 5. Home Assistant app on your phone can as which app to open? Select `other` and then `Home assistant`. 6. The app will guide you through pairing the device with your Thread network. It should pass through this satuses: - Connecting to device... - Generating Matter credentials... - Connecting device to network... - Checking netwoek connectivity... - Connecting device to Home Assistant... - Device connected! 7. Note: - If a Matter-over-Thread end-device has been powered up for a long time, it may require a reset of device to put back into pairing mode. - In case you have Google home devices (Nest hub) and experiances issues with pairing, try to turn them off before starting OpenThread Border router add-on on your Home Assistant and your Home Assistant app. ### Verifying Connection and Control 1. Once the pairing is complete, head back to the Home Assistant interface. You should see your Eve Energy socket listed on your `Dashboard` or under the `Devices` section . [](https://smlight.tech/support/manuals/uploads/images/gallery/2026-01/uKOimage.png) 2. Click on the device to access its controls. You should be able to turn the socket on and off remotely within the Home Assistant interface. **Congratulations**! You've successfully connected your Matter-over-Thread device to Home Assistant using the OpenThread Border Router and Matter Integrations. Now you can enjoy the benefits of Matter's secure and interoperable smart home ecosystem, connected via SMHUB. ## OTBR Safe Reflash Procedure (Type-C) **Important:** Reflashing SMHUB via Type-C may wipe OTBR (Thread) data. If you don’t back it up, you will most likely need to **re-pair all Thread/Matter devices** again. ### Recommended Safe Steps 1. **Stop OTBR app** - Go to **Apps → OTBR** - Click **Stop** 2. **Backup OTBR database** - Open **Console** - Backup the OTBR data folder: - `/var/lib/thread/*` 3. **Re-flash OS** - Reflash SMHUB using **Type-C** as usual. 4. **Restore OTBR database** - After the OS is reflashed, restore the backup to: - `/var/lib/thread/*` ### ⚠️ What happens if you skip backup? If OTBR data is lost during reflash, you will likely need to: - reset OTBR configuration - **pair all Thread devices again** (Matter/Thread network rebuild) # Tailscale set-up ## Tailscale on SMHUB (Quick Setup Guide) **Applies to all SMHUB models:** Professional, Essential, Nano Mg24 **Tested with:** - SMHUB-OS **v0.3.10** - smhub-services **v0.2.7** - smhub-web **v0.2.23** - Tailscale app **v1.78.1-2** --- ### 1. Install Tailscale - Open **Apps** - Install the **Tailscale** app --- ### 2. Start Tailscale (Optional: Enable Autostart) - Go to **Apps → Tailscale** - Click **Run** - *(Optional)* Enable **Start on boot** if you want Tailscale to start automatically after reboot --- ### 3. Authenticate Device In **Console**, run: `sudo /opt/bin/tailscale up` The system will print a login URL (for example): `https://login.tailscale.com/a/xxxxxx` Open the link in your browser and authorize the device. --- ### 4. Connect Another Device - Install Tailscale on your PC - Log in with the **same account** - Authorize the device Once both devices are in the same tailnet, they can communicate securely. --- ### Notes - Authentication is **interactive** (browser required) - After authorization, the terminal is no longer needed - Tailscale reconnects automatically on reboot - No port forwarding or firewall changes required # Change IEEE address on SMHUB radio ## EFR32 IEEE Address change **Minimum firmware requirements for this change**: - smhub-os: 0.3.11 (prod) or 0.9.3 (dev) - smhub-services: 0.2.8-1 - smhub-web: 0.2.24-1 1. **Stop all applications using the EFR32 SoC**, including internal apps on SMHUB (e.g. Zigbee2MQTT) or any external applications if the EFR32 is used remotely (for example, Zigbee2MQTT running on another server). 2. Open **SMHUB-OS Console** (main Menu, tab Console). 3. Run the command below (replace the IEEE address `00124b1209d43d4f` if needed): **SMHUB Nano Mg24**: `universal-silabs-flasher --device /dev/ttyS1 write-ieee --ieee 00124b1209d43d4f` **SMHUB Essential/Premium**: `universal-silabs-flasher --device /dev/ttyS2 write-ieee --ieee 00124b1209d43d4f` 4. Wait until the EFR32 SoC is detected and the IEEE address is written. 5. Confirm the operation by checking the output. ```bash INFO Probing ApplicationType.EZSP at 115200 baud INFO Detected ApplicationType.EZSP, version: 8.0.2.0 INFO Current device IEEE: ec:f6:4c:ae:fe:21:ae:12 INFO Wrote new device IEEE: 00:12:4b:12:09:d4:3d:4f ``` [](https://smlight.tech/support/manuals/uploads/images/gallery/2026-02/image-2026-02-03-16-12-57.png) 6. Should work without a restart, but if not, please reboot with a power cycle (e.g., power off from the power and then power it on). ## CC26xx IEEE Address change **Minimum firmware requirements for this change**: - smhub-os: 0.3.11 (prod) or 0.9.3 (dev) - smhub-services: 0.2.9-1 - smhub-web: 0.2.24-1 1. **Stop all applications using the CC26xx chip**, including internal apps on SMHUB (e.g. Zigbee2MQTT) or any external applications if the CC26xx is used remotely. 2. Open **SMHUB-OS Console** (main Menu, tab Console). 3. Choose the required operation and run **one** of the commands below depending on the variant you have:| **SMHUB Essential, SMHUB NanoP7** (CC2652X SoC) | **SMHUB Premium** (CC2674X SoC) |
| **Set IEEE only** (works only if custom IEEE is blank, e.g. custom IEEE never set before): **Set IEEE and flash firmware** (can change IEEE even if already set): where `znp.hex` is a CC firmware file. | **Set IEEE only** (works only if custom IEEE is blank, e.g. custom IEEE never set before): **Set IEEE and flash firmware** (can change IEEE even if already set): where `znp.hex` is a CC firmware file. |