Matter Addon Server, no connection: CHIP Error 0x00000003: Incorrect state

Configuration Matter/Thread
1

I am running HAOS in a VM and want to connect my matter devices to it. I have a few tado X devices connected to the tado X bridge (so thats my TBR) and now I want to share the devices via the tado app to my HA. In the app I can click “pair device”, select HA app (on android) and then I get an error after a few seconds. Here is my Matter server log:

2025-01-09 23:47:40.017 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 22.
2025-01-09 23:48:10.037 (Dummy-2) CHIP_ERROR [chip.native.CTL] Discovery timed out
2025-01-09 23:48:10.038 (Dummy-2) CHIP_ERROR [chip.native.ZCL] Secure Pairing Failed
2025-01-09 23:48:10.039 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to establish secure session to device: src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:96: CHIP Error 0x00000003: Incorrect state
2025-01-09 23:48:10.040 (MainThread) ERROR [matter_server.server.client_handler] [139654486499184] Error while handling: commission_with_code: Commission with code failed for node 22.

I am pretty sure it is not a problem with my network, as usual with matter. So I checked the standard stuff when matter does not work. What I did so far:

  • checked that ipv6 is enabled on HAOS (it is on automatic), I get an ipv6 in the settings, but I dont know if the subnetmask is correct

  • checked if ipv6 is enabled on my network itself. I have a Fritzbox 6591 as a router and behind that 2 TP-Link EAPs (245 + 653) behind that as wireless access points. No Vlan, no fancy stuff. IPv6 is enabled on my fritzbox

    image
    image1659×1153 89.3 KB

  • checked if ipv6 is enabled on both of my APs: Here is the only thing that I cant garantue is correct. For my EAP653 I can enable ipv6 in the config. The same setting is missing on my EAP245, but google says it supports it, but the devices should connect to the EAP653 anyway.

Things I also did:

  • disabled multicast to Unicast conversion
  • disabled ARP to Unicast conversion
  • disabled mutlicast filtering So the only thing I found so far that is a common problem, is mDNS. But I have no idea what I should check for that

The only setting in my Omada Controller where I can do stuff with mDNS is creating a new rule with the following settings: I create a test rule that enabled mDNS and selected “all” at Bonjour Service, Services Network and Client Network, but didnt worked

2

I put some troubleshooting tools in this post that might help with mDNS/network issues. Let me know if you figure out a way to resolve your error, as I am running out of ideas.

3

Thanks. Checked out your threat but did not helped much. I am not able to find anything with a mdns browers (tried an android app and a windows tool).
But what I noticed too, I can ipv6 ping my ubuntu machine that is running the haos VM. But I can not ping the haos itself from the ipv6 ip that I got from the menu settings

image
image639×543 16.1 KB

not reachable. Does that mean something is wrong configured with my ubuntu machine?

4

Do you run Docker on your Ubuntu host machine? In the past it’s firewall rules messed with virtual machines IPv6. Try disabling to see if that helps.

5

I do. I disabled the firewall but it seems like it broke more than it helped :smiley:
Some other stuff does not work anymore and port forwarding on ubuntu is broken now. I only can reach HA from the ubuntu host machine itself, not from any other pc.
I had an old pi flying around and installed HAOS on that and it worked flawless. Set it up, imported the thermostat over the matter pair and done. No problem.
So it is not a problem with mDNS/ipv6 etc, its a problem from my ubuntu host and using HAOS in a vm.
I had to change a decent amount of network stuff to get everything working before. Not just HAOS, but docker, dropbear etc. All kinda had network problems and I had to fix stuff. Maybe something broke while doing that.
I followed this video go setup the HAOS vom:

6

Reply 2:
I tried to fix the network stuff but was not able too.
I switched from KVM to VirtualBox and it worked instantly. (I used a bridged network)
Followed this guy:

7

I have the same problem. I had already integrated the thermostat via Matter and everything worked. From one day to the next there were problems. I reinstalled everything and reset it to the factory settings. I can also add the thermostat to Apple’s HOME app and Alexa without any problems, so it simply can’t be the devices. Only Home Assistant is causing stress and no longer allows the thermostat to be integrated… Could it be due to an HA update in the last few days?