Utility Helper units

Energy
1

I have created two Utility Meters Helper with three supported tariffs for ‘peak’, ‘offpeak’ and ‘standard’ tariffs. One for import and one for export. They are linked to a sensor exposed by a GivEnergyTCP integration which reports energy (i.,e. kWh).
When the helpers were created, they created three sensors each for the three tariffs. It seemed all was well.

However when I check the sensors in the Developer Tools> Statistics, although the three import sensors for the three tariffs show the unit as kWh, foe the export sensors, only the peak tariff is showing with a unit kWh. The standard and offpeak unit is not showing any unit. As such I cant add them to the Energy dashboard.

Is this because they have not detected any export during that tariff period and I need to wait or is there something else going on?

Is there a way to set the unit so I can add them to the Energy dashboard?

2

In configuration.yaml add

homeassistant:
  customize: !include customize.yaml

then add a file named customize.yaml and there add each missing sensor like this

sensor.blablabla:
  device_class: "energy"
  state_class: "total"
  unit_of_measurement: "kWh"
3

Thanks Jon for the suggestion. I did review the automation that I had created to set the export tariffs which was a copy of an import automation that sets the tariff in entity id energy_grid_octopus_flux_import, but forgot to change the target entity id. to energy_grid_octopus_flux_export.

That seems to work, but when I check the current entity states for the sensor sensor.energy_grid_export_octopus_flux_peak, when compared to the equivalent import sensor, I can see that the attributes device class and unit of measurement are missing, so I manually added them and all is fine. That is until the state changes and the attributes are removed again.

I have made a number of changes and plan to let it run for a few days (not much in the way of solar being exported at the moment) and will see if it continues to strip the device class and unit of measurement.

4

Well that is because you did edit it with the Developer Tools right?

If you want a permanent solution:

5

Thanks John. You are right I didnt appreciate that the Developer Tools would only put a temporary plaster on the problem. I have doe as suggested and created both the entry in the confiuration.yaml and created a new customize yaml file which I hope will be a more permanent fix.

6

But afaik, waiting until the utility meters start recording actual data should do the trick, no need to customize.

7

I think the problem is that I am unlikely to be exporting during offpeak. So it is not getting initiated. Anyway for now it all seems good.