MoT Standalone Server with HA in different VLAN (attempt #3)

I’ve been trying to get Matter over Thread to work without success. I have Unifi and am fully aware of the Unifi IPV6 VLAN mDNS challenges. This is already attempt #3 after some rage quits… :frowning: (Thread HA and VLANs - will this work? - #5 by wmaker)

My Unifi network setup:

Network Vlan Wifi Used by IPV4 IPV6
Main VLAN1 n/a homeasisstant, DNS 192.168.1.4/24 fd00:1::/42 SLAAC
Users VLAN20 Wifi_Main phone, laptops 192.168..20.4/24 fd00:20::/42 SLAAC
IOT VLAN30 Wifi_IOT, Wifi_IOT24 OTBR RPi, Matter Devices 192.168.30.4/24 fd00:30::/42 SLAAC

I know unifi and IPV6 dont place well so i need to find a way to make it work. I realized that my main wifi is not in the same VLAN as the HA instance, maybe also adding to the IPV6 mDNS issues.

To deal with the routing challenges, I want to setup a standalone OTBR router on a RPI with fixed IP in VLAN30. Then use REST.API from HA to this RPI to connect HA to OTBR.

RPI has a ZBT2 connected on /dev/ttyACM0, uGreen BT6.0 bluetooth dongle and network port eth0. IPV6 forwarding is enabled. On the RPI i followed GitHub - ownbee/hass-otbr-docker: Stand-alone Home Assistant OpenThread Border Router docker container. · GitHub. Firewall rules from RPI to HA + return is unrestricted.

On HA I am connecting to OTBR router using the Rest API to http://192.168.30.15:8081

Afterward I joined my phone to the IOT “Wifi_IOT24”, setup companion app to HA URL IP address and Home Network = “Wifi_IOT24”.

MoT Credentials were synced before adding new matter devices. When adding a new Ikea devices, I am going through the credentials phase but then nothing.

what else can I do this time?

compose.yaml

#
# https://github.com/ownbee/hass-otbr-docker/tree/main
#
services:
  otbr:
    container_name: otbr
    image: ghcr.io/ownbee/hass-otbr-docker
    restart: unless-stopped
    privileged: true # don't change this !
    network_mode: host # don't change this !
    cap_add:
      - SYS_ADMIN
      - NET_ADMIN
    environment:
      DEVICE: "/dev/ttyAMC0"
      BACKBONE_IF: eth0
      FLOW_CONTROL: 1
      FIREWALL: 1
      NAT64: 1
      BAUDRATE: 460800
      OTBR_REST_PORT: 8081
      OTBR_WEB_PORT: 7586
      # OTBR_WEB_INTERFACE: "0.0.0.0"
      AUTOFLASH_FIRMWARE: 0
      OTBR_LOG_LEVEL: error
    devices:
      - /dev/ttyAMC0:/dev/ttyAMC0
      - /dev/net/tun:/dev/net/tun
    volumes:
      - ./otbr_data:/data/thread
    logging:
      driver: "json-file"
      options:
        max-file: "3"
        max-size: "1m"

  # Matter server example (the standard image)
  matter-server:
    image: ghcr.io/home-assistant-libs/python-matter-server:stable
    container_name: matter-server
    restart: unless-stopped
    network_mode: host
    privileged: true
    security_opt:
      - apparmor:unconfined
    volumes:
      - ./matter_data:/data/
      - /run/dbus:/run/dbus:ro  # For bluetooth
      - /etc/localtime:/etc/localtime:ro
    logging:
      driver: "json-file"
      options:
        max-file: "3"
        max-size: "1m"
    command: >
      --storage-path /data
      --paa-root-cert-dir /data/credentials
      --bluetooth-adapter 0
      --log-level-sdk progress
      --primary-interface eth0

Matter server needs WAN access
I generally block WAN on IOT vlan and presumed you may have done same.

When connecting devices I think phone, device, matter server and HA must all be on same network.

Matter & Thread Deep Dive

You wrote that you were aware of the mDNS issues, but I do not see a solution for them anywhere in your setup description.