Solar PV Monitoring/Automation Thread

I just do max export allowed, and fix an SOC threshold for every hour.

So imaybe 20% per hour @ 5kW. So stop discharging when you hit 20% between 1 and 2, stop when you hit 40% between 12 and 1 etc......

You will finish each night at 20% SOC irrespective of the starting position

I do 15% per hour. It finishes early (reaches the low threshold) so reverts to discharging normally for the last 15 mins or so of each hour.

So you might end up actually hitting 9% that way, so you could set the threshold for 1 to 2 at 12%

So basically, Trigger time between 1:00 and 2:00 If SOC% > bottom level Then Dump Discharge Else Normal Discharge

Then repeat for all hours from 21:00

I'd be the same. Every 10 secs on a Gen 1 Hub, with a v5 Eddi and Zappi. No issues as far as I can see

looking to do same with SOlis invertor to feed into HA

Did you create the defined time periods and names in automations.yaml? The example below is for a day/night meter (peak and offpeak), I don't see a reason why it can't have three periods.

- id: '1634335289003'
  alias: ESB Meter Electricty Meter Tariffs
  description: Day and Night PEAK Tariffs
  trigger:
  - platform: time
    at: 08:11:00
    variables:
      tariff: peak
  - platform: time
    at: '23:11:00'
    variables:
      tariff: offpeak
  action:
  - service: select.select_option
    target:
      entity_id: select.hourly_energy
    data:
      option: '{{ tariff }}'
  - service: select.select_option
    target:
      entity_id: select.daily_energy
    data:
      option: '{{ tariff }}'
  - service: select.select_option
    target:
      entity_id: select.monthly_energy
    data:
      option: '{{ tariff }}'

Then create utility_meter in configuration.yaml:

utility_meter:
  hourly_energy:
    source: sensor.shelly_em_esb_meter_channel_1_energy
    name: ESB Meter Hourly Electrical Energy
    cycle: hourly
    tariffs:
      - peak
      - offpeak
  daily_energy:
    source: sensor.shelly_em_esb_meter_channel_1_energy
    name: ESB Meter Daily Electrical Energy
    cycle: daily
    tariffs:
      - peak
      - offpeak

And then a pricing template in the same file:

template:
  - sensor:
      - name: "Hourly Cost Total Peak"
        unique_id: "template_sensor_4"
        device_class: monetary
        unit_of_measurement: "€"
        icon: mdi:currency-eur
        state: >
          {{ (states('sensor.hourly_energy_peak') | float * 0.3648 ) | round(2) }}

      - name: "Hourly Cost Total Off Peak"
        unique_id: "template_sensor_5"
        device_class: monetary
        unit_of_measurement: "€"
        icon: mdi:currency-eur
        state: >
          {{ (states('sensor.hourly_energy_offpeak') | float * 0.105) | round(2) }}

Some of the cards on my energy dashboard.

If I were you'd add templates with "readable names" and use them instead of the "3EM …." when it comes to the dashboard.

Really not too difficult - you basically just clone the values out to another metric and show that one instead.

e.g. add to your configuration.yamlfile

sensor:

  - platform: template

    sensors:

      # Can we obfuscate the shelly channels and use the values from a friendly name instead?

      mains_energy:

        friendly_name: "Mains Energy"

        device_class: energy

        unit_of_measurement: kWh

        value_template: >-

          {{ states('sensor.shellyem_channel_1_energy') | float(0) }}

This for me gives me a mains_energy entity with "Mains Energy" as the UI name - which ends up with exactly the same values as the sensor.shelly_em_channel_1_energy (in my case the CT1 clamp is on the Mains).

For me one of the main reasons to do this is that if I ever have to add another shelly to monitor or if I want to use the CT1 clamp to monitor something else - I just do the switch physically, and then update the template here and I haven't lost any of the historical data.