Nice work guys. Migrated my two ResinOS to HassOS and it is working great.
Small issue: https://www.home-assistant.io/hassio/installation/ the link indicates for Rpi3 63-bit. A bit is missing somewhere! 
pull request submitted to fix this.
The instructions are a bit outdated but anyone (including you!) can submit a pull request on github for the documentation.
Is it possible to install this to boot off a USB stick like we can with ResinOS? Or is it possible to have configuration and database on a USB? So then the SD-Card would only contain the OS and HA?
2 replies
I also don’t know whether to use 32 or 64 bit for the RPI 3. There is actually a different image for 64 bit RPI on github ( i.e. at https://github.com/home-assistant/hassos/releases ) , even if both RPI links in the announcement point to the same 32 bit release image. I think my old hass.io image is 32 bit FWIW. I believe the ARM V7 on the RPI 3 (non plus) supports 64 bits, but what are the pros and cons. Will all of the addons be available if I select the 64 bit image?
3 replies
I have installed 64 bit version and now I’m getting this error with some add-ons
Home Assistant on hassos runs in docker.
The add-ons don’t care if the host is 32 or 64 bit.
Just install 64bit
Looks like the script is trying to download based on the OS architecture…hmm. That’s not the direction I would have gone with. Lol.
I’d like to know this too.
I had an issue with snapshots NOT showing up once copied over
when I SSH’d in the command hassio sn reload . got them to appear!
THANKS TO EVERYONE FOR THIS AWESOME SOLUTION!
That would be HassOS-Lite.
There’s no upgrade path I can see. Make a snapshot and do a clean install/restore snapshot.
1 reply
The upgrade path is the making of a snapshot and restoring it. All your old settings will be restored.
I think the config.txt is still in a fat16 partition and you should be able to mount it. Pretty sure I could on my Windows pc
1 reply
Hi,
Could you please explain the rational for moving away from ResinOS to this ? Seems there is a lot of churn with the Home-Assistant OS’s
Hmm something must have changed with HassOS as it used to mount the boot partition automatically.
Let me know what you find out - I’m not getting any smarter on this topic really, specially if 64 bit is giving problems for some addons.
hi, I have installed HassOs 64bit on my rpi3B and I works great apart of rpi_rf that gives me error:
GPIO.add_event_detect(self.gpio, GPIO.BOTH)
RuntimeError: Failed to add edge detection
I haven’t happened on previous Hassio imaes. Any help??
Thank You
Etcher is doing everything for you
Etcher will format the card correctly.
Backup not displayed in HAssOS?
The install of HassOS went fine. Copied previous HassIO backups to HassOS, and they do not show up in the GUI. Only my newest Test backup made by HassOS is displayed in the GUI. And I have done several restarts of HassOS for hoping this will pick up the old backups.
Looks like I am not able to install my HassIO backup.
Anny ideas?
For me restart was working. Snapshots were available after reboot.
Otherwise install ssh addon, connect and isssue the “hassio snapshots reload” command.
I saw some mentioning this method
Can you make some comments about HA running on Docker? You mentioned that HassOS will be a Docker host but I already have one of those… (Intel Nuc running Ubuntu Server with Docker). Is HassOS in any way relevant to my setup, I can’t tell? Have ignored HassIO for quite a long time now because I don’t understand why one would care about that either? Is the whole world RasPi now? I used those for a while but upgraded to the Nuc. Seems a ton of effort going into everything except home automation unless I’m missing something fundamental which is entirely possible! I would love more effort on the basics like Bluetooth le, presence detection, detecting and maintaining state so we can automate based on that without writing lots of custom code.
2 replies
Can anyone tell me where the previous releases are (resinOS)? I’m not having any luck with this release so would like to revert back.
Right after burning the SD with etcher I get this:
I’m expecting to be able to read the boot partition to modify some files before booting but can’t do this anymore with HassOS.
2 replies
Found the previous resin image and the resin-boot partition mounts fine. I’ll stick with this release for now!
64 should be OK. See how you go…
I’m actually trying that right now, if this fails I’ll go back to resin. Man, pretty frustrating not spotting that 5 sd card burns ago…
I don’t know about running slower but I am pretty sure it starts slower.
It was bad enough before but several minutes to restart when making changes to my config is putting me off wanting to change/add/enhance anything! 
Hi, guys. I installed a new HassOS on my Raspberry Pi 3B+ and I am a little confused: How should I connect like Pi user now for installing some new features or configurations? e.g. I need to install LIRC, configure CloudMQTT bridge, configure raspi-config, setting up platform rpi_rf, etc. Thanks in advance for yours advices.
1 reply
HassOS is for the pi. It has no bearing on what is going on inside any other OS.
Just use normal Home Assistant Docker.
It sounds an awful lot like you need hassbian.
Anyone clear instruction on how to setup wifi on hassos?
All good so far, thanks for all the hard work your an amazing team
I setup 64bit on rpi b. Everything is ok, except the dht sensor (there was an error since 0.73) and rpi_gpio . Everyone else has the same problem?
1 reply
It actually appears that the correct method (and other updates regarding this new version) got pushed to the Getting Started page already: https://www.home-assistant.io/getting-started/
I have been running hass.io on a rpi3B+ with Raspbian Stretch. Webmin and Node-Red are also running.
Conversion to HassOS worked as advertised except that four of thirteen add-ons were not installed. They are all from third parties. One is a local modification found in the Addon directory. Not difficult to fix if you have local backups of the other available Samba directories (share, addon, config, ssl) in addition to backup.
But, the HassOS version seems slower to (re)start than the Raspbian version. So I timed them. The HassOS version consistently takes 4 minutes and 24 seconds to present the UI upon restart. The Raspbian version is ready in 2 minutes and 26 seconds. No errors in either log. Have repeated these results many times.
1 reply
same for me…very slow to boot whitout error
thanks for this I’ll donate now.
I install HassOS to Raspbian Stretch Lite as Docker, but I can not install HA. Hassio folder content has all files, but the “homeassistant” subfolder is empty. Do anyone know, how can I figureout this problem?
root@raspberrypi:~# curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s -- -m raspberrypi3-64
[Info] Install supervisor docker
[Info] Install supervisor startup scripts
[Info] Install AppArmor scripts
[Info] Run Hass.io
I see this, but nothing happens.
Thanks
1 reply
HassOS IS the OS. You can’t install HassOS IN Docker.
I think you are slightly confused on what HassOS is.
1 reply
OK, but I have installed that as you advised from official link: [https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio]. It’s probably not the OS but IO
Excellent stuff - nice work. Migrated my system to hassIo 1.5 earlier today.
I hit a corrupt SD card on first attempt, but second attempt on another fresh 16gb class 10 went through fine,
Just has to adjust the DHCP reservation for the new RPI3B+ to match the original IP, and restore in the snapshot - all good using zwave.
Also I had to cut away a little plastic on an existing RPI2B+ case for it to be able to take the rpi3b+ board.
Couple of random questions;
Is the general opinion still that the reliability of the RPI3b+ platform is help back by the reliability of SD cards in general?
Just on the startup time…
Today I restarted and got these warnings:
These first four: it doesn’t seem right to take this long to set up something so simple and I have never seen them before
2018-07-13 07:50:22 WARNING (MainThread) [homeassistant.setup] Setup of group is taking over 10 seconds.
2018-07-13 07:50:22 WARNING (MainThread) [homeassistant.setup] Setup of input_select is taking over 10 seconds.
2018-07-13 07:50:24 WARNING (MainThread) [homeassistant.setup] Setup of input_text is taking over 10 seconds.
2018-07-13 07:50:25 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
This I always used to get so no change:
2018-07-13 07:50:33 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
This I started getting since v0.7x.x (not sure exactly) and I’d really like to know why:
2018-07-13 07:51:44 WARNING (SyncWorker_12) [soco.discovery] Can't make a discovery socket for 92.242.132.15: OSError: [Errno 99] Address not available
And this too is not new but included for completeness:
2018-07-13 07:52:11 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
I’m just adding this info in case it is useful for anyone who might be looking into the slow start-up times
Well that’s my question as well but no one is answering that question.
I have completed the upgrade! Everything seems to be working great Pi 3 B - 64bit image installed.
I only have one issue, binary sensors and device trackers seem to be reporting the opposite information to the histogram, ie if a binary sensor is off, the histogram view shows that it is on…
Also the logbook says there are no entries.
You’re confusing installing hass.IO into Docker running on raspbian with hass.OS which is a complete preconfigured OS with docker and a hass.IO container all in one ready to roll image.
1 reply
No 
For some reason I can`t install Hass.IO from this guide “hassio-build/install at master · home-assistant/hassio-build · GitHub” But nothing happens.
[Info] Install supervisor docker
[Info] Install supervisor startup scripts
[Info] Install AppArmor scripts
[Info] Run Hass.io
Hassio folder content has all files, but the “homeassistant” subfolder is empty.
For me works only one this installer: GitHub - dale3h/hassio-installer: Hass.io Installer for Raspberry Pi 3 B+ (Raspbian Stretch Lite) from dale3h.
That’s actually a ‘yes’ or you wouldn’t have posted in this thread in the first place 
No, you can only provide configuration through an additional USB stick at the moment. See the documentation a few posts above.
do you see anything like this in your log…?
Error executing query: (sqlite3.DatabaseError) database disk image is malformed [SQL: 'SELECT events.event_id AS events_event_id, events.event_type AS events_event_type, events.event_data AS events_event_data, events.origin AS events_origin, events.time_fired AS events_time_fired, events.created AS events_created \nFROM events LEFT OUTER JOIN states ON events.event_id = states.event_id \nWHERE events.event_type IN (?, ?, ?, ?) AND events.time_fired > ? AND events.time_fired < ? AND (states.last_updated = states.last_changed OR states.state_id IS NULL) ORDER BY events.time_fired'] [parameters: ('state_changed', 'logbook_entry', 'homeassistant_start', 'homeassistant_stop', '2018-07-13 04:00:00.000000', '2018-07-14 04:00:00.000000')] (Background on this error at: http://sqlalche.me/e/4xp6)
if so delete the “home_assistantv2” database file in /config (or cut it somewhere else) and restart, should be back to normal. 
That being said, you will loose your logbook history as you are deleting or removing the file that holds it all…
2 replies
Yes, thank you. That did fix it for me.
I have installed this 5 times now. Everytime I edit the configurator.yaml file and reboot it gets stuck. I can’t access anymore. No one else is having this issue? I can play around and add samba ssh mosquito. But as soon as I edit anything in the configurator and reboot the system doesn’t connect?
1 reply
How I access to boot partition?
We want to add gpio.
My problem:
2018-07-13 21:18:55 ERROR (SyncWorker_9) [homeassistant.components.sensor.onewire] No onewire sensor found. Check if dtoverlay=w1-gpio is in your /boot/config.txt. Check the mount_dir parameter if it’s defined
DuckDNS with Ngnix not working
I’m running the DuckDNS and Nginx addons together, and I’m no longer able to connect through to HA from the DuckDNS domain. My configs were recreated from a snapshot when I migrated to HassOS so there shouldn’t have been an issue there. Since then I’ve deleted and re-added both of them but still no luck. Is there anything additional I need to do to integrate with the new security features in HassOS?
Thanks,
Honnestly I don’t really know.
Here’s what I did:
Yes so it’s still booting from the SD-Card. I suspect it’s running fully off the SD-Card. The USB seems to only be used to transfer files from the docs.
What happens if you do remove the USB and re-boot the Pi? I bet everything still works.
1 reply
Well if it is writing to SSD that would be good news… makes the SD-Card like a read only ROM… if the yaml files are there as well anyway…
1 reply
I’m brand new to this. But I setup a few switches and are playing around currently. My last setup the SD card crashed and I didn’t have a backup. So what I’ve learned Im starting brand new again. All I did was copy the few lines at the bottom and move them up to organize. Then to test I rebooted. When I refresh the screen it defaults back to setup then can’t connect. Then setup then can’t connect in a continuous loop. I’m setting this up exactly like I did before.
The only one I’m touching is the config.yaml file right now.
(I just tried going back to resinos 1.3 and it’s working perfectly)
Trying to restart/rebuild my system from the ground up today, figured I’d go with the new 64-bit image… got it up and running fine but once I performed DuckDNS setup using this written guide as help: https://www.juanmtech.com/hassio-duckdns-add-on-set-up/ I’m getting no UI at all now. Can’t even access via https://local_ip:8123 getting a “Corrupted Content Error” when I try to reach the UI via the local IP. I can see the config files via Samba Share and have a bunch of errors. When I performed the initial DuckDNS setup inside the UI the log there said everything worked fine. Here’s the HA log I’m getting after rebooting and updating my configuration.yaml with the info mentioned in step 3 of the guide:
2018-07-14 23:23:44 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2018-07-14 23:23:57 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 593, in uvloop.loop.SSLProtocol._on_handshake_complete
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
2018-07-14 23:23:57 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 497, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
2018-07-14 23:23:58 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-07-14 23:24:10 ERROR (MainThread) [homeassistant.components.device_tracker] Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml
2018-07-14 23:24:18 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 593, in uvloop.loop.SSLProtocol._on_handshake_complete
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
2018-07-14 23:24:18 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 497, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
2018-07-14 23:24:18 ERROR (SyncWorker_13) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-07-14 23:24:48 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 593, in uvloop.loop.SSLProtocol._on_handshake_complete
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
2018-07-14 23:24:48 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 497, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
2018-07-14 23:25:49 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: SSLV3_ALERT_BAD_CERTIFICATE
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 497, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 182, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 633, in read
v = self._sslobj.read(len)
ssl.SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:2217)
2018-07-14 23:25:50 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: SSLV3_ALERT_BAD_CERTIFICATE
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 497, in uvloop.loop.SSLProtocol.data_received
File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
File "uvloop/sslproto.pyx", line 182, in uvloop.loop._SSLPipe.feed_ssldata
File "/usr/lib/python3.6/ssl.py", line 633, in read
v = self._sslobj.read(len)
ssl.SSLError: [SSL: SSLV3_ALERT_BAD_CERTIFICATE] sslv3 alert bad certificate (_ssl.c:2217)
I’ve just managed to get this running using the DuckDNS and Nginx addons and if you follow that route you’ll end up with a HA that can be accessed both externally and with a local IP address, and it’s a much simpler process to set up. For some reason after the update to HassOS i had to remove both of those addons, restart, then add them back in again.
Just remember that if you go with Nginx, you’ll need to have a single port forwarding rule that maps port 443 to port 443 on the IP address of your HassOS server (say your Raspberry Pi).
1 reply
Thanks, I actually just barely realized what I was doing wrong so PSA to anyone looking to “restart” like I did… need to use a new DuckDNS account to get a new Token, I was getting tons of errors because I was using the same token as my previous install, once I setup a new DuckDNS everything works fine. I will need to do some reading up on the Nginx after I get come of my basic functions re-built.
