You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changed router on LAN (so DHCP changed). HA (on x86 PC) acquired an IP address. Appeared to reboot OK - BUT could not be seen on network by other devices, nor reconnect to external data sources e.g. for backup or media. Showed CIFS error but no network error.
Swapped cables, switch etc - no change.
Found this previous report from 2022 and solution which eventually worked, but looks like it has not been addressed so bringing it to attention again (as that thread is now closed)
What version of Home Assistant Operating System is installed?
6.6.20
Did the problem occur after upgrading the Operating System?
No
Hardware details
No USB devices.8GB RAM. 300GB hard disc. CPU celeron
Steps to reproduce the issue
remove router (and DHCP)
replace router and DHCP
...NOTE have not repeated as there is too much work involved in sorting the IP addresses for all other devices - but it is confirmed in the link to previous issue in the description
Anything in the Supervisor logs that might be useful for us?
-
Anything in the Host logs that might be useful for us?
Workaround/solution is:
ha network update eno1 --ipv4-method auto
from HA server CLI
Desired solution is to avoid this happening if network/DHCP becomes unavailable, though a minimum might be a warning on reboot (similar to the CIFS warnings) to at least point in the right direction.
Thanks
The text was updated successfully, but these errors were encountered:
I wanted to mention something similar happened to me with my NUC 12 running HAOS 13.1. There was a bios FW update for my NUC (oringinal dated for sometime in in 2022, and the new FW dated June 2024). I shutdown the system and moved my NUC to a computer screen via HDMI so that I can update the bios via USB, it updated sucessfully, and moved it back to its permanent (headless) spot. When I rebooted it, HA did not come back, nor could I connect to it. When I connected a monitor to it again and logged in via CLI/HDMI, everything was working, core started up but it was complaining there was no netwrok access.
Long story shory, I did a backup and restore and seems the network adapter changed from enspXX something to enspXX something else, not sure if this was because of a FW update or some issue in HAOS.
Describe the issue you are experiencing
Changed router on LAN (so DHCP changed). HA (on x86 PC) acquired an IP address. Appeared to reboot OK - BUT could not be seen on network by other devices, nor reconnect to external data sources e.g. for backup or media. Showed CIFS error but no network error.
Swapped cables, switch etc - no change.
Found this previous report from 2022 and solution which eventually worked, but looks like it has not been addressed so bringing it to attention again (as that thread is now closed)
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
6.6.20
Did the problem occur after upgrading the Operating System?
No
Hardware details
No USB devices.8GB RAM. 300GB hard disc. CPU celeron
Steps to reproduce the issue
...NOTE have not repeated as there is too much work involved in sorting the IP addresses for all other devices - but it is confirmed in the link to previous issue in the description
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
Workaround/solution is:
ha network update eno1 --ipv4-method auto
from HA server CLI
Desired solution is to avoid this happening if network/DHCP becomes unavailable, though a minimum might be a warning on reboot (similar to the CIFS warnings) to at least point in the right direction.
Thanks
The text was updated successfully, but these errors were encountered: