ZimaOS Web UI and Server Screen Network Status Inconsistency (Despite Wi-Fi Being Connected and Static IP Acquired)

noktanyus · June 15, 2025, 11:14am

Hello ZimaOS Community,

I recently completed my ZimaOS setup and am now looking for help with a network status display issue I’m encountering. Although my device is connected to the internet via Wi-Fi, both the web interface and the physical server screen are showing incorrect or incomplete network status information.

Problem Summary:

My ZimaOS is successfully connected to my Wi-Fi network and has correctly obtained the static IP address I set: 192.168.1.50. I’ve confirmed this via SSH using nmcli device and ip addr show wlan0 commands. The nmcli device output clearly shows wlan0 as connected.

However, on the physical ZimaOS server screen, I still see the warning “Searching for network address”.

When accessing the web interface (via http://192.168.1.50 in my browser), the situation is even stranger:

On the “Settings > Network” page, the Wi-Fi (wlan0) section is not showing as green/active as it should be.
Furthermore, when I try to change the IP address settings in the web UI, even after switching from DHCP to manual and entering 192.168.1.50, these changes don’t seem to be correctly reflected or saved in the interface.
Currently, only “Virtual Network (Remote)” (ztz4o4q7t4) is actively listed on the “Network” page; the status of my Wi-Fi connection is still not being accurately displayed in the web UI.

Steps I’ve Taken (Troubleshooting Attempts):

Wi-Fi Connection: I connected to my Wi-Fi network via the ZimaOS interface. (The SSID is visible from my SSH outputs, for example, it might be “MyHomeWiFi”.)
Static IP Assignment: I assigned the static IP address 192.168.1.50, subnet mask 255.255.255.0, and gateway/DNS 192.168.1.1 via the interface. I also repeated this process via SSH using nmcli connection modify commands to ensure the static IP is persistent.
Ethernet Cable: The Ethernet cable has been physically disconnected; the device is exclusively accessing the internet via Wi-Fi.
System Reboots: I’ve rebooted the system multiple times.
Service Restarts (via SSH):

sudo systemctl restart NetworkManager
sudo systemctl restart zimaos-gateway.service
sudo systemctl restart zimaos.service After running these commands, I cleared my browser cache and refreshed the interface, but the situation remained unchanged.

System Update Attempt: Since the apt command was not found, I used apk update and apk upgrade commands. The update was successful, and I rebooted the system, but the incorrect display in the interface persists.

My Expectation:

I expect the ZimaOS web interface and the physical server screen to accurately reflect the current network status reported by NetworkManager (showing that Wi-Fi is connected and has acquired the 192.168.1.50 IP address). Is this a known UI bug, or is there a deeper issue related to the system’s network detection?

I would be grateful for any help, guidance, or shared experiences from anyone who might have encountered a similar problem.

Thank you in advance!

Additionally, when checking through the ZimaOS client application, it also fails to recognize the Wi-Fi connection and still believes it’s connected via Ethernet.

Zima-Giorgio · June 16, 2025, 2:43am

For now, ZimaOS does not officially support Wi-Fi.

Abrahamup · January 19, 2026, 9:49pm

Allo, did you solve it? I’m having the same problem, and all my Home Assistant is failing bc of that

gelbuilding · January 19, 2026, 10:30pm

Hi Abrahamup,

Yep I’ve seen this one. In most cases Wi-Fi is actually working fine (you can SSH and access the Web UI), but ZimaOS UI/server screen sometimes don’t report wlan0 correctly - especially when using static/manual IP or when the “Virtual Network (Remote)” interface is enabled.

Important: this UI inconsistency shouldn’t break Home Assistant by itself. If HA is failing, it’s more likely DNS / gateway / route issues rather than the UI display.

Quick checks:

Confirm internet + routing:

ip route
ping -c 4 1.1.1.1
ping -c 4 google.com

Easiest test: temporarily set Wi-Fi back to DHCP, reboot, then test HA again.
If you need maximum stability for HA: use Ethernet (or a Wi-Fi bridge / travel router in bridge mode so ZimaOS sees eth0).

If you paste the output of:

ip route
cat /etc/resolv.conf
docker logs homeassistant --tail=50

I can help pinpoint what’s actually causing HA to fail.

Abrahamup · January 19, 2026, 11:28pm

My problem is that every time I ping 1.1.1.1 or 8.8.8.8 on my ZimaOS, it tells me “Network is unreachable,” even though I’m connected by cable and my Proxmox server isn’t showing any connection errors or anything. This started happening suddenly. My Home Assistant suddenly stopped showing my cameras. The only thing I did differently was to set up HA on a tablet so I could have it on the wall (the tablet is connected via Wi-Fi). Here is a copy and paste of the results of the commands you sent me:

Abrahamup@ZimaOS:~ ➜ $ ip route
10.21.0.0/16 dev br-e5c874ffe22b proto kernel scope link src 10.21.0.1 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
172.18.0.0/16 dev br-4d872ebba84d proto kernel scope link src 172.18.0.1
172.19.0.0/16 dev br-1a77e442593b proto kernel scope link src 172.19.0.1
172.20.0.0/16 dev br-70e3310451d5 proto kernel scope link src 172.20.0.1
172.21.0.0/16 dev br-9bb834e8e5f7 proto kernel scope link src 172.21.0.1
172.22.0.0/16 dev br-9b7371dec537 proto kernel scope link src 172.22.0.1
172.23.0.0/16 dev br-68a13459a7f7 proto kernel scope link src 172.23.0.1
172.24.0.0/16 dev br-0ee41bebb3bf proto kernel scope link src 172.24.0.1
172.25.0.0/16 dev br-855bb47ccb4d proto kernel scope link src 172.25.0.1
172.26.0.0/16 dev br-8c6b6f7f9b76 proto kernel scope link src 172.26.0.1
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

Abrahamup@ZimaOS:~ ➜ $ cat /etc/resolv.conf

Generated by NetworkManager

search lan
nameserver 2603:8080:3200:e0b::1

Abrahamup@ZimaOS:~ ➜ $ sudo docker logs homeassistant --tail=50
2026-01-19 16:52:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=63 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=63, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46990)>
2026-01-19 16:52:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=81 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=81, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44586)>
2026-01-19 16:52:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=82 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=82, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 48599)>
2026-01-19 16:52:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=83 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=83, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 49709)>
2026-01-19 16:52:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=84 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=84, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46355)>
2026-01-19 16:52:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=85 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=85, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44664)>
2026-01-19 16:52:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=86 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=86, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 57096)>
2026-01-19 16:53:48.840 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error ‘ClientConnectorError’
2026-01-19 16:55:09.095 ERROR (MainThread) [metno]
2026-01-19 16:56:29.475 ERROR (MainThread) [metno]
2026-01-19 16:57:49.834 ERROR (MainThread) [metno]
2026-01-19 16:59:09.972 ERROR (MainThread) [metno]
2026-01-19 17:00:30.218 ERROR (MainThread) [metno]
2026-01-19 17:01:50.723 ERROR (MainThread) [metno]
2026-01-19 17:02:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=67 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=67, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46218)>
2026-01-19 17:02:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=70 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=70, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44234)>
2026-01-19 17:02:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=76 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=76, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 57771)>
2026-01-19 17:02:31.530 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=78 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=78, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 39403)>
2026-01-19 17:02:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=79 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=79, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 54512)>
2026-01-19 17:02:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=63 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=63, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46990)>
2026-01-19 17:02:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=81 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=81, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44586)>
2026-01-19 17:02:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=82 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=82, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 48599)>
2026-01-19 17:02:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=83 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=83, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 49709)>
2026-01-19 17:02:31.532 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=84 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=84, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46355)>
2026-01-19 17:02:31.532 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=85 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=85, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44664)>
2026-01-19 17:02:31.532 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=86 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=86, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 57096)>
2026-01-19 17:03:11.052 ERROR (MainThread) [metno]
2026-01-19 17:04:31.164 ERROR (MainThread) [metno]
2026-01-19 17:05:51.557 ERROR (MainThread) [metno]
2026-01-19 17:07:11.871 ERROR (MainThread) [metno]
2026-01-19 17:08:31.925 ERROR (MainThread) [metno]
2026-01-19 17:09:52.354 ERROR (MainThread) [metno]
2026-01-19 17:11:12.740 ERROR (MainThread) [metno]
2026-01-19 17:12:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=67 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=67, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46218)>
2026-01-19 17:12:31.531 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=70 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=70, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44234)>
2026-01-19 17:12:31.532 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=76 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=76, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 57771)>
2026-01-19 17:12:31.532 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=78 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=78, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 39403)>
2026-01-19 17:12:31.532 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=79 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=79, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 54512)>
2026-01-19 17:12:31.533 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=63 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=63, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46990)>
2026-01-19 17:12:31.534 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=81 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=81, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44586)>
2026-01-19 17:12:31.534 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=82 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=82, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 48599)>
2026-01-19 17:12:31.534 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=83 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=83, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 49709)>
2026-01-19 17:12:31.534 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=84 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=84, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 46355)>
2026-01-19 17:12:31.535 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=85 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=85, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 44664)>
2026-01-19 17:12:31.536 ERROR (MainThread) [async_upnp_client.ssdp] Received error: [Errno 101] Network unreachable, transport: <_SelectorDatagramTransport fd=86 read=polling write=<idle, bufsize=0>>, socket: <asyncio.TransportSocket fd=86, family=2, type=2, proto=0, laddr=(‘0.0.0.0’, 57096)>
2026-01-19 17:12:33.086 ERROR (MainThread)
2026-01-19 17:13:53.375 ERROR (MainThread)
2026-01-19 17:15:13.610 ERROR (MainThread)
2026-01-19 17:16:34.019 ERROR (MainThread)
2026-01-19 17:17:54.251 ERROR (MainThread)

gelbuilding · January 19, 2026, 11:45pm

This isn’t the old “UI reporting Wi-Fi wrong” issue - your output shows a real network routing problem.

In your ip route there is no default route (no default via 192.168.1.1 dev eth0/wlan0), so the OS literally has no gateway to reach the internet. That’s why ping to 1.1.1.1 / 8.8.8.8 returns Network is unreachable, and Home Assistant throws the same error.

Also your /etc/resolv.conf only has an IPv6 DNS server, which won’t work if IPv6 routing isn’t up.

Quick fix steps:

Check what interface is actually up and has the LAN IP:

ip a
nmcli device

Restart networking (often restores default route):

sudo systemctl restart NetworkManager
sudo systemctl restart docker

If you paste ip a + nmcli con show, we can tell exactly which connection profile lost the gateway/static settings.

Abrahamup · January 20, 2026, 12:26am

I did all the commands, but it still the same, the main difference is it took like 30 min to be online again, here’s the **ip a:
**
Abrahamup@ZimaOS:~ ➜ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 02:5e:6c:70:9b:27 brd ff:ff:ff:ff:ff:ff
altname enp6s18
inet6 2603:8080:3200:e0b::100b/128 scope global dynamic noprefixroute
valid_lft 604067sec preferred_lft 604067sec
inet6 2603:8080:3200:e0b:d67f:8885:916d:8ab3/64 scope global dynamic noprefixroute
valid_lft 604701sec preferred_lft 604701sec
inet6 fd00:90d3:cfea:a71b:ba63:5bb1:2b65:e5b4/64 scope global dynamic noprefixroute
valid_lft 604701sec preferred_lft 604701sec
inet6 fe80::8745:1918:50fc:3399/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:09:d3:c0 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
4: br-68a13459a7f7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:d9:9e:48:dd brd ff:ff:ff:ff:ff:ff
inet 172.23.0.1/16 brd 172.23.255.255 scope global br-68a13459a7f7
valid_lft forever preferred_lft forever
inet6 fe80::42:d9ff:fe9e:48dd/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
5: br-70e3310451d5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:be:29:de:af brd ff:ff:ff:ff:ff:ff
inet 172.20.0.1/16 brd 172.20.255.255 scope global br-70e3310451d5
valid_lft forever preferred_lft forever
inet6 fe80::42:beff:fe29:deaf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
6: br-855bb47ccb4d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:f1:4c:22:cb brd ff:ff:ff:ff:ff:ff
inet 172.25.0.1/16 brd 172.25.255.255 scope global br-855bb47ccb4d
valid_lft forever preferred_lft forever
inet6 fe80::42:f1ff:fe4c:22cb/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
7: br-9bb834e8e5f7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:f8:ae:93:37 brd ff:ff:ff:ff:ff:ff
inet 172.21.0.1/16 brd 172.21.255.255 scope global br-9bb834e8e5f7
valid_lft forever preferred_lft forever
inet6 fe80::42:f8ff:feae:9337/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
8: br-e5c874ffe22b: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:46:03:9c:07 brd ff:ff:ff:ff:ff:ff
inet 10.21.0.1/16 brd 10.21.255.255 scope global br-e5c874ffe22b
valid_lft forever preferred_lft forever
9: br-0ee41bebb3bf: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:df:61:e3:f0 brd ff:ff:ff:ff:ff:ff
inet 172.24.0.1/16 brd 172.24.255.255 scope global br-0ee41bebb3bf
valid_lft forever preferred_lft forever
inet6 fe80::42:dfff:fe61:e3f0/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
10: br-1a77e442593b: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:41:a8:70:ab brd ff:ff:ff:ff:ff:ff
inet 172.19.0.1/16 brd 172.19.255.255 scope global br-1a77e442593b
valid_lft forever preferred_lft forever
inet6 fe80::42:41ff:fea8:70ab/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
11: br-4d872ebba84d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:a6:20:6a:c0 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global br-4d872ebba84d
valid_lft forever preferred_lft forever
inet6 fe80::42:a6ff:fe20:6ac0/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
12: br-8c6b6f7f9b76: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:32:fc:c2:47 brd ff:ff:ff:ff:ff:ff
inet 172.26.0.1/16 brd 172.26.255.255 scope global br-8c6b6f7f9b76
valid_lft forever preferred_lft forever
inet6 fe80::42:32ff:fefc:c247/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
13: br-9b7371dec537: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:93:17:3b:10 brd ff:ff:ff:ff:ff:ff
inet 172.22.0.1/16 brd 172.22.255.255 scope global br-9b7371dec537
valid_lft forever preferred_lft forever
inet6 fe80::42:93ff:fe17:3b10/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
14: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:d4:28:15:ca brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fd00:dead:beef::1/48 scope global nodad
valid_lft forever preferred_lft forever
inet6 fe80::42:d4ff:fe28:15ca/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
20: vethb981af3@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-4d872ebba84d state UP group default
link/ether c2:7f:35:17:10:7d brd ff:ff:ff:ff:ff:ff link-netnsid 2
inet6 fe80::c07f:35ff:fe17:107d/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
22: veth53959a2@if21: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-4d872ebba84d state UP group default
link/ether 96:9b:da:98:1f:d4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::949b:daff:fe98:1fd4/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
24: veth288ff7c@if23: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-4d872ebba84d state UP group default
link/ether ca:34:55:44:41:dc brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::c834:55ff:fe44:41dc/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
26: veth481c01d@if25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-4d872ebba84d state UP group default
link/ether 9a:ac:e0:9b:78:a1 brd ff:ff:ff:ff:ff:ff link-netnsid 3
inet6 fe80::98ac:e0ff:fe9b:78a1/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
28: veth6fc9e8d@if27: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-70e3310451d5 state UP group default
link/ether 7a:fa:2b:0e:ff:2c brd ff:ff:ff:ff:ff:ff link-netnsid 4
inet6 fe80::78fa:2bff:fe0e:ff2c/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
30: veth2b0fc9f@if29: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-70e3310451d5 state UP group default
link/ether 12:22:b7:75:78:29 brd ff:ff:ff:ff:ff:ff link-netnsid 5
inet6 fe80::1022:b7ff:fe75:7829/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
32: veth9f0f994@if31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-70e3310451d5 state UP group default
link/ether 86:7c:8a:8d:89:f2 brd ff:ff:ff:ff:ff:ff link-netnsid 6
inet6 fe80::847c:8aff:fe8d:89f2/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
34: veth44040f4@if33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-70e3310451d5 state UP group default
link/ether 3e:f5:de:a9:95:c0 brd ff:ff:ff:ff:ff:ff link-netnsid 7
inet6 fe80::3cf5:deff:fea9:95c0/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
36: vethf6e8d63@if35: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-855bb47ccb4d state UP group default
link/ether ea:81:d8:82:e2:9c brd ff:ff:ff:ff:ff:ff link-netnsid 9
inet6 fe80::e881:d8ff:fe82:e29c/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
38: vethfeef6d4@if37: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-855bb47ccb4d state UP group default
link/ether 8e:a5:ad:8a:7d:c6 brd ff:ff:ff:ff:ff:ff link-netnsid 8
inet6 fe80::8ca5:adff:fe8a:7dc6/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
40: veth1c61b70@if39: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9b7371dec537 state UP group default
link/ether d6:ac:af:73:81:5a brd ff:ff:ff:ff:ff:ff link-netnsid 10
inet6 fe80::d4ac:afff:fe73:815a/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
42: vethe5a86d1@if41: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9b7371dec537 state UP group default
link/ether ae:45:fc:e3:05:48 brd ff:ff:ff:ff:ff:ff link-netnsid 12
inet6 fe80::ac45:fcff:fee3:548/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
44: veth3acba4d@if43: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9b7371dec537 state UP group default
link/ether f2:b2:d8:aa:7d:a8 brd ff:ff:ff:ff:ff:ff link-netnsid 11
inet6 fe80::f0b2:d8ff:feaa:7da8/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
46: veth0465ced@if45: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9b7371dec537 state UP group default
link/ether b2:f6:fd:4d:b0:a6 brd ff:ff:ff:ff:ff:ff link-netnsid 13
inet6 fe80::b0f6:fdff:fe4d:b0a6/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
48: vethcfe7b95@if47: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9b7371dec537 state UP group default
link/ether e6:cf:95:8e:51:32 brd ff:ff:ff:ff:ff:ff link-netnsid 14
inet6 fe80::e4cf:95ff:fe8e:5132/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
50: veth07a9fb9@if49: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-8c6b6f7f9b76 state UP group default
link/ether f2:cf:8f:e4:dc:c5 brd ff:ff:ff:ff:ff:ff link-netnsid 15
inet6 fe80::f0cf:8fff:fee4:dcc5/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
52: veth12cc35b@if51: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-8c6b6f7f9b76 state UP group default
link/ether 42:00:cf:b3:57:63 brd ff:ff:ff:ff:ff:ff link-netnsid 16
inet6 fe80::4000:cfff:feb3:5763/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
54: veth083aaf0@if53: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-1a77e442593b state UP group default
link/ether 26:1e:1d:c9:28:b6 brd ff:ff:ff:ff:ff:ff link-netnsid 17
inet6 fe80::241e:1dff:fec9:28b6/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
56: vethab2a86c@if55: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-9bb834e8e5f7 state UP group default
link/ether e6:dd:3b:fe:14:cb brd ff:ff:ff:ff:ff:ff link-netnsid 18
inet6 fe80::e4dd:3bff:fefe:14cb/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
58: veth392b71a@if57: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-68a13459a7f7 state UP group default
link/ether f2:17:a9:fc:91:4b brd ff:ff:ff:ff:ff:ff link-netnsid 19
inet6 fe80::f017:a9ff:fefc:914b/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
60: vethbf13413@if59: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 02:d9:20:99:25:68 brd ff:ff:ff:ff:ff:ff link-netnsid 20
inet6 fe80::d9:20ff:fe99:2568/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
62: veth922b9e9@if61: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-0ee41bebb3bf state UP group default
link/ether 62:6b:13:68:f6:b0 brd ff:ff:ff:ff:ff:ff link-netnsid 21
inet6 fe80::606b:13ff:fe68:f6b0/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
64: veth39754ce@if63: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 3a:7b:97:6a:d0:65 brd ff:ff:ff:ff:ff:ff link-netnsid 22
inet6 fe80::387b:97ff:fe6a:d065/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
66: vethae68b92@if65: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 9a:42:bb:cb:04:9e brd ff:ff:ff:ff:ff:ff link-netnsid 23
inet6 fe80::9842:bbff:fecb:49e/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
68: veth0a703b4@if67: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 4a:6e:c5:90:6a:63 brd ff:ff:ff:ff:ff:ff link-netnsid 24
inet6 fe80::486e:c5ff:fe90:6a63/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever

And the nmcli con show:

NAME UUID TYPE DEVICE
ZimaCube-eth0 dc21f0dc-f5dc-46a4-8942-3759c8e5a948 ethernet eth0
docker0 9d4a67ae-ba24-4f8b-a36f-5a6d4bd0adef bridge docker0
br-0ee41bebb3bf c4bff897-bda0-4b3e-b2b7-4c06b9333613 bridge br-0ee41bebb3bf
br-1a77e442593b 755d1063-f3a8-447f-83f4-e06444bad5c7 bridge br-1a77e442593b
br-4d872ebba84d b753c425-ee8c-4155-8779-5b006609245d bridge br-4d872ebba84d
br-68a13459a7f7 989cf6d7-42b1-4ce6-869c-fe122b1af0e5 bridge br-68a13459a7f7
br-70e3310451d5 61374260-a555-49b9-8f90-042e6228e425 bridge br-70e3310451d5
br-855bb47ccb4d b120a4d1-cdf5-4b79-82fb-2e9a86a20f1b bridge br-855bb47ccb4d
br-8c6b6f7f9b76 9290aa2d-5080-479c-a7bb-fea7515d1c65 bridge br-8c6b6f7f9b76
br-9b7371dec537 80af1aa8-61de-4dc1-aea8-79a4cdbd6f7b bridge br-9b7371dec537
br-9bb834e8e5f7 caa46e27-26cf-4d97-aa3c-9632524fe65b bridge br-9bb834e8e5f7
lo 116603ab-86df-4876-bc31-e072519600c5 loopback lo
br-e5c874ffe22b 4979d2a7-911d-4a06-8b0e-f40ea43cedbf bridge br-e5c874ffe22b
virbr0 d4eddb07-7ba1-45b4-b8b0-651ae123ccad bridge virbr0
Wired connection 1 7c9a53cc-c835-3656-a889-d762850904b0 ethernet –

~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

gelbuilding · January 20, 2026, 1:07am

Thanks, this output explains it clearly.

Your eth0 currently has no IPv4 address at all (only IPv6). That’s why you get “Network unreachable” when pinging IPv4 targets (1.1.1.1 / 8.8.8.8), and why Home Assistant/cameras suddenly broke (most camera discovery + SSDP is IPv4).

So this isn’t the old UI display issue - it’s an IPv4 config/routing issue on eth0.

Quick fix:

Check if IPv4 is being assigned (DHCP):

nmcli dev show eth0 | grep -E "IP4|GATEWAY"

Bring the connection down/up (forces DHCP renew):

sudo nmcli con down "ZimaCube-eth0"
sudo nmcli con up "ZimaCube-eth0"

After that, ip a should show something like inet 192.168.1.x/24 on eth0, and HA should recover.

If it still doesn’t pull IPv4, then something on the router/DHCP/static config is blocking IPv4 assignment.