Changelog SLZB-OS

📦 v3.4.5.dev0 - Release Notes

New features

Port forwarding for the Wi-Fi bridge. SLZB can share its Ethernet or 4G/LTE connection over its own Wi-Fi (NAPT mode). Now a device on that Wi-Fi can also be reached from outside: from your network, or from a remote Home Assistant through the VPN (WireGuard / Tailscale). It is made for low-traffic devices such as sensors and relays. Example: a country house has no internet line and no Wi-Fi router. SLZB with the 4G/LTE add-on connects to the internet and runs its own Wi-Fi network. A Wi-Fi relay and a Wi-Fi sensor connect to that network. Your Home Assistant at home then reaches them over Tailscale, together with all your Zigbee devices. Up to 10 rules, on the Mode page.
A rule maps an external port of SLZB (1–49151) to a port of a Wi-Fi client, on the Ethernet / LTE side or on the VPN side. For example, VPN port 8081 can lead to port 80 of the relay. Ports SLZB uses itself are not forwarded. Pick the client by its MAC address so the rule survives DHCP address changes.
Thread command console (for advanced users). Run OpenThread CLI commands from the OTBR page, or from scripts with the new Berry module OT_CLI. Example: state shows the border router's role, and netdata show shows the Thread network data. Commands that would break the border router (reset, factoryreset, ...) are blocked.
Scripts know when the MQTT broker goes offline. New MQTT.getState() and MQTT.on_state_change(). Example: a script subscribes to its topics again as soon as the broker is back.
Berry NETWORK module: HTTP PUT method, for web services that update data with PUT.

Zigbee Hub mode: big update

Zigbee Hub mode turns SLZB into a standalone Zigbee hub: it pairs your Zigbee devices and runs local automations by itself, with no extra software. It is made for small, simple setups.

More than 4 thousand devices supported, thanks to device support generated by AI. AI probably learns from knowledge that people share, including the mit-licensed zigbee-herdsman-converters, so this big step really belongs to everyone across the internet who has studied, documented and shared how Zigbee devices work. Thank you! Read more in the manual
Device support is downloaded from the internet. The descriptions ("converters") of so many devices would not all fit into the device's limited memory, so the hub downloads only the ones you need from the SMLIGHT server. Each one is downloaded only once, when the device is paired, and then kept on SLZB. Only the device's model and manufacturer name are sent. U-series and Ultima download it by themselves. On non-U models, your browser does it, so keep the web interface open for a minute after pairing.
More devices per hub: up to 16 on non-U models and up to 80 on U-series and Ultima. When the hub is full, a new device is refused and the web interface tells you why.
Network map. Press Scan to see how your devices connect to each other and how strong each link is. Example: a sensor that often drops out shows a weak link. Place a mains-powered plug or bulb (they relay the signal) between it and the hub.
Groups. One command switches all members at once, and Home Assistant shows the group as one light or switch. Example: put 4 ceiling bulbs into a "Living room" group, and they turn on together instead of one after another.
Better security and easier network changes (Zigbee 3.0):
- Install codes: devices that only join with the code from their QR sticker can now be paired.
- Your own network key for a new network. Note: Generate starts a new network, so all devices must be paired again. To keep your devices, use Change the key keeping the devices.
- Channel change without pairing again. Example: if your Wi-Fi interferes with Zigbee, move Zigbee to another channel. The devices follow by themselves (battery devices when they wake up).
⚠️ Default network key. Zigbee Hub networks use a default key that is the same on every SLZB hub. It works like the default password on a new Wi-Fi router. Change "Network key" in the Zigbee Hub settings, press "Change the key keeping the devices": it takes about 30 seconds and you don't need to pair the devices again.
Offline devices (optional, off by default, in the Zigbee Hub settings): a device that stays silent is shown as offline in Home Assistant and on the dashboard. By default, a mains-powered device is marked offline after 10 minutes, a battery device after 25 hours. Example: an unplugged smart plug shows "unavailable" instead of its last state.
Dashboard: control thermostats, blinds, lights, fans, locks and sirens directly. Buttons, separate Settings and Diagnostics groups, and offline devices are marked.
Sensor charts. Click a sensor on the dashboard to see its values for the last 1, 6 or 24 hours. Example: how the bedroom temperature changed overnight. The history starts over after a restart.
More device types understood out of the box: thermostats, energy meters, CO₂ and PM2.5 sensors, door locks, sirens, alarm keypads and more. The dim and color buttons of remotes now work as triggers for Home Assistant automations.
New ZCL clusters (Thermostat, Metering, CO2, PM2.5, Door Lock, IAS WD, IAS ACE, Analog / Binary / Multistate Input and more), all ZCL data types, Level Control and Color Control remote actions.
Battery devices: settings for a sleeping device are sent when it wakes up, instead of failing. Tip: press the device's button to wake it up right away.
Requests (binding, reporting) are queued per device; Poll Control and Time cluster support.
MQTT: optional timestamp in data reports. A new button removes all Home Assistant entries of a device, which helps clean up old or duplicate entities.
EFR32 radios: more stable connection to the radio (reworked EZSP transport). While the radio runs the hub, its network port for Zigbee2MQTT / ZHA (socket server) is off.
Faster MQTT publishing and dashboard updates, and many fixes.

