Diogo Gomes

It is not working :/ I though this could be a quick fix, but by working on a test I've realised the `device_id` does not get set: ``` RegistryEntry(entity_id='select.energy', unique_id='my_unique_id',...

This would take an architectural change to work for which I don't have the time at the moment. The author of the issue has dismissed the issue, and I'm therefore...

This is related to https://github.com/home-assistant/core/pull/119761

@dougiteixeira only applies to utility_meters setup using config_entry

> > @dougiteixeira only applies to utility_meters setup using config_entry > > No, entities created via YAML also appear in the "Helpers" tab. They appear, but since they are not...

> One way around this is to return the attributes for entities created by YAML, [but exclude those attributes from the recorder](https://developers.home-assistant.io/docs/core/entity/#excluding-state-attributes-from-recorder-history). If makes no sense, they used to be...

I think we might need to close this issue as not supported :(

I'm struggling with a similar use case (sensor vs calendar) The calendar has the benefit of conveying future information as the sensor will only show current values. If I want...

looking into this issue before submitting yet another integration tracking tariff using a calendar entity.

> Or maybe this is not the last state of the utility meter but the last state of the input sensor? precisely: https://github.com/home-assistant/core/blob/1e14fb6dab4cfde1a1605addff327f821f2d5cd9/homeassistant/components/utility_meter/sensor.py#L526C34-L526C47 This value is kept to recover utility...