Can't update HA Core updates when HA is plugged into a switch

Configuration
1

I am running HA on a RPi 5 and have been having troubles with the last several releases of HA Core updates. However, I’ve seen other posts so I know I’m not alone.

Sometimes a full shutdown and restart of HA is required before a core update will work. Other times that doesn’t help.

However, with the last two or three updates I found that if I unplug the RPi from my switch and plug it directly into my hardware firewall the core update will work. I don’t understand this - but it is the case. Also, either way, the RPi gets assigned the same static IP address.

When plugged into my switch HA can do all other types of updates, for example with ESPHome or other services that need updating - its only the core update that is causing issues.

Any ideas?

2

Do you use VLANs?

3

Do you use VLANs? No.

4

Where is your DNS server located?

In the hardware firewall or on another device connected to the switch?

5

Is your switch also routing?

Post the system error log [appropriately formatted using the forum </> option] for clues.

6

DNS server is managed by the hardware firewall (OPNSense - Unbound DNS).

7

I no longer have the logs form when the update last ran

8

@IOT7712
I just had the same thing happen when I tried to do a matter update.
Basically, it immediately knocked the switch offline and I have to power recycle the switch to get network access back to the RPi running Home Assistant.

Also, the update window which normally shows the installation progress doesn’t do that (it stays at 0%).

here is the log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2026-01-28 12:28:18.778 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.779 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.779 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ha_ecowitt_iot which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.780 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.780 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.781 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.781 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.782 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ha_ecowitt_iot which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.782 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:18.783 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-01-28 12:28:22.549 WARNING (MainThread) [custom_components.localtuya.common] [506...7c5] Disconnected - waiting for discovery broadcast
2026-01-28 12:28:29.431 WARNING (MainThread) [custom_components.tapo_control] Home Assistant is running on HTTPS or it was not able to detect base_url schema. Disabling webhooks.
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
E0000 00:00:1769621309.671001      67 alts_credentials.cc:93] ALTS creds ignored. Not running on GCP and untrusted ALTS is not enabled.
2026-01-28 12:29:29.918 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for esphome-sonoff-ch4 @ 192.168.2.196: Timeout while connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.2.196', port=6053))] (TimeoutAPIError)
E0000 00:00:1769621479.848547      67 alts_credentials.cc:93] ALTS creds ignored. Not running on GCP and untrusted ALTS is not enabled.
2026-01-28 12:31:24.637 WARNING (MainThread) [homeassistant.components.go2rtc.server] 12:31:24.637 ERR github.com/AlexxIT/go2rtc/internal/mjpeg/init.go:49 > error="streams: read tcp 192.168.1.173:35652->35.201.72.176:443: i/o timeout, exec/rtsp\n[in#0 @ 0x7f8ec12b00] Error opening input: Invalid data found when processing input\nError opening input file rtsp://127.0.0.1:18554/camera.front_door?audio&source=ffmpeg:camera.front_door%23audio%3Dopus%23query%3Dlog_level%3Ddebug&log_level=debug.\nError opening input files: Invalid data found when processing input\n"
2026-01-28 12:31:34.869 WARNING (MainThread) [homeassistant.components.go2rtc.server] 12:31:34.869 ERR github.com/AlexxIT/go2rtc/internal/mjpeg/init.go:49 > error="streams: read tcp 192.168.1.173:53602->35.201.72.176:443: i/o timeout, exec/rtsp\n[in#0 @ 0x7fa5c12b00] Error opening input: Invalid data found when processing input\nError opening input file rtsp://127.0.0.1:18554/camera.front_door?audio&source=ffmpeg:camera.front_door%23audio%3Dopus%23query%3Dlog_level%3Ddebug&log_level=debug.\nError opening input files: Invalid data found when processing input\n"
2026-01-28 12:31:46.566 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.19 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.19:9999: 
2026-01-28 12:31:46.569 ERROR (MainThread) [homeassistant.components.ipp.coordinator] Error fetching ipp data: Invalid response from API: Timeout occurred while connecting to IPP server.
2026-01-28 12:31:46.641 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.18 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.18:9999: 
2026-01-28 12:31:46.770 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.165 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.165:9999: 
2026-01-28 12:31:46.827 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.105 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.105:9999: 
2026-01-28 12:31:49.645 ERROR (MainThread) [homeassistant.components.brother.coordinator] Timeout fetching brother data
2026-01-28 12:31:52.475 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.14 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.14:9999: 
2026-01-28 12:31:52.562 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.31 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.31:9999: 
2026-01-28 12:31:52.565 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.188 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.188:9999: 
2026-01-28 12:31:52.627 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.10 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.10:9999: 
2026-01-28 12:31:52.670 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.21 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.21:9999: 
2026-01-28 12:31:52.703 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.104 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.104:9999: 
2026-01-28 12:31:52.717 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.181 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.181:9999: 
2026-01-28 12:31:52.790 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.15 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.15:9999: 
2026-01-28 12:31:52.793 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.205 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.205:9999: 
2026-01-28 12:31:52.816 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.13 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.13:9999: 
2026-01-28 12:31:52.824 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.2.106 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.2.106:9999: 
2026-01-28 12:32:30.786 ERROR (MainThread) [homeassistant.components.tile] Error fetching Rob's Galaxy S10+ data: Error while retrieving data: Error requesting data from tiles/p!d4054e434113d2314a35ebdccf62eb79: Cannot connect to host production.tile-api.com:443 ssl:default [Timeout while contacting DNS servers]
2026-01-28 12:32:30.787 ERROR (MainThread) [homeassistant.components.tile] Error fetching Camera data: Error while retrieving data: Error requesting data from tiles/54127a3f1174b3c6: Cannot connect to host production.tile-api.com:443 ssl:default [Timeout while contacting DNS servers]
2026-01-28 12:32:30.787 ERROR (MainThread) [homeassistant.components.tile] Error fetching Keys data: Error while retrieving data: Error requesting data from tiles/a532d338d4186cfa: Cannot connect to host production.tile-api.com:443 ssl:default [Timeout while contacting DNS servers]
2026-01-28 12:33:03.132 ERROR (MainThread) [custom_components.tapo_control] Failed to sync time for 192.168.2.216: Request to http://192.168.2.216:2020/onvif/device_service timed out
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/onvif/zeep_aiohttp.py", line 160, in _post_internal
    content = await response.read()
              ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/client_reqrep.py", line 693, in read
    self._body = await self.content.read()
                 ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/streams.py", line 442, in read
    block = await self.readany()
            ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/streams.py", line 464, in readany
    await self._wait("readany")
  File "/usr/local/lib/python3.13/site-packages/aiohttp/streams.py", line 371, in _wait
    await waiter
