Unit of Current Import warning messages

[GrantKeymer]

When my Pulsar Plus started charging all by itself last night (another story), I noticed the following WARNING message...

sensor.wallbox_power_active_import has unit None which is unsupported for device_class power
January 20, 2022, 10:00:10 PM – (WARNING) Sensor

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:269
Integration: Sensor (documentation, issues)
First occurred: January 20, 2022, 10:00:10 PM (1 occurrences)
Last logged: January 20, 2022, 10:00:10 PM

sensor.wallbox_power_active_import has unit None which is unsupported for device_class power

Followed by another WARNING message...

The unit of sensor.wallbox_current_import is changing, got multiple {None, 'A'}, generation of long term statistics will be suppressed unless the unit is stable and matches the unit of already compiled statistics (A)
January 20, 2022, 10:00:10 PM – (WARNING) Sensor

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:244
Integration: Sensor (documentation, issues)
First occurred: January 20, 2022, 10:00:10 PM (1 occurrences)
Last logged: January 20, 2022, 10:00:10 PM

The unit of sensor.wallbox_current_import is changing, got multiple {None, 'A'}, generation of long term statistics will be suppressed unless the unit is stable and matches the unit of already compiled statistics (A)

Do I need to be concerned about either of these?

[lbbrhzn]

This might be caused by a MeterValues.req from the charger that contains meterValues with an empty or missing unit field. All MeterValues should have proper units. If the unit field is omitted it defaults to 'Wh'.
Can you send a log fragment that shows the contents of the MeterValues.req?

[GrantKeymer]

Thanks for the quick reply. Here are the log entries I think are relevant...

2022-01-20 21:59:13 DEBUG (MainThread) [websockets.server] < TEXT '[2,"71b1db97-89b0-4805-8c79-ddd9ca972960","Mete...actionId": 1642669128}]' [1094 bytes]
2022-01-20 21:59:13 INFO (MainThread) [ocpp] : receive message [2,"71b1db97-89b0-4805-8c79-ddd9ca972960","MeterValues",{"meterValue": [{"timestamp": "2022-01-20T08:59:13Z","sampledValue": [{"value": "13","format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Energy.Active.Import.Register","unit": "Wh"},{"value": "2210","format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Power.Active.Import","unit": "W"},{"value": "7621","format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Power.Offered","unit": "W"},{"value": "1e+01","format": "Raw","location": "Outlet","context": "Sample.Periodic","phase": "L1","measurand": "Current.Import","unit": "A"},{"value": "11","format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Current.Offered","unit": "A"},{"value": "221.000000","format": "Raw","location": "Outlet","context": "Sample.Periodic","phase": "L1-N","measurand": "Voltage","unit": "V"},{"value": "50.000000","format": "Raw","location": "Outlet","context": "Sample.Periodic","measurand": "Frequency"} ]} ],"connectorId": 1,"transactionId": 1642669128}]
2022-01-20 21:59:13 INFO (MainThread) [ocpp] : send [3,"71b1db97-89b0-4805-8c79-ddd9ca972960",{}]
2022-01-20 21:59:13 DEBUG (MainThread) [websockets.server] > TEXT '[3,"71b1db97-89b0-4805-8c79-ddd9ca972960",{}]' [45 bytes]

[drc38]

Usually you can fix in HA under developer tools | statistics . Given the issues you had setting up the environment once you fix hopefully it should not come back.

[lbbrhzn]

That looks ok, all the MeterValues have a unit, except for Frequency.

[GrantKeymer]

Thanks guys. Good to know I can use the 'Fix Issue' links in Statistics to sort this out.

Also good to know that MeterValues are how they should be. I remember the OCPP spec saying that Frequency doesn't need to have any unit and will be defaulted to Hz.