I’ve also run the following two commands with no success:
ls -lRa /home/homeassistant/
systemctl status [email protected]
The first command returns the following list:
.bash_aliases
.bash_history
.bash_logout
.bashrc
.cache
.profile
The second command returns the following:
Loaded: loaded (/etc/systemd/system/[email protected]: enabled: vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019=02-22 06:08:00 UTC; 29min ago
Process: 3272 ExecStart=/srv/homeassistant/bin/hass (code=exited, status=203/EXEC)
Main PID: 3272 (code=exited, status=203/EXEC)
I’m really not sure what it could be – I’ve tried Googling everything I can think of, and haven’t found anything that works so far. Any help is seriously appreciated!
If you’re at this early stage I’d say the easiest option would be to just start again; if it’s a fresh install you’re doing starting from the beginning would probably be quicker than trying to diagnose what went wrong.
Ha! I guess you’re right. How in the heck could I have missed that? That’s a pretty specific post title for a brand new user who just joined 7 hours ago. I wonder if that was edited after my post?
Just wanted to let everyone know that this isn’t my first attempt to install Hassbian. I’ve done quite a few installs after wiping my SD card to try again, each attempt at installation running into the same problem. I’ve left the pi running for in excess of 30mins when it’s setting up, it’s always been connected directly to my router, and I haven’t done anything differently than any of the instructions have indicated. The most frustrating thing is I’ve had this installed correctly and running previously — Hassbian then too, same install process — so I know it’s possible to get working, but just apparently not the way I’m trying to do it.
And yeah, finity, the issue is I can’t even get my /home/homeassistant/.honeassistant/ directory to even show up.
Why not just get it set up using a hard line to the router to make sure it’s not a network issue? Then after you get it up and running switch it over to wireless if you really still want to at that point.
finity, I have been doing so already. I’ve tried first wirelessly, then with a hard line connection to my router with the same results. Did a couple resets with the hard line connect, but still no change.
then maybe there is something corrupted in the latest hassbian image. try to find an image from a version or two ago and see if that works. then just do a normal upgrade once it finally works.
without knowing exactly what are doing, and assuming you haven’t made any mistakes following the instructions then that’s all i’ve got. It honestly is so easy to install hassbian from an sd card image it should just work.
Right but the OP plainly stated hassbian, and even provided information that supports that claim based on the commands run and the info provided in later posts.
This, from the hassbian instructions, should be tried by the original poster:
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 .
Hello all! Thank you for the suggestions, I’m going to try to address each one as well as I can.
@nickrout I’ve attempted to do this a number of times, but each time I’ve been met with no error messages or results of any sort. I’ve tried using “ls -la” and “ls -lRa /home/homeassistant/” to check for a .homeassistant hidden folder, but both return nothing out of the ordinary (the exact list is mentioned in my first post).
@finity Just wanted to add that the version I was trying to do this with was the Hassbian 1.5 image. As per your suggestion, I’m going to try wiping the SD card once more and trying with the 1.4 image. Will update if anything is different, or if I’m still getting the same results!
@nickrout I’m aware that I shouldn’t be ending up in the state, assuming I’ve followed all the directions correctly, yet here I am. I’ve been following the instructions to a T, and I keep ending up in the same spot with no /home/.homeassistant/ folder.
I used BalenaEtcher to flash the v1.4 Hassbian image (which I got here: https://github.com/home-assistant/pi-gen/releases/tag/v1.4.0) onto a 32GB microSD card. I’ve tried with v1.5 before, but I downgraded one version to see if that would solve anything (so far, it hasn’t).
I have my RPi 2B+ hooked directly to my router, and am watching the install process on a separate monitor each time. After the initial installation (mine takes ~2-3 minutes, not 10, which I’m not sure is indicative of something going wrong?) I sign in with the default pi/raspberry login credentials, and check /home/homeassistant/ with the two commands “ls -la” and “ls -lRa /home/homeassistant/” and both keep returning no hidden directories.
At this point, I tried to run the command “sudo systemctl start install_homeassistant.service” and absolutely nothing happens. As in, no error message, no output of any sort, and seemingly no effect at all. At this point, I tried a few other things.
From here, the first thing I did was “sudo hassbian-config upgrade hassbian” command to see if an updated version would be able to handle things. After that finished, I tried the “sudo systemctl start install_homeassistant.service” command, but still nothing. Moved onto “sudo hassbian-config upgrade homeassistant” command to see if I could upgrade homeassistant this way, but I’m running into a weird error. I’ve attempted to try writing the output to a file so I can share it here, but it seems my normal method of using “> output.txt” isn’t working. If anyone knows how I can pipe the upgrade homeassistant command error output into a file, I can get the exact error messages to share.
This is about as far in-depth as I’m able to go right now. I hope this added some useful information, or otherwise made it easier to diagnose what’s going wrong for me.