Difference Home Assistant / Hass.io

Yeah I will install manually what I need, samba already in so hope my son can pull this of if we stuck maybe we consider reinstallation in Docker, will see.

What I am missing under those 3 dots menu?

Just the hassio stuff. Nothing you need

Thx, so I off to go, just awaiting raspbee hat for ZigBee gate. So fascinated.

cheers

Iā€™m new and want to setup a smart home. I just read this whole conversation and I still donā€™t know the disadvantages/advantages of installing hass_io vs home assistant AFTER itā€™s installed. I get that hass.io is easier, but will I be missing something if I donā€™t go down that route?

I have a Pi2 but from what Iā€™ve read it will be slow with hass_io. I also have a Mac mini running all the time that I could use. But would the ā€˜home assistantā€™ method on the Mac be more difficult down the road? I have some Linux experience so Iā€™m not afraid of the Terminal, but at the same time I donā€™t know what I donā€™t know.

1 Like

Hassbian Iā€™d say. Hass.io is nasty on anything but a Pi 3B.

hassio is much easier to administer, but you have to wait for someone to write an addon for anything new before it will work with hassio. Also, you cannot use your Pi for anything other than hassio.

This largely depends on what hardware you might need. HA itself will run much happier on the Mac, but if you donā€™t have the drivers that you need for your hardware on the Mac, then it wonā€™t work.

If you donā€™t have anything you need to plug in to the Pi, then use your Mac. Home Assistant is a just a python program, and will work on any computer that will run python.

Here is a text-book example of why this all matters and why the HA community needs to be careful with the names it uses. i.e. Home Assistant, or is it homeassistant, or is it HA vs hass.io.

I am having some script-already-running issues and, as a result of grubbing on the interweb, I discovered Node Red this morning. I am instantly hooked. Lots of search hits for node red and homeassistant give me confidence that it is sufficiently mainstream to move forward. In 4 minutes I have node.js and node red installed on my Ubuntu server.

Off to the web and youTube to rtfm for installation and hello-world examples. WHAT? Almost every search result indicates node red and homeassistant. It is so ubiquitous that I donā€™t even see anything referencing node red and hass.io. Not until I watch the install videos do I learn that node red only works with hass.io.

I have found my way to this forum thread because I too am trying to understand the difference between homeassistant and hass.io and what it will take to move my 30-device, z-wave / mqtt, 100-automation, year-old homeassistant instance to hass.io.

IMHO, all of the node red stuff should not indicate that it works with homeassistant. Rather, it should be node red for hass.io. The name matters to us.

This is 100% incorrect.

I do not run hassio, and 100% of my automations are done in Node-Red.

flamingm0e,

This is great news! Are you able to point me to references that show how to complete the node red install for an HA instance that is not hass.io?

Thanks in advance.

And, re the main topic, I am completely in alignment with you that there needs to be some resource, maintained by someone in the know, that explains the difference between the two.

What do you mean?

You install Node-Red, you open the palette manager, you install home-assistant nodesā€¦

What part are you getting stuck on?

If only there was an FAQ covering it :wink: