search

tomaae / homeassistant-truenas

TrueNAS integration for Home Assistant
Apache License 2.0
183 stars 16 forks source link

[Bug] - home assistant continuously reports that an update available #160

Open muddro1 opened 3 months ago

muddro1 commented 3 months ago

After upgrading to dragon fish 24.04.1, HA still reports an update available. Seems the naming convention is off.

Screenshot_20240528-142459

slovdahl commented 2 months ago

I also saw a repair for a TrueNAS update today with no update actually being available. But it's gone now without me doing anything about it. I think it said that the version to update to is "unknown" or something like that. Running CORE, version TrueNAS-13.0-U6.1. Integration version 1.3b2.

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

slovdahl commented 1 month ago

Still seeing the occasional repair saying an update is available.

jpettitt commented 3 weeks ago

Looks like if the version comes back unknown (like just after a home assistant restart) it reports an update available becasue unknown != <the latest version>. Once the running version becomes available the update warning clears on my system.

github-actions[bot] commented 1 week ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

slovdahl commented 1 week ago

I tried to read the code a bit and I get the feeling these unknown instances are defaults defined in code in the integration, and are just used as placeholders until something is actually returned from TrueNAS. Should unavailable be used instead @tomaae?

tomaae commented 1 week ago

no, unavailable is an entity state. that would just make it confusing. it would be best if entities could be in unavailable state until first cycle is finished, but that may not be possible in current implementation.