Where is `updater.updater` entity?

Some time ago, I remember using the updater component and it worked nicely.

However, I recently checked and, although I have the updater: line in my configuration, I cannot find any updater.updater entity. The documentation says that I can use that entity to show things when an update is available, for instance, or show some information on the frontend… but that is not possible.

Am I missing something? Is that component deprecated? Is the documentation not up-to-date?

Do you have errors in the logs? Component is alive and well and the entity is updater.updater. So we have to assume that the component didn’t start up properly. Sidebar, you did restart after adding it in your config, correct?

I overlooked this

Got unexpected response: None

Now I see that I am not the first one: Updater - Got unexpected response: None

And maybe it is the same as: Updater Dont Work · Issue #18301 · home-assistant/core · GitHub

However, @petro do you have 0.83? Do you have any explicit configuration, or simply the updater: line in your configuration?

My updater component hasn’t worked for several months now. Not just since the latest version.

I don’t think I ever really got to the bottom of it so I just stole some config code posted by another member that works really well and gave up on the updater component.

I’m not running updater. I just looked at the code and verified that it was the same to let you know that output hasn’t changed. It’s entirely possible that the component is broken as @finity eluded to.

I could be wrong, but I feel like I’ve noticed this before and the entity WILL end up appearing. But only when there is an active update available. And even then it takes some time to refresh and actually show one available.

If you are currently at the latest build, I’d wait for 0.84 and then give it a day to see if the entity shows up.

Here’s what I’ve noticed: when I first boot up HA, I get

Entity not available: updater.updater

But if I wait a few hours, then it appears. Anyone know if that a known limitation or a bug?

Yeh its one of those strange ones that only exists if there is an update … once the update is applied, it no longer exists.