Problems with network connection RPI4

Hi,
I have a problem with network connection on RPI4 over ethernet. Few weeks ago, I couldn’t connect to the HA remotely (over homeway addon) and it was also inaccessible in a local network. Both LEDs on RPI ethernet connector were blinking, but router didn’t saw the device connected. It does not responded to the ping requests too. After restarting RPI4, device was visible on network and was responding to ping until HA core has started.

After few days of frustration, I have connected it to an another network, where it worked for week without any problem. So I have moved it back to the original network. For few weeks it worked without any problem, but yesterday the problems with network started again. At this time, restarting router and RPI solved the problem. At this time, I have set static IP except DHCP (with MAC binding in router). I have disabled UPnP, Matter and Ping. But it didn’t worked for more than 1 hour. I restarted both router and RPI again and until now it works, but I don’t think it will last long.

After reset I have checked if HA was running when it was inaccessible. I have checked CPU percentage entity and there was record even when it was inaccessible. Other entities from devices, which are connected over LAN network, were unavailable. There was nothing related to this problem in logs, but it might be because logs are removed when reset. During this problem other devices on network worked normally. From the first occurrence I have updated both Core (to 2025.7.2) and Supervisor (to 2025.07.1), but it does not solved the problem. What can cause this?

Thank you for any help.

First thing the log files from before it was rebooted can be fond in home-assistant.log.1 in the config folder.

Next are you running on an SD card if so this would always be the first choice of issue.

Might be worth checking the troubleshooting section here

similar problem here, new RASPI 4 followed installation information. Got DHCP range address but installtion process says cannot get internet access. I am behind a FritzbxX 7490 allmy other devices on the same network can acess the internet,DHCP and fixed IPv4 adresses, need help

solved, got it the network cable was faultiy

Thank you for a fast response.

It is inaccessible again, so I will try to retrieve logs directly from SD card from file you mentioned.

I am running from SD card, but I changed it to the new one when the issue firstly appeared. I though it might be caused by SD card, but unfortunately it was not.

I will check the troubleshooting section.

I’ll get back if I get more information from the logs.

OK, I’ve got logs from system.journal from yesterday.

2 minutes before connection issue, this information from HomeWay addon is shown.

july 14 12:24:10 homeassistant addon_6a6435e4_homeway[643]: 2025-07-14 14:24:10,198 - INFO - Server con wss://fra.homeway.io/PluginWebsocketConnection[15] IS past it's RunFor time 1 day, 23:00:00.407287, but IS NOT past it's time since last user activity 0:01:34.199703

After 2 minutes, the connection is completly lost and a lot of timeout connection errors are shown. The first one is:

july 14 12:27:48 homeassistant homeassistant[643]: 2025-07-14 14:27:48.666 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.105 for modules 'Time, AutoOff, DeviceModule, Energy, Matter, PowerProtection' after first update: ('Unable to query the device: 192.168.1.105: ', TimeoutError())

The same error is with all network devices, such as MQTT, Huawei solar, etc.

But the weird one is this one:

july 14 12:28:40 homeassistant hassio_dns[643]: [INFO] 127.0.0.1:53659 - 15845 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000653601s

The same error with DNS is then still repeating, for example:

july 14 12:30:04 homeassistant hassio_dns[643]: [INFO] 172.30.32.1:54842 - 62905 "AAAA IN starport-v1.homeway.io. udp 40 false 512" - - 0 12.007389024s
july 14 12:30:04 homeassistant hassio_dns[643]: [ERROR] plugin/errors: 2 starport-v1.homeway.io. AAAA: read udp 127.0.0.1:40180->127.0.0.1:5553: i/o timeout
july 14 12:30:04 homeassistant hassio_dns[643]: [INFO] 172.30.32.1:54842 - 62072 "A IN starport-v1.homeway.io. udp 40 false 512" - - 0 12.007389246s
july 14 12:30:04 homeassistant hassio_dns[643]: [ERROR] plugin/errors: 2 starport-v1.homeway.io. A: read udp 127.0.0.1:52788->127.0.0.1:5553: i/o timeout
july 14 12:30:04 homeassistant hassio_dns[643]: [INFO] 127.0.0.1:46644 - 61149 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000395753s
july 14 12:30:04 homeassistant hassio_dns[643]: [INFO] 127.0.0.1:46802 - 18372 "AAAA IN starport-v1.homeway.io. udp 40 false 512" - - 0 6.562584707s
july 14 12:30:04 homeassistant hassio_dns[643]: [ERROR] plugin/errors: 2 starport-v1.homeway.io. AAAA: dial tcp 1.0.0.1:853: connect: no route to host
july 14 12:30:04 homeassistant hassio_dns[643]: [INFO] 127.0.0.1:49720 - 33349 "A IN starport-v1.homeway.io. udp 40 false 512" - - 0 6.564244681s
july 14 12:30:04 homeassistant hassio_dns[643]: [ERROR] plugin/errors: 2 starport-v1.homeway.io. A: dial tcp 1.1.1.1:853: connect: no route to host
july 14 12:30:05 homeassistant hassio_dns[643]: [INFO] 127.0.0.1:43733 - 39512 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000266273s
july 14 12:30:05 homeassistant hassio_dns[643]: [INFO] 127.0.0.1:47969 - 30912 "NS IN . udp 17 false 512" REFUSED qr,aa,rd 17 0.000389809s

But the core configuration works:

july 14 12:30:36 homeassistant addon_core_configurator[643]: INFO:2025-07-14 14:30:36,579:hass_configurator.configurator:127.0.0.1 - "GET / HTTP/1.1" 200 -

It looks, like there is some problem while contacting (internal docker?) DNS, so no IP address can be resolved. The DNS servers I have set in static IP settings were 8.8.8.8 and 1.1.1.1.

After few days of trying different solutions, I probably found, what causes the problem.

First thing I tried was clean installation of home assistant in docker on Raspbian OS. It doesn’t helped, but it worsen the problem with ethernet. It was loosing connection every day.

Then I have disabled MAC&IP binding in router and set static IP. Disabled IPV6, but it didn’t help too. The next day the connection was lost again.

After that, I have reset eth0 on RPI using those command:

ip link set eth0 down
ip link set eth0 up

and it suddenly started working again. After that I restarted home assistant to reconnect network devices. It is working for one week continuously without any problem.

But I have a question. What caused it and won’t it lost connection again after restarting RPI?

Finally, I can say, that the problem was caused by the MAC&IP binding in my router. When I disabled it previously I reset the router, but some settings in DHCP persisted, until DHCP record for RPI expired. That’s why problem occurred the next day.

I came back from from HA on docker to HAOS for RPI. While the binding is disabled in a router everything works fine. It looks like there is some problem with a RPI link layer, when the MAC&IP binding is enabled.