Why Zigbee Hub mode? Its main purpose is local automation without any additional software: SLZB pairs your devices and runs your automations (scripts) by itself. Example: a motion sensor turns on the hallway light, and it keeps working even while your server or the internet is down. It can also bring your Zigbee devices into Home Assistant over MQTT, without separate Zigbee software. The hub runs on the SLZB's own small processor, so it stays lightweight by design and we pick its features carefully. Your suggestions are always welcome. For large networks or advanced features, Zigbee2MQTT and ZHA remain the right choice, and SLZB keeps working as their coordinator.

Improvements

Philips Hue scripts respond faster: a command to the Hue bridge takes about 20 ms instead of 600 ms, because the connection stays open. Example: a button that switches a Hue lamp now feels instant.
Smaller firmware: the AI assistant and the advanced script editor are now loaded from the SMLIGHT server when you open them, and the web files are compressed better.
The device stays fast while the web interface is open in a sleeping browser tab or on a slow connection.
The Apps page is translated and has links to the apps repository and documentation.
The RF add-on is now called "433MHz Transceiver".
Ultima: new Ambilight driver, with the same effects in a smaller firmware.

Fixes

Scripts running at the same time no longer mix up their data. Before, a script could get a variable or function of another script and fail with strange errors.
Scripts now receive messages on their custom MQTT topics (MQTT.subscribeCustom()).
Script timers keep running while a script waits in ZHB.await().
EFR32 radios: fixed a rare radio freeze caused by stray flow-control bytes from the connected Zigbee software.
USB-C: a USB device powered from the SLZB's USB-C port could lose power at random. Fixed (power-source detection is now debounced).
Tailscale: the admin console no longer refuses to edit the device, for example to change its tailnet IP. The device now reports a client version.

Thread + OTBR running on device

Fixed the custom OMR prefix and the border router information other systems read over mDNS (MeshCoP). For example, Samsung SmartThings could reject the border router.
Fixed the border router hanging at startup on some networks (when the network reported its IPv6 link-local address as a duplicate).
If Thread freezes, the device now restarts by itself within about a minute, instead of staying unreachable.
mDNS is now always on in this mode, because Home Assistant and other Thread apps find the border router through it.

📦 v3.4.3.dev1 - Release Notes

New features

USB Passthrough now supports up to two USB devices simultaneously. More information
New Berry module USBH: scripts can take over a USB Passthrough port and talk to the USB device directly.
New methods for the ZB module: chipModel(), isEFR(), isCC(), isZW(), getFirmwareRev(), getFirmwareType(). initUart() got the hwFlow option.

Improvements

The USB Passthrough page has been redesigned and updated: connected devices, USB host channel usage, device status and a button to put a dongle into bootloader mode (BSL).
The OS will now apply adaptive timing and UART FIFO configurations based on the selected baud rate.
Berry scripts can no longer hang the OS: a callback (TIMER, MQTT, ZB, ...) running longer than 1 second is stopped with an error, and a busy loop in a script gives CPU time to the rest of the system.
Logging level selectors (OTBR, Tailscale) now warn that levels above Warning are meant for debugging only.

Fixes

HUE module fixes (again). The HUE module will now attempt HTTPS if the HTTP connection is rejected.
Fixed corrupted data for FTDI USB devices.
Fixed the VPN page not saving settings, and validation errors are now shown on it.
Tailscale: fixed peers relaying through the wrong DERP region (the device showed online but was unreachable without a direct connection).
Tailscale: fixed STUN probes being rejected by Headscale's STUN server, more accurate nearest DERP region detection.
Fixed possible crashes when other tasks write to the device log.
Berry NETWORK module: fixed a possible crash when streaming large HTTP responses.
Radio firmware auto-update no longer blocks other updates while it only checks for a new version.

Thread+OTBR running on device

Custom OMR config support: automatic, custom prefix with preference or disabled. The page also shows the local, favored OMR and on-link prefixes.
NAT64 can now be disabled.
Added button to stop/start OTBR. Stopping leaves the Thread network gracefully: routes are withdrawn and the border router is removed from the Network Data.
A device reboot keeps the Thread router ID and role, so the mesh no longer rebuilds around the border router after a quick reboot.
More NAT64 fixes. Now we are absolutely certain that this works.
Fixed a wrong Border Agent port advertised over mDNS after Thread was restarted.
High OTBR logging levels no longer cause crashes.
Task buffers and priorities have been optimized to increase performance and improve stability. RCP errors have now been minimized.

