Is updater not working for anyone else lately? Haven't gotten notifications for the last few updates

Thanks, that works for me too!

Bob - will that work with an all-in-one installation on raspbian?

I donā€™t know why that sensor doesnā€™t work for, seems strange. Thankfully fanaticDavidā€™s version works for me.

Iā€™m using the AIO install with Rasbian Stretch. Hereā€™s what works for me:

sensor:

- platform: rest
  name: "HASS Current Version"
  resource: https://pypi.python.org/pypi/homeassistant/json
  value_template: '{{ value_json.info.version }}'
  scan_interval: 3600

- platform: command_line
  name: "HASS Installed version"
  command: "head -5 /home/homeassistant/.homeassistant/.HA_VERSION"

- platform: template
  sensors:
    hass_update_available:
      friendly_name: "Update Available"
      value_template: >-
        {%- if states.hass_current_version.state != states.hass_installed_version.state -%}
           {{ states.hass_current_version.state }}
        {%- else -%}
           No
        {%- endif -%}

I've added the automation but, as we haven't had an update yet I can't tell if that works (although the code looks OK so I can't see a reason why it wouldn't).
1 Like

Yes, Iā€™m running the all-in-one myself.

Jono - what is your automation? Iā€™m also on Stretch and AIOā€¦

Thanks Bob

I added this one yesterday, but it didnā€™t work after the new update came out:

automation:

- alias: Update Available
  trigger:
    - platform: state
      entity_id: sensor.hass_current_version
  condition:
    - condition: template
      value_template: '{{ states.hass_current_version.state != states.hass_installed_version.state }}'
  action:
    - service: notify.ios_jonos_iphone
      data:
        title: 'Home Assistant Update'
        message: "Home Assistant {{ states.sensor.hass_current_version.state }} is now available"

But the old one I had setup but hadn't been working for a while **did** work:

automation:

- alias: "Home Assistant Update Notifications"
  trigger:
  - platform: state
    entity_id: updater.updater
  action:
    - service: notify.ios_jonos_iphone
      data:
        title: "Home Assistant"
        message: "New release available"

[EDIT]

I realised I forgot to add the ā€˜sensorā€™ part in the first automation. This should work:

automation:

- alias: Update Available
  trigger:
    - platform: state
      entity_id: sensor.hass_current_version
  condition:
    - condition: template
      value_template: '{{ states.sensor.hass_current_version.state != states.sensor.hass_installed_version.state }}'
  action:
    - service: notify.ios_jonos_iphone
      data:
        title: 'Home Assistant Update'
        message: "Home Assistant {{ states.sensor.hass_current_version.state }} is now available"

[/EDIT]

So I tried entering this. It looks different in my automations.yamlā€¦

- action:
  - data:
      message: Home Assistant {{ states.sensor.hass_current_version.state }} is now
        available
      title: Home Assistant Update
    service: notify.notify
  alias: Update Available
  condition:
  - condition: template
    value_template: '{{ states.sensor.hass_current_version.state != states.sensor.hass_installed_version.state
      }}'
  id: '1509933513624'
  trigger:
  - entity_id: sensor.hass_current_version
    platform: state

Have I done something wrong or should this work OK?

I just cut and pasted yours in the automations file and now it looks like yours with the addition of the ID. I guess we will see if it works or not on the next update. I used notify.notify as I donā€™t have multiple devices.

Since I fixed the first one it worked at sending a notification for the 0.57.2 update.

Iā€™ve just changed over to the Hass.io platform on a RPi3 and even though the sensors show:
current: 0.57.3
installed 0.57.2
It says Update is not available.

If I click on Hass.io from the hamburger menu it also shows no update.
The advanced settings menu under hass.io says installed and available is 0.57.2 so I guess I need to just remain patient for a day or so and wait for it to tick over. Itā€™s killing me not just forcing an update by restarting the Pi or running the ssh commandā€¦

The sensors are pointing to the AIO version of Home Assistant (and referring to new versions of AIO Home Assistant), not Hass.io (I think), even though they might have the same or similar version numbers.

I guess youā€™d need to ask in the Hass.io section of the forums on this.

Well I think youā€™re right. The Sensor is still saying no update is available; the current version and available are showing the update and correct current. The Hamburger>Hassio shows a button to update today so Iā€™ā€™ā€™ just delete the automation which didnā€™t and the update available sensor.

hello @DavidFW1960 did you solve your problem with hassio? i would like use that automation,

I have a package that finds the latest version and has an update automation in it but I donā€™t really use it because I always tend to update before the version is ā€˜pushedā€™ You can see my package here on github Note I am using a generic linux install now on an Intel NUC so you might need to edit the platform you want information about in the sensors section.

1 Like

@DavidFW1960 thanks , i saw you package and i dont understand this:

  - platform: rest
    resource: https://s3.amazonaws.com/hassio-version/stable.json
    name: Hass Current HassOS Version
    scan_interval: 7200
    value_template: "{{ value_json.hassos['rpi3-64'] }}" 

If you see on resource -> https://s3.amazonaws.com/hassio-version/stable.json
The value json for hassos[ā€˜rpi3-64ā€™] is rpi3-64: "1.12

So, did you sure that this automation, works fine?

That is the HassOS versionā€¦ 1.12 it isnā€™t Home Assistant Version which is currently 0.81.2. If I was running HassOS it would tell me the latest.

Hi @jono, is this automation working for you?

I donā€™t use it anymore.

Iā€™m using HA in a Docker container, and that updates automatically so I never really bother about it anymore. I do show a sensor in HA though, just to let me know what version Iā€™m using :blush: