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

1 messages · Page 1 of 1 (latest)

queen holly
#
  • 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

image.png
#

Anyone has an idea?
Or at least a way to check if ipv6 isnt the problem and a way to check if mDNS isnt the problem?

odd bronze
#

hm, so many things that could be a problem. Maybe try to run 'avahi-browse --all' on your HA host or some Linux host that is in the same network as HA, check if see the tado bridge announcing an ipv6 address, and then ping it ('avahi-resolve -6 -n tadoBridgeIB.....local' then ping6 on that address). If that works then I think the network is ok in general.

pulsar steppe
#

Hello, I'll try to explain my issues and would be grateful for any assistance

Setup

Mikrotik Router
HA Running Under Hyper-V
All IOT Running in own VLAN

Every time I attempt to connect a matter to HA it errors ( every time ) I'll post so logs shortly.

I've gone through my network setup extensively and there are no issues.

I setup a new Home Assistant to rest and I can get matter devices to connect immediately which confirms there is nothing wrong with my network configuration.

I've removed the Matter integration and re-added back in on my Live HA and this has made no difference.

Could anyone point me to any direction with regards to matter and home assistant and wiping and starting again with the setup on my live configuration?

#

2025-01-22 23:17:02.652 (MainThread) INFO [matter_server.server.device_controller] Starting Matter commissioning with code using Node ID 93.
2025-01-22 23:17:03.125 (Dummy-2) INFO [chip.ChipDeviceCtrl] Established secure session with Device
2025-01-22 23:17:07.075 (Dummy-2) INFO [chip.ChipDeviceCtrl] Commissioning complete
2025-01-22 23:17:07.075 (MainThread) INFO [matter_server.server.device_controller] Commissioned Node ID: 93 vs 93
2025-01-22 23:17:07.075 (MainThread) INFO [matter_server.server.device_controller] Matter commissioning of Node ID 93 successful.
2025-01-22 23:17:07.075 (MainThread) INFO [matter_server.server.device_controller] Interviewing node: 93
2025-01-22 23:17:08.985 (MainThread) ERROR [matter_server.server] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/matter_server/server/client_handler.py", line 214, in _run_handler
raise err
File "/usr/local/lib/python3.12/site-packages/matter_server/server/client_handler.py", line 197, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/matter_server/server/device_controller.py", line 339, in commission_with_code
await self._interview_node(node_id)
File "/usr/local/lib/python3.12/site-packages/matter_server/server/device_controller.py", line 601, in _interview_node
await self._chip_device_controller.send_command(
File "/usr/local/lib/python3.12/site-packages/matter_server/server/sdk.py", line 308, in send_command
return await self._chip_controller.SendCommand(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/chip/ChipDeviceCtrl.py", line 1215, in SendCommand
return await future
^^^^^^^^^^^^
chip.interaction_model.InteractionModelError: InteractionModelError: InvalidCommand (0x85)

prime carbon
#

@pulsar steppe can you please create your own issue report here? That way we can help you the best. Thanks!

#

@queen holly I have heard about more issues with the Tado-X devices, especially with sharing them towards other ecosystems. Do you have any other Matter devices to quickly test if Tado is the issue or its a generic issue ?

queen holly
#

I found the issue. I used an ubuntu mini pc with kvm to run haos in a vm. Network setting were somehow corrupted. Instantly worked with a virtual Box vm. So I am using now the virtual Box vm

pulsar steppe