Matter integration is down - entities are still not working

[Flashshad0w]

The problem

I think it was the last core-update from friday last week: Matter entities are still listed, but grey and not working via HA.

What version of Home Assistant Core has the issue?

System Information version | core-2024.10.4 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.4 os_name | Linux os_version | 6.6.31-haos-raspi arch | aarch64 timezone | Europe/Berlin config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.1 Stage | running Available Repositories | 1451 Downloaded Repositories | 1

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 13.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.10.3 agent_version | 1.6.0 docker_version | 27.2.0 disk_total | 27.5 GB disk_used | 7.1 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | board | rpi4-64 supervisor_api | ok version_api | ok installed_addons | Terminal & SSH (9.15.0), AdGuard Home (5.1.4), Advanced SSH & Web Terminal (19.0.0), File editor (5.8.0), deCONZ (7.0.0), motionEye (0.21.0), Matter Server (6.6.0)

Dashboards

dashboards | 3 -- | -- resources | 0 views | 5 mode | storage

Recorder

oldest_recorder_run | 18. Oktober 2024 um 17:08 -- | -- current_recorder_run | 27. Oktober 2024 um 16:54 estimated_db_size | 166.36 MiB database_engine | sqlite database_version | 3.45.3

What was the last working version of Home Assistant Core?

core_2024.10.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter-Beta 6.5.1

Link to integration documentation on our website

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

Diagnostics information

config_entry-matter-01J5THFEFHS34Y39HAK64JE0WX(1).json

Example YAML snippet

I don´t think it´s an YAML issue and i don´t made any snippeds by now.

Anything in the logs that might be useful for us?

Tell me - i want to help if i could.

Additional information

No response

[home-assistant[bot]]

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)}}

[marcelveldt]

Question 1 Can you go to Settings --> Addons --> Matter Server --> Open Web UI ? Check if the Matter nodes are still there and available. You could even make a screenshot and post it here if in doubt.

Question 2 Can you check the Home Assistant logs for errors about the Matter integration. If you're in doubt, just attach the logfile here (quickly scan it for personal info please).

[ChrisClever-ger]

Here you are. All the devices are offline

[BradHinegardner]

I'm having the same issue here (I see the same behavior as the above comment) . The log within Matter Server shows this error repeatedly:

2024-10-30 04:54:01.334 (MainThread) ERROR [matter_server.server] Error doing task: Exception in callback MatterDeviceController._on_mdns_operational_node_state('D8A914DA9730...r._tcp.local.', <ServiceState...ge.Updated: 3>)
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/asyncio/events.py", line 84, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/local/lib/python3.11/site-packages/matter_server/server/device_controller.py", line 1505, in _on_mdns_operational_node_state
    node_id = int(name.split("-")[1].split(".")[0], 16)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: invalid literal for int() with base 16: '000000000000000A (3)'

[drvup]

Same here. Same behavior of the nodes, being not reachable. The only thing I can see on the matter server log is the following:

CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:416: OS Error 0x02000065: Network is unreachable
2024-10-30 22:13:37.889 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 507 ms, for event type 2
2024-10-30 22:13:37.908 (MainThread) 

[ChrisClever-ger]

Seems to be a problem with my fritz box. I have one Matter-Plug still working over an DLAN Wifi 2,4GHz network instead. The others are all connected via fritzbox.