There is a nice architecture diagram on the hassio github:
https://github.com/home-assistant/hassio/blob/dev/misc/hassio.png?raw=true
The three underlying tiers (OS, init and docker) can be provided by ResinOS in a standard RPi/NUC image, or by your preferred linux OS (in my case ubuntu server minimal with docker installed).
Well, after I figured out how to make RPi wi-fi act as AP, situation gain better. But again, documentation for Hass.io is very poor at this moment. And Resin documentation is about a little bit another things with complex solutions like their servers and development on another machine using resin-cli.
I am not against Hass.io, but I afraid that developers will concentrate their work on it only. Home-assistant is Python software and one of the main Python ideas is to keep things simple.
@hijinx, interesting solution, maybe I’ll try it if pure Hass.io installation is not what I need, thanks.
hassio is is running the homeassistant docker file as a base.
Whenever developers develop for homeassistant (hassio or not) it will be on both platforms.
When you need software which is not available as addons (which are docker files, just like homeassistant itself), then use a OS suitable for your needs, install docker and run homeassistant as a docker container.
This is also what hassio does, but on a resinOS image.
Running hassio, you would normallly not even need the auth keys and there is no need to do anything with the resinOS its based on.
dnsmasq and MQTT are available as adon (MQTT is even build in also)
hostapd and npm might be available as addons, but you can create addons yourself if needed.
Hi, I’m new to Home Assistant and am impressed by how organized you guys are. It’s made it easy for me to see the value proposition and I’m excited to get started.
I found you because I am horrified that common consumer devices put control of people’s houses into the hands of corporations via the cloud. I want sovereignty over my house so I’m pleased that I can buy my own hardware and use open source software to achieve this.
I appreciate the goals of Hass[.]io to make installation easier and maintenance simpler. Using Docker is a great idea.
I started down the path of installing Hass[.]io before I gradually woke up to the fact that it would put control of my house into the hands of a corporation (Resin.io) via the cloud. Resin.io has a pretty website (I like pretty websites) but that’s not enough for me to trust them with control of my house.
I’m now aborting and starting over again with Hassbian and I’m grateful that it exists as an alternative. Given that there are probably other people who share my concerns it might be a good idea to add a clear note to the Hass[.]io installation page which explains that using it will give a remote corporation control over your home automation system.
A little bit of FUD here. Hass.io is based on ResinOS an open source linux based OS created by the guys at resin.io. They use ResinOS in their IoT framework, but Hass.io is not based on Resin.io’s IoT framework. ResinOS is open sourced and used in a few other projects and so I doubt there is anything nefarious going on or more than likely they would have been called out on it by now. You are no more trusting your house to Resin.io if you use Hass.io than you would be trusting your house to Ubuntu, Microsoft, or Apple by installing HA on those platforms.
My apologies. I’m corrected and greatly reassured! Thank you for replying.
Short statement about resinos.io / resin.io:
First we based on a resinOS fork that remove all things that allow external control over the cloud. ResinOS is not like a OS that the website suggested. It include all stuff that it need to run a resin.io application. It include also the supervisor and cloud connector. That are in ResinOS and not resin.io
Actual it is to many work with this fork to stay on resinOS in future. If I find time or any Yocto specialist jump into that project, I will start with a own Yocto bases platform with meta-virtualisation. Maybe resinOS will change the direction and produce a real unmanaged OS for project like this.
Anyway, Resin.io and ResinOS are a great product and we need really thankful to this guys. I had learn a lot and that have help me to create this platform. But the heart of that platform is not the hardware image, it is our supervisor that is written in Python.
If hass.io is just a Docker container with home-assistant inside, what are the actual benefits of using ResinOS as a base?
I mean, Docker is available for many distros, and there are even many Docker-specified distros, like CoreOS.
I am not saying ResinOS is bad, I’m just curious why Resin was chosen.
I would assume because it works great on embedded devices (like the Raspberry Pi 3). You don’t need to use resinos to get hassio working, as there is an installer that can transform any generic linux in hassio (https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio).
NOOB here, followed directions for getting started on home assistant, installed on rpi3, saw logo screen, waited over an hour, now screen is just gray. Have reflashed card twice same result each time.
Thoughts? Perhaps Hass.IO image damaged?
Hassio cannot be accessed directly from the rPi, you have to ssh/telnet into it as well as access it from a different device via http.
Hassio noob here too, i see a similar issue.
steps so far ( repreated 2 x):
dd the image to the sdcard
boot the rpi.
see a boot screen logo
see that an ip has been assigned via dhcp
see traffic to/from the web
( wait till no more traffic has been flowing for some time)
no indication on the screen that anything is happening.
try a web browser at http://<ip>:8123 - no responce
telnet to <ip> :8123 - no connection
powercycle rpi
(dhcp, internet traffic again)
browser to http://<ip>:8123 - responce, but its a blank page
view source - there is code there.
after much hair tearing and various browsers on diifferent platforms, IE6 will show the page.
ie6! what century is this?
And immediately after I post, i find another post refering to a javascript_version issue.
sadly editing the configuration.yml file as suggested does not help.
Not that it’s that unexpected, but using IE to try to configure via the web page will not “save” when buttons are clicked on.
i guess its hassbian, or an install over rasbian lite for me.
