core: binary_sensor.updater not working
The problem
I have the automation for the binary_sensor.updater sending me a message when a new OS is ready. The binary_sensor.update has not worked for the past year.
Suddenly it worked for OS version 0.107.3 (or was it version 0.107.2?).
Then the binary_sensor.updater stoped working for the upcoming versions, latest 0.107.5.
Environment
Home Assistant 0.107.5
| arch | armv7l |
|---|---|
| dev | false |
| docker | true |
| hassio | true |
| os_name | Linux |
| os_version | 4.19.106-v7 |
| python_version | 3.7.7 |
| timezone | Europe/Oslo |
| version | 0.107.5 |
| virtualenv | false |
- Home Assistant release with the issue:
- Last working Home Assistant release (if known):
- Operating environment (Hass.io/Docker/Windows/etc.):
- Integration causing this issue:
- Link to integration documentation on our website:
Problem-relevant configuration.yaml
Traceback/Error logs
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 69 (16 by maintainers)
I suspect that the problem has to do with this line of code: https://github.com/home-assistant/core/blob/34b911203cfcaa34080012d829d5950b57ec7ff4/homeassistant/components/updater/__init__.py#L81
if I’ve understood everything correctly, this line finally ends up in the supervisor code:
https://github.com/home-assistant/supervisor/blob/7a1af3d346dfd60a5d4e51d3ebd1d8a81f1caca1/supervisor/api/info.py#L34
… and returns the current version => the update available check will never return true as it compares always the same versions (see lines 84ff in the linked file https://github.com/home-assistant/core/blob/dev/homeassistant/components/updater/__init__.py)
But these are just guesses, which have to be validated by a dev.
I’m getting the same issue. The system definitely knows there’s an update available as it’s prompting me to update to 0.112.1, but binary_sensor.updater is set to false with it claiming the newest version is 0.112.0. Haven’t seen that sensor come on in 2-3 major versions.
With the last update has been working for a while. Minutes later, again the same problem, the sensors didn’t update the state 😦
El vie., 30 oct. 2020 17:54, brianm71 notifications@github.com escribió:
might be not for this issue, but I do think most people’s expectations for an update sensor, be it core at that, would be that it reports, per direct on the occasion. This binary_sensor.updater does nothing of the sorts, and even if operating per design (as it now seems to be doing again) reports once every 24 hours? why not make that happen every hour… would that hurt the servers that much?
Seems silly one needs to add secondary sensors for the instance to be reported an update is available.
There was a fix in 0.114.0 but it required further work.
There was a change to the max number if workers in 0.114.1 that may have helped. We won’t really know until 0.114.2 is out though since you have to be running 0.114.1 already.
I tried this and, while the binary sensor did update, it did not update correctly. It changed from “Unavailable” to “Off”. when I know there are newer versions available. That tells me that the sensor is updating from somewhere other than the true source. Even after forcing it to update yseterday, it still hasn’t updated itself.
@svh1985 Until this issue is resolved, maybe you can use the service «homeassistant.update_entity» in an automation for updating the binary sensor? https://www.home-assistant.io/docs/scripts/service-calls/#homeassistant-services