[Bug] Providing upgrade to "unknown" version

[Cougar]

Describe the issue

Somehow it can't read latest version info and then suggests to do an upgrade to "unknown" version

Expected behavior

Find an actual latest version. It should also check if 6.x or 7.x version is running at the moment.

Screenshots

Software versions

• Home Assistant version: 2022.8.6
• Mikrotik Router integration version: v2.1.1
• Mikrotik Hardware: 951G-2HnD
• RouterOS version: 6.49.6

[tomaae]

I will need debugs for this.

[Cougar]

Redacted debug output is attached.

Strange is that custom_components.mikrotik_router.version is 0.0.0.

fw-update.status is ERROR: could not resolve dns name which is actually correct because these CAP clients don't have internet access. CAPsMAN controller does upgrade them. It is probably not very common case and therefore not supported so far.

config_entry-mikrotik_router-6b4a92317a5c1e4e48a77f4c04f93449.json.txt

[tomaae]

dont mind that version, that hardcoded version in manifest file.

this seems to be a shortcoming of the update integration. I have already contacted maintainer to find a standardized solution.

how is it setup that capsman controller upgrade slaves? I would like to detect such a feature, it does not make much sense to have an update sensor on slaves that have managed upgrades.

btw, those are not debugs, but diagnostics. but I understand the issue now so no need for debugs.

[Cougar]

It is not easy to detect unless you can somehow relate CAP clients with CAPsMAN. This is CAPsMAN (controller) setting

/caps-man manager upgrade-policy (none | require-same-version | suggest-same-upgrade)

[PavelD]

I had the same issue on the same model.

When I tried to check updates on the web console I got DNS error or reported no internet.

Ping was working only for local IPs and not for the external one.

The problem has been resolved when i add default gateway as /ip/route/add dst-address=0.0.0.0/0 gateway=192.168.1.1.

Anyway It seems to me as not an issue. You can always hide/disable this generated sensor. And unknown version seems to me as good value when checking is not working on the monitored system.

[tomaae]

I had the same issue on the same model.

When I tried to check updates on the web console I got DNS error or reported no internet.

Ping was working only for local IPs and not for the external one.

The problem has been resolved when i add default gateway as /ip/route/add dst-address=0.0.0.0/0 gateway=192.168.1.1.

Anyway It seems to me as not an issue. You can always hide/disable this generated sensor. And unknown version seems to me as good value when checking is not working on the monitored system.

Its different root cause. For OP's case, update should not run like this due to centralized update system.

[sermayoral]

The bug still persists.

Maybe its should control that an "unknown" version doesn't enable the update entity. Doesn't it? It's not the best solucion, but i think it's better than the actual behaviour.

[reedy]

version 2.1.4

[sermayoral]

Is not there a solution for this problem yet?? It's very annoying