wblondel

I would lke to use a VPN with this container, is it possible?

Hi, I raised the issue to the dev and he was able to fix it 😁 One of my DBMS didn't have a database yet, causing Databasement to crash.

I can't get the backups to be automatically executed. ENABLE_QUEUE_WORKER is set to True, yet nothing happens. When I run a job manually, it works though.

Hello, may I have the fix too? The 7.2 is still in beta, the plugin shouldn't assume that everyone already has it.

Alright, so after trying to make the commissioning work with other routers configured as a media bridge (which failed), I bought a pair of CPL. I connected one to my ISP box downstairs, and one to the Ethernet port of my NAS. Then I passed through the Ethernet NIC to the Home Assistant VM and configured the VM so that it uses only this NIC. It now works flawlessly.

I edited my first post with the source of the issue.

Yes, I can control the devices and get data from them using HA. I put back the original network setup NAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> Asus RT-BE58U -----via Wi-Fi-----> ISP box And it still works (control + data retrieval). It is only a problem for commissioning...

I have some news. I am not sure if it is great news though 🤣 I connected the Netgear switch directly to my ISP box downstairs with the 40m cable. I rebooted my NAS just in case, and tried to commission again the device, and........... it worked! Does that mean that the Asus RT-BE58U configured as a media bridge is somehow filtering things it shouldn't filter? Commissionning works with this: NAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> ISP box Commissionning doesn't work with this: NAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> Asus RT-BE58U -----via Wi-Fi-----> ISP box

Sorry but Matter over WiFi and Matter over Thread are definitely different things 😅 https://docs.silabs.com/matter/2.5.1/matter-fundamentals-introduction/#matter-enablement

Pairing a Matter over Thread device directly on HA without a phone is not convenient, as it requires a Bluetooth adapter and the machine where HA is installed needs to be physically near the device to commission. If nothing else works I'll buy a Bluetooth USB adapter but I would not consider that a solution...