Berry apps (preview)

App permissions: apps run in a sandbox, the installer shows the permissions an app requests before it is installed.
Apps can import their own Berry modules from the app folder.
Developer mode: an app with "dev": true gets a file manager and the script editor for its files.
App README: rendered in the app details, the installer checks the minimum OS version and supported models.
App backend errors are written to the app's own log.

Socket Server refactoring

Fixed TCP_NODELAY not being applied: one lost TCP packet could delay all following radio frames by up to several seconds.
The logic for detecting connection losses has been modified to minimize false positives.
Each server received an additional stash for packets from the radio module to compensate for potential delays in TCP/IP networks.
The stash will be sent to the client whenever possible. If the stash does not move for 5 seconds, the connection will be considered lost.
A radio frame is now sent as a single TCP packet instead of several small ones.
Lower latency of data sent to radio modules without flow control.
Delays in the data path are now reported in the device log.

📦 v3.4.1.dev1 - Release Notes

New features

Tailscale VPN for U-series devices (yes, you are awake).
New Berry modules: LTE, WG, NETWORK, TCP, UDP
Preview: Berry apps.

Improvements

Added more socket server debug info to device log.
Added support for parsing V3 sililabs-firmware-builder manifests for EFR32 firmware.
Zigbee OTA API has been switched to the POST method.
WireGuard refactoring and fixes for better LTE modem compatibility.
The VPN page now displays the status.
MQTT and BLE traffic can now be routed to WireGuard peers.
LTE driver rework: improved stability, better connection recovery.
LTE now supports two connection modes:
- primary (all internet traffic is routed via LTE)
- backup (default. internet traffic switches to LTE only if there are no internet connection via Ethernet or Wi-Fi).
LTE received support for reading/sending SMS.
RAM optimizations for U-series devices.
Allowed ZHB and IoT AP at same time for U-series devices.
Increased the keepalive setting for the socket server to 60 seconds.

Fixes

HUE module fixes.
Ultima3: fixed custom RTTTL play button.
Fixed WDT triggering during local CORE firmware update.

Thread+OTBR running on device

Fixed a race condition where the BR could listen on the wrong IP, causing Thread devices to become unreachable.
NAT64 fixes.
Fixed "Failed to get LL address".
Now generates true random Thread network upon the first launch.
Logging level setting.

Zigbee Hub mode

Backup support for EFR32 radio modules.
Added a watchdog to monitor the connection to the radio module and automatic Zigbee network restart upon loss of connection.
Automatic Zigbee network restart if an RST frame is received from the radio module.
Zigbee Hub will not remove records with the status "unsupported attribute" from memory.

📦 v3.3.8.dev7 - Release Notes

New features

New Berry modules: ISC, UI, BEAPP

Improvements

Minor socket server improvements.
Added more missing localizations.
Improved the layout of the "Zigbee Automatic Update" block on mobile devices.
Added RAM watchdog for U devices. The device will reboot if the amount of free RAM drops to a critical level.

Fixes

Thread+OTBR running on device: fixed IPv6/OMR forwarding breaks after Ethernet link loss or device reboot.
Ultima: fixed a crash on the RF add-on page if RF addon is not installed.
Berry: fixed large scripts saving.
Berry: fixed TIMER can fire immediately.

Zigbee Hub mode

Fixed incorrect parsing of Zigbee packets containing a manufacturer code.
Logging refactor.

📦 v3.3.8.dev5 - Release Notes

New features

New advanced Berry Script Editor with type/class parser, advanced autocomplete and built-in documentation.
When you visit the "Script Engine & Editor" page, you will be prompted to try the advanced editor.

Fixes

Fixed OS deadlock when syslog and "Thread+OTBR running on device" is enabled together.
Fixed OTA update issues on non-U devices that occurred in v3.3.8.dev1 and dev3.
If you have the error "req code -1" or "FW size mismatch, written: 0kb of total: 2821kb", please read this update guide

📦 v3.3.8.dev3 - Release Notes

New features

New socket server IP whitelist: up to 3 IP addresses, with subnet support via CIDR
Thread+OTBR running on device REST API now supports IP whitelist: up to 2 IPs. Check it out on the security page!

Improvements

Added some missing localizations
Added 125000 baud rate for \"USB Passthrough\"

Fixes

Thread+OTBR running on device: fixed meshcop state bitmap which caused problems with adding Thread devices in some cases
Fixed OS crash on SLZB-Ultima3 when receiving IR code (this time we fixed it for sure)

