Matter server beta not starting during internet outage

[juliodee]

Describe the issue you are experiencing

I enabled matter.js beta (to fix IKEA firmware otherwise not updating). During a recent unplanned internet outage and restarting Home Assistant Green, I found all my Matter devices disabled. Checking the log I noticed the Matter server stalled at wanting to install the latest matter server from npm.

Effectively:
[07:34:20] INFO: Installing latest matter-server from npm...
npm error code ETIMEDOUT
...
[07:35:43] ERROR: Failed to install Matter Server from npm. Aborting startup.

I originally posted as an issue at https://github.com/matter-js/matterjs-server/issues/678#issue-4505740446. @Apollon77 kindly replied and advised this is likely because of the way beta works, hence reposting here.

The issue was that I lost access to all my locally based Matter devices because I didn’t have internet (which feels a bit ironic 😊). In this situation I would have expected the system to continue using the most recently installed beta.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which app are you reporting an issue with?

Matter Server

What is the version of the app?

8.5 (beta enabled)

Steps to reproduce the issue

1. Matter Server App - Enable "Use the latest beta version"
2. Start server and once installed, Stop server
3. Disconnect internet
4. Start Matter Server

System Health information

System Information

version	core-2026.5.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	aarch64
user	root
virtualenv	false
python_version	3.14.2
os_name	Linux
os_version	6.12.85-haos
arch	aarch64
timezone	Australia/Sydney
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4999
Installed Version	2.0.5
Stage	running
Available Repositories	3126
Downloaded Repositories	34

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 17.3
update_channel	stable
supervisor_version	supervisor-2026.05.0
agent_version	1.8.1
docker_version	29.3.1
disk_total	28.0 GB
disk_used	13.7 GB
nameservers	192.168.69.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	green
supervisor_api	ok
version_api	ok
installed_addons	Matter Server (8.5.0), Mosquitto broker (7.1.0), MQTT Explorer (browser-1.0.3), Filebrowser (2.63.5), Zigbee2MQTT (2.10.1-1), OpenThread Border Router (2.16.8), Cloudflared (7.0.7), ESPHome Device Builder (2026.5.0), Advanced SSH & Web Terminal (23.0.9), Node-RED (21.0.10)

Dashboards

dashboards	7
resources	22
views	12
mode	storage

Network Configuration

adapters	lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), vethd0aa429 (disabled), veth0e05b44 (disabled), veth532b0d3 (disabled), veth1c8c5b7 (disabled), veth7b3fd21 (disabled), veth0ffc2de (disabled), wpan0 (disabled), veth12de98b (disabled), vethf09636c (disabled), veth5f3573e (disabled)
ipv4_addresses	lo (127.0.0.1/8), end0 (192.168.69.99/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vethd0aa429 (), veth0e05b44 (), veth532b0d3 (), veth1c8c5b7 (), veth7b3fd21 (), veth0ffc2de (), wpan0 (), veth12de98b (), vethf09636c (), veth5f3573e ()
ipv6_addresses	lo (::1/128), end0 (fd0a:5c1d:e2f8:3b47:d8ec:d617:377f:977f/64, fe80::9925:c16e:3659:9c8b/64), docker0 (fe80::348c:5cff:feac:1bf6/64), hassio (fd0c:ac1e:2100::1/48, fe80::501c:73ff:fe25:bd1b/64), vethd0aa429 (fe80::3034:46ff:feee:f547/64), veth0e05b44 (fe80::478:5dff:fece:88a2/64), veth532b0d3 (fe80::1ce3:62ff:feb3:11e7/64), veth1c8c5b7 (fe80::b02e:d9ff:fea6:7349/64), veth7b3fd21 (fe80::8e0:74ff:fecb:4cea/64), veth0ffc2de (fe80::7428:3ff:fedb:97c0/64), wpan0 (fddd:c8c1:74d2:fa0d:0:ff:fe00:fc11/64, fd1b:e245:f84a:1:c4e9:6f89:c446:1449/64, fddd:c8c1:74d2:fa0d:0:ff:fe00:fc38/64, fddd:c8c1:74d2:fa0d:0:ff:fe00:fc10/64, fddd:c8c1:74d2:fa0d:0:ff:fe00:ac00/64, fddd:c8c1:74d2:fa0d:40cb:f240:7b87:db1b/64, fe80::4835:1763:27fb:ceaa/64), veth12de98b (fe80::5091:46ff:fef6:54f/64), vethf09636c (fe80::ec57:65ff:fea5:20d4/64), veth5f3573e (fe80::ef:1cff:fe14:def8/64)
announce_addresses	192.168.69.99, fd0a:5c1d:e2f8:3b47:d8ec:d617:377f:977f, fe80::9925:c16e:3659:9c8b

Recorder

oldest_recorder_run	14 May 2026 at 3:46 pm
current_recorder_run	24 May 2026 at 7:04 am
estimated_db_size	553.74 MiB
database_engine	sqlite
database_version	3.49.2

Anything in the Supervisor logs that might be useful for us?

Anything in the app logs that might be useful for us?

Additional information

No response

[RaniDrama82]

I had the exact same issue. We had a power outage in the area that knocked out the ISP. Everything was working fine except for the matter server. My z-wave network, zigbee, and all was operational. I received a 502 or 503 error when trying to check the matter server.

[liangjian199]

neither！

[agners]

Yeah this is an unfortunate consequence of the current beta phase, which uses npm to install matter.js. It will soon be promoted to stable, and with that matter.js will be preinstalled. Then a app restart will no longer be problematic.