Why is HA so difficult to set-up?

Installation
21

You can try

ping -c 3 192.168.50.61

to see if host is up.
If it isnt then maybe something is wrong with your ha yellow or it just went iin sleep mode or whatever.
Edit:
You basically have 2 possibilities. If this device is connected to your router with lan cable then either it is going into some sleep mode and you have to wake it up from time to time or ha is for some reason crashing on this device. Maybe haos crashed, i dont know.
This is how i see this problem. It doesnt mean that I’m right about this but this is my opinion.

22

C:\Windows\System32>ping -c 3 192.168.50.61
Bad value for option -c.

I assume the "3 " in that string was a typo.

C:\Windows\System32>ping -c 192.168.50.61
Bad value for option -c.

It is connected to my LAN with Ethernet.

If sleep mode is the issue, are you suggesting sleep mode caused by the router? I would think HA would be designed to avoide this.

If crashing, I could re-install the SW from scratch. I have no automations or custom dashboards yet as I was waiting to resolve this first. Kind of useless if I have to do multiple power cycles every week.

23

just use ping 192.168.50.61, you don’t need any additional value.

When you get it up running, check if you see anything in the logs.

24

No it isnt but im using linux, so maybe in windows is different.
if sleep mode is an issue router doesnt have anything to do with it. It is your raspberry pi bios settings. But maybe, I dont know as I never used this device anyway. I use desktop comp running linux and ha is in docker.

25

C:\Windows\System32>ping 192.168.50.61

Pinging 192.168.50.61 with 32 bytes of data:
Reply from 192.168.50.61: bytes=32 time=2ms TTL=64
Reply from 192.168.50.61: bytes=32 time=2ms TTL=64
Reply from 192.168.50.61: bytes=32 time=3ms TTL=64
Reply from 192.168.50.61: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.50.61:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

I assume this means my HA Yellow is awake?

26

This means your ha yellow is online and probably it is not the problem.
Very likely ha is for some reason.
Try to install nmap and scan this ip for open ports.

27

Yes. Can you access http://192.168.50.61:4357 from a browser?

28

ddaniel

not sure what nmap is but I am sure I can get the info I need using google. Once I have it, do you mean scan 192.168.50.61 for open ports?

fleskefjes

I cannot access with port 4357.

29

Note, to check the HA Observer the link is:
http://192.168.50.61:4357
but not
https://192.168.50.61:4357

30

No point in installing nmap. I’d start looking at doing a factory reset on the device.

31

Thanks for clarifying

“http://192.168.50.61:4357” gives the error refused to connect.

32

OK, I will look into factory resetting. Thanks

33

OK, the reset steps for Yellow with CM5 are much more complicated than CM4. I always get hung up on this https://support.nabucasa.com/hc/en-us/articles/25454894609693-Using-the-serial-console-on-Home-Assistant-Yellow-for-debugging-Windows where device manager never shows the Silicon Labs CP210x USB to UART Bridge. It is so much easier to just wipe my NVMe clean and do a fresh install.

34

Might b e obvious and probably too late, but check if the USB cable you’re using is wired for data & not power-only.

35

not too late. Will check tomorrow.

36

I am able to transfer photos from my Cell Phone to my PC with the same USB cable that does not show the Silicon Labs CP210x USB to UART Bridge in Device Manager, so something strange going on, but it is most likely a PC/Windows issue (just a guess).

37

I used Raspberry Pi Imager and reinstalled the software on my NVMe. Will see if this resolves my problem. Last time it took 6 days before I could no longer log in. Lets see if I experience the same or maybe I just had a bad install the previous time.

38

ok, it has been 8 days since I re-Imaged mu NVMe. All was working fine until today. This morning, I saw two updates, one core and another update that seemed to be linked to core as the core update gave me an error stating I had lo update the other first. I tried updating the other but that would not update either. I also notices all of the other items in teh left hand menu such as maps, history, etccame up with an error page. I rebooted my PC that I was using to log in and now I am seeing the same Home Assistant Splash Screen that never disappears again. This is the original issue that I had when opening this thread. I don’t want to proceed with home assistant when there seem to be so many stability issues.

Any suggestions for next steps?

39

After removing the power from my HA Yellow and reconnecting power I am still not able to get past the splash screen. The companion App on my Andriod says There was an error loading Home Assistant. Please review the connection settings and try again…

I checked the settings in the app and it still had “http://192.168.50.61.local:8123/”. When I enter this in my browser I get the login screen. Previously I was using “http://homeassistant.local:8123/” which still displays the frozen splash screen.

Maybe I need to clear my browser cache again, But the companion app is still stuck on the splash screen.

I don’t know if the two power cycles helped enable me to log in with the actual IP address rather than homeassistant.local or if I would have been able to log in before power cycling.

I dont know how to close on this stability issue.

40

Doesn’t make sense…
It is either

http://192.168.50.61:8123

Or

http://homeassistant.local:8123