📦 v3.3.8.dev2 - Release Notes

New features

Experimental TREL support for "Thread+OTBR running on device" mode.
Dev comment: In a previous releases we already tried to add TREL support but it caused TCP/IP deadlocks. Our tests for this release did not find any deadlocks, we also tested TREL between OTBRs and it works fine.
If you have deadlocks after the update please open a support ticket!

Improvements

Updated helper text on BLE page
Added warning about using a proxy to the OTBR page

Fixes

Fixed OS crash on SLZB-Ultima3 when receiving IR code

📦 v3.3.8.dev1 - Release Notes

New features

New login page: the web interface now uses a modern sign-in page with a session cookie instead of the browser's native password prompt. API clients (Home Assistant integration, curl, etc.) keep working with HTTP Digest auth as before
Zigbee Hub can now run on EFR32 radios (SLZB-06M/g24/Mg26 and the EFR32 radio of MR devices). On multi-radio devices you can choose which radio runs the hub. No Zigbee network backups for EFR32 at this stage
(Preview) Zigbee Hub: new ZCN Builder page — a visual constructor that generates the Berry converter code, with built-in examples, and can run/update the converter script directly on the device
RF Transceiver add-on support for SLZB Ultima (CC1101, 315/433/868/915 MHz): sniff, replay and save OOK/ASK commands from remotes, wireless sockets, doorbells, etc. New RF page, REST API, MQTT topic status/rf and Berry RF module
BLE: configurable scan interval and scan window
New Berry integration: Prowl (iOS push notifications)
Berry ZHB module: ZHB.await(), ZHB.on_response() and ZHB.lastStatus() — wait for the device's reply to a Zigbee request (sync or async); ZHB.mqttAction() also supports await

Improvements

Socket server (LAN/USB bridge to the radio) refactored: select()-based loop, larger UART buffers, async UART writes, stalled TCP clients are dropped instead of blocking the radio path
Web interface assets are now minified and cached by the browser — faster page loads, no stale files after an update
Wi-Fi TX power is now fixed at 20 dBm
MQTT broker address field extended to 64 characters
OTBR: the UI respects a custom REST API port on the OTBR and Mode pages
OTBR: REST API returns 404 for unknown URLs (fixes OTBR flavor auto-detection for matter.js)
OTBR: (Experimental change) increased the limit of Thread devices that can be connected from 10 to 32.
Dev comment: this is a theoretical limit, currently only 16 devices have been successfully tested but we do not have more devices to test yet
LTE add-on: better modem init and restart, forced modem reset on start
IR receiver: repeated IR frames are ignored — only the first frame of a button press is reported via MQTT/SSE/Berry
U2L: the mode button no longer switches USB mode
Updated Berry to the latest version; Berry scripts embedded in the firmware are now pre-compiled (solidified)
Berry: errors raised inside custom scripts are handled and logged instead of crashing the VM

Fixes

Fixed NAPT on Wi-Fi bridge (WBR) mode
Fixed MQTT port being overridden on MQTT page load
OTBR: fixed infinite loop on startup if the RCP radio does not respond
OTBR: fixed SecurityPolicy flags that could not be set to false
LTE add-on: fixed Wi-Fi AP not starting with the modem
Berry: fixed heap corruption on VM delete

Zigbee Hub

Status feedback for device controls: binding, reporting and other ZCL requests now show whether the device accepted or refused the command
Reporting configuration is built from the actual device clusters, with an optional multiplier override
Option to publish /zhub/data/ MQTT messages with the retain flag
Confirmation dialog before removing a device
Improved IAS Zone enrollment (correct enroll attribute, delay after writing IEEE, fixed enroll stage)
Interview timeouts adjusted to match fast polling; fixed attribute read spam during interview
Converter for Sonoff SNZB-03P motion sensor
Converter for Tuya ZY-M100-S presence sensor (TS0601 _TZE284_iadro9bf / _TZE204_qasjif9e / _TZE200_qasjif9e / _TZE204_ztqnh5cg / _TZE204_iadro9bf)
Converter for Tuya NAS-AB02B2 siren (TS0601 _TZE200_t1blo2bj / _TZE204_t1blo2bj / _TZE204_q76rtoa9)
Converter for Tuya TS0601 presence sensor (_TZE204_ex3rcdha / _TZE204_lbbg34rj)
Better matcher for Lumi/Aqara temperature & humidity sensors
Fixed wrong firmware offered for the P10 radio
Updated slider UI

💙💛 Special congratulations to our Ukrainian team on Independence Day and to everyone who supports Ukraine during this difficult time 💙💛

📦 v3.3.5.dev1 - Release Notes

Breaking changes in this update!

Please read breaking changes note before this update: documentation

Improvements

