How to tell which installation approach I used?

Installation
, ,
1

It’s been about a year since I worked on HA and I can’t recall which installation approach I took. I have a raspberry pi, and I did setup AppDaemon and used one of the dashboards on it.

I think I may have used the Raspbian installation onto my Raspberry Pi and then used pip (this seems quite familiar - https://www.home-assistant.io/docs/installation/virtualenv/ _

Anyway questions were coming back to this:

Q1 - How can I tell which install approach I used? (or even just confirm I didn’t use HASS.io)

Q2 - If I didn’t use Hass.io, then should I be considering re-installing fresh with this? Noting I do need AppDaemon. That is any advantages? [I kind of recall that Hass.io may not have had AppDaemon as a package previously, but now it seems to suggest it does].

thanks

2

What is the path to your configuration file? That will give us a clue.

How do you update home assistant?

3

also what does this report

cat /etc/*release*
4

Start with the developer tools, info page

image
image814×1005 56.3 KB

When you SSH in, do you get core-ssh# or do you see pi@nameofyourpi?

5

tks - I get:

pi@homeassistant:~ $ cat /etc/release
PRETTY_NAME=“Raspbian GNU/Linux 9 (stretch)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“9”
VERSION=“9 (stretch)”
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/”
SUPPORT_URL=“RaspbianForums - Raspbian”
BUG_REPORT_URL=“RaspbianBugs - Raspbian”

6

yes - and I see “pi@homeassistant”

7

You’re running Raspbian, now check how you installed Home Assistant. Dev tools, info

8

ok:

Home Assistant
0.67.1
Path to configuration.yaml: /home/homeassistant/.homeassistant
Developed by a bunch of awesome people.
Published under the Apache 2.0 license
Source: server — frontend-ui
Built using Python 3, Polymer 2.6.0, Icons by Google and MaterialDesignIcons.com.
Frontend JavaScript version: latest

9

Your version is really old, I suggest starting from scratch, there were too many changes in the mean time and it will be very hard to upgrade from such an old version.

10

Which approach do you suggest noting I have used AppDaemon and python heavily? Ie should I look at just using HASS.io now?

11

That depends on your needs. The general options you have:

  • Unix system + docker + home assistant
  • Unix system + docker + hass.io
  • Unix system + home assistant in a virtual environment
  • HassOS + hass.io (all-in-one installer, no full control over the host system)

Personally I installed docker on an ubuntu system and then home assistant on top of that. I have a test environment as well where I installed hass.io on top of docker on an ubuntu system. I use appdaemon heavily as well and it works in both environments without any issues.

12

I’ll use a Raspberry Pi 4, so could follow the Hass.io instructions here https://www.home-assistant.io/hassio/installation/… would this be then HassOS + [hass.io] option you mention no doubt?

Is that a worry to not have the full control over the host system?

I basically have

  • Home Assistant
  • a few Zwave switches
  • AppDameon - and pull input from a mosquitto queue
  • Mosquitto queue
  • Python 3 script I run every x minutes to grab data from current cost input and publish to Mosquitto queue
  • Have the current cost device plugged in by USB
13

Yes and No, on top are the images for the HassOS + hass.io method, on the bottom are the instructions for linux + docker + hass.io.

Generally I don’t see a problem for your needs with not having full control over the host system. However I’m not sure on the Python script. Personally I’d recommend linux + docker + hass.io but it depends on your skill levels and on your willingness to maintain the base OS, because with this method you need to maintain (updates etc.) the base OS as well.

14

Ok thanks - might be best for me to try hass.io then as it might cover me, and save me some administration rampup

15

Both of the methods I suggested are hass.io, but one uses a generic linux + docker as a base and the other uses HassOS as a base.