aiohttp.client_exceptions.SocketTimeoutError: Timeout on reading data from socket

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/tapo_control/__init__.py", line 664, in async_update_data
    await syncTime(hass, entry.entry_id)
  File "/config/custom_components/tapo_control/utils.py", line 1776, in syncTime
    await device_mgmt.SetSystemDateAndTime(time_params)
  File "/usr/local/lib/python3.13/site-packages/zeep/proxy.py", line 64, in __call__
    return await self._proxy._binding.send_async(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/zeep/wsdl/bindings/soap.py", line 156, in send_async
    response = await client.transport.post_xml(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        options["address"], envelope, http_headers
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/onvif/wrappers.py", line 52, in _async_wrap_connection_error_retry
    return await func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/onvif/client.py", line 142, in post_xml
    return await super().post_xml(address, envelope, headers)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/onvif/zeep_aiohttp.py", line 209, in post_xml
    response, content = await self._post_internal(address, message, headers)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/onvif/zeep_aiohttp.py", line 173, in _post_internal
    raise TimeoutError(f"Request to {address} timed out") from exc
TimeoutError: Request to http://192.168.2.216:2020/onvif/device_service timed out
2026-01-28 12:33:20.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Dryer
2026-01-28 12:33:36.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Oven
2026-01-28 12:33:52.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Top Load Washer
2026-01-28 12:34:08.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Dryer
2026-01-28 12:34:10.396 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Network connection error - Device: Oven
2026-01-28 12:34:36.681 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547333132736] Error during service call to update.install: Error updating Matter Server: An unknown error occurred with addon core_matter_server. Check supervisor logs for details (check with 'ha supervisor logs')
2026-01-28 12:34:37.658 WARNING (MainThread) [custom_components.localtuya.common] [506...7c5] Disconnected - waiting for discovery broadcast
2026-01-28 12:34:38.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Top Load Washer
2026-01-28 12:34:40.668 WARNING (MainThread) [zeroconf] Error with socket 16 (('192.168.1.173', 5353))): [Errno 101] Network unreachable
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/asyncio/selector_events.py", line 1276, in sendto
    self._sock.sendto(data, addr)
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
OSError: [Errno 101] Network unreachable
2026-01-28 12:34:41.610 ERROR (Thread-13) [pychromecast.socket_client] [Living Room speaker(192.168.2.72):8009] Failed to connect to service MDNSServiceInfo(name='Google-Home-Mini-70399e3ea51a9e137a2a44d67323ba25._googlecast._tcp.local.'), retrying in 5.0s
2026-01-28 12:34:43.273 ERROR (Thread-11) [pychromecast.socket_client] [Basement speakers(192.168.2.73):32229] Failed to connect to service HostServiceInfo(host='192.168.2.73', port=32229), retrying in 5.0s
2026-01-28 12:34:43.670 ERROR (Thread-7) [pychromecast.socket_client] [Rob's bedroom display(192.168.2.70):8009] Failed to connect to service HostServiceInfo(host='192.168.2.70', port=8009), retrying in 5.0s
2026-01-28 12:34:44.120 ERROR (Thread-10) [pychromecast.socket_client] [Basement speakers(192.168.2.73):32109] Failed to connect to service HostServiceInfo(host='192.168.2.73', port=32109), retrying in 5.0s
2026-01-28 12:34:44.845 ERROR (Thread-12) [pychromecast.socket_client] [Rob's office display(192.168.2.71):8009] Failed to connect to service HostServiceInfo(host='192.168.2.71', port=8009), retrying in 5.0s
2026-01-28 12:34:45.225 ERROR (Thread-8) [pychromecast.socket_client] [Speaker left(192.168.2.73):8009] Failed to connect to service HostServiceInfo(host='192.168.2.73', port=8009), retrying in 5.0s
2026-01-28 12:34:54.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Dryer
2026-01-28 12:35:10.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Oven
2026-01-28 12:35:21.409 WARNING (MainThread) [custom_components.localtuya.common] [506...7c5] Failed to connect to 192.168.2.54: [Errno 101] Network unreachable
2026-01-28 12:35:22.237 WARNING (MainThread) [homeassistant.components.dlna_dms] Failed connecting to recently alive device at http://[fe80::218:ddff:fe0a:a5cf%2]:80/dms/device.xml: UpnpConnectionError("ClientConnectorError(ConnectionKey(host='fe80::218:ddff:fe0a:a5cf', port=80, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(22, 'Invalid argument'))", None)
2026-01-28 12:35:23.365 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546931673824] Rob_Latour from 192.168.1.10 (Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/6.9.3 Chrome/130.0.0.0 Safari/537.36): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2026-01-28 12:35:23.366 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [546934690560] Rob_Latour from 192.168.1.10 (Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/6.9.3 Chrome/130.0.0.0 Safari/537.36): Disconnected: Received error message during command phase: No PONG received after 27.5 seconds
2026-01-28 12:35:25.365 ERROR (MainThread) [homeassistant.components.matter] Unexpected exception: Connection failed.
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/matter/__init__.py", line 186, in _client_listen
    await matter_client.start_listening(init_ready)
  File "/usr/local/lib/python3.13/site-packages/matter_server/client/client.py", line 646, in start_listening
    msg = await self.connection.receive_message_or_raise()
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/matter_server/client/connection.py", line 125, in receive_message_or_raise
    raise ConnectionFailed
matter_server.client.exceptions.ConnectionFailed: Connection failed.
2026-01-28 12:35:26.365 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Top Load Washer
2026-01-28 12:35:27.592 ERROR (Thread-3) [websocket] Connection timed out - goodbye
2026-01-28 12:35:27.593 ERROR (Thread-3) [websocket] error from callback <bound method Listener.on_close of <PushBulletNotificationProvider(Thread-3, started daemon 546573270120)>>: Listener.on_close() takes 2 positional arguments but 4 were given
E0000 00:00:1769621730.260614      67 alts_credentials.cc:93] ALTS creds ignored. Not running on GCP and untrusted ALTS is not enabled.
2026-01-28 12:35:42.364 WARNING (MainThread) [custom_components.smartthinq_sensors.wideq.device] Connection to ThinQ failed. Timeout error - Device: Dryer
2026-01-28 12:36:08.042 WARNING (MainThread) [homeassistant.components.go2rtc.server] 12:36:08.041 ERR github.com/AlexxIT/go2rtc/internal/mjpeg/init.go:49 > error="streams: read tcp 192.168.1.173:34536->35.201.72.176:443: i/o timeout, exec/rtsp\n[in#0 @ 0x7f8bc12b00] Error opening input: Invalid data found when processing input\nError opening input file rtsp://127.0.0.1:18554/camera.front_door?audio&source=ffmpeg:camera.front_door%23audio%3Dopus%23query%3Dlog_level%3Ddebug&log_level=debug.\nError opening input files: Invalid data found when processing input\n"
9

