Readings are too large

[dinki]

Me again. I've successfully configured my new meter but the readings appear to be too large. I am using aa Itron SK9C1A-3 and it's configured like this:

meters:
  - id: XXXXXXXX
    protocol: scm
    name: Electric_Meter
    #format: "######.###"
    unit_of_measurement: "KWh"
    icon: mdi:gauge
    device_class: energy

My last two hours have read 528kW and 453kW. I'd expect these readings to be more in the order of 5.28kW and 4.53kW. I thought this might be an issue where the unit of measure was actually Wh but that would make the readings too small, right? The meter does say that it is an 'Itron Watthour Meter', but I think .5kW and .4kW for the last two hours is too low as my central air conditioning has been running a lot. I checked yesterday's usage and it was around 4-5kW per hour as read with the old meter.

Can the format line be used to force these readings to be reading/100 or should I create a template sensor in HA to do this? I'm just making guesses

[allangood]

Yes, the format os exactly for this purpose! Some meters and their readings as a "flat" number when they should have a decimal somewhere. This format parameter is to help to put the decimal in the right place!

…

On Thu., May 19, 2022, 4:59 p.m. Chuck Connors, ***@***.***> wrote: Me again. I've successfully configured my new meter but the readings appear to be too large. I am using aa Itron SK9C1A-3 and it's configured like this: meters: - id: XXXXXXXX protocol: scm name: Electric_Meter #format: "######.###" unit_of_measurement: "KWh" icon: mdi:gauge device_class: energy My last two hours have read 528kW and 453kW. I'd expect these readings to be more in the order of 5.28kW and 4.53kW. I thought this might be an issue where the unit of measure was actually Wh but that would make the readings too small, right? The meter does say that it is an 'Itron Watthour Meter', but I think .5kW and .4kW for the last two hours is too low as my central air conditioning has been running a lot. Can the format line be used to force these readings to be reading/100 or should I create a template sensor in HA to do this? I'm just making guesses — Reply to this email directly, view it on GitHub <#135>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFY2XSKNUZMFVD5CLP3R2LVK22U7ANCNFSM5WNSI5GQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[dinki]

@allangood Thank you again. Can you tell me how I would use that to format 528 to 5.28? Would it be:

format: "######.##"

[allangood]

Yes, exactly like that :)

…

On Thu., May 19, 2022, 5:43 p.m. Chuck Connors, ***@***.***> wrote: @allangood <https://github.com/allangood> Thank you again. Can you tell me how I would use that to format 528 to 5.28? Would it be: format: "######.##" — Reply to this email directly, view it on GitHub <#135 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFY2XSP34RGYKGCBUT2TPLVK272DANCNFSM5WNSI5GQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[dinki]

@allangood Most excellent. Last question. So my values look like this now 000031.85 . Is there a way to eliminate the leading zeroes? I don't know how large this number can potentially get.

[allangood]

These leading zeros will be ignored (converted to float) by Home Assistant. But you can change the format parameter to have less numbers. Basically, the format means "put a number where a # is found".

…

On Thu., May 19, 2022, 5:59 p.m. Chuck Connors, ***@***.***> wrote: @allangood <https://github.com/allangood> Most excellent. Last question. So my values look like this now 000031.85 . Is there a way to eliminate the leading zeroes? I don't know how large this number can potentially get. — Reply to this email directly, view it on GitHub <#135 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFY2XQLCCGKIZ5ELSNJ6VLVK3BTLANCNFSM5WNSI5GQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>