Matter Server 9.1.1 crashes immediately on start

Configuration Matter/Thread
,
1

– /usr/local/bin/node exits with code 1 (Raspberry Pi 5 + HAOS 18.2)

Description:
Matter Server 9.1.1 fails to start on Raspberry Pi 5 running Home Assistant OS 18.2. The service exits immediately with code 1 right after detecting the network interface.

What I already tried:
• Fresh install of Matter Server (with and without deleting data)
• Disabled Watchdog
• Beta mode (fails to install from npm due to broken Debian keyring, then falls back to the same crash)
• Restored a full backup from 2 weeks ago → same error
• Confirmed IPv6 is set to Automatic on end0
• System has 8 GB RAM with only ~1 GB used (plenty of free memory)

System info:

image
image1152×1536 403 KB

• Home Assistant OS: 18.2 (aarch64 / raspberrypi5-64)
• Home Assistant Core: 2026.8.1
• Supervisor: 2026.07.5
• Matter Server: 9.1.1
• Hardware: Raspberry Pi 5 (8 GB)
The crash happens even on a completely clean install, so it appears to be an issue with the Node.js binary inside the aarch64 Matter Server 9.1.1 image on HAOS 18.2.

Log (consistent every time):

[xx:xx:xx] INFO: Starting Matter Server…
[xx:xx:xx] INFO: Time sync ‘auto’: host NTP is synchronized, enabling time sync.
[xx:xx:xx] INFO: Using ‘end0’ as primary network interface.
./run: line 219: /usr/local/bin/node: Success
[xx:xx:xx] WARNING: matter-server service exited with code 1 (by signal 0).

2

image
image1320×752 37.4 KB

3

Strange name of interface you have ?
You saying, you starting frech.
Do you have any other interfaces another than the builtin in the RPI5 ?

This text is from my working RPI3 with only 1GB running Matter

[08:14:54] INFO: Starting Matter Server...
[08:14:54] INFO: Time sync 'auto': host NTP is synchronized, enabling time sync.
[08:14:55] INFO: Using 'enu1u1u1' as primary network interface.

You can also set what nic that the app and integration should use:
Settings
Network
Network Adapter

4

Thanks, end0 is just the b-i eth on the RP5 (HAOS18 naming). There are no other network int.. I think it is a .js bin error inside the aarch64.. but Im just simple guy haha

5

image
image1567×649 45.8 KB

*added beta mode fail.

6

Seems like a problem worthy of filing an issue on.

7

How about IPV6, have you enable it in HA (enable it on the nic)?

image
image606×536 20.2 KB