#Home Assistant - ZBT-2 - Thread - New Setup, help needed ...

1 messages · Page 1 of 1 (latest)

plain torrent
#

Hello,

I recently baught a "ZBT-2" to connect a bunch of thread enabled devices after reading the HA website.

I didn't see before purchaisng the "Fine Print" that it is "best" to use HA OS, as this was not my intentions.

I'm using docker on a synology NAS, and enabled USB on DSM-7.

I've successfully install HA and ZBT-2 in Zigbee mode and successfully used this to control some devices. So i know HA, ZBT-2 and the USB connections are all good.

I've now trying to connect to some thread devices ... and stuck as the documentation has become vauge. (https://support.nabucasa.com/hc/en-us/articles/31347057208989-Switching-from-Zigbee-to-Thread-support-on-Home-Assistant-Connect-ZBT-2)

What i've 'done' so far:

What's next, I'm now lost should I see the ZBT-2 on the matter server? ( See attached )

📎 message.txt
dry garnet
#

You should see the Thread border router listed via the Thread integration on home assistant (this is used to get the thread network credentials copied to your phone so you can provision matter devices)

#

The matter integration won't show anything thread related. Thred is just one of several lower-level network protocols that Matter can use - Matter just works via IPv6 addressing.

#

You will need to run an openthread border router separately.

#

(that's the part that's kinda difficult to get working properly, unfortunately, and is the main reason why HAOS is recommended)

#

the openthread border router is the part that actually talks to the thread radio - it creates or joins the thread network, and sets up ipv6 routing between your lan and the thread network.

#

To clarify - the python-matter-server does not talk directly to the thread radio at all. It only knows how to talk to devices over IPv6 network, and relies on there being a separate thread border router available if you want it to be able to talk to thread devices.

plain torrent
#

Hi @dry garnet -- Much appreciate the input.

Keep in mind we are talking about the the ZBT-2 product.
( https://www.home-assistant.io/connect/zbt-2/ )

I don't follow this:

The openthread border router is the part that actually talks to the thread radio - it creates or joins the thread network, and sets up ipv6 routing between your lan and the thread network.

The ZBT-2 should connect to hardware that I install Matter-Server on that should act as the border router, Right?

------- Review Below ----

Did I get this correct?
*** Pretend I don't have a Lan, Internet or Wifi, unless noted below ... I'm trying to build a stand along / minimal setup ...

-- Device to be controlled --

Is only supported:
[ Matter + Thread ]

-- Antenna --

ZBT-2 - Only supports "Tread" wireless devices ... No WiFi or internet required.
ZBT-2 --USB--> Matter-Server --> HomeAssistant

-- Software --

https://www.home-assistant.io/integrations/matter/
( If you run Home Assistant in a container, you can run a Docker image of the Matter server. The requirements and instructions for your host setup are described on that GitHub page. )

Then Connect Matter -> HA ...

-- Overview --
https://www.home-assistant.io/images/integrations/matter/matter_thread_infographic.png

plain torrent
#

Prepare Android or iPhone
https://www.home-assistant.io/integrations/matter/


At a minimum, have Android version 8.1. Recommended is version 12 or higher.
Have the latest version of the Home Assistant Companion app, installed from the Play Store (full version).

If you are using Thread: Make sure there is a Thread border router device (Nest Hub (2nd Gen) or Nest Wi-Fi Pro or Home Assistant with the OpenThread Border Router add-on) present in your home network.

*** HERE ***
If you are using OpenThread (for Connect ZBT-1, ZBT-2, or SkyConnect) """as border router""", make sure you followed the steps in the Thread documentation.

Directly:

If you are using OpenThread (for Connect ZBT-1, ZBT-2, or SkyConnect) as border router, make sure you followed the steps in the Thread documentation.

It seems that OpenThread should be used to allow the ZBT-2 to work as the border routher ... I have not done this ( missed it ) and doing so now ...

plain torrent
#

ok ... stuped but i had to reinstall HA as it refused to detect the ZBT-2 at all... after it was prior assinged as Zigbee device ...

#

Now i'm seeing:

image.png
#

. . . Why did the documentation not advise this before starting . . .

image.png
distant copper
#

I'm using the following containers for OTBR and Matter:

  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/thread"
      BACKBONE_IF: enp1s0
      FLOW_CONTROL: 1
      FIREWALL: 1
      NAT64: 1
      BAUDRATE: 921600 #460800
      OTBR_REST_PORT: 8082
      OTBR_WEB_PORT: 7586
      AUTOFLASH_FIRMWARE: 1
    devices:
      - /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_640ce34f9514ed11a206bc8be054580b-if00-port0:/dev/thread
      - /dev/net/tun:/dev/net/tun
    volumes:
      - ./otbr_data:/var/lib/thread

  matter-server:
    image: ghcr.io/matter-js/python-matter-server:stable
    container_name: matter-server
    restart: unless-stopped
    # Required for mDNS to work correctly
    network_mode: host
    security_opt:
      # Needed for Bluetooth via dbus
      - apparmor:unconfined
    volumes:
      # Create an .env file that sets the USERDIR environment variable.
      - ${USERDIR:-$HOME}/docker/matter-server/data:/data/
      # Required for Bluetooth via D-Bus
      - /run/dbus:/run/dbus:ro
#

Change the baudrate based on the firmware you're using

plain torrent
#

@distant copper - Much appreciated! ... I'll give it a try shorty.