I did as per previous messages, I set the correct sysctl configs and enabled host access in the Docker settings (I still don't understand why the latter is needed). I rebooted everything (ISP box + Asus + my NAS) in case and tried again to commission. It still failed. It's ok it's also not my first language :D

How do you do that? My device is NOT Matter over WiFi, but Matter over Thread.

Mmmh, yes. How can HA communicate with Thread devices if I don't set it up? I'm puzzled by your question 😁 I'm planning to add multiple Matter over Thread devices in the future.

To me there is only one network, it's just that there is a wireless bridge between the ground floor and the first floor. There is no double NAT of any kind. There is also only one WiFi AP, it's the one of the ISP box downstairs. Tomorrow I'll receive a 30m Ethernet cable, I'll be able to plug my NAS directly to the ISP box, bypassing the Asus bridge. Let's see if it changes anything!

that was before you replied. "but with reedits and reverting that makes this difcult..." You are so over-acting. I edited BEFORE you replied. I reverted ONE thing. Please stop replying.

@bmartino1 I am not editing past posts.

I did the VM and Docker changes you asked me to make on the previous message, even though it didn't make sense to me (you even talked about "unraid hpyer-v virtual network", what does Hyper-V have ANTHING TO DO with my issue ??????? Where are we talking about Windows ??). I asked why I had to change Docker configuration and you didn't give me a reason. Since I didn't want to keep configuration changes that 1/ seems unrelated 2/ didn't have any effect, I reverted them. This is the ONLY thing I reverted. I don't know why you're making such a big drama about that. You say "Its also not clear how your connecting to HA from the Android device" The answer is on my very first post. ---> "I am trying to commission an Eve Eenergy (Matter over Thread) plug with the Home Assistant Android app on my Samsung A55 5G phone." You say "as you were seeing some matter udp on the android but not else where" --> I never saw Matter UDP anywhere. Only Matter TCP services after trying to commission a device. And I see them from any device. You say "I prefer you had some linux laptop to run other commands to test connect to and run" --> I have. Go on, what should I do? About your remark on IGMP (my edit was already there when you replied BTW) --> someone else asked me to try to switch to v2 if it made a difference, it didn't. You're not the only person trying to help me (but honestly I feel I'm talking to an AI more than a person). You say "you don't know what your doing" --> not sure why you're saying that. I'm trying to find the point of failure. I've already read all the resources you gave me and all the threads related to that on this forum, all the solutions that were given didn't solve my issue. So I ask for help. But your messages seem to be written by an AI... Tomorrow I will receive a 30-meter ethernet cable. I'll plug my switch directly to the ISP box downstairs, to bypass the Asus configured as a media bridge. If it still doesn't work then the Asus is not the issue. What's strange to me is that there doesn't seem to have any error on Home Assistant's side (OTBR logs etc).

@bmartino1 "FYI yes you can temp disabled ipv4 on android. it requires going into the network and seting manul setting and disabling ipv4 and enabling ipv6" No. I don't have this option. Do you see any issue on the log I shared? The default network source on the VM Manager is br0. For Docker, host access to custom networks is disabled but why does it matter in my case? HAOS is in a VM... Anyway, I enabled it and changed the VM interface to this: <interface type='direct' trustGuestRxFilters='yes'> <mac address='52:54:00:ca:c3:f3'/> <source dev='br0' mode='bridge'/> <target dev='macvtap0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface>The issue was still there so I reverted the changes.

@bmartino1 Border Router DiscoveryI am able to see the _meshcop UDP service using the mDNS Discovery app on my phone, and avahi-browse on Unraid. However, I don’t see anything for _matter UDP. After trying to commission a device, I see 2 devices for _matter TCP: one for IPv4 and one for IPv6. OTBRI first had to enable the Web UI in the add-on configuration. This is what I see on the Status page: IPv6:LinkLocalAddress fe80:0:0:0:d088:33ae:4207:8978 IPv6:LocalAddress fd4c:f03e:4bbd:1:a7f8:42a8:2a62:e3c8 IPv6:MeshLocalAddress fdcc:2c3b:173c:81bb:7644:8069:9eeb:bced IPv6:MeshLocalPrefix fdcc:2c3b:173c:81bb: Network:Name ha-thread-f150 Network:PANID 0xf150 Network:PartitionID 265239192 Network:XPANID bb29c51f4d16770b OpenThread:Version OPENTHREAD/thread-reference-20230706-1129-g7bd3abd67-dirty; POSIX; Jan 14 2025 21:04:25 OpenThread:Version API 470 RCP:Channel 15 RCP:EUI64 04e3e5fffe6b996a RCP:State leader RCP:TxPower 5 dBm RCP:Version SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4; EFR32; Apr 5 2025 16:25:05 WPAN service associated Phone’s IPv6 Reachability to OTBRTcpdump: command not found on Unraid. But I confirm I can see traffic coming to the OTBR when I commission a device, as shown on the logs I uploaded on my previous message. It’s not possible to disable IPv4 on Android. Firewall / NPT / RA issuesOutput of iptables -L -v -n Chain INPUT (policy ACCEPT 225K packets, 30M bytes) pkts bytes target prot opt in out source destination 223K 30M LIBVIRT_INP all -- * * 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 76M 87G LIBVIRT_FWX all -- * * 0.0.0.0/0 0.0.0.0/0 76M 87G LIBVIRT_FWI all -- * * 0.0.0.0/0 0.0.0.0/0 76M 87G LIBVIRT_FWO all -- * * 0.0.0.0/0 0.0.0.0/0 76M 87G DOCKER-USER all -- * * 0.0.0.0/0 0.0.0.0/0 76M 87G DOCKER-ISOLATION-STAGE-1 all -- * * 0.0.0.0/0 0.0.0.0/0 56M 75G ACCEPT all -- * docker0 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 425 25712 DOCKER all -- * docker0 0.0.0.0/0 0.0.0.0/0 20M 12G ACCEPT all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- docker0 docker0 0.0.0.0/0 0.0.0.0/0 212 53889 ACCEPT all -- * br-ad0cdd8ab999 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 7 448 DOCKER all -- * br-ad0cdd8ab999 0.0.0.0/0 0.0.0.0/0 189 870K ACCEPT all -- br-ad0cdd8ab999 !br-ad0cdd8ab999 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- br-ad0cdd8ab999 br-ad0cdd8ab999 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- * br-7829c5bf10a9 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 0 0 DOCKER all -- * br-7829c5bf10a9 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- br-7829c5bf10a9 !br-7829c5bf10a9 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- br-7829c5bf10a9 br-7829c5bf10a9 0.0.0.0/0 0.0.0.0/0 0 0 WIREGUARD all -- * * 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT 184K packets, 47M bytes) pkts bytes target prot opt in out source destination 183K 46M LIBVIRT_OUT all -- * * 0.0.0.0/0 0.0.0.0/0 Chain DOCKER (3 references) pkts bytes target prot opt in out source destination 7 448 ACCEPT tcp -- !br-ad0cdd8ab999 br-ad0cdd8ab999 0.0.0.0/0 172.18.0.4 tcp dpt:2283 22 1408 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:8112 0 0 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:8118 0 0 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:9118 0 0 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:58846 0 0 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:58946 0 0 ACCEPT udp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 udp dpt:58946 Chain DOCKER-ISOLATION-STAGE-1 (1 references) pkts bytes target prot opt in out source destination 20M 12G DOCKER-ISOLATION-STAGE-2 all -- docker0 !docker0 0.0.0.0/0 0.0.0.0/0 189 870K DOCKER-ISOLATION-STAGE-2 all -- br-ad0cdd8ab999 !br-ad0cdd8ab999 0.0.0.0/0 0.0.0.0/0 0 0 DOCKER-ISOLATION-STAGE-2 all -- br-7829c5bf10a9 !br-7829c5bf10a9 0.0.0.0/0 0.0.0.0/0 76M 87G RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-ISOLATION-STAGE-2 (3 references) pkts bytes target prot opt in out source destination 0 0 DROP all -- * docker0 0.0.0.0/0 0.0.0.0/0 0 0 DROP all -- * br-ad0cdd8ab999 0.0.0.0/0 0.0.0.0/0 0 0 DROP all -- * br-7829c5bf10a9 0.0.0.0/0 0.0.0.0/0 20M 12G RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-USER (1 references) pkts bytes target prot opt in out source destination 76M 87G RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 Chain LIBVIRT_FWI (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * virbr0 0.0.0.0/0 192.168.122.0/24 ctstate RELATED,ESTABLISHED 0 0 REJECT all -- * virbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable Chain LIBVIRT_FWO (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- virbr0 * 192.168.122.0/24 0.0.0.0/0 0 0 REJECT all -- virbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable Chain LIBVIRT_FWX (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- virbr0 virbr0 0.0.0.0/0 0.0.0.0/0 Chain LIBVIRT_INP (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67 0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67 Chain LIBVIRT_OUT (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT udp -- * virbr0 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT tcp -- * virbr0 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 0 0 ACCEPT udp -- * virbr0 0.0.0.0/0 0.0.0.0/0 udp dpt:68 0 0 ACCEPT tcp -- * virbr0 0.0.0.0/0 0.0.0.0/0 tcp dpt:68 Chain WIREGUARD (1 references) pkts bytes target prot opt in out source destinationOutput of docker exec addon_core_openthread_border_router ot-ctl state leader DoneOutput of docker exec addon_core_openthread_border_router ot-ctl router table, before trying to commission a device: Output of the same command, after trying to commission a device (it failed): Output of docker exec addon_core_openthread_border_router ot-ctl netdata show Output of docker exec addon_core_openthread_border_router ot-ctl prefix Output of docker exec addon_core_openthread_border_router ot-ctl backbonerouter Error 35: InvalidCommandI am already on the latest version of Unraid: v7.1.4. Configuration of my Mikrotik CRS305I figured it would be useful for you to know the configuration of the switch my NAS is connected to. I do not use VLANs and IGMP Snooping is disabled. (I temporarily set the IGMP version to v2, it didn't change anything. it's now back to v3.)

@bmartino1 Unfortunately, the issue remains. Output of sysctl -p on Unraid: Below, the debug log from the OpenThread Border Router during the commissionning steps: core_openthread_border_router_2025-06-21T18-51-44.609Z.log

@bmartino1 alright, I'll try with these settings. I wasn't sure if they were applicable to my situation.

@bmartino1 hey, thanks for replying. I went through again this post (I've already read it before). It seems OP has part of HA in a VM, and another part in Docker in Unraid. My HA is entirely in a VM. He does say "I am using HA (Docker) and I am currently using a VM with HAOS in it but only the Matter server. However, I want to use the Matter server in Docker to get rid of the VM.". Then the rest of the thread is about Docker, so it seems it's not applicable to me. However, you mentioned that IPv4 and IPv6 forwarding needs to be enabled. That's something I already did (see 5th point of "What I tried so far"). root@NAS:~# sysctl net.ipv4.ip_forward net.ipv4.ip_forward = 1 root@NAS:~# sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.forwarding = 1This is right after Unraid booted. Should I try to set net.ipv6.conf.eth0.accept_ra=2 ?

I have the same problem. Installed version is "2025.05.01.2159" but the dashboard reports version "2021.10.12.1921" (!!!)

EDITThe source of the issue has been found: the Asus media bridge between my switch upstairs and my ISP box downstairs causes the commissioning to fail. Commissionning works with this: NAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> ISP box Commissionning doesn't work with this: NAS ---> Mikrotik CRS305-1G-4S+ switch --> Netgear GS108v4 switch ---> Asus RT-BE58U -----via Wi-Fi-----> ISP box The new question is: how can I solve this? Thank you! END OF EDIT Hello, I'm asking for your help here because I've been trying to fix this issue for 2 weeks with no success. I will try to give as many details as possible. I have a two-storey house. My Fiber ISP internet box is at the ground floor, and I have both IPv4 CGNAT and IPv6 connectivity. SLAAC is enabled, but I have the option to enable DHCPv6 as well. WAN info on my ISP box: IPv4 ----- IP address: 10.153.29.150 Default gateway: 10.153.29.151 Primary DNS: 109.0.66.10 Secondary DNS: 109.0.66.20 IPv6 ----- IPv6 address: 2a02:8428:aa24:2601:da78:7fff:fe41:683f IPv6 prefix: 2a02:8428:aa24:2600::/56 Default gateway: fe80::5555 Primary DNS: 2a02:8400::6001 Secondary DNS: 2a02:8400::6000My computer lab is upstairs. I have an Asus RT-BE58U configured as a "Media Bridge", connected to the wifi downstairs. On this Asus device, a Netgear GS108v4 switch is connected. On this Netgear switch, I have a printer, a Raspberry Pi and a Mikrotik CRS305-1G-4S+ running SwOS v2.17. On this Mikrotik device, my desktop computer and my Unraid NAS (v7.1.4) are connected with each a Mellanox MCX311A-XCAT ConnectX-3 card and a Cisco-Molex 74752-3701 SFP+ cable. My computer and the NAS do have IPv6 connectivity. Output of ifconfig en0 on my desktop computer: en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM> ether d2:31:9d:b5:ca:a9 inet6 fe80::1cf5:e3cc:b692:3597%en0 prefixlen 64 secured scopeid 0xe inet6 2a02:8428:aa24:2601:1499:6045:20ea:51c5 prefixlen 64 autoconf secured inet6 2a02:8428:aa24:2601:10eb:fde8:b956:54f4 prefixlen 64 autoconf temporary inet6 fdbb:29c5:1f4d:770b:1499:2b49:8d89:28f5 prefixlen 64 autoconf secured inet 192.168.1.235 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=201<PERFORMNUD,DAD> media: autoselect status: activeOutput of ifconfig br0 on my Unraid NAS: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.20 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fe80::f652:14ff:fe89:4250 prefixlen 64 scopeid 0x20<link> inet6 fdbb:29c5:1f4d:770b:f652:14ff:fe89:4250 prefixlen 64 scopeid 0x0<global> inet6 2a02:8428:aa24:2601:f652:14ff:fe89:4250 prefixlen 64 scopeid 0x0<global> ether f4:52:14:89:42:50 txqueuelen 1000 (Ethernet) RX packets 16654 bytes 2290570 (2.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7089 bytes 11395535 (10.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0I can ping, traceroute, and access websites via IPv6 on both these devices. On my Unraid NAS, I created an Home Assistant OS VM, and I configured USB passthrough for the Home Assistant Connect ZBT-1. The configuration of the VM is : <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>HomeAssistant OS</name> <uuid>01cbc3e3-bfed-6023-551b-c45e53971159</uuid> <metadata> <vmtemplate xmlns="http://unraid" name="Linux" iconold="linux.png" icon="linux.png" os="linux" webui="" storage="default"/> </metadata> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='2'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-9.2'>hvm</type> <loader readonly='yes' type='pflash' format='raw'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram format='raw'>/etc/libvirt/qemu/nvram/01cbc3e3-bfed-6023-551b-c45e53971159_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' clusters='1' cores='1' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='hpet' present='no'/> <timer name='hypervclock' present='no'/> <timer name='pit' tickpolicy='delay'/> <timer name='rtc' tickpolicy='catchup'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback' discard='unmap'/> <source file='/mnt/cache/domains/haos_ova-15.2.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='sata'/> <serial>vdisk1</serial> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ca:c3:f3'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/run/libvirt/qemu/channel/1-HomeAssistant OS/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' sharePolicy='ignore'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='16384' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x10c4'/> <product id='0xea60'/> <address bus='1' device='2'/> </source> <alias name='hostdev0'/> <address type='usb' bus='0' port='1'/> </hostdev> <watchdog model='itco' action='reset'> <alias name='watchdog0'/> </watchdog> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Version of Home Assistant: Installation method: Home Assistant OS Core: 2025.6.1 Supervisor: 2025.05.5 Operating System: 15.2 Frontend: 20250531.3The Home Assistant VM does have IPv6 connectivity. Output of ha network info in the CLI: I configured the Home Assistant Connect ZBT-1 on HomeAssistant, and I now have the "Matter Server" (v8.0.0) and the "OpenThread Border Router" (v2.13.0) add-ons installed. The OpenThread RCP v2.4.4.0 firmware has been flashed on the ZBT-1. Now here is the problem... I am trying to commission an Eve Eenergy (Matter over Thread) plug with the Home Assistant Android app on my Samsung A55 5G phone. This phone is connected to the WiFi network broadcasted by the ISP box and does have IPv6 connectivity too. The commissioning procedure fails at the last step "Checking network connectivity to [...]". This is what I tried so far : I had the Tailscale plugin installed and configured on the HomeAssistant VM, I uninstalled it, deleted the configuration and rebooted Unraid. I had the Tailscale plugin installed on Unraid, I uninstalled it and rebooted Unraid. I connected the Mikrotik CRS305-1G-4S+ directly to the Asus RT-BE58U, bypassing the Netgear GS108v4 switch. I disabled any custom DNS configuration (like NextDNS) on Unraid, my phone, my router. I verified that IP forwarding are enabled in Unraid for both IPv4 and IPv6, they are (net.ipv4.ip_forward = 1 and net.ipv6.conf.all.forwarding = 1). On my phone, I deleted all data for the "Google Play Services" and, on the HA mobile app, I went to "Companion app > Troubleshooting > Sync Thread credentials". After 10 seconds, it said "Added network from Home Assistant to this device.". If I try again, it says "Home Assistant and this device use the same network.". How can I debug this? Do you have any idea what the issue could be? Thanks a lot in advance 😁

Hi, I have the same problem, the write speed is only 6MB/s, at this rate it will take 34 days to finish clearing the drive... How do I stop the process? I can't find any `dd` running. Thanks! EDIT : looks like there is no way to interrupt the script so I'll just reboot the server. EDIT2: rebooting makes Unraid waiting for the script to finish..... EDIT3: it finally timed out