I’m pretty new to Linux and HASS, but wanted to report in on what worked for me for posterity.
Problem
After burning the HASS1.1 image (2017-02-03-HASSbian.img) to an 8GB SD card in a USB adapter attached to my Pi3B (via linux command-line dd), then inserting the burned SD card into my Pi with attached monitor and keyboard/mouse (but no ethernet), I could boot the Pi to a login screen. I changed the password and waited at the command prompt for nothing to happen. I connected ethernet and rebooted, coming to the same command prompt. Logging in did not start any action other than blank/idle command prompt. I could not log in from another computer via HTTP to http://hassbian.local:8123/ nor to http://[THE_PI_IP_ADDRESS_HERE_NO_BRACKETS]:8123/ .
What worked for me
After trying the below, getting stuck in a boot loop, and re-flashing the image with win32diskimager, I got mine working with
sudo ./usr/local/bin/install_homeassistant.sh
It takes about 2 minutes to connect through http://hassbian.local:8123
HTTP access is still functional after rebooting
There should be directory in ~ now called hassbian-scripts
update: After installing duckdns cron, I learned that I had to follow the other suggestions from above posters too:
add “127.0.1.1 hassbian” to /etc/hosts using
sudo nano /etc/hosts
Other attempted solutions (didn’t work for me)
I added “127.0.1.1 hassbian” to /etc/hosts, as suggested by this thread (and another forum), which didn’t fix immediately
sudo nano /etc/hosts
I attempted to install services suggested by another thread
sudo pip3 install --upgrade aiohttp
sudo pip3 install --upgrade homeassistant
I checked to see if the HASS service was running via
sudo systemctl status [email protected]
(note: I had to change keyboard bindings from UK to US to get the @ sign working. I did this via sudo raspi-config then changing the keyboard in “localization settings”)
It had been loaded, but had failed to run:
Started Home Assistant for homeassistant.
[email protected]: main process exited, code=exited, status=203/EXEC
Unit [email protected] entered failed state
I attempted rchiarelly’s fix (this thread) by navigating to
sudo nano /etc/systemd/system/[email protected]
and trying “ExecStart=/usr/local/bin/hass” to no avail.
Like the previous commenters, I noticed that there is no “hass” located in /srv/homeassistant/bin/ but there is a “hass” located in /usr/local/bin/ . I navigated to the directory and ran hass manually. This engaged the setup of hass, and after 5 minutes of updating the HTTP server was working on my network!
cd ~
cd /sur/local/bin/
hass
However, rebooting the pi did not autostart hass again. I tried
sudo nano /etc/systemd/system/[email protected]
again to check spelling of “ExecStart=/usr/local/bin/hass” and to try “ExecStart=hass”, to no avail.
Addding hass to rc.local caused my Pi to be stuck in a forever-booting-and-not-responding-to-console-during-hass-launch-while-no-http-access loop.