Energy Current with wrong values

[Diegaco2005]

I've two air conditioners on my house, but using the sensor Energy Current, my devices reports values too differents. One of this has 12000 BTU, and the integration reports 50w in Energy Current on standby mode, while the 18000 BTU shows only 5w in the same sensor.
In case of my 12000 BTU unit, it's label reports a 3.51w to the idle consuption. How I can update the correct idle consuption on the idle energy sensor?

[Xitro01]

I have issues with power readings as well. Turned it on and it went from 0W to 50W. Then turned it off and suddenly went to 56W? If it's on I expect something around 400-600W, and when it's off I expect something around 3W.

I would like to add this to my Energy Dashboard, but this entity is currently unusable.

[Tymose]

Same issue hereon DC18RQ NSK unit. Seems to be showing 50W constantly when turned off. Keeps showing like that after I've turned it on first time with integration enabled. Before first turning on it was showing 0W.

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[ollo69]

Please attach device diagnostics while your device is idle so that I can check the value in payload,

[Xitro01]

Please attach device diagnostics while your device is idle so that I can check the value in payload,

While off/idle:
smartthinq_sensors-841bdbf7cdcba74f0490298a2e010220-Airconditioner-50b9fa0937b72643ace0be6c2f022be1.json.txt

While heating (takes a couple of minutes to show the higher power consumption):
smartthinq_sensors-841bdbf7cdcba74f0490298a2e010220-Airconditioner-50b9fa0937b72643ace0be6c2f022be1.json.txt

I don't think there really is a good (easy) alternative of reading energy consumption values right now, which is discussed here as well: sampsyo/wideq#75

So for the solution: the 50 should either be replaced with 0 or a fictional (3/4W) idle usage, while the device is in the 'idle' state. This will give a much better indication of the usage of the device.
After that we can finally use these measurements and perform calculations to create a daily energy entity for our energy dashboards. With something like this:

sensor:
 - platform: integration
   name: airconditioner_energy
   source: sensor.airconditioner_energy_current
   unit_prefix: k
   method: left

You might be able to implement something like this in your integration as well?

[Xitro01]

For those looking for a work-around/temporarily fix, put this in your config:

template:
  - sensor:
      - name: "Airconditioner Energy current fixed"
        unique_id: airconditioner_energy_current_fixed
        unit_of_measurement: "W"
        state: >
          {% if is_state('sensor.airconditioner_energy_current', '50') %}
            3.5
          {% else %}
            {{ states('sensor.airconditioner_energy_current') }}
          {% endif %}

sensor:
  - platform: integration
    name: Airconditioner
    unique_id: sensor.airconditioner_energy
    source: sensor.airconditioner_energy_current_fixed
    unit_prefix: k
    method: left

After that you can add sensor.airconditioner_energy to your Energy Dashboard.

[rzmeu]

Hello, maybe someone has more insights. My AC is lg b07ts
I installed a pzem-004t to monitor power usage. In standby it was showing around 2.6W, but yesterday it started showing around 44W. In the LG applciation "Current power consumption" is 0.05kW.

The only difference I can think off is that the temperature dropped. Does my AC have some sort of anti freezing mechanism which is consuming more power?

If so then this adds more variables to this integration. I don't use it anymore because I configured local management using IR and the PZEM-004t, but still would like to know more about power consumption.

[ollo69]

I just added in last release the same work-around that was already present for ThinqV2 device. The rule is very simple (similar to what @Xitro01 implements in sensor template): if device is in stand-by and power <= 50, it reduce the value to 5.

Unfortunately, as I know, there aren't other ways to get the real power usage in stand-by mode, because the api just return the fixed value 50. My opinion is that solution implemented by @rzmeu (external power sensor) is the most reliable way to get real power usage (and also not so much expensive).

[Xitro01]

Applied the update and seems to work for me, thanks @ollo69

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.