This has happened to me today as well in a space of 5 hours. It seems to fix upon restart of host machine. I’m bit worried now that I’m travelling overseas and I’ll lose access to HA cos of this bug. Anyone else experiencing this as of late?
It took a reload (new image of my TF) but i’d been up an running a day+ after my last post… and just now went looking for this error as it has apparently started again.
RPi4 stand alone HAOS, but with a tft screen attached to the RPi.
My lack of web access aletered me to turn up the brightness on my server and see this error on the screen again
bcmgenet fd580000.ethernet end0: netdev watchdog: cpu: 2: transmit queue timeout
ok…as of last night… I found my errors were actually being caused by a network hub that had gone down. It appears HAOS was seeing traffic that was NOT internal to anything HAOS or bme680 or Di mini related. Network IP camera server local hub had dropped out and not come up after a power glitch (I know i know, need a ups on that net switch) The Camera server PC was on line but 3/4’s of the cameras were off line. Rebooting the switch, the RPi display attached to my RPi running HAOS stopped outputting the timeout error. ymmv we’ll see if this ever repeated (as it had this time) Ha…perhaps i’ll build an ‘automation’ that alerts me the cam server is offline by tracking this timeout error!
I’ll add my 2 cents/guess …the NETDEV in this case is the Ethernet network device and its linux driver. It says it is timing out trying to transmit a packet. About the only reason I can think of for this is that the Ethernet hardware has tried to transmit a number of times and has given up. I presume that this Ethernet interface is operationally UP, but something on the other end or perhaps the cabling is somewhat marginal in its operation causing this packet to fail to be transmitted out of HA.
nachdem in meinem Raspi Pi 4 die SD-Card kaputtgegangen ist, habe ich das Homeassistant OS mit dem Raspi Imager auf einen USB Stick gespielt.
Beim Start des Raspi bootet er auch ordentlich vom Stick. Ich schaffe es leider nicht Homeassistant zum laufen zu bringen.
Es kommen mehrere Fehlermeldungen, welche ich als Bild beigefügt habe.
Ich mir kann jemand weiterhelfen.
Same for the last month, Since 2025.7 I think.
Also several other possibly unrelated intermittent issues. Random failures in esphome builds that work on the 3 or forth run. Auto-entities sometimes erroring out for an entire boot until recycle.
Anyone have any diagnostics that could shed light.
Running HAOS on Win Virtualbox. I have 3 other Ubuntu images running on the same box with no errors. So iI assume its not hardware
Updated to latest virtualbox today no change.
