Every time it starts I get no IP to login to, nor does my network say it’s on line… I have a tiny TFT screen so can see the command line when booted. No IPs for 4 or 6. and the xxx.local:8123 is a noop.
So I stuffed in a full Buster TF card in the RPi and it booted right to the desktop with full eth0 and wifi working without issue.
Two different TF cards, and even now 2, 64g USB drives are all doing the same thing (written from different machines even) trying to install the latest image as in the instructions for installing home assistant from the Main instructions and tutorial links! (https://www.home-assistant.io/installation/raspberrypi)
WHAT the heck can I execute/look at/edit to set/see/configure the IP again???
This had all been working for the last couple months, and seems to either have died on me or after some updates the last day or three. I’m on a battery ups right at the RPi so I know it wasn’t a power issue, and the fact that testing validates the hardware is fine.I previously had a fixed IP, but now have none
HELP!!!
wow…nothing even cloes…2nd/3rd command I get a list of connectivity looking info
nothing notable. Sorry I know posting pics of text sucks, but its the only way to get anything off the RPi at this moment!
when people get netdev timouts… THAT is network congestion/collisions, or some switch or hub drop out etc, somewhere in your HA net of communications. (BTDT)
Net is good. RPi simply has a x3 18650 battery supply UPS between wall wart and RPi. (yep…historic personal data here from trashed TF cards due to pwr spikes/drops As mentioned up front, putting a Buster TF card in it booted with all net assets on line as expected. It’s just these latest image files at issue! … damn i wish I could find the orig I’d loaded from back in Oct/Nov!.
I don’t think your network is good. As you can see from your screenshot it is stuck at getting IP configuration on your wired connection. Which means you have a DHCP or connectivity issue.
so how does the Raspian Buster load/image find it? Same hardware, just software is different
my net is xx. 0 .xxx 150 is fixed IP, with DNS all above .150.
I’d previously had no issue running with the RPi server on a fixed IP address.
could it really be negotaitions between RPi and the DNS server? again…confused why just swapping TF cards it would all fly as expected. HA DID previously ‘fly’ almost flawlessly for me till …well… the last update or two.
DNS and DHCP are two different things. You cannot contact DNS before you get an IP from DHCP. If you had a fixed IP it would not stay at “getting IP configuration”.
correct… for these ‘fresh first installs’ , and as it did before, it should be finding the IP without issue.
I just tested a 13.2 img (haos_rpi4-64-13.2.img.xz) and got this same issue. If HA is simply attempting to obtain an IP from my router, WHAT am I missing that is any different from any other device I switch on and connect?
Then you need to figure out why you are not getting an IP. Have you tried connecting a different device (laptop for example) to the cable where HA is, to see if that gets an IP?
that’s how i tested the hardware… simply shut down the RPi, swapped media, and rebooted.
Regular Pi desktop comes right up with all networks operable. Normal shut down. Swap media, and HA is not finding an IP.
…and the instruction for setting IP you linked… does not return the type of stuff it states, and the PRINT command returns command not found
ok…router logs… 2:20 a.m. 1/12/25…couple of time stamps with flaky entries from various HA attached ESP32 devices. issues with HA responding.
…must be what set me on the fox hunt
sorry…that was the moderator Tom_I …really appreciate the help.
Many times it’s something dirt simple you keep tripping over …until the other guy tells you your sunglasses on on top your head… thanks again seriously. every little bit helps at this point.
…v/r