The dashboard now shows a full list of IPv6 addresses when the device is in OTBR mode
Optimized main loop
Improved SBL synchronization for EFR32 radios
Updated Berry ZB module
Updated Berry HTTP module
Updated Berry TG module
Guarded all network-dependent Berry modules from calling before network interface is created. Now this will throw an error instead of a crash.
MQTT client now supports MQTTS
Logging system and syslog optimizations
Blocking multicast traffic at the PHY layer if mDNS is disabled
OTBR: Now you can change individual network parameters
OTBR: Added the ability to reset the node, which may be useful if you accidentally specified a broken TLVs and the TLVs are no longer updated
OTBR: You can change the OTBR REST API port

Fixes

Fixed Berry TG module not sending long messages
Fixed Berry TG module crashing if many messages arrived while it was offline
Fixed LTE addon not working on Ultima3
Fixed broken transparent bridge for non-U devices (again)
Fixed Berry HTTP.isOpened()
Fixed memory leak in Berry HTTP module
Fixed broken packet mode for EFR32Mg24 and Mg26
Fixed race condition on EZSP start for IEEE read/write via web interface

Zigbee Hub

📦 v3.3.3.dev7 - Release Notes

Improvements

Improved firmware rollback mechanics after OTA update. The device will roll back to the previous firmware if a crash occurs within 30 seconds after the update.
Increased tcp keep alive timeout to prevent socket drops on unstable networks.
New BLE page and BLE proxy for U line and Ultima devices documentation
New BLE Berry module for U line devices documentation
All Berry scripts on U line and Ultima devices now use PSRAM by default and no longer crash when trying to access the file system.
RAM optimization for U line and Ultima devices.
Improved deinitialization for "Thread+OTBR running on device" mode.

Fixes

Fixed an issue where a user could accidentally copy the text of a crash message even if the crash did not occur.

Zigbee Hub

Fixed JSON validation for system_control topic

📦 v3.3.3.dev4 - Release Notes

Improvements

Added the ability to select a firmware update channel on the \"Firmware update\" page. After selecting, you will only see firmware of the selected channel in the coordinator interface. As of now, this only applies to the coordinator interface (in Home Assistant, you can still see notifications about firmware of another channel)
For coordinators with EFR32 radio modules, an option to clear NVM has been added to the firmware update dialog. This option is enabled by default to prevent problems when migrating between firmwares. You can still uncheck this in the dialog to not clear NVM.
Automatic updates will now only use stable Zigbee firmware

Fixes

Fixed an issue where empty DNS could be assigned in some cases
Fixed automatic OTA baudrate update issues
Fixed IEEE read/write functionality for firmware 20260416 of the EFR32 radio module

Zigbee Hub

Fixed discovery payload for illuminance cluster
Minor improvements to electric valve support
Fixed handling of custom MQTT commands for cluster ON/OFF

📦 v3.3.3.dev1 - Release Notes

Improvements

Experimental support for SLZB-OS configuration backup/restore
Optimized the processing speed of SSE messages
Added a button to copy the device log
Added autocomplete for TIMER module
SUN module redesigned documentation
OTBR on device moves from experimental to beta
U-series coordinators now store 12x larger device log in PSRAM (50KB vs 4KB)
(SLZB-Ultima) New "Audio" page and MP3 audio player support!
(SLZB-Ultima) Added new Berry audio player module documentation
(SLZB-Ultima) Added optional argument for number of repetitions for sending IR command for berry IR module documentation
(SLZB-Ultima) Improved stability of Z-Wave addon
(SLZB-Ultima) Improved 4G modem processing
(SLZB-Ultima) The IR receiver will be disabled while transmitter active
Added 10s timeout for OTBR startup. If after that the radio module still does not respond - you will see an error on the OTBR page

Fixes

Fixed an OS crash that caused OTBR in some cases
Fixed ZigBee network scanning not working if OTBR is running on radio module 2
Fixed DNS issues for NAPT bridge mode
Fixed SPAM in device log when using SMLIGHT SLZB integration

Zigbee Hub

Added experimental ZigBee Hub backup functionality
Added missing subscriptions to new zHub control topics. Now new topics will work (attribute read request, system_control)
When creating a new random network, only channels 11, 15, 25 will be used
Automatic firmware updates of the radio module will be disabled if the Zigbee Hub is active
Fixed an issue that caused a ZigBee network start error when the network was actually started
Fixed issues with network key comparing
Fixed broken Zigbee buttons triggers

📦 v3.3.1 - Release Notes

Improvements

OS will now reboot the EFR32 radios at startup

Fixes

Fixed broken static IP config for Trasparent WiFi bridge mode

Zigbee Hub

Added attribute read request for MQTT API: documentation
Added new system_control MQTT API: documentation
Added test converter for "Moes ZS-EUB_2gang"

