Introducing Hass.io

TL;DR: Today we’re introducing Hass.io. Hass.io is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration and can easily be extended using Hass.io add-ons including Google Assistant and Let’s Encrypt.

Home Assistant is 2 months away from being 4 years old. In that time the Internet of Things has really taken off and we’ve seen many new devices and services. We saw the introduction of voice assistants like Google Home and new standards like Apple HomeKit.

Some things have been supported natively in Home Assistant, others have been integrated into Home Assistant via third party applications. All these moving parts caused our users to spend a lot of time maintaining their systems and applications instead of automating their homes.

So we decided to take a step back from day-to-day Home Assistant development and see if we could offer a solution that makes updating a breeze for our users. A solution that you can flash to your Raspberry Pi and no longer worry about. A solution that would still be local first and respect the user’s privacy.

And this is how Pascal Vizeli came up with Hass.io, an operating system based on ResinOS and Docker. Hass.io will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows taking/restoring snapshots of your configuration and can easily be extended using Hass.io add-ons.

![](upload://2597t7dQHuXqawor3s8VBaY34cg.png) Hass.io dashboard

To install add-ons, a user can browse the built-in add-on store and install, configure and update any available application. Want to turn your device into a Google Assistant or make your configuration accessible via Samba/Windows networking? Both are a couple of clicks away! (Video demo - 38s, no audio)

At launch we have included a couple of built-in add-ons like Google Assistant, Let’s Encrypt and Duck DNS. Besides our internal add-ons, it is also possible to create and share your own add-on repositories. During our beta period we’ve already seen some great add-ons being shared: Homebridge, InfluxDB, HASS Configurator and AppDaemon.

As we strongly believe in the openness of technology, we are releasing Hass.io as open source under the Apache 2.0 license. That way any user can make sure that the code that runs in their homes is secure and safe.

Some frequently asked questions are answered below in the read more section.

Hass.io has been built by Pascal Vizeli, the UI has been made by Paulus Schoutsen and BRUHAutomation made the introduction video. Big thanks to Resin.io for building ResinOS and helping us get started with it. Also a big thanks to the community for early feedback, helping out with the documentation and add-on development ❤️

Will Hass.io be the only way to run Home Assistant?

Hass.io is and will always be optional. You can still run Home Assistant wherever you can run Python.

Which devices are supported at launch?

Initially we support the Raspberry Pi 1, 2, 3 and Intel NUC. Advanced users can also install Hass.io on a Linux server.

Can I install packages or scripts on the machine?

No, this is not possible as we’re using stateless Docker containers. To install a package you’ll have to write a local add-on that interacts with Home Assistant. See our tutorial.

Can I restore a snapshot on a different device?

Yes, any Hass.io snapshot can be restored on any device.

The Hass.io configuration panel contains powerful tools. Why is there no extra security besides the Home Assistant login?

This is in the works. We have already implemented the backend and plan to release the UI soon.

Is there a roadmap?

We use Pivotal Tracker to track things that are in progress and what we might work on.


This is a companion discussion topic for the original entry at https://home-assistant.io/blog/2017/07/25/introducing-hassio/

Hello,

Why is the pi 4 not listed and is it possible to boot from SSD?

Kind reguards

You react to a blog of 3 years ago. The raspberry pi 4 did not exist at that time.

This post should be updated however ??!

No, because Hass.IO no longer exists. If anything the thread could potentially just be deleted…

that’s one point about blogs. It is an important historical artefact. It should stay, but perhaps with a “outdated” tag?

1 Like

Yep, and locked

1 Like