Ok here is what I am doing differently and so far it seems to be working.
Instead of using copy/paste the whole thing, I manually pasted each line 1 at a time
Basically it kept telling me “already done that”… in fact when I got to this line:
curl -fsSL get.docker.com | sh
It gave me a warning that running it again may screw up docker.
But I let it run and this time I can see it installing ha right now .
Letting it finish …
Hass.io at last!
I can only access it within the vm using it’s internal ip, but it is working.
Now I know I can do this when my NUC arrives tomorrow.
Thanks for all the help guys…
Yes, each line of the code needs to be copy/pasted and run one at a time. (excluding the numbers listed)
1.) sudo -i
2.) apt-get install software-properties-common
3.) add-apt-repository universe
4.) apt-get update
5.) apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
6.) curl -fsSL get.docker.com | sh
7.) curl -sL "https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh" | bash -s
Well done on working it out and, (for the most part), followiing the guide. I’m sure you’ll agree it is as simple as it was stated to be when you do it correctly.
Thank you for your guide- yes it worked perfect… I just wanted to be sure (in my mind) that we were on the same page. When I looked into this months ago, I kept seeing threads saying I would not get the version with the snapshot ability (ie the other one in my picture) and that was a big part of my confusion.
Just waiting on the fedex truck now…thanks again!
How did you go with the install on the NUC, everything go smoothly?
So far great!
The hardware came in Monday night and I have most of it setup now other than dealing with the Zwave usb key being seen inside the vm.
I put that off until I get Ubuntu to play nicer when under the vm and to also make sure I am doing proper backups as I had never even seen proxmox until Monday night.
But yes it was well worth it to get HA running this way!!
Thanks again for the help…
How quiet is the i7 NUC? The advantage of Pi is dead silent and I just back up the current image and could restore to another when SD Card will be corrupted. Kinda of wanting the NUC too but it seems overkill.
It’s very quiet- I can’t even hear it unless I walk right over to it. To be fair I an not putting it under any real load with it only running ubuntu/hassio right now.
If you want this just for hass.io, then yes it’s overkill. But I am doing this with a hypervisor so I can run just about any os from my chromebook , old pc etc. So I can now experiment with HA now without having to worry about messing up my “production” HA.
So if just for hass.io, yes this is overkill. But for what I want to do, it is not enough. I should have got more memory but that can be fixed…Christmas is not that far off.
I was going to go live tonight and did the last step of copying my config files over and that broke it.
Stupid me did not do a snapshot before hand- I am going to try to do a reinstall to repair but if not will do completely over and then transfer 1 file over at a time till I see what is killing HA.
Bet it’s configuration.yaml but we will see.
Also anyone else that is going to go this route: I have learned a lot over the past few days:
If going with proxmox- setup ubuntu bios as UEFI. It will work fine with normal bios but some of the fancy remote control protocols (they are worth it) won’t work without it.
If you have a nas, use nfs for your guest storage. My local SSD is faster on bootup but it’s expensive and once up, it’s just as fast.
Any particular reason you are using proxmox / VM’s? The procedure I posted literally takes 20min and it’s completely done, up and running.
I don’t really care how you do it, but if you are after simple and reliable…
It was working fine as a new install until I copied the files over so not sure what went wrong.
I am using proxmox so I can get more use out of the hardware basically working it as a thin client server.
I went ahead and started building a new vm tonight and will start taking snapshots so I can retry if it happens again. Have to get up early so will have to finish later…thanks.
I’ve resisted asking this question yet again but I am really struggling with the pros and cons…
so far I have come up with a few…
Proxmox Pros
Proxmox Cons
I have only played very briefly with Ubuntu/Docker/HA which I setup in a separate VM in my Proxmox (and yes @kanga_who it is very simple but I think even 20 mins was very generous!) so I am no expert and therefore cant really describe what is good or not about this setup - maybe it covers everything Proxmox does? Access to Bluetooth would be a big plus though.
And,
@fletch101e Can you expand on this a little please?
Ok as you have seen Promox comes with vnc and that is normally how you access your vm’s and it works well. But it also supports other remote protocols like spice. Those splice clients work a little bit better than vnc as they support clipboard and even usb connectivity. I got it working on my chromebook last night and it looks just like ubunta is on the machine. Vnc is good this is just a bit better imho.
Not sure why you can’t do bluewave with prox? I know Zwave usb was very easy to get working with prox but if not, why not do it remotely via mqtt with the bluetooth on the pi?
But @kanga_who is right about simplicity. If all I wanted was a reliable HA, I would have never bought an I7. I would have used an old computer or bought a cheaper I3 / chinese clone and put ubunta straight on top of it. You just need to decide what you want to do.
Ok here is why copying my configs from the Pi to the new install are killing Ha:
File not found: /config/configuration.yaml is what I get when I run config checker.
So it can’t find itself…
My raspberry Hass.io has that /config directory but my ubunta install does not. It leaves everything in a root directory called homeassistant.
I tried creating a directory under homeassistant called /config and moving a copy of configuration.yaml over to it but same thing.
Where is it getting the /config from?
Hold on. No. HASSIO uses a bind mount to the host. Inside HASSIO, it is /config. Inside of any Home Assistant docker container it is set to that unless you change it yourself.
That “root” directory is not a root directory. It’s actually /usr/share/hassio/homeassistant
This is not how it works.
HassIO is running in DOCKER. It’s a DOCKER bind mount. Inside the container it is /config. Outside the container it is whatever you have on your host. If you ran the script on Ubuntu, it’s in /usr/share/hassio/homeassistant
So where is that error coming from then? That file is located in homeassistant dir yet it doesn’t see it. I even tried changing ownership to root to see if that was the problem
I have an idea but it’s going to take me a while to see if it will work…
Without the lights on I can only stab in the dark.
A. How are you accessing the directory?
B. How are you copying your files across?
C. Explain the configuration. A VM running Ubuntu, and you ran the hassio script? Or you’re running the HassOS vmdk?
A: From ubunta directly
B: I think that is the issue. The first time I went from hassio’s share (on the pi) to my local computer. Then from there I used SSH to ubunta. I saw that changed ownership from root to me as I didn’t have ssh setup to do root.
This time for the yaml files, I am doing a copy paste from the PI to ubunta with both configs open at the same time. So far it is working but I have to take a break and take fiance to the store for quick trip…
C It’s ubuntu vm.
Ubuntu. Not ubunta
And you shouldn’t.
As I stated about 1,000,000 posts back in my original instructions, the location to copy files too, is above. As @flamingm0e noted, the /config is just a bind address.
Navigate to the above file location and you will find all of your config.