📦 SLZB-OS 3.2.9 - Release Notes

Fixes

Fixed Berry Telegram integration
Fixed boot-loop in WiFi mode when activating OTBR on the device
Fixed crash when ping is enabled for Wireguard

Zigbee Hub

Added a new tab "Exposes"
Fixed crash when saving settings if Zigbee Hub is not enabled
Fixed LQI unit warning
Fixed Tuya DP sensor update
Fixed: ZigBee network always reset when saving settings, even if channel/panId or key was not changed

📦 SLZB-OS 3.2.8 - Release Notes

Highlights

Integrated 30+ services for local automatiations, including WLED, Telegram, Weather, Slack, Wake-on-Lan, MS Teams, E-mail, OpenWRT, and more.
AI is here: Added AI Assistant to help users write automation scripts more easily. in Beta test. Requires AI credentials (so far - Anthropic only). Watch the quick 4-minute YouTube overview .
SLZB-xU devices can now try a new experimental mode with native OTBR app running directly on the SLZB-xU device. Mode is still experimental, and there is reported bug in some installations - the coordinator may become unavailable after some time. Pattern is unknown, that is why still experimental status.

Improvements

Moved Ethernet processing to Core 0 for better load balancing.
Optimized the scripts virtual machine for better performance.
For U devices, the BT Proxy option now links directly to the activation manual.
IPv6 has been temporarily disabled for rework.
All localizations except EN have been moved to a cloud server to reduce firmware size. On first opening the coordinator interface, the localization will load in the browser if internet access is available. Without internet access, EN will be used.

Fixes

Fixed crash on "Playground: AI Assistant" page.
Fixed visibility of "Playground: AI Assistant" and "Scripts Integrations" pages.
Fixed metadata overflow crashes for older .gbl update files.
MRW10/10U now use the Z-Wave packet parser, improving socket stability.
Fixed a crash in the hard reset handler.

Zigbee Hub

Replaced the LQI unit with "none".
Fixed logging of values for Tuya DP.
MQTT now sends correct values even for unsupported devices, allowing them to be used in automations.
Added support for new Zigbee devices.

📦 SLZB-OS 3.2.7 - Release Notes

Highlights

Integrated 30+ services for local automatiations, including WLED, Telegram, Weather, Slack, Wake-on-Lan, MS Teams, E-mail, OpenWRT, and more.
AI is here: Added AI Assistant to help users write automation scripts more easily. in Beta test. Requires AI credentials (so far - Anthropic only). Watch the quick 4-minute YouTube overview .
SLZB-xU devices can now try a new experimental mode with native OTBR app running directly on the SLZB-xU device. Mode is still experimental, and there is reported bug in some installations - the coordinator may become unavailable after some time. Pattern is unknown, that is why still experimental status.

Improvements

Moved Ethernet processing to Core 0 for better load balancing.
Optimized the scripts virtual machine for better performance.
For U devices, the BT Proxy option now links directly to the activation manual.
IPv6 has been temporarily disabled for rework.
All localizations except EN have been moved to a cloud server to reduce firmware size. On first opening the coordinator interface, the localization will load in the browser if internet access is available. Without internet access, EN will be used.

Fixes

Fixed metadata overflow crashes for older .gbl update files.
MRW10/10U now use the Z-Wave packet parser, improving socket stability.
Fixed a crash in the hard reset handler.

Zigbee Hub

Replaced the LQI unit with "none".
Fixed logging of values for Tuya DP.
MQTT now sends correct values even for unsupported devices, allowing them to be used in automations.
Added support for new Zigbee devices.

📦 SLZB-OS 3.2.6.dev3 - Release Notes (dev)

🛠️ Improvements

SLZB-MRW10 and MRW10U: rewritten socket handling for ZWave to improve stability
Add Window Covering cluster (0x0102) support to Zigbee Hub mode
Add Occupancy Sensing cluster (0x0406) support to Zigbee Hub mode
Added speed 2400 for USB page
Updated localizations
Updated datapoint /ha_sensors
Added presets for the SLZB-Ultima3 buzzer

🐛 Fixes

✅ Fixed logging and sending Tuya DP data for Zigbee Hub mode
✅ Fixed running multiple berry scripts
✅ Fixed Wireguard (which was broken in a previous build)

📦 SLZB-OS 3.2.6.dev2 - Release Notes (dev)

✨ Thread + OTBR running on the device - update

Many users have asked for the ability to set TLVs for this mode via SLZB-OS and now you can do this on /otbr page!

🛠️ Improvements

New Ambilight effects for SLZB-Ultima3
New Berry modules and integrations (documentation)

🐛 Fixes

✅ Fixed Zigbee automatic update ignores speed change in new firmware
✅ Fixed a crash in Berry error handler

