Hi @fversteegen, can you say a bit more about the steps between the Portainer install and hass.io install? For me, there is a little “and then a miracle appears” step here. Thanks! 
What step?
Did you click the link?
I installed Portainer and then it says “You’ll just need to access the port 9000 of the Docker engine where portainer is running using your browser.”
But what is the URL here?
The URL is whatever the URL is of the box it’s running on.
If you access HA on 192.168.1.100:8123 then portainer is 192.168.1.100:9000
1 Like
I find this fairly well stated. You installed portainer. What machine did you install portainer on? You’re probably connected via ssh? What IP is it?
0.84.6 (Beta) HassOS image is now available for download for the Intel NUC platform. Testing today.
2 Likes
Any luck? I tried with no success. Freezes at the autoloader menu on first boot. Maybe I’m missing something
Sadly, me too.
Anyone know of these steps are still required?
Installation
Currently there is no shiny installation method. Checklist:
Boot PC to live-environment using PXE or USB
Copy or download the hassos image into your live environment
zcat the image to local harddisk
Reboot
Here I was hoping I could just use etcher with the mssd and install back into the device and boot.
1 Like
Apologies for the late reply. Did you manage to install Hass in Docker?
What I did in the step you are in now (guessing) is I didn’t install hass.io through Portainer, but I installed it by ssh’ing into the host and running the following command:
docker run -d --name=“home-assistant” -v /PATH_TO_YOUR_CONFIG:/config -v /etc/localtime:/etc/localtime:ro --net=host homeassistant/home-assistant
After a while you will see homeassistant popping up in Portainer after which you can configure things like config directory and mounts easily through the Portainer interface (through editing the container and redeploying it)
The challenge starts if you want to leverage USB devices as after every reboot the name of the USB devices changes. You can overcome this by creating udev rules which essentially bind an usb device to a specific port based on serial number and/or manufacturer
No worries because you can’t install hassio through Portainer.
Why do so many people have problems with this? My zwave stick never changes dev names on reboot.
Do you have 1 usb device attached or multiple ones? The issue only pops up if you have more than 1 usb device installed.
I only have one zwave USB stick.
Everything else is over the network
That then explains why you don’t have the issue
The naming of USB devices (or specifically their mount points) determines on the order through which they are discovered after boot. So if you do not use UDEV it is a bit of a gamble whether your usb devices gets mounted to /dev/ttyUSB0 or to /devices/ttyUSB1
Just to let
Hi Frank, thanks for continuing to help! I now have access to Portainer on the NUC now and I can use your terminal command to install hass.io. However, what do I put in as /PATH_TO_YOUR_CONFIG?
I am on the NUC itself, so not SSH’ing from another computer.
That’s the nice part: you decide it can be any path in the container or a path inside the host (don’t forget to make it available inside Portainer!)
My suggestion is to go for the simple “/config” option and to install the hass.io samba plugin later. If you do that you can always approach your config directory through a samba client.
1 Like