Add "entity id's" to generated sensors ?

[SteffanH]

No idea if this at all possible, but I would like to be able to assign all generated sensors to the Area where the original enitity belongs, but this is not possible because there are no unique entity_ids associated:

This entity ('sensor.<light>_energy_daily') does not have a unique ID, 
therefore its settings cannot be managed from the UI. 
See the documentation for more detail.

[bramstroker]

When the source entity has a unique id powercalc should give the power and energy sensor a similar unique id.
So in your case I suspect light.<light> also doesn't have a unique id. Could you check that?

When the source entity does not have a unique id powercalc cannot create a unique id for it. As the unique id always need to be the same (for example MAC address). name and/or entity_id cannot be used as a unique id in Home Assistant.

[SteffanH]

Hi!

The light.<light> is a Hue lamp that's made available through the Hue integration and it does seem to have a unique id, as I can assign it to an Area.

How can I verify this is actually the case ?

FWIW, the sensor.<light>_powersensor and sensor.<light>_energy sensors do indeed have unique id's assigned, as I was able to assign those to the correct Area

[bramstroker]

Yes, the utlity_meters don't have a unique id. Also see home-assistant/core#22970.
I will see what I can do.

[bramstroker]

Was able to do it. Have been merged into master. When the energy sensor has a unique_id, the utility meters will also have a unique_id.
Are you able to test with master branch?

[SteffanH]

Yes, will do.

[SteffanH]

Confirmed.
The sensor that prompted me to create this issue now has a unique_id, enabling assignment to an Area!

Thanks.

[bramstroker]

great, will release today or tomorrow in a new version

[SteffanH]

Not sure if this was already present (didn't check 🤦‍♂️) but after updating to 0.14.1 my daily/weekly/monthly powercalc sensors have now duplicated, with the original ones being listed as "Unavailable".
The 'history' graphs for the new ones start graphing right after the upgrade.

And, the new ones no longer have the unique id ?

[bramstroker]

Hmm very strange, must have been caused by the change regarding the unique_id. Need to have a look into this. Hope I will be able to reproduce it.
Do you have a screenshot of both sensors?

[SteffanH]

Not exactly sure what you'd like to see, but here goes
Two sensors

new (note the _2)


and old

[bramstroker]

I have no clue why this happens yet. I am unable to reproduce on my development instance.
I tried one thing to resolve it. Released in v0.15.0-beta.1. However I'm unsure if this solves your issue. At least you could give it a try.

[SteffanH]

That fixed it, all the _2 sensors are gone.
Also the option to select an Area is back again.

Thanks

[bramstroker]

Great. Hope it stays that way ;-)