utility meters

[daring hazel]

We can just make a thread.
My utility meters:

daily_energy:
  source: sensor.grid_energy_consumption
  cycle: daily
  tariffs:
    - peak
    - offpeak
monthly_energy:
  source: sensor.grid_energy_consumption
  cycle: monthly
  tariffs:
    - peak
    - offpeak

my comsuption meter template sensor:

    - name: grid_power_consumption
      # friendly_name: "Grid power consumption"
      unit_of_measurement: "W"
      state: >-
        {% if states('sensor.power_meter_power')|float(0) > 0 %}
          {{ states('sensor.power_meter_power')|float(0)|round(2) }}  
        {% else %}
          0
        {% endif %}
      availability: "{{states('sensor.power_meter_power') != 'unavaliable' and states('sensor.power_meter_power')|float(0) < 30000 and states('sensor.power_meter_power')|float(0) > -30000}}"

Stats sensor to feed the meter:

- platform: integration
  source: sensor.grid_power_consumption
  name: grid_energy_consumption
  unit_prefix: k
  unit_time: h

[south blaze]

thx.. what I dont understand, is why that does work in your config, but does not in mine.... source sensor.<device_current>_power should turn into the kwh sensors for the energy panel

o wait, you feed them to the integration integration.....

[daring hazel]

ya

[south blaze]

aha....

[daring hazel]

gotta convert the Watts to WattHours

[south blaze]

yes sure, I was hoping the utility integration did that..

[daring hazel]

ya sorry missed that step the other day

[south blaze]

right, its fine, I had been experimenting there too... its just so many entities on top of each other..

add the tariff selects to that, and it is getting way overboard imho...

some serious optimization should/could be done there 😉

btw, using this autmation:```
automation:

• alias: Set utility meters tariff
  id: set_utility_meters_tariff
  trigger:
  platform: state
  entity_id: sensor.huidig_tarief

to: '1'

variables:

tariff: dal

- platform: state

entity_id: sensor.huidig_tarief

to: '2'

variables:

tariff: piek

action:
  - service: select.select_option
    target:
      entity_id: >
        {% set ns = namespace(selects=[]) %}
        {% for s in states.select
                |selectattr('entity_id','search','_daily_energy|monthly_energy')%}
        {% set ns.selects = ns.selects + [s.entity_id] %}
        {% endfor %}
        {{ns.selects}}

- select.cv_stookhok_daily_energy

- select.cv_stookhok_monthly_energy

    data:
      option: >
        {{'dal' if trigger.to_state.state == '1' else 'piek'}}

ofc it needs tariff sensor, but my main hub provides that, dal (off-peak) = 1, piek (peak..) = 2

[daring hazel]

nice

[south blaze]

as I wrote, I made 2 (daily/monthly) peak/off-peak utility sensors for 1 source sensor , but it is in W. I have no idea what it is showing now... what does that value indicate?

given the current power:

it returns

[daring hazel]

pipe that into the integration integration

Watt sensor -> Integration integration -> Utility Meter

utility meters

[south blaze]

yes, I will do. but what does Utility meter do with a regular power sensor? it says 395.7 W, but how/what/when/why is that. I just don't understand what it does with a power sensor.

[daring hazel]

AFAIK it's just totaling up the readings till reset 🤷‍♂️

[south blaze]

yeah, so thats really a useless value then. Suppose this integration is not for power sensors, but meant for already totalling energy sensors. I deleted those I made previously.