HA Green: rk_gmac NETDEV WATCHDOG - Ethernet driver crash causing HA to become unreachable

Installation
21

I doubt your Router knows it’s actually the same device, the devices MAC addresses for wifi and lan interface are unique and not the same, and that’s what the router use to register a device and assign an IP ( It doesn’t know it the same “Device” , and really don’t care or need to )
As i said Fritz-box has issues with Rockchip, You can verify that in multiple various forums, where i.e Pi’s or Green for that matter, and other single board devices using this.

i have 2 android tv’s , wired and wifi, my phones like to “switch” mac addresses often 2.4 vs 5.0 gHz, so a phone sometimes “register” with “new”and thus fu it’s own identity in i.e mdns

thou all my devices have reserved ip’s and different for wifi vs their lan (for those which have both)
Only my phones are not, and allowed to “float around” among the “free” numbers

22

I boughta new Green to replace a Raspberry Pi 4, which was only a temporary solution but runs without problems for weeks. After restoring the Pi 4 backup onto the Green, things went wrong and the system threw OS-Agent error. Maybe because i tried to restore a pi backup on a a grren. I had to factory reset the device and reboot it multiple times to get it to respond.

Now, I am completely locked out again. The current state is that the HA Green is entirely unreachable. In my Fritz!Box (router) network settings, the homeassistant device is the only one that does not show up as "online" , while every other device in my house works perfectly fine.

Deleting the device entry from the Fritz!Box or completely restarting the Fritz!Box via the system menu does not fix it. It briefly shows up as online for a single second, but then immediately drops off and goes offline again.

To me, this it seems linke a fritzbox issue ...

I tried also to reset the ha green via button. Not reachable anymore under the displayed ip from fritzbox...

23

Yes, might be , trying with a basic/cheap/old/used other Router would/could verify that

24

After reconnect the green fritz says "online" for only a few minutes.....then nothing is displayed.

25

"Nothing" as the FritzBox is dead, or your connection to the HomeAssistant green disappears? While it is up, what is shown, MAC, IP Address, port number, Time to live, etc? Is the time it stays up consistent before it crashes?

Interested to know what the FritzBox CPU and memory usage is with your setup. Statistics on network errors and retries would also be valuable. You haven't mentioned which FritzBox model and firmware revision level you are using. This would be very useful information.

Have you involved FritzBox technical support in your troubleshooting path? Yes, I know you have had the device replaced, but are they still tracking the problem, and what have they suggested? No point in duplicating troubleshooting in both forums if the results are consistent. The issue is probably the correct question hssn't been asked yet, and the '"it still doesn't work" is a little too broad to work with.

Wireshark may offer insights as to network traffic.

Try it without the green HomeAssistant server connected first, and then with it switched on and compare the difference. Try it again with the Raspberry Pi version instead.

Alternate option to check: Is your power supply to each and every device reliable? Your home switchboard, (particularly the neutral and earth links - if installed - are functional and not sparking or loose)? Your UPS? Each plug pack/wall wart? The green? The Raspberry Pi? The FritzBox? Any power boards and extension leads? What is your actual measured home AC voltage, not the nominal voltage?

Use the process of elimination to narrow down the issue, leaving everything off and adding one thing at a time and observing what changes. After a few different combinations, a pattern should emerge that will point towards the underlying issue.

If the problem is widespread as hinted, your carefully documented process of elimination should enable the solution to be found. Yes, it may be the FritzBox, but you may have to narrow it down to whether it is hardware, firmware, drivers, or a rogue app that causes the problem in the first place.

As part of troubleshooting, Fritz technical support may offer you alternate customised firmware, hardware, etc to narrow down the problem. I'm certain they are following here (I hope you have pointed them to it). It would be nice if we could have a cross reference to their support forums here as well. It is in their very best interest to avoid ruining or boosting their reputation, something this thread is contributing to. The choice offered to just go with another router or HomeAssistant platform may or may not fix your problem, but how about everybody else following along - is it something unique to a particular combination of factors and how to break that chain? Don't leave us hanging!

26

Fritz!Box model: 7530, firmware 8.25 (latest available). Fritz support has been contacted and is tracking the issue.

When the HA Green is connected, the Fritz!Box shows the correct IP and the port it is connected to, but the device only appears as "online" for approximately 1 second, then "online" disappears. The time it stays online is consistent – always just 1-2 seconds.

I have already replaced the HA Green with a brand new unit – same behaviour immediately. This rules out a defective individual device.

I have also tested with a Raspberry Pi 4 running the same HA backup – the Pi 4 works reliably without any issues on the same Fritz!Box port with the same cable. Power supply issues are also ruled out as the Pi 4 runs flawlessly in the exact same setup.

Given the time I have already invested in troubleshooting, I have decided to switch to the Pi 4 as my primary HA device and will return the HA Green. I will keep monitoring this thread for any firmware fix from the HAOS side, and will share any findings from Fritz support when available.

27

Your actions are understandable from an uptime point of view, but frustrating from a point of view where the ultimate problem has not been identified and remedied.
Thanks for your patience and trying different options to narrow down the problem.
A link to the respective threads at Nabu Casa and Fritz technical support forums would be interesting for others that may experience the same issue and have read this far.

I'd be curious for my own satisfaction on the FritzBox internal system log to see the relevant entries when connections are made, with the green as well as the Pi. Any IPv6 issues interfering? DHCP failing? What connection speed? It may be getting unfairly blamed.