My first post but I’ve been lurking for quite some time. I’ve tried to install several times and several methods with very poor results.
I tried the hassio installation which seemed to deliver the best results but I could not get SSH to work at all. I was able to install several component/add-ons and things seemed to be moving along but where ever there was a need to get to the command line, no SSH was possible. I also connected an hdmi monitor/keyboard/mouse but never got to a command line prompt. I felt I was so close but then a complete stop.
I then tried the long way around and installed raspian but when it came time to create users in python the instructions seem incomplete and leave you hanging out.
I’ve done a bit of looking through the forums and other on-line sources and there seems to be so many open ended and uncompleted threads. I ran the hassio installation several times and while researching support I found a message that said this wasn’t recommended and has been “deprecated”.
Sorry but my frustration level is fairly high but here goes…I’m trying to install onto Rasberry Pi 2 and eventually, I was hoping to utilize a Z-stick gen 5. Is there a fully vetted installation/set-up guide for this scenario?
Hass.io is a docker container running on top of an OS called resinos, and it isn’t a regular distro. You don’t have access to do anything in the host os, and there are no utilities to run. Your zwave stick should just work with the normal /dev/ACM0(?).
If you use hass.io, forget what you know about using a Linux os, because you don’t have access to a standard distro at that point. It’s basically just an appliance
I’m sorry but I haven’t even gotten that far into the installation. The Hass.io installation has you use SSH to install additional components but it doesn’t work. I installed the SSH server but every time I selected start…a few moments later it stopped or failed to run. I also attempted to connect a monitor, keyboard and mouse but all I got was the Hassbian logo…no prompt.
Is there a complete installation guide that is known to work?
Hass.io installation doesn’t require the use of SSH at all. You don’t install any ‘additional components’ at all. There is no underlying OS to use to install anything.
Please show me where it says you need to do such a thing?
I’ve got an RPi 2 too (with a Z-wave stick and integrated with Google Assistant) and tried the various HA setups until currently settling on Hass.io. I’ll echo the other comments and say it’s been very stable and easier to update, although not without some glitches.
-Correct power supply?
-Remove your Rpi wifi adapter if you have one for now and use a LAN connection to your router.
-Did you full format your SD card (that you’re seeing a Hassbian logo says it might not be a clean install)?
-It really does take a while for Hass.io to compile, especially on a slower RPi2. Try leaving it for longer than you think you need.
It should be as simple as going to the web address http://hassio.local:8123 to see the home page. If that address doesn’t work, check your router if you can to find out the IP address of the RPI and use http://rpi_ip_address:8123. If you’re not having luck with SSH, try enabling the SAMBA addon which will allow you to see your Pi’s config directory and allow you to edit the files. It’s truly a headless device so a keyboard and monitor don’t help here.
If it’s not working, try again and perhaps swap SD cards is the only other advice that come to mind. Lots of work to come up to speed, but not much after that. Good Luck
PS Hass.io doesn’t require SSH to manage addons, but I do find it much more reliable to restart HA or reboot the RPi via SSH. The instructions do lay that out.
I’ll admit that perhaps my patience had worn a bit thin. Pushing away and having a fresh start at it again later today may bring a more positive attitude.
When I did the Hass.io installation, it described adding packages which I did and they did appear to install. One of the recommendations was to install the SSH feature. It did install but would never run. I read in a number of the forum threads where it wasn’t working for other people as well and digging in deeper I found several different recommendations on how to enable it from within the OS. I’m now understanding that it may not be possible to instigate command line commands to enable SSH. As I mentioned previously, when I connected a monitor and keyboard directly to the RPi all I saw was the Hass.io banner page and never did get a command prompt. Perhaps this is normal for the Hass.io installation. Further confusing me is the statement that the Hass.io installation process isn’t recommended and won’t be supported in the future.
I did try my hand at one of the alternative methods of installation whereby Debian or other OS’ were installed manually which never did render as much success as the Hass.io process.
I thank you all for the recommendations. I’ll have a fresh go at it again later this evening.
My apologies, I’m not familiar with some of the lingo being used here but I think I may be getting somewhere.
I did the all-in-one installation again and I’m back where I was the first time. Perhaps I’m expecting something different in terms of a successful installation. I have the Hass.io installed. I have installed some of the add- ons (Configurator, Gitpull, Check Homeassistant Configuration, SSH Server and MQTT).
As before, the SSH Server doesn’t seem to want to stay running and the MQTT is warning that it should not be running as administrator.
I think this is the part that led me astray during my last attempt. When I start to research these two items and then start digging through the various forums, many of the work arounds, recommendations seem to suggest that I need a command prompt to start adding/modifying some commands in the OS. After reading some of the helpful replies here, I’m getting the sense that maybe this is not the case.
HASS.IO is the newest method of installation of Home Assistant. As such, the vast documentation from the last few years are geared more to the old installation methods. It is a struggle of software that moves so quickly. HASS.IO is gaining more traction and you will start seeing more and more documentation geared toward it. You have to learn to decipher the lingo and understand when and where things apply. That is probably the hardest part for someone new to the project. Stick around, read a bit, and you will start picking up on where and when you need to use certain knowledge.
I first tried Home Assistant over 2 years ago, hated it, and started working on my own solution. After a couple years and many different renditions of how I thought it should look and run, I decided to give it another shot, since there had been so much progress on the project. I learned that it ticked nearly every box I was wanting and I spent a few months just making sure I had the majority of the process and knowledge to implement it, before going ‘All In’ on HA. I am glad I did. It has been much easier on me over the last several months, and it just appears to be getting better every month! I can even order pizza from my Telegram bot! “Bot, order me a pizza”.
I believe that when I’ve run into a few issues, some of the info that I dig up is dated and/or does not apply to this installation method.
I did finally manage to get the SSH log in to work but it seems I don’t have permissions to get out of the root login to access the yaml file. Would anyone have any advice on this?
I think the preferred method to access the config directory is by using the SAMBA add-on. Personally I just use syncthing, but that is a more advanced setup. Samba is what everyone tends to use on HASS.IO.