Naming Convention for new BALANCE sensors

[robtheone]

I noticed the new BALANCE sensors this morning, which is great. Would it be possible to make an enhancement request in a future update to have them name themselves in the same manner as other sensors?

sensor.power_balance_{Device_Id}_{Channel_Id}

The channel ID may not be needed, but the Device_ID would be VERY helpful since I have 3 Emporia Systems on my account. Currently on home assistant, they are being named as follows, on the 1 day sensors for example:

sensor.power_balance_balance_1d sensor.power_balance_balance_1d_2 sensor.power_balance_balance_1d_3

and there is no way to distinguish from which device the sensors are coming from. I normally can see the name used in the Emporia app in the Entity_ID field, but that isn't the case with these sensors. I can figure it out and rename them, but having the name in the entity_ID field will be helpful in identification.

I can see the logs showing the sensors being added with the device_gid: [custom_components.emporia_vue] Adding channel for channel 19111-Balance [custom_components.emporia_vue] Adding channel for channel 39222-Balance [custom_components.emporia_vue] Adding channel for channel 39333-Balance

and when sensor data is pulled into HA, the device ID's are also visible: 19111-Balance-1MIN': {'device_gid': 19111, 'channel_num': 'Balance', 'usage':

Also unclear WHY the word balance is being used twice, _balance_balance as it seems redundant. sensor.power_balance_balance_1d

Thanks for all your work. It has been awesome having this data available in Home Assistant.

[magico13]

Copying my reply from the other issue:

I agree that the balance sensor naming is unfortunate. The normal naming scheme is "Power {Name} {ChannelNum} {Scale}" and for the balance sensors the Name and ChannelNum are both "Balance". The internal unique id is built off the device id and the channel number which ensures uniqueness.

What you can do without changes is figure out which is which and rename the sensors within Home Assistant to something more useful. I can look into handling Balance as a special case, separate from the normal naming scheme, so the name would include the name of the Vue that it's associated with.