Home Assistant is Home Assistant no matter what OS supports it. Hass.io is just Home Assistant running inside a Docker on ResinOS. So, the links I posted works for Hassio too. What specific documentation do you need?
Yes, I understand.
Hass.io is a thing. Does it have a version number? Is there documentation about each release or update to it? Is there documentation about how to use it and manage it? Perhaps I should not have said “HA/Hass.io” in the title of my post as that seems to have caused confusion. I’m asking about managing Hass.io and documentation about that.
Open Home Assistant. On the left menu select Hass.io, click the three dots on the top left and choose Advanced Settings. There you’ll see a card named Host OS, Hass.io version is what appears after Host Control version (currently 1.1). Is there is an update the Latest available version will be higher number.
About the Hass.io releases you can have a look in Releases · home-assistant/hassio-build · GitHub. You have there the links to the image download and a small list of changes.
But, in my opinion, there is no Hass.io per se. It is a “thing” like you said. There is Home Assistant and ResinOS. So if you want to manage anything, it will be ResinOS.
On the website there is lots of documentation. Getting Started Docs for 18 different systems, with step-by-step information.
Hope this helps!
To get HA current version, use this sensor:
#### HA Version
- platform: command_line
name: "HA ver."
command: "cat .HA_VERSION"
To be notified of new versions, use this automation:
#### CHECK FOR SYSTEM UPDATES
- alias: 'Update Notifications'
initial_state: 'on'
trigger:
platform: state
entity_id: updater.updater
action:
- service: notify.browser_alerts
data_template:
title: '{{ as_timestamp (now()) | timestamp_custom("%d/%b/%Y %T") }}'
message: 'New Home Assistant version available!'
data:
renotify: '1'
Remember that this notification is for the “general” HA version, Hassio version will be available about 48 hour after…
1 Like
Awesome. I was not related (for some stupid reason) “Host OS” as Hass.io and the underlying ResinOS. Thanks for persisting with me and for the link to the release notes. That’s exactly what I couldn’t find.
I haven’t done much with notifications yet, so I’ll take a look at your code and maybe use that to get me started.
Thanks again.
1 Like
Your welcome!
If you connect to the system via the SSH addon, you have restricted access to the command line but you have a few commands specific to Hass.io. When i type the command hassio ha info i get:
{
"result": "ok",
"data": {
"version": "0.60.1",
"last_version": "0.60.1",
"image": "homeassistant/raspberrypi3-homeassistant",
"custom": false,
"boot": true,
"port": 8123,
"ssl": true,
"watchdog": true
}
}
This is JSON and using platform: command_line and a template you can get info to use in automations.
Ok. here goes.
Because i was trying to check whether we could delete older snapshots from within Hassio, i unwantedly clicked a backup which was hence executed.
(why is there no confirmation button in that process…)
luckily i had just copied al my config files the night before, so i copied those back again, resulting in the odd error which isnt too bad considering.
My Threshold binary sensors won’t work anymore though, and that reminded me of the exact same error message i got before when updating to 0.61.1 and the format of those sensors had changed. So checking the hassio version indeed shows my restores backup was from 0.60.1, the version not recognizing the newer threshold sensors.
Simple, click Hassio, see a new version is available and click update. I thought. Unfortunately thats errors out with an unknown error in the frontend. Checking the advanced settings shows the same available update, and gives the same error:
Any thought on how to update Hassio, maybe from the ssh terminal command-line? Ive tried this, but unfortunately no succes:
core-ssh:~# hassio ha update
{
“result”: “error”,
“message”: null
}
Appreciate your help.
Thanks,.
Marius
This question is not related to the initial post. Please open another thread.
It is exactly that.
I am trying to update my Hassio back again , checking for available versions to do so and manage updates in the various available methods.
Managed to get back to 0.61 via the Curl command but it won’t update to 0.61.1 like that or the Hassio updater.
I use the following to ascertain current version of Hass.io (running on a RPi3), and the latest available version, and then to send an alert when a new version is available. Please note that this works for the release of Hass.io updates, and not for the general release. I think that is what people were asking for was it not?
##sensors.yaml file
- platform: rest
resource: https://raw.githubusercontent.com/home-assistant/hassio/dev/version.json
name: HA Latest Version
value_template: '{{ value_json.homeassistant }}'
- platform: version
name: HA Installed Version
- platform: template
sensors:
ha_update_available:
friendly_name: 'HA Update Available'
value_template: >-
{%- if states.sensor.ha_latest_version.state != states.sensor.ha_installed_version.state -%}
Yes
{%- else -%}
No
{%- endif -%}
icon_template: >-
{%- if states.sensor.ha_latest_version.state != states.sensor.ha_installed_version.state -%}
mdi:alert-box
{% else %}
mdi:approval
{% endif %}
## automations.yaml
- alias: Update Notification
action:
- data:
message: "New Home Assistant version {{ states.sensor.ha_latest_version.state}}\
\ is available for download.\r\n\r\nYou are currently running {{ states.sensor.ha_installed_version.state}}.\r\
\n\r\nhttps://home-assistant.io/blog/categories/release-notes/"
title: New Home Assistant version
service: notify.my_email
condition: []
id: '1515492307283'
trigger:
- entity_id: sensor.ha_update_available
from: 'No'
platform: state
to: 'Yes'
2 Likes
A couple of false positives over the last 48 hours, caused by the REST sensor returning “unavailable” for one reason for another (could be my internet connection or the webpage itself … not really sure). Updated the template sensor for “HA Update Available” to check for this.
- platform: template
sensors:
ha_update_available:
friendly_name: 'HA Update Available'
value_template: >-
{%- if states.sensor.ha_latest_version.state != "unavailable" and states.sensor.ha_latest_version.state != states.sensor.ha_installed_version.state -%}
Yes
{%- else -%}
No
{%- endif -%}
icon_template: >-
{%- if states.sensor.ha_latest_version.state != "unavailable" and states.sensor.ha_latest_version.state != states.sensor.ha_installed_version.state -%}
mdi:alert-box
{% else %}
mdi:approval
{% endif %}
1 Like
Yeah this was also driving me crazy - the notifications - so I had already added that condition to my notifications. Thanks for this though. Works great.
… and back to the drawing board on this one.
Due to the way updates are not being “staged” to be betas for a week before becoming “stable” releases, my sensors are reporting a new version when there in fact is no update.
Current sensor is returning 0.66.0.b2 when the latest hassio stable release is in fact 0.65.6
same but I fixed it with a new condition in my automation (to turn off the notifications). You can amend the sensor in config l guess.
- alias: Update Available
trigger:
- entity_id: sensor.hass_current_version
platform: state
condition:
- condition: template
value_template: '{{ states.sensor.hass_current_version.state != "unavailable"
and "b" not in states.sensor.hass_current_version.state and states.sensor.hass_current_version.state
!= states.sensor.hass_installed_version.state }}'
action:
- data:
message: Home Assistant {{ states.sensor.hass_current_version.state }} is now
available
title: Home Assistant Update
service: notify.notify
2 Likes
Great idea. I modified my template sensor to look as follows:-
- platform: template
sensors:
ha_update_available:
friendly_name: 'HA Update Available'
value_template: >-
{%- if states.sensor.ha_latest_version.state != "unavailable" -%}
{%- if states.sensor.ha_latest_version.state != states.sensor.ha_installed_version.state and "b" not in states.sensor.ha_latest_version.state -%}
Yes
{%- else -%}
No
{%- endif -%}
{%- endif -%}
I won’t know for sure that the sensor and resulting alerts are working until the next update becomes available. Should work though.
Thanks for the idea to test for the “b” in the latest version … much appreciated.
1 Like
@aheath, @DavidFW1960
Hey guys,
Great ideas, but not what this original thread was about. You may want to start a new thread.
This is a nice enhancement, Thanks! The only thing I am trying to play with is the ability to get a repeating notification if I restart HA. For example, I see there is currently an update available for me but it will not trigger the notification because it’s not changing the state from No to Yes when I restarted HA because it is already Yes. So is there a way to maybe change the default state to “No” when HA restarts to have it change to “Yes” and then trigger the automation?
This was great while it lasted but “https://raw.githubusercontent.com/home-assistant/hassio/dev/version.json” no longer gives current version of hassio.
This is how the current json files provides ‘{“hassio”: “105”, “homeassistant”: “0.70.0”}’, but the current version is actually 0.71.0.
Nm, I found your new topic Wrong Version Showing? with updated link: https://s3.amazonaws.com/hassio-version/stable.json
Is this advanced feature still available? I don’t see it on my hassio