Matter CHIP Error 0x00000032: Timeout

Veldkornet commented 11 months ago

The problem

I am currently using the HomeAssistant SkyConnect with the silabs-multiprotocol add-on Matter add-on to connect to several Matter/Thread enabled devices, however, I do get a notification from Apple Home that the device has been added to HomeAssistant.

A month or two ago, I was able to successfully add 2x Eve Energy plugs as well as 2x Nanoleaf e27 bulbs. Unclear if it's due to recent updates, but I am no longer able to add additional Nanoleaf lights (lightstrips)

I do have 3x AppleTV $k's and 1x HomePod Mini to server as border routers. Additionally, I have added the SkyConnect to the Apple Thread Network:

Basically, I follow the following process:

Plug in Nanoleaf lightstrip
Add Lightstrip to network via Nanoleaf app via MAtter QR code
Update firmware
Add lightstrip to AppleHome via Matter QR code
Add lightstrip to HomeAssistant via Matter QR code --> fails.... although Apple Home Does give a notification that the device has been added to HomeAssistant
On my iPhone, if I check under Settings -> General -> Matter Accessories, if I select the lightstrip I can see that it's connected to two "homes": AppleHome and "4939". (I'm not sure why my HomeAssistant home is called 4939???)

The below is basically what I see on the phone when trying to add it in HomeAssistant:

Image - Step 1 Image - Step 2 Image - Step 3

I did find two other related issues, however these are closed with no real solution. https://github.com/home-assistant/core/issues/103257 https://github.com/home-assistant/core/issues/102951

What version of Home Assistant Core has the issue?

core-2023.12.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

config_entry-matter-621dc959b9530d5db372ed9a44fbcc4a.json.txt

See also the core=matter addon logs: _addon_core_matter_server_logs.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-12-29 10:51:46 core-matter-server chip.CTL[126] ERROR Failed to perform commissioning step 18
2023-12-29 10:51:47 core-matter-server matter_server.server.client_handler[126] ERROR [547630521936] Error handling message: CommandMessage(message_id='c74cb831bf7c48adb44bb5736597f3a5', command='commission_with_code', args={'code': 'MT:EZW01UC112PDBK34R10'})
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
    result = await result
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 167, in commission_with_code
    raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission with code failed for node 38
2023-12-29 10:51:47 core-matter-server chip.EM[126] ERROR Failed to send Solitary ack for MessageCounter:111371594 on exchange 21691i:src/messaging/ExchangeContext.cpp:103: CHIP Error 0x00000002: Connection aborted
2023-12-29 10:54:35 core-matter-server chip.DIS[126] ERROR Timeout waiting for mDNS resolution.
2023-12-29 10:54:49 core-matter-server chip.DIS[126] ERROR OperationalSessionSetup[2:0000000000000006]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout

Additional information

Matter Server (5.0.1
Silicon Labs Multiprotocol (2.3.2)

home-assistant[bot] commented 11 months ago

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `matter` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign matter` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

matter documentation matter source _{^{(message by IssueLinks)}}

asjmcguire commented 11 months ago

What's the firmware version of the light strip? I'm on 3.6.79 and it's buggy, very very buggy. ALL my nanoleaf bulbs have mDNS timeouts. I factory reset the light strip and it refuses to re-add to matter, via Home Assistant or Google Home. I did not have these issues on earlier firmware.

There are no issues with my Onvis socket which uses matter over thread, and responds instantly to mDNS queries.

Veldkornet commented 11 months ago

What's the firmware version of the light strip?

I'm on 3.6.79 and it's buggy, very very buggy. ALL my nanoleaf bulbs have mDNS timeouts. I factory reset the light strip and it refuses to re-add to matter, via Home Assistant or Google Home.

I did not have these issues on earlier firmware.

There are no issues with my Onvis socket which uses matter over thread, and responds instantly to mDNS queries.

All of my Nanoleaf devices, both HomeAssistant paired and non-paired, have firmware 3.5.41.

However, I don't think that there has been any firmware updates since I was able to successfully add the E27 bulbs and now with the non-working ones.

asjmcguire commented 11 months ago

Yeah it's beta firmware, you have to join up to the beta program.

marcelveldt commented 10 months ago

Sorry, but I can not accept this issue report due to the following reasons;

1) You are running Multi-PAN which is not supported yet (and also known to be unstable) 2) We are not yet supporting using the Skyconnect for Thread. Only border routers from apple or Google are considered stable. 3) You have one or more devices from Nanoleaf on your setup, which are VERY unstable.

Please remove the Nanoleaf devices from your setup, remove the SkyConnect from the Thread network and test again. A small hunch on what is going on is the network destabilizing, causing a lot of unwanted packets.

If you can not use a Border router from apple or google, the only way is to use the Thread only firmware on the SkyConnect, which is more stable.

Closing this issue now as you are running an unsupported environment. Please join our discord channel for community support. Thanks!

Veldkornet commented 10 months ago

For what it's worth, I updated to Matter Server 5.0.2 and changed to the Thread only firmware for SkyConnect using the OpenThread Border Router add-on, version 2.4.1.

However, the result is the same.

2024-01-03 21:47:27 core-matter-server matter_server.server.device_controller[127] INFO Starting Matter commissioning with code using Node ID 46.
2024-01-03 21:47:37 core-matter-server matter_server.server.client_handler[127] ERROR [547868411792] Error handling message: CommandMessage(message_id='3b1877b8f29c4360bb13c4a48de0f5bc', command='commission_with_code', args={'code': 'MT:EZW01EQM00H6P81DQ00', 'network_only': True})
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
    result = await result
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 196, in commission_with_code
    raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission with code failed for node 46
2024-01-03 21:47:40 core-matter-server chip.DIS[127] ERROR OperationalSessionSetup[2:0000000000000006]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:119: CHIP Error 0x00000032: Timeout

Additionally, I removed the SkyConnect completely and used only the Apple BR's with Matter add-on, but the result is still exactly the same:

2024-01-04 09:16:55 core-matter-server matter_server.server.device_controller[126] INFO Starting Matter commissioning with code using Node ID 48.
2024-01-04 09:17:04 core-matter-server matter_server.server.client_handler[126] ERROR [548148722448] Error handling message: CommandMessage(message_id='992c7afd875f49ac99be9d4e4c5e6b53', command='commission_with_code', args={'code': 'MT:EZW01ONY16M4-E02Z10', 'network_only': True})
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/client_handler.py", line 188, in _run_handler
    result = await result
             ^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 196, in commission_with_code
    raise NodeCommissionFailed(
matter_server.common.errors.NodeCommissionFailed: Commission with code failed for node 48

Lastly, the Nanoleaf devices all work perfectly from within Apple Home and always respond instantly (both those that I've been able to add via MAtter and those which I can't), so now I've just resorted to creating automations within Apple Home instead as a temporary workaround. The whole point is that I want to add the Nanoleaf devices via Matter to HomeAssistant, so it makes absolutely no sense for me to remove them.... the problems would obviously not exist if the Nanoleaf devices were not there.... because then there would be nothing to add.....

Krusenbaum commented 10 months ago

I have the same issue pairing 2 new EVE energy devices (after already having paired 10 of them).

Pairing via HomePod Mini worked well but when I then try to add them to HA, I get the "ERROR Failed to perform commissioning step 18" error.

Setup:

device: Eve energy matter
via HomePod Mini border router
latest version of HA
SkyConnect running Thread

Krusenbaum commented 10 months ago

What solved the issue for me:

restarted HomePod minis
saw that in the Apple Home App, the device was already added to HA
in Apple Home, removed the device from HA
then re-added the device to HA. Worked the first time.

Veldkornet commented 10 months ago

What solved the issue for me:

restarted HomePod minis

saw that in the Apple Home App, the device was already added to HA

in Apple Home, removed the device from HA

then re-added the device to HA. Worked the first time.

I've tried this as well, no success. Rebooted the entire house, no luck.

Veldkornet commented 10 months ago

Just thought I'd give some feedback to say that I eventually sorted it all out....

The following is what I did:

I read somewhere of a "ghost" device causing issues in the matter add-on, and I saw in my logs that it kept trying to connect to some node.... but it wasn't clear to me which node was what, so I just nuked everything (matter related in HomeAssistant). Removed all the devices from the HomeAssistant in the Apple Home -> Settings -> Matter, also purged and re-installed the Matter add-on (rebooted in between). Start from scratch. The devices were left in the default Apple Home thread network ( I didn't touch that side of things)
Additionally, I have (since logging the initial issue) moved to the OpenThread Border Router add-on, instead of the Multiprotocol add-on
Then, I added the First Eve Energy into HA, bingo! First time was snappy and did everything in one go.
Tried to add the second Eve Energy... fail... fail.... fail.... fail...
Tried some Nanoleaf items... one wokren, then fail.. fail... fail...
At this point I decided to try something different. I turn off all Thread Border routers and only left 1x on (AppleTV or HomePod etc) that was closest to the device itself. This allowed me to successfully add the device. After doing this, I turned the Border Routers off and on depending on where the device was located and eventually got all of my devices added! Woohoo!

Some Notes:

I should also note that, at the time, I was just scanning the QR code on the device again when adding it to HomeAssistant. I only saw in the Matter livestream that I was actually supposed to copy the pairing code.... I tried this as a test and I see that the flow is a bit different, there's no "finding device" phase from the Apple Home pop-up, it just goes to setting-up immediately. Anyway, I'll try this route when I get more Matter over Thread devices.
The OTBR add-on has since been updated to use TREL. I would assume that this would also improve things, but I haven't tested that yet when adding devices of course.
I tried so many times before it all worked.... 39 times to be exact before everything was added, as now according to the matter add-on, I have nodes: 01, 10, 11, 21, 27, 28, 39. (It annoys me a bit that the node numbers are now out of wack, just like in zwave, but at least it works). I also noted down which node numbers where which device, in case I ever need to troubleshoot something from the Matter logs, at least I know which node is what.

Everything works perfect now, via AppleHome or Home Assistant, all the lights and switches work perfectly and snappy!

home-assistant / core