What type of installation are you running and on what setup of hardware/hypervisor?
Hi @WallyR
It is set up on a Proxmox, and have been for years.
It’s the ‘Core’ version running in a VM.
The SkyConnect is looped into the HA through a USB ‘Vendor/device’ mapping.
HA sees the Skyconnect, and I can flash it with different firmwares.
But I’m really lost here.
At some point I had a VLAN60 set up. I found out that was in nmcli, so I’ve removed that as it is no longer in use.
That removed the ‘/VLAN60/’ errors from the log.
I then read that I had to make sure that IPv6 was enabled on HA, as thread uses that.
So I did that.
I then removed all addons and integration, and did a reboot of the entire VM, not just HA.
I then went to hardware, and asked it to set up the skyconnect as a thread device.
It installed the OpenThread Border Router as it should.
It also discovered the Thread integration.
I then added the Matter Server Add On.
And it showed the Matter integration as well.
But I still see errors:
From the OpenThread Border Router:
[18:23:30] INFO: Starting otbr-agent...
otbr-agent[175]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[175]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[175]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[175]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-flow-control
otbr-agent[175]: [NOTE]-AGENT---: Radio URL: trel://enp0s18
otbr-agent[175]: [NOTE]-ILS-----: Infra link selected: enp0s18
otbr-agent[175]: 00:00:00.062 [N] RoutingManager: BR ULA prefix: fd33:1de0:627b::/48 (loaded)
otbr-agent[175]: 00:00:00.064 [N] RoutingManager: Local on-link prefix: fd61:61c8:baec:e0bb::/64
otbr-agent[175]: 00:00:00.102 [N] Mle-----------: Role disabled -> detached
otbr-agent[175]: 00:00:00.127 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[175]: 00:00:00.139 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[175]: 00:00:00.140 [W] Platform------: [netif] ADD [U] fe80:0:0:0:5c8d:5950:470:8b2c failed (InvalidArgs)
otbr-agent[175]: 00:00:00.140 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:00.140 [W] Platform------: [netif] ADD [U] fdbe:ac6a:35cd:690f:abca:2e38:84ad:139e failed (InvalidArgs)
otbr-agent[175]: 00:00:00.141 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:00.141 [W] Platform------: [netif] ADD [U] fdbe:ac6a:35cd:690f:0:ff:fe00:f800 failed (InvalidArgs)
otbr-agent[175]: 00:00:00.141 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:00.141 [W] Platform------: [netif] Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
s6-rc: info: service otbr-agent-configure: starting
Done
otbr-agent[175]: 00:00:00.515 [W] Platform------: Failed to write CLI output: Broken pipe
s6-rc: info: service otbr-agent-configure successfully started
[18:23:31] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
otbr-agent[175]: 00:00:27.828 [N] Mle-----------: RLOC16 f800 -> fffe
otbr-agent[175]: 00:00:27.886 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[175]: 00:00:34.386 [N] RouterTable---: Allocate router id 62
otbr-agent[175]: 00:00:34.386 [N] Mle-----------: RLOC16 fffe -> f800
otbr-agent[175]: 00:00:34.392 [N] Mle-----------: Role detached -> leader
otbr-agent[175]: 00:00:34.393 [N] Mle-----------: Partition ID 0x6c682f6b
otbr-agent[175]: 00:00:34.430 [W] Platform------: [netif] ADD [U] fdbe:ac6a:35cd:690f:0:ff:fe00:f800 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.430 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:34.432 [W] Platform------: [netif] ADD [U] fdbe:ac6a:35cd:690f:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.433 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[175]: 00:00:35.312 [W] Platform------: [netif] ADD [U] fdbe:ac6a:35cd:690f:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[175]: 00:00:35.312 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:35.350 [W] Platform------: [netif] ADD [U] fdbe:ac6a:35cd:690f:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[175]: 00:00:35.351 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:35.352 [W] Platform------: [netif] ADD [U] fd33:1de0:627b:1:c1f6:2cc8:9771:9ae0 failed (InvalidArgs)
otbr-agent[175]: 00:00:35.352 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:47.262 [W] Platform------: [netif] ADD [U] fdbe:ac6a:35cd:690f:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[175]: 00:00:47.262 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6066:ceff:fe28:2e22/veth0e5b693/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6066:ceff:fe28:2e22/veth0e5b693/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6066:ceff:fe28:2e22/veth0e5b693/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6066:ceff:fe28:2e22/veth0e5b693/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6066:ceff:fe28:2e22/veth0e5b693/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::6066:ceff:fe28:2e22/veth0e5b693/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::301b:73ff:fe6f:e1ad/veth9c5dde9/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::301b:73ff:fe6f:e1ad/veth9c5dde9/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::79:49ff:fef0:a60a/vethaa59a71/33
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::301b:73ff:fe6f:e1ad/veth9c5dde9/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::301b:73ff:fe6f:e1ad/veth9c5dde9/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::301b:73ff:fe6f:e1ad/veth9c5dde9/35
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::301b:73ff:fe6f:e1ad/veth9c5dde9/35
Looking at NMCLI it looks like this:
So it does have IPv6 set up, and there is a fe80… interface, but it’s not what’s shown in the nmcli list??
Furthermore, at the current state I can’t even sync thread credentials from the HA app (I have an Android).