v2.7.0 release, the model column

[TexTown]

In the latest release notes, I read this:

"ECU and inverter models are now explicitly displayed in the Model column. ℹ️ For this to be effective you need to remove the Hubs, restart Home Assistant and add the Hub(s) back. You will not lose any historical data on the entities by doing this. Historical data on the entities will only be lost if you actually remove the integration via HACS."

I'm still runnig the older version, but already see model information:

How is this different in v2.7.0 ? (I'm a little hesitant about removing and re-adding the ECU from the config. So I would like to see how model information appears after performing these steps.

[HAEdwin]

Model "ECU_R_1.2.31" is a representation of the firmware version. The new release displays it like:

In you case just "ECU-R"
and like so:

This is the correct way to present the models.
Removing the hubs does not remove the integration from the custom_components folder. Also the entities will remain in place in the database but not on the UI (hence the warning). When you add the integration again the same entities will appear in the UI and mapped to the entities in the database.

[TexTown]

This looks much better indeed, good work.

What exactly do you mean by removing 'hubs'? Would that be all the devices used by the integration? Or the integration itself?

[HAEdwin]

Like so:

A hub is a collector of things, at the head of the hub is of course the ECU which collects data from the inverters.
Removing a hub does not delete the entities from the database, it does delete them from the UI.
Removing the integration using HACS does remove the sources and the entities from the database (so don't if you want to keep history!)

[TexTown]

Ah, indeed.
Seems that every integration can have its own naming of that section. Some are called 'Sevices' , some 'Integration entities', some 'Devices'. I never notices this part was named 'Hubs' in this integration.

[c0mplex1]

[HAEdwin]

That's right! It is specified in the integrations manifest just like the IoT class. It is an architectural definition.

[TexTown]

Strange, I was about to remove the Hub in order to get the good Model values, but it is already OK.
Simply upgrading to 2.7.0 and a reboot results into:

Looks good to me

[TexTown]

@HAEdwin , might have been a frontend cache issue that showed the wrong/old Model values after the update?
Maybe someone who still needs to upgrade can confirm this is a cache issue and the Hub removal and re-add is not required after all, simply clearing the browser cache?