Home Assistant - how to tell which install

Installation
1

Been many months since i have Home Assistant running. Flawlessly on my PI.
Want to add Blink onto it, but Home Assistant is out of date.
i can’t recall how it is set up. So is there a quick way of determining whether it is Hass.io, HASSbian Vagrant or Virtualenv?

my details:
Home Assistant
0.39.3

Path to configuration.yaml: /home/homeassistant/.homeassistant

The following errors have been logged this session:

18-02-27 14:48:41 ERROR (MainThread) [homeassistant.loader] Unable to find component blink
18-02-27 14:49:22 WARNING (MainThread) [homeassistant.core] Unable to find service media_player/play_media
18-02-27 14:49:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/lib/python3.4/asyncio/tasks.py”, line 233, in _step
result = coro.throw(exc)
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/core.py”, line 1001, in _event_to_service_call
yield from service_handler.func(service_call)
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/notify/init.py”, line 136, in async_notify_message
yield from notify_service.async_send_message(**kwargs)
File “/usr/lib/python3.4/asyncio/futures.py”, line 388, in iter
yield self # This tells Task to wait for completion.
File “/usr/lib/python3.4/asyncio/tasks.py”, line 286, in _wakeup
value = future.result()
File “/usr/lib/python3.4/asyncio/futures.py”, line 277, in result
raise self._exception
File “/usr/lib/python3.4/concurrent/futures/thread.py”, line 54, in run
result = self.fn(*self.args, **self.kwargs)
File “/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/notify/pushbullet.py”, line 93, in send_message
self.pushbullet.push_note(title, message)
File “/home/homeassistant/.homeassistant/deps/pushbullet/pushbullet.py”, line 238, in push_note
return self._push(data)
File “/home/homeassistant/.homeassistant/deps/pushbullet/pushbullet.py”, line 267, in _push
raise PushError(r.text)
pushbullet.errors.PushError: {“error”:{“code”:“invalid_request”,“type”:“invalid_request”,“message”:“Account has not been used for over a month.”,“cat”:"(=ｘェｘ=)"},“error_code”:“invalid_request”}

The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install Hass.io, HASSbian, Vagrant, or Virtualenv.

Many Thanks Mike

2

This look suspiciously like a venv

3

This says that it is a virtual environment.

This says you are using the homeassistant user.

So you are probably using hassbian. Updating instructions are here. But there will be so many breaking changes between 0.39 and now, you will spend some time updating your config.

https://home-assistant.io/docs/installation/hassbian/common-tasks/#update-home-assistant

4

Or you are using a plain virtualenv setup:

5

Ok if it’s so out of date, would i be better off doing a fresh install?
Is Hass.io the now recommended.
I would keep a copy of my configuation.yaml and then edit these into the new platform.

6

You would have to do the same work with a fresh install, so not really. Unless you want to start with a completely new configuration.

Hassio is recommended if you don’t have anything else on your pi. It is apparently easier to upgrade, which might encourage you to do it more often :grinning: Although downgrading when things go wrong doesn’t sound quite so simple.

1 Like
7

yeah, what i’m trying to figure out is assuming i get it all up and running and then it’s untouched for another year. Then in a year or so i need to add something… what’s going to be the easiest to maintain, per additions only once or twice a year. Including trying to remember all the setups etc each time.
Viz i would say i’m a typical end user vs real enthusiast, who once it’s up and running leaves it alone.

8

Probably then, if everything you do is supported by Hass.io and it’s add-ons, you’re best installing Hass.io.

It’s designed to be an “appliance like experience”. The result is that you’re much more isolated from the mechanics, which is both good and bad, but in your case probably more good than bad.

9

But on the other hand if you don’t need to update because everything is working the way you want then not using hassio night be better.

Doesn’t hassio do an automatic update without operator intervention? If that’s the case and there is a breaking change that affects your set up then you will be forced intervene to deal with the breaking changes or your system might no longer work.

Or i may be (and probably am) wrong about how hassio functions since I don’t use it.

10

No. There are some parts of the Hass.io UI that are auto-updated, but not Home Assistant itself.

11

I went with a clean install of hass.io.
Everything went smoothly (aside from… etcher frying the sd card…so had to buy a replacement. in hindsight it would have been good to do this anyways and keep the old SD as a backup (original))

My only problem is getting the z-wave door opening sensor to work:
it’s listed in Home Assistant and it’s actively being reported in the logbook

08:36
FIBARO System FGK101 Door Opening Sensor Sensor turned off
08:36
FIBARO System FGK101 Door Opening Sensor Sensor turned on

but i can’t seem to reference the correct entity_id in my automatons script.

in my old o(previous) setup it was:
entity_id: binary_sensor.fibaro_system_fgk101_door_opening_sensor_sensor_2_0

but now i can’t seem to reference it?

The states section shows:

Filter entities:
binary_sensor.sensor

Filter state:
off

Attributes:
node_id: 2
value_index: 0
value_instance: 1
value_id: 72057594076463104
old_entity_id: binary_sensor.fibaro_system_fgk101_door_opening_sensor_sensor_2_0
new_entity_id: binary_sensor.fibaro_system_fgk101_door_opening_sensor_sensor
friendly_name: FIBARO System FGK101 Door Opening Sensor Sensor

have tried: in automations.yaml:

entity_id: binary_sensor.fibaro_system_fgk101_door_opening_sensor_sensor_2_0
entity_id: binary_sensor.fibaro_system_fgk101_door_opening_sensor_sensor
entity_id: binary_sensor.sensor

have tried in configuration.yaml

zwave:
usb_path: /dev/ttyACM0

zwave:
usb_path: /dev/ttyACM0
new_entity_ids: true

but nothing works?

Home Assistant
0.64.3

Any suggestions?

12

problem solved. i just changed the name in the entity_register.yaml