📦 SLZB-OS 3.2.6.dev0 - Release Notes (dev)

✨ New: Thread + OTBR running on the device (SLZB-xU only) - evaluation/beta mode.

You can now run OpenThread Border Router (OTBR) directly on the SLZB device, instead of running the OTBR add-on/app in Home Assistant.

✅ Why this could be a no-brainer:

Home Assistant connects to OTBR via network REST API, so you no longer rely on the Serial-over-IP link used in “Thread to external OTBR” mode.
This aims to improve reliability of Thread connectivity between Home Assistant and SLZB devices fpr those, who experiences issues with connectivity.

🏠 Home Assistant setup:

OTBR REST API is available at http://device-ip:8080

⚠️ Important notes / limitations:

🧪 Initial (beta) integration — may have limitations or unexpected behavior.
🌐 IPv6 is required and will be force-enabled when this mode is activated.
🧠 "Thread + OTBR running on the device" mode can't work with "router (standard)" mode for Ethernet ↔ WiFi bridge and Zigbee Hub mode. To activate back these features, device mode should be othar than "Thread + OTBR running on the device".
"Transparent" mode for WiFi ↔ Ethernet bridge is incompatible with "Thread + OTBR running on the device". If you need "Transparent" mode for WiFi ↔ Ethernet bridge - please use any of the previous versions of the SLZB-OS.
🔒 Availability: only on SLZB-xU series.
🔁 Alternative: you can still use Thread + remote OTBR mode (USB/Ethernet) if you prefer OTBR running elsewhere.

🛠️ Improvements

⏱️ Added uptime info for Socket2 and Socket3 in /ha_sensors

🐛 Fixes

✅ Fixed a crash in Zigbee Hub mode when a received value is larger than expected

🚀 SLZB-OS v3.2.5.dev1 - Release Notes

✨ New Features & Enhancements

✅ Zigbee Hub mode: support for Tuya datapoint data writes.
!BREACKING CHANGE! Changed the format of the write topic Zigbee Hub for Tuya Zigbee Hub MQTT API
✅ Zigbee Hub mode: Added support for MOES Star Feather (2-key models)
✅ Berry: New BUZZER module for Ultima3 documentation
✅ Berry: New BUTTON module documentation
✅ Increased the web server authentication password limit length from 63 to 64 characters

🐞 Fixes & Improvements

🐞 Fixed corrupted date/time in time settings
🐞 Fixed script list reload on error
🐞 Fixed crash when parsing metadata in .gbl files
🐞 Fixed random ISR crash on startup
🐞 Fixed wrong baudrate for CC26XX radio after factory IEEE read
🐞 fixed EFR32 custom firmware flashing issues
🐞 Fixed LTE addon start on Ultima3
🐞 Fixed Blue LED logic on Ultima3
🐞 Fixed AP delay if SSID and password are empty
🐞 Fixed memory leak in usb_list API
🐞 Fixed web server lockup when option "Disable web server when socket is connected" is active

🚀 SLZB-OS v3.2.4 - Release Notes

The latest version of SLZB-OS (v3.2.4) brings improvements to MQTT integration, internal scripting (automations), Zigbee diagnostics, and overall system stability.

✨ New Features & Enhancements

✅ Added MQTT module support for scripts, so internal automations can send/receive MQTT messages - View usage examples
✅ Introduced MQTT API support for SLZB-Ultima - control IR receiver, Transmitter, Buzzer, WS2812 via MQTT (alongside with HTTP control method) - Read MQTT API docs
✅ MQTT can now be activated independently of Zigbee Hub
✅ Pinned socket tasks to dedicated core for improved performance
✅ Zigbee channel scanning added for MR devices (on Z2M/ZHA page)
✅ Display of USB mode added for non-U series devices
✅ IEEE-related controls disabled for Thread or Zigbee Router firmware
✅ Added SSE module for internal scripting

🐞 Fixes & Improvements

🐞 Fixed possible web server overflows during reboot waits
🐞 Fixed MQTT discovery crashes in Zigbee Hub mode
🐞 Optimized overall web server performance
🐞 Fixed incorrect baudrate info for radio3 on Ultima
🐞 Fixed syslog-related crashes
🐞 Hidden socket statuses for USB mode on U devices
🐞 Fixed incorrect display of Z-W addon info on Ultima
🐞 Tuned serial settings for improved communication
🐞 Fixed router reconnect issue on MR4
🐞 Fixed incorrect baudrate / crash during .gbl metadata parsing
🐞 Fixed radio module OTA updates in USB mode (U series)
🐞 Fixed IEEE read issue for MR1U
🐞 Fixed bs-target display issue in addons accordion
🐞 Fixed socket time/status reporting

🚀 SLZB-OS v3.2.0 - Release Notes

We’re happy to announce the release of SLZB-OS v3.2.0 - a stability-focused update with new device support, major improvements for U-series USB functionality, and multiple Zigbee Hub reliability enhancements.

✨ Highlights

✅ FULL support of SLZB-Ultima added - SLZB‑Ultima
✅ Improved USB capabilities for U series (new alternative driver)
✅ Better stability during OTA updates and Zigbee Hub operation
✅ Updated dashboard layout

🆕 New Features

✅ Added Full support for the new SLZB-Ultima device - Learn more
✅ New alternative USB driver can be selected on the "USB" page (U series)
- Provides advanced USB capabilities
✅ USB passthrough now supports 1200 baud

📡 Zigbee Hub Improvements

✅ Zigbee Hub now includes a Reset option if startup fails
✅ Zigbee Hub now stops automatically when an OTA update is in progress
✅ Added missing Zigbee Hub device configurations after reboot
✅ Added Zigbee Hub reset option for recovery when startup fails
✅ Fixed a Zigbee Hub crash that could occur in some situations on the U series

🔌 USB & Passthrough

✅ Added selectable new alternative USB driver on the USB settings page (U series)
✅ USB passthrough now supports 1200 baud
✅ Zigbee OTA now working in USB mode on U series devices

🌐 Wi‑Fi & Network

✅ Wi‑Fi connection now checks hidden SSIDs when connecting
✅ Fixed rare crash when using Wi‑Fi in some cases

⚙️ OTA & System Stability

✅ Reboot confirmation modal is now shown only when reboot is actually required
✅ Dashboard layout updated for improved usability
✅ Fixed WDT (watchdog timer) triggering during OTA updates in some cases

🛠️ Other Fixes and Improvements

✅ Fixed Berry VM manager free logic
✅ Fixed language cache issues
✅ Fixed MR3U EFR32 bootloader issues
✅ Fixed wrong IEEE writes after reboot for CC radio modules
✅ SLZB‑06Mg26U now uses a separate Zigbee OTA firmware

SLZB-OS v3.0.9

We’re excited to release SLZB-OS v3.0.9, bringing major improvements to Zigbee Hub, Thread, and network stability, along with performance boosts, script engine fixes, and a few critical updates.

⚠️ BREAKING CHANGES - ONLY FOR ZIGBEE HUB MODE USERS - NO EFFECT ON ZIGBEE2MQTT OR ZHA USERS!!!

If you use device as Zigbee coordinator (with Zigbee2MQTT or ZHA) / Thread router - it does not affect you. Again, this change is only for those who use device in a Zigbee Hub Mode.

❗ Zigbee Hub Users: All Zigbee devices must be re-paired after this update due to core changes in the Zigbee stack and API.
❗ MQTT Broker Format Changed:
- Old format: 'mqtt://example.com'
- New format: 'example.com' (or, IP format: '127.0.0.1')
You can now use DNS and DDNS hostnames for your MQTT broker.
📘 Updated MQTT API for Zigbee Hub: View the new MQTT API documentation

📡 Zigbee Hub Improvements

✅ Redesigned Zigbee Hub network startup - now significantly faster
✅ Hub now responds to Time attribute and Identify queries
🐞 Fixed: Some Zigbee devices not sending reports in Hub mode
🐞 Fixed: Zigbee Hub mistakenly available for EFR32 on MRx devices

🌐 MQTT & DDNS Enhancements

✅ MQTT Broker now accepts plain domain names, not only IP addresses
✅ "IP Provider" setting for DDNS is now optional
🐞 Fixed DDNS update interval and max value behavior
🐞 Fixed excessive DNS requests from NTP client

⚡ Performance & System Stability

🔧 Increased socket task priority for better responsiveness
🔧 Moved secondary tasks on U series to PSRAM for improved memory usage
🔧 Improved Thread stability for U series devices
🔧 Enhanced EFR32x bootloader activation routine
🔧 Improved USB power switch logic on U series
🐞 Fixed second radio status display in web interface header

🧩 Berry Script Engine (zHub)

🛠 Improved support for sendTuyaData()
🛠 Fixed readAttr() not returning correct values

🌍 Localization

📘 Updated and improved UI translations across supported languages

💡 How to Update SLZB‑OS

You can update your coordinator using one of the following methods:

🔄 OTA Update (Recommended):
Open the SLZB Web UI → Settings and Tools → Firmware updates → Check for updates (SLZB-OS)
🔌 USB Update (Manual Flash):
Go to smlight.tech/flasher, select your model, and follow the flashing instructions.

Revision #25
Created 2025-11-10 12:37:17 UTC by Support3
Updated 2026-10-28 09:24:10 UTC by Taras