Unable to commission Thread devices through Matter about ot-br-posix HOT 12 OPEN

@fostergorman , I was responding directly to this comment:

Shouldn’t make any difference, but note I never figured out how to get commissioning working from the web interface.

The OTBR web interface only implements Thread Commissioning, and not Matter Commissioning.

My assumption (maybe bad) was that the commissioning tab in OTBR would let me add a device that had a built on thread logo AND a matter logo. I assumed I would enter the key off the device and see it in the topology tab of OTBR. Personally I have no devices that have a thread logo without the matter logo.

Matter chose not to implement Thread Commissioning.

from ot-br-posix.

Thanks, does this mean if a device has a matter key printed on it that this precludes thread commission / the device won’t suppport pure thread commissioning? I had assumed the devices were in effect dual mode…

Matter devices are not currently required to implement Thread Commissioning. As a result, most do not.

from ot-br-posix.

I got this working using a macvlan network, this is my compose file (i created the macvlan using portainer). I think this is because mDNS is required to have full UDP multicast access to the network. This runs on my pi with an RCP. I am using with home assistant in a VM on proxmox which connects to this OTBR. I also have full IPv6 routed network. Nothing worked until i did a)this and b)realized i need to use android not iOS to commission a device.

services:
  otbr:
    container_name: otbr
    image: "openthread/otbr:latest"
    privileged: true
    restart: unless-stopped
    networks:
      - otbr_mvl
    sysctls:
      net.ipv6.conf.all.disable_ipv6: 0
      net.ipv4.conf.all.forwarding: 1
      net.ipv6.conf.all.forwarding: 1
      net.ipv6.conf.all.accept_ra_rt_info_max_plen: 64
      net.ipv6.conf.all.accept_ra: 2
    command: --radio-url spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=460800
    devices:
      - /dev/ttyUSB1
    dns: 127.0.0.1

networks:
   otbr_mvl:
     external: true

from ot-br-posix.

I got this working using a macvlan network, this is my compose file (i created the macvlan using portainer). I think this is because mDNS is required to have full UDP multicast access to the network. This runs on my pi with an RCP. I am using with home assistant in a VM on proxmox which connects to this OTBR. I also have full IPv6 routed network. Nothing worked until i did a)this and b)realized i need to use android not iOS to commission a device.

services:
  otbr:
    container_name: otbr
    image: "openthread/otbr:latest"
    privileged: true
    restart: unless-stopped
    networks:
      - otbr_mvl
    sysctls:
      net.ipv6.conf.all.disable_ipv6: 0
      net.ipv4.conf.all.forwarding: 1
      net.ipv6.conf.all.forwarding: 1
      net.ipv6.conf.all.accept_ra_rt_info_max_plen: 64
      net.ipv6.conf.all.accept_ra: 2
    command: --radio-url spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=460800
    devices:
      - /dev/ttyUSB1
    dns: 127.0.0.1

networks:
   otbr_mvl:
     external: true

Thank you for the reply. I will give that a shot sometime this week or next and let you know if it works for my case. We aren't using Home Assistant, so I'm hoping that doesn't make much of a difference.

from ot-br-posix.

from ot-br-posix.

Shouldn’t make any difference, but note I never figured out how to get commissioning working from the web interface.

Matter devices do not support Thread Commissioning - they support Matter Commissioning.

from ot-br-posix.

Matter does support commissioning of Thread devices. I am able to use Matter to bring a Thread device onto the Thread network. You can see the device be brought onto the Thread network during Matter commissioning. The issue is after the device is brought onto the Thread network, it can't be reached again.

from ot-br-posix.

Shouldn’t make any difference, but note I never figured out how to get commissioning working from the web interface. Get Outlook for iOShttps://aka.ms/o0ukef
…
________________________________ From: fostergorman @.> Sent: Tuesday, June 4, 2024 7:32:29 AM To: openthread/ot-br-posix @.> Cc: scyto @.>; Comment @.> Subject: Re: [openthread/ot-br-posix] Unable to commission Thread devices through Matter (Issue #2277) I got this working using a macvlan network, this is my compose file (i created the macvlan using portainer). I think this is because mDNS is required to have full UDP multicast access to the network. This runs on my pi with an RCP. I am using with home assistant in a VM on proxmox which connects to this OTBR. I also have full IPv6 routed network. Nothing worked until i did a)this and b)realized i need to use android not iOS to commission a device. services: otbr: container_name: otbr image: "openthread/otbr:latest" privileged: true restart: unless-stopped networks: - otbr_mvl sysctls: net.ipv6.conf.all.disable_ipv6: 0 net.ipv4.conf.all.forwarding: 1 net.ipv6.conf.all.forwarding: 1 net.ipv6.conf.all.accept_ra_rt_info_max_plen: 64 net.ipv6.conf.all.accept_ra: 2 command: --radio-url spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=460800 devices: - /dev/ttyUSB1 dns: 127.0.0.1 networks: otbr_mvl: external: true Thank you for the reply. I will give that a shot sometime this week or next and let you know if it works for my case. We aren't using Home Assistant, so I'm hoping that doesn't make much of a difference. — Reply to this email directly, view it on GitHub<#2277 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACWXVXHIJPVTH7FHFV57FPLZFXFX3AVCNFSM6AAAAABHLIBVV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXGY4TENZZGA. You are receiving this because you commented.Message ID: @.***>

By the web interface do you mean OTBR's interface? I have never been able to get that to work either.

from ot-br-posix.

Matter does support commissioning of Thread devices.

Matter does NOT support Thread Commissioning as defined in the Thread Specification. The OTBR web interface implements Thread Commissioning.

Matter Commissioning supports configuring Thread interfaces, but that is not the same as Thread Commissioning. As a result, Thread Commissioning CANNOT be used to commission Matter devices.

from ot-br-posix.

I think their may be a mix up of words here since both Matter and Thread use the terminology "commissioning". What I'm saying is that, through Matter commissioning, you are able to connect a Thread device to a Thread network, not that Matter is doing Thread commissioning.

from ot-br-posix.

from ot-br-posix.

from ot-br-posix.