ok - I found a fix / work around (or at least my handy dandy MS 365 Copilot AI did):

Basically it said it was a known issue with some unmanaged switches - more specifically:

The likely causes:
1) 2.5GbE NIC on the Raspberry Pi 5 causing a renegotiation bug
The Pi 5 uses a Broadcom BCM2712 with a 2.5GbE PHY.
Some unmanaged switches — and TRENDnet is known for this — experience:

Link renegotiation storms
Autonegotiation lockups
Flow‑control loops
Pause frame floods
Sudden MAC address reannounce behavior causing a switch panic

This happens most commonly during software restarts that momentarily drop link.
Your symptoms perfectly match this.
2) Multicast burst during HA/Matter restart overwhelming an unmanaged switch
Home Assistant Core and Matter use:

mDNS (224.0.0.251:5353)
SSDP (239.255.255.250:1900)
CoAP/multicast for Matter
IPv6 NDP multicast
Avahi re‑announcements of services

Unmanaged switches sometimes choke on large multicast bursts, especially combined with link renegotiation.
TRENDnet devices in particular have had several reports of:

“Switch locks until power cycle”
“Port goes dead after multicast storm”
“Crash triggered by Bonjour/mDNS floods”

3) Power draw or board reset NOT the issue

In anycase it went on to offer me some debugging / fix options.

