However, it sounds like it could just be that itâs still starting up and installing. As long as you didnât reboot it in the middle of that, youâll just have to wait up to 30 minutes.
If you find that the web page is not reachable after 30 minutes or so, check that you have files in /home/homeassistant/.homeassistant/, if there are no files in this location then run the installer manually using this command: sudo systemctl start install_homeassistant.service.
However when I put in; http://192.168.1.23:8123/
I got the image in the original documentation instructions telling me to wait for installation.
It has now finished loading, and it is asking me for a password. Just tried;
raspberry
but the circle is just going round and round and saying loading.
as it is the latest version, and the one I tried 1st, and the one Iâve had the most success with, I would prefer to stick with hass.io. I only tried the other one as I was getting nowhere originally with the latest one.
The hass io approach gives you an appliance like experience, with less ability to change things. Hassbian gives you more control and flexibility. Thereâs no right answer, itâs about personal preference (which is why I went with a base operating system on my Pi, and then used the All In One approach).
That said, hass io is new, so there are less people with experience to help you. Iâd probably suggest Hassbian if you want it simple, or AIO if you want to know your OS is working first. The latter approach will take a bit longer, but itâs easier to know whatâs going on.
As for that login screen, thatâs expecting the API password, which I donât believe is supposed to be set at that point.
well, I am getting nowhere with the other 2 approaches. Stuck with it asking for password.that said I would prefer the version which involves the least amount of typing. On my PC I can use speech recognition. So from that criteria, I guess the IO version would be the best.
So I will startagain another day. Getting tired now.
That looks to be a Barefruit IP address, doing an âerror resolutionâ service. Itâs either a piece of software you installed, or something your ISP does by default.
When youâve done your next re-install, or decide to stick where you are, you need to ensure you set up a static DHCP lease for your Pi. How you do that depends on whatâs handing out your DHCP leases - though some cheap ISP routers donât have that capability.
The same issue, using HA for the first time & using a Pi for the first time no one knows what to expect. After the screen just goes black it is normal to assume something went wrong.
Installed Hassbian this morning it worked fine. Now its just gone again - restarted the pi and have the HA logo again. Does this go away after it installs and updates only leaving a black screen i.e. you cant do anything with Pi anymore or does it provide the same usability as Rassbian minus resources used for HA.?
