SLZB-MR1 über PoE mit OTBR auf Docker für Matter over Thread

[Qlink]

Hi Leute,

ich möchte gerne einen SLZB-MR1(https://smlight.tech/product/slzb-mr1/) über Ethernet (PoE) mit OTBR(https://openthread.io/guides/border-router/build-docker) auf Docker für Matter over Thread in Verbindung mit iobroker verwenden.

Kurz zu meiner Umgebung:

Synology NAS inkl. Portainer als Host System für Docker.
Alle Container per macvlan über eine eigene IP eingerichtet und erreichbar.
IP Syno: 192.168.30.5
IP iob: 192.168.30.90
IP slzb-mr1: 192.168.30.9
IP otbr Container: 192.168.30.26

Allgemeine Frage: Kann das setup so mit iobroker funktionieren ?
Im Home Assistant Forum haben das scheinbar einige so am Laufen. Es gibt aber für HA ein eigenes Thread Border Router Addon(https://smlight.tech/manual/slzb-06/guide/thread-matter/), welches die Netzwerkverbindung zwischen HA und dem SLZB-MR1 herstellt.

Ich hätte versucht den otbr Container per Portainer Stacks (Compose) zu starten.
Hier mein Test Stacks:

services:
##### OTBR #####
  otbr:
    container_name: otbr
    image: openthread/border-router:latest
    restart: always
    privileged: true # don't change this !
    networks:
      # MACVLAN
      iobroker-redis-agent-dvr_LAN_public:
        ipv4_address: 192.168.30.26
      # Bridge
      iobroker-redis-agent-dvr_iob_private:
        ipv4_address: 172.18.0.10
    
    cap_add:
      - SYS_ADMIN
      - NET_ADMIN
    environment:
      DEVICE: "/dev/ttyUSB0"
      BACKBONE_IF: eth4
      FLOW_CONTROL: 1
      FIREWALL: 1
      NAT64: 1
      BAUDRATE: 460800
      OTBR_REST_PORT: 8081
      OTBR_WEB_PORT: 8080
      AUTOFLASH_FIRMWARE: 0
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0
      - /dev/net/tun:/dev/net/tun
    volumes:
      - /volume3/docker/otbr_data:/data


        ##### NETWORKS #####
networks:
  iobroker-redis-agent-dvr_LAN_public:
    driver: macvlan
    external: true
          
  iobroker-redis-agent-dvr_iob_private:
    driver: bridge
    external: true

Ich erhalte allerdings beim Starten des Containers folgende Errors im Log:

2025-08-08T08:24:45.958836418Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:45.960598805Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:45.962378653Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:45.964214801Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:45.966209150Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.968077098Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.970111937Z Warning: Extension pkttype revision 0 not supported, missing kernel module?
2025-08-08T08:24:45.971067751Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.975328750Z Warning: Extension set is not supported, missing kernel module?
2025-08-08T08:24:45.975446761Z ip6tables v1.8.10 (nf_tables): Couldn't load match `set':No such file or directory
2025-08-08T08:24:45.975488401Z 
2025-08-08T08:24:45.975512581Z Try `ip6tables -h' or 'ip6tables --help' for more information.
2025-08-08T08:24:45.979555229Z Warning: Extension set is not supported, missing kernel module?
2025-08-08T08:24:45.979674729Z ip6tables v1.8.10 (nf_tables): Couldn't load match `set':No such file or directory
2025-08-08T08:24:45.979705699Z 
2025-08-08T08:24:45.979724889Z Try `ip6tables -h' or 'ip6tables --help' for more information.
2025-08-08T08:24:45.981576627Z Warning: Extension pkttype revision 0 not supported, missing kernel module?
2025-08-08T08:24:45.982423771Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.984530080Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.984681241Z Configuring OpenThread NAT64...
2025-08-08T08:24:45.987984155Z Warning: Extension MARK revision 0 not supported, missing kernel module?
2025-08-08T08:24:45.988807429Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.991900253Z Warning: Extension mark revision 0 not supported, missing kernel module?
2025-08-08T08:24:45.992712476Z Warning: Extension MASQUERADE revision 0 not supported, missing kernel module?
2025-08-08T08:24:45.993533880Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.995545549Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.997618098Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:45.997735628Z Starting otbr-agent...
2025-08-08T08:24:46.001023583Z [NOTE]-AGENT---: Running 0.3.0-e2f9b20
2025-08-08T08:24:46.001139463Z [NOTE]-AGENT---: Thread version: 1.4.0
2025-08-08T08:24:46.001177233Z [NOTE]-AGENT---: Thread interface: wpan0
2025-08-08T08:24:46.001201533Z [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000
2025-08-08T08:24:46.001235484Z [NOTE]-AGENT---: Radio URL: trel://wlan0
2025-08-08T08:24:46.002565609Z [NOTE]-ILS-----: Infra link selected: wlan0
2025-08-08T08:24:46.002632670Z [INFO]-RCP_HOS-: OpenThread log level changed to 5
2025-08-08T08:24:46.002665470Z 54d.23:51:30.760 [C] Platform------: Init() at hdlc_interface.cpp:153: No such file or directory
2025-08-08T08:24:46.005783473Z otbr-agent exited with code 5 (by signal 0).
2025-08-08T08:24:46.014181060Z OpenThread firewall rules removed.
2025-08-08T08:24:46.015309705Z s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
2025-08-08T08:24:46.015418716Z s6-rc: warning: unable to start service otbr-agent: command exited 1
2025-08-08T08:24:46.016595391Z s6-rc: info: service legacy-cont-init: stopping
2025-08-08T08:24:46.021511552Z s6-rc: info: service legacy-cont-init successfully stopped
2025-08-08T08:24:46.021624803Z s6-rc: info: service fix-attrs: stopping
2025-08-08T08:24:46.022804378Z s6-rc: info: service fix-attrs successfully stopped
2025-08-08T08:24:46.022935149Z s6-rc: info: service s6rc-oneshot-runner: stopping
2025-08-08T08:24:46.025957602Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2025-08-08T08:24:52.892217473Z s6-rc: info: service s6rc-oneshot-runner: starting
2025-08-08T08:24:52.894997795Z s6-rc: info: service s6rc-oneshot-runner successfully started
2025-08-08T08:24:52.895107826Z s6-rc: info: service fix-attrs: starting
2025-08-08T08:24:52.899360575Z s6-rc: info: service fix-attrs successfully started
2025-08-08T08:24:52.899468015Z s6-rc: info: service legacy-cont-init: starting
2025-08-08T08:24:52.903535293Z s6-rc: info: service legacy-cont-init successfully started
2025-08-08T08:24:52.903634133Z s6-rc: info: service otbr-agent: starting
2025-08-08T08:24:52.910873225Z Configuring OpenThread firewall...
2025-08-08T08:24:52.912962344Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:52.915036763Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:52.916984182Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:52.918887730Z ipset v7.19: Kernel error received: set type not supported
2025-08-08T08:24:52.921146260Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.923332730Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.925455479Z Warning: Extension pkttype revision 0 not supported, missing kernel module?
2025-08-08T08:24:52.926426233Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.931249644Z Warning: Extension set is not supported, missing kernel module?
2025-08-08T08:24:52.931379385Z ip6tables v1.8.10 (nf_tables): Couldn't load match `set':No such file or directory
2025-08-08T08:24:52.931546106Z 
2025-08-08T08:24:52.931592656Z Try `ip6tables -h' or 'ip6tables --help' for more information.
2025-08-08T08:24:52.936025315Z Warning: Extension set is not supported, missing kernel module?
2025-08-08T08:24:52.936137876Z ip6tables v1.8.10 (nf_tables): Couldn't load match `set':No such file or directory
2025-08-08T08:24:52.936178826Z 
2025-08-08T08:24:52.936204336Z Try `ip6tables -h' or 'ip6tables --help' for more information.
2025-08-08T08:24:52.938334515Z Warning: Extension pkttype revision 0 not supported, missing kernel module?
2025-08-08T08:24:52.939277540Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.941484769Z ip6tables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.941643880Z Configuring OpenThread NAT64...
2025-08-08T08:24:52.945310956Z Warning: Extension MARK revision 0 not supported, missing kernel module?
2025-08-08T08:24:52.946106119Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.949089852Z Warning: Extension mark revision 0 not supported, missing kernel module?
2025-08-08T08:24:52.949939396Z Warning: Extension MASQUERADE revision 0 not supported, missing kernel module?
2025-08-08T08:24:52.950737720Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.953047400Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.955229039Z iptables v1.8.10 (nf_tables): Could not fetch rule set generation id: Invalid argument
2025-08-08T08:24:52.955374240Z Starting otbr-agent...
2025-08-08T08:24:52.958995596Z [NOTE]-AGENT---: Running 0.3.0-e2f9b20
2025-08-08T08:24:52.959103656Z [NOTE]-AGENT---: Thread version: 1.4.0
2025-08-08T08:24:52.959143737Z [NOTE]-AGENT---: Thread interface: wpan0
2025-08-08T08:24:52.959173927Z [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=1000000
2025-08-08T08:24:52.959212077Z [NOTE]-AGENT---: Radio URL: trel://wlan0
2025-08-08T08:24:52.960795704Z [NOTE]-ILS-----: Infra link selected: wlan0
2025-08-08T08:24:52.960896494Z [INFO]-RCP_HOS-: OpenThread log level changed to 5
2025-08-08T08:24:52.960965525Z 54d.23:51:37.718 [C] Platform------: Init() at hdlc_interface.cpp:153: No such file or directory
2025-08-08T08:24:52.964536730Z otbr-agent exited with code 5 (by signal 0).
2025-08-08T08:24:52.973819971Z OpenThread firewall rules removed.
2025-08-08T08:24:52.975143977Z s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
2025-08-08T08:24:52.975335557Z s6-rc: warning: unable to start service otbr-agent: command exited 1
2025-08-08T08:24:52.976671183Z s6-rc: info: service legacy-cont-init: stopping
2025-08-08T08:24:52.981811406Z s6-rc: info: service legacy-cont-init successfully stopped
2025-08-08T08:24:52.981956877Z s6-rc: info: service fix-attrs: stopping
2025-08-08T08:24:52.983190552Z s6-rc: info: service fix-attrs successfully stopped
2025-08-08T08:24:52.983257402Z s6-rc: info: service s6rc-oneshot-runner: stopping
2025-08-08T08:24:52.985013300Z s6-rc: info: service s6rc-oneshot-runner successfully stopped

Das Problem ist, dass ich nicht weiß wie ich dem otbr Container sagen kann, er soll nicht per USB mit dem SLZB kommunizieren, sondern per Ethernet auf die IP 192.168.30.9. Ich finde dazu auch nix auf der otbr Site oder in diversen anderen Foren...

Kann mir hier jemand weiterhelfen, wie ich das Setup zum Laufen bekomme ?

Danke.
Beste Grüße

[Qlink]

@ioT4db

Kannst du mir hier eventuell weiterhelfen ?

[Marc Berg]

Wo hast du die Info her, dass OTBR per IP kommunizieren kann?

EDIT: Ich sehe immer nur die Anbindung per serieller Schnittstelle

[Qlink]

@marc-berg

hier in Verbindung mit homeassistant:

https://smlight.tech/manual/slzb-06/guide/thread-matter/

Oder verwechsle ich hier ein paar Dinge.
Ich muss gestehen, ich durchblicke diese Matter over Thread Geschichte immer noch nicht so ganz °_°

[Marc Berg]

@qlink

HA kann das wohl, der OTBR Container aber nicht. Der erwartet zwingend eine serielle Schnittstelle. Du müsstest also so etwas wie serial-over-IP Workarounds bauen. Ob das funktioniert - keine Ahnung.

[Qlink]

@marc-berg said in SLZB-MR1 über PoE mit OTBR auf Docker für Matter over Thread:

serial-over-IP

Danke für die Klarstellung, sowas ähnliches hab ich befürchtet...

Das lasse ich dann lieber bleiben.

[ioT4db]

hi @qlink, mit otbr hab ich (noch) nichts gemacht, kann dir da leider adhoc auch nichts zu sagen. Der Einfachheit halber verwende ich einen Homepod mini als TBR. Das läuft mit meinen 2 Aquara U200 sehr stabil... VG