One option was to put a cheap 1GB switch in between my current switch and the RPi.

The second option, which I tested and it worked fine, was to turn of IPV6 for Home Assistant.

The AI didn’t give me the right instruction for that, but they are:

goto HA → Setttings → System → Network → Conigure Network Interfaces → under the end0 tab (as I’m using an ethernet connection) - clicked the down arrow beside IPv6 → checked ‘Disabled’ → Save.

Restarted HA

Matter update worked fine.

10

And how about Core Update ?

Broadcasts/Multicast/Discovery Issues is what i see, but is this “only” a problem for your Managed Switch ?
Matter needs IpV6, so maybe this is not what you want to disable in HA ?
Maybe disabled this in Your Router ?

1 Like
11

@boheme61

(just to clarify, my switch is unmanaged)

Also, unfortunately, I won’t know about if this works for a Core update or not until the next one is released and I try to update to it.

However, when that happens, I will post back here with my results.

12

@bohem61

re:

Matter needs IpV6, so maybe this is not what you want to disable in HA ?

Given this error only happens when I update Matter (or the Core) I have re-enabled IPv6 given you said Matter uses it.

Also, I noticed when I set it back on, there was a spot for me to enter my IPv6 address of my DNS server. I believe before it might have been blank, so that may have been part of the problem too. In any case, I filled that in and enable IPv6 again.

Looking forward to the next Core or Matter update to see if that made a difference.

Will post back here with my results.

13

ahh ok, i confused it with your DNS, however soon comes a new core update :slight_smile:

1 Like
14

Here is an update (so far):

HA Core Update for February (26.02) came out.

With IPv6 Enabled in HA - System - Networking:
I tried to apply the Core update.
However, immediately my switch locked out.

Power recycled the switch (and restarted HA):
disabled IPv6.
Tried to apply the Core update again,
immediately the switch locked out.

As the system was restarting, I set up a cheap 1GB switch between my RPi running HA and my 2.5GB switch that keeps locking up when I do these updates.

However, to my surprise, when the network came back to life HA was in the process of restarting and the Core update had been applied.

I have re-enabled IPv6 on HA and when the next core update comes out I will post back here to let you know if it can be updated without all these problems now that I have the 1GB switch in between the RPi and the 2.5GB switch.

15

@boheme61

So this will hopefully be my final update.

HA Core 2026.2.1 came out today.

With my system setup as follows:
HA running on a Raspberry Pi with IPv4 and IPv6 enabled
connecting to a cheap 1GB switch connecting to
my problematic 2.5GB switch (a Trendnet TEG-S5091)

the update ran fine without knocking out my 2.5GB switch.

So the solution / workaround, appears to be, to put the cheap 1GB switch between the RPi and the 2.5GB switch.

Hope this will be of help to others.

1 Like