OpenThread BorderRouter auf SMLight SLZB-xU (SLZB-OS v3.2.6.dev0) (on-device)!

The latest SLZB-OS beta release supports running OTBR on-device (for SLZB-xU models only). This seems like a good step forward to avoid issues with running serial-over-IP

Dev firmware
Release notes:

:package: SLZB-OS 3.2.6.dev0 - Release Notes (dev)
:sparkles: 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.

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

:house: Home Assistant setup: OTBR REST API is available at http://device-ip:8080

:warning: Important notes / limitations:
:test_tube: Initial (beta) integration — may have limitations or unexpected behavior.
:globe_with_meridians: IPv6 is required and will be force-enabled when this mode is activated.
:brain: “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.

:locked: Availability: only on SLZB-xU series.

:repeat_button: Alternative: you can still use Thread + remote OTBR mode (USB/Ethernet) if you prefer OTBR running elsewhere.

:hammer_and_wrench: Improvements
:stopwatch: Added uptime info for Socket2 and Socket3 in /ha_sensors
:bug: Fixes
:white_check_mark: Fixed a crash in Zigbee Hub mode when a received value is larger than expected

siehe auch
Running OTBR on-device is now possible on SMLight SLZB-xU models

Ich habe den SLZB-MR4U am Laufen. Mittlerweile mit der Version SLZB-OS 3.2.6.dev3.

Leider brechen bei mir bei einigen Matter Geräten immer die Verbindung ab bzw. sind die Geräte manchmal schläfrig und antworten erst nach einiger Zeit wieder.

Jetzt weiß ich nur nicht, ob das an der noch nicht ganz stabilen Implementierung des OTBR liegt oder generell an meinem Netzwerk/Endgeräten.

Hat jemand ähnliche Erfahrungen hiermit?