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

Neither. It wasn’t updated to latest version on the server side. It’s now been updated.

1 Like

Should updater.updater be showing up in states as an entity? The update notification hasn’t worked for me and I don’t have a updater.updater in as an entity

that was easy!

I have it as an entity in my default view, but I’m still not seeing the update.

Fortunately I built my own sensor to report the version numbers so I can see there is one available. I always rely on this.

-  platform: command_line
   command: python3 -c "import requests; print(requests.get('https://pypi.python.org/pypi/homeassistant/json').json()['info']['version'])"
   name: Current HA Version

-  platform: command_line
   name: Installed version
   command: "/srv/hass/hass_venv/bin/hass --version"

If i’m right, the updater runs 1 hour after HA start and then every day at the same time.
-> /srv/homeassi/lib/python3.4/site-packages/homeassistant/components/updater.py

    # Update daily, start 1 hour after startup
    _dt = datetime.now() + timedelta(hours=1)

If you can’t wait, change to 1 or 2 minutes.

    _dt = datetime.now() + timedelta(minutes=1)

and restart HA.

When your loglevel is debug,

logger:
  default: warn
  logs:
    homeassistant.components.updater: debug

you would see something like this:

17-04-21 00:57:30 INFO (Thread-6) [homeassistant.components.updater] Submitted analytics to Home Assistant servers. Information submitted includes {‘uuid’: ‘dontknowyoushouldsee’, ‘timezone’: ‘Europe/Berlin’, ‘os_version’: ‘12.04’, ‘arch’: ‘x86_64’, ‘python_version’: ‘3.4.5’, ‘dev’: False, ‘distribution’: ‘ubuntu’, ‘os_name’: ‘Linux’, ‘virtualenv’: True, ‘docker’: False, ‘version’: ‘0.42.4’}
17-04-21 00:57:30 INFO (Thread-6) [homeassistant.components.updater] You are on the latest version (0.42.4) of Home Assistant

The last line (You are on the latest version) missed before robbiet480`s fix.

If an update is available, the entity updater.updater gets populated and i think we should see our notifications.

Can’t wait for the next! :yum:

1 Like

You can use these sensors as an updater replacement, just include this:

sensor.hass_update_available

Wherever you want to check if an update is available.

(Modify '/usr/local/bin/hass' to reflect your binary location)

##################################################################
### Current HASS Version
###################################################################
- platform: command_line
  command: python3 -c "import requests; print(requests.get('https://pypi.python.org/pypi/homeassistant/json').json()['info']['version'])"
  name: Current HASS Version

##################################################################
### Installed HASS Version
###################################################################
-  platform: command_line
   command: "/usr/local/bin/hass --version"
   name: Installed HASS Version

##################################################################
### HASS Update Available
###################################################################
- platform: template
  sensors:
    hass_update_available:
      friendly_name: 'HASS Update Available'
      value_template: >-
        {%- if states.sensor.current_hass_version.state != states.sensor.installed_hass_version.state -%}
           {{ states.sensor.current_hass_version.state }}
        {%- else -%}
           No
        {%- endif -%}
5 Likes

@VDRainer – Thanks, I kept meaning to check updater.py to see when the updater.updater is scheduled to check for new versions.

The if logic has been updated because it didn’t work with dev versions.

Awesome, received the notification this morning. Appears to be working again!

Thank you!

@robbiet480, in 0.44 the line is missing once again. [quote=“robbiet480, post:5, topic:15936”]
It wasn’t updated to latest version on the server side.
[/quote]

Yep, now updated, was waiting for any major bugs to be found. Thanks for the reminder!

Is this broken again? I’ve used the automation in the docs and it’s been 2 versions now with no updates.

I was on 0.47.1 and got notified when 0.48 was released.

I haven’t had a notification in about 7 or 8 versions tbh

I’m going to start triggering the notification based on whether the installed version is lower than the version online. (like in Post 10 above).

Updater component is too unreliable (and appears, based on this conversation, to not be automated).

I have an automation rule setup and I got for .48.

This is what I have. Should I just delete the automation copied from the docs and use the ones above?

  - alias: 'update available'
    trigger:
      platform: state
      entity_id: updater.updater
    action:
      service: notify.notify
      data:
        message: "Update for Home Assistant is available"

What is your notify.notify? For example I had to change it to notify.pushover to make it work. I then had to configure pushover.

It hasn’t shown an update notification for me for quite a while.

I think I’ll also try one of the alternatives above.

That’s what I will be doing.

If you are running HASSbian image use sensors below

  - platform: command_line
    command: python3 -c "import requests; print(requests.get('https://pypi.pyth$
    name: Current HA Version

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