Currently running Hass as a docker image (v 0.97.2) on my Synology NAS. Still a n00b, so sorry if this is a stupid question. Couldn’t really find something recent about this on the forum. Added this to configuration.yaml updater: include_used_components: true Since 0.98 is out I would have expe…

Add an entities card with the binary_sensor.updater entity.

OK, I will try that. Maybe an idea to add that info here too https://www.home-assistant.io/components/updater/ I assumed it would be automatically added like many other integrations.

Sure go for it: [Screenshot_2019-08-30%20Updater] [image] Editing the Documentation and Creating a Pull Request on Github Community Guides I have seen a number of people complain about the documentation at https://home-assistant.io/ (HA site). Great news! Everyone can…

Cool, that’s good to know. I will update it after I get it working!

Keep in mind that the sensor only updates once a day. So if you restart HA it can show as “unknown” for a day. For this reason I don’t show it in the front end and just trigger a notification when it’s state becomes ‘on’.

OK, but as you said, you first need to add the binary_sensor.updater entity before even showing up as unknown. Or should I already have a circle at the top stating unkown (which I haven’t) without adding the code?

[image] spudje: OK, but as you said, you first need to add the binary_sensor.updater entity before even showing up as unknown. Correct. Just thought I’d mention it in case you thought it wasn’t working when you saw ‘unknown’.

Updater doesn’t work as it should be, there is a new update since yesterday and it has not changed state. Seems to me that the problem is the web address against which he campares the version of HA, It still shows 0.98.1. [image]

So I got everything setup in terms of sensors etc, so my lovelace is fully populated. So now I can start edit the lovelace config. I still don’t understand how to get this to work. I have the updater in my configuration.yaml as top level entity, but no binary_sensor.updater shows up in the develope…

Not sure where I should ask this. Homeassistant 0.100 has bean released for a few days by now, but https://updater.home-assistant.io (and thus the updater-component) still show 0.99.3 as the newest version. If the release on that page isn’t updated, the updater component is rather useless.

Updater component not working, what am I doing wrong?

Configuration

tom_l August 30, 2019, 6:57am 4

Sure go for it: