Names and device

[kifort]

First of all: thanks for your great project.
In "both" mode, I see 78 wemportal entities and I am bit lost between them. Some of them are in german, some in english due to issue #22. Some of them have a prefix of "heat_pump", "heating_circuits" or "wez", others have none of these.
Could you maybe add a "Heat Pump" device? That would allow to add all entities to an area in one step. Also all sensors or all controls could be added to a dashboard in one step.
Otherwise, I suggest to add some common entity prefixes that can be used in entity filtering of the lovelace cards. Something like:

• wem_
• wem_web
• wem_api

[dm82m]

We are using the default names we get from wemportal api or Web. If you want you can just go ahead and rename your entities however you prefer.

[erikkastelec]

Fixing naming is quite hard in this case. By dynamically combining data from API and website there are a lot of naming conflicts, which can't be resolved with simple logic. To get everything fixed I would probably need to hard code a lot of things. There is also the problem with different devices having different entities and settings, which complicates this further. For now, I will focus on improving the functionality and leave the naming when everything else works sufficiently well.

Some of them have a prefix of "heat_pump", "heating_circuits" or "wez", others have none of these.

Prefixes are used for entities that are scraped from the WEM portal website. Prefixes are the categories that can be seen on the website and are there to help you narrow down what the entity name actually means.

Could you maybe add a "Heat Pump" device?

This sounds like a good idea. Will add this, but can't provide an accurate time frame.

Otherwise, I suggest to add some common entity prefixes that can be used in entity filtering of the lovelace cards. Something like:

I think that Home Assistant developers discourage this. Grouping the entities into a device should solve this anyway.

[kifort]

Thank you both for the quick answer. I fully agree, that device is the right thing. Once it comes naming won't be a big issue anymore.

"Could you maybe add a "Heat Pump" device?
This sounds like a good idea. Will add this, but can't provide an accurate time frame."

Should I leave this ticket open for "Heat Pump" device, or close it and create a new one?

[erikkastelec]

You can leave it open

[erikkastelec]

Device support is finally here and should be released soon after I test it out.

If anyone is interested in testing:

• Put all the files from /custom_conponents/wemportal/ that are in dev branch into homeassistat_config/custom_components/wemportal folder on your server.
• Add new integration inside Home Assistant frontend (yaml support is deprecated)

[dm82m]

Is there anything we need to know if we Test it. Any migration steps needed? Or just straight forward?

[erikkastelec]

It will probably brake names of entities ( append 2 at the end because entity with that name already exists). Other than that everything should work fine.

[dm82m]

And will brake history aswell, right? Maybe we should think about an entity migration so that people are not losing their history!?

[dm82m]

Maybe something like we did here: dm82m/hass-Deltasol-KM2@9a500f3

[erikkastelec]

Looks good, will add this.

[dm82m]

migration seems not to work, I tried the dev branch on a clean install. started with current released version and then migrated to dev branch. old sensors will get state "restored" and new sensors are created. maybe this has something to do with changing from yaml config to config flow? not sure tbh.

I also get no info logs about entity migration, I guess something is not good there.

[erikkastelec]

Interesting, I did the same and it worked. Will spin up a new instance, see if I can reproduce this and keep you posted.