Updater advice please

Configuration
1

Hiya,

I used to use the updater binary sensor component but I found that it wasn’t updating frequently enough for my liking.

I switched to using the rest platform using the sensor below which seemed to be working out well.

- platform: rest
  name: Home Assistant Latest Release
  resource: https://updater.home-assistant.io/
  json_attributes:
    - version
    - release-notes
  scan_interval: 3600
  value_template: '{{ value_json }}'

Since. 0.114.3 I noticed that my sensor seemed stuck. When I took a look though, it seems that https://updater.home-assistant.io/ hasn’t yet been updated to point to 0.114.3.

{"release-notes":"https://www.home-assistant.io/latest-release-notes/","version":"0.114.2"}

My question is this … there seem to be pro’s and con’s each way, but is there a better approach to get an accurate and timely updater that either of the above?

Thanks in advance!

2

This is what I use:

Sensors:

- platform: version
  name: Current Version
  image: intel-nuc    ### Adjust for your system, see https://www.home-assistant.io/integrations/version/
  source: local

- platform: version
  name: Latest Version
  image: intel-nuc    ### Adjust for your system, see https://www.home-assistant.io/integrations/version/
  source: hassio

Automation:

- id: update_available
  alias: 'Update Available'
  trigger:
    platform: template
    value_template: "{{ states('sensor.latest_version') != states('sensor.current_version') }}"   
  action:
  - service: notify.telegram_system
    data_template:
      title: '*Information*'
      message: "An update for Home Assistant is available. You are running {{states('sensor.current_version') }}, the latest version is {{ states('sensor.latest_version') }}."
3

Great, thanks @tom_l - I love seeing that there are so many ways of doing it! lol
I’m giving yours a shot and will see how I get on. Have a great day!