Skip to main content

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
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) by executing these commands:

 

sudo opkg update
sudo opkg upgrade

 

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 

 
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) by executing these commands:

 

sudo opkg update
sudo opkg upgrade

 

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 
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.
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 


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
1 26 Sep 2025 OS 0.2.0 Initial release

What’s Already Installed (Ready to Use)

  • Zigbee2MQTT (for CC26XX or EFR32XX radios)

  • Mosquitto MQTT broker

  • Matterbridge

  • Node-RED

Hardware – Working Now

  • CC26XX radio

  • EFR32MGXX radio

  • 100 Mb Ethernet port

  • 12× WS2812B RGB LEDs (Ambilight effects)

  • eMMC storage

  • PoE module support (optional)

  • Z-Wave module support (optional)

Hardware – Present but Still in Development

  • Wi-Fi 6 (2.4 / 5 GHz) and Bluetooth (currently CLI only, UI support coming)

  • IR receiver and transmitter

  • USB ports: 2× USB-C (1 for power/upstream, 1 downstream), 1× USB-A

  • SD card slot

  • 3.5 mm audio jack

  • 4× Service LEDs

  • 3× Hardware buttons

  • Expansion connectors: UART, I²C, SPI, DIY pinouts

Updates & Roadmap

  • More hardware functions will be enabled gradually via SMHUB-OS updates.

  • New features will roll out continuously (but availability is not guaranteed).

  • Early adopters receive updates and improvements first.

Updating SMHUB Firmware

This section is moved to the dedicated page here https://smlight.tech/support/manuals/books/smhub/page/smhub-os-update-restore-methods 

Updating Zigbee Firmware

EFR32

  1. Connect to device via SSH terminal https://smlight.tech/support/manuals/books/smhub/page/3-getting-started#bkmrk-ssh-access
  2. Type following commands:
  3. sudo pip install python_magic~=0.4.27 && sudo pip install pysmlight~=0.1.3 && sudo pip install universal-silabs-flasher
cd /home/
sudo wget -O ncp-uart-hw-v7.4.1.0-slzb-07-115200.gbl  http://updates.smlight.tech/firmware/slzb-07/ncp-uart-hw-v7.4.1.0-slzb-07-115200.gbl
sudo wget -O efr_btl_enabler.sh  http://updates.smlight.tech/firmware/smhub/utils/efr_btl_enabler.sh
sudo chmod 777 efr_btl_enabler.sh
sudo ./efr_btl_enabler.sh
universal-silabs-flasher --device /dev/ttyS2 --probe-method bootloader flash --firmware ncp-uart-hw-v7.4.1.0-slzb-07-115200.gbl

    EFR32 firmware will be updated to v7.4.1.0

Accessing the Web Interface

image.png

On first boot, no apps are running. You must enable them.

Running Apps (Example: Zigbee2MQTT)

  1. Open the Apps tab.

  2. In Z2M app settings:

    • Choose your Zigbee chip:

      • ttyS1 → CC26XX SoC

      • ttyS2 → EFR32XX SoC

    • Configure MQTT broker if needed.

  3. Toggle:

    • Enabled → allows the app to run.

    • Start on boot → app starts automatically after reboot.

      image.png

  4. Reboot SMHUB (press Reset or power cycle).

  5. Once booted, open the Zigbee2MQTT tab – you’ll see the configuration page.

image.png

You can repeat the same steps for:

  • Matterbridge

  • Node-RED

    image.png



    image.png

Note 1

  • The Settings tab is under development – more options will appear in future updates.

  • Once per day, the device automatically runs opkg update to check for available updates.

  • If you do not see package updates in the web interface, you can force an update manually:

    1. Connect to the device using an SSH terminal (e.g., PuTTY).

    2. Log in with credentials:

      • User: smlight

      • Password: smlight

    3. Run the command:


      sudo opkg update using password `smlight`

    4. Return to the web interface and refresh the Apps page.

    5. Please note that this update feature is applicable only for packages (apps) and is not applicable for SMHUB-OS. 
      SMHUB-OS OTA is planned to be released in the coming weeks.

Note 2


If you cannot flash the device and the flash.bat window disappears, follow the steps below to get more information about why the process stops. This can help in troubleshooting:

  1. Check drivers
    Make sure the required drivers are installed (see the manual above).

  2. Open Command Prompt as Administrator

    • Click the Windows button, type CMD.

    • Right-click Command Prompt and select Run as Administrator.

  3. Navigate to the flash.bat folder
    Type the following command:


    cd full_path_to_the_file_flash_bat

    Replace full_path_to_the_file_flash_bat with the actual folder path where flash.bat is located.
    Example:


    cd C:\Users\zigbee\Downloads\smhub_v0.1.3

  4. Run the flashing script
    Type:


    flash.bat

    and press Enter.

  5. Check the error message
    Review the output in the Command Prompt window to identify the error.

Back to top