Add sensor to ouput Import and Export in Watts or kWh

[Roving-Ronin]

Hi,

Thanks for this great integration ! I've been using it for a while now and just looked to add the ability to calculate power costs in the Energy Dashboard. Unfortunately it appears that HA, when defining an entity to track power total costs for the day, works on the basis that data being feed in, is either Watts or kWh. Given that SA / this integration outputs the import/export in Watt Hours (Wh) its proving a real pain to get it working.

Just wondering if there's any chance you might be able to add an extra lot of sensors to output the sa_todays_energy_imported and sa_todays_energy_exported with a corresponding alias in kW (i.e. sa_todays_energy_imported_kw and sa_todays_energy_exported_kw), or even plain Watts (users could then just add a Riemann sum integral (left), that would allow converting W to kWh easily.

Going from Wh, given its watts x , but how long is that period of time to divide it by to get back to W, is the painful issue.

Thanks !

[PeterH24x7]

Hi @Roving-Ronin - thank you for your feedback. Integration with the HA Energy module should not be difficult and the SA integration already provides everything you need. Importantly, don't mix up your power draw in units Watts or kilo-Watts, with your energy usage which is in units of Watt-hours or kilo-Watt-hours - which also the units that you pay for in $/kWh. I trust that you're using the latest "solar_analytics.yaml" file as published in August.

As described in the code header comments ... to complete the HA Energy Configuration, enter the details for

Grid consumption - as sa_todays_energy_imported
Return to grid - as sa_todays_energy_exported
Solar production - as sa_todays_energy_generated_total

For example, here is my config for Grid consumption:

The sensors above are in Wh and the Energy module does any conversions (e.g. to kWh) as required. My energy data as displayed by the HA Energy module as good as matches the data in the Solar Analytics portal (subject to any minor timing discrepancies).

I hope this helps. If not, let me know and we can organise a time to chat further.

[Roving-Ronin]

Hi Peter,Thanks but I wasn’t referring to the data sources for using to track the kWh being used / exported, but said data (in W or kWh instead of Wh) so it can be used to define an entity that tracks and calculates the actual running daily cost in the energy dashboard.Ie below where you’ve chosen your Total Daily Export / Import, and then have four options to add in / track the cost of it.  As per this screenshot: 

[PeterH24x7]

Hi @Roving-Ronin - I'm with Amber so use their HA API integration for realtime price updates (changes every 5 mins or so). My EM daily cost total is usually within about 30c compared to that calculated by Amber (likely a meter read/time-sync issue). See image below.

What's your source for your retailer's unit-rate ($/kWh) data? Is it fixed (ie. "use a static price"), or do you have peak/off-peak/shoulder time of day unit-rates? If the latter, then you need to create an "entity with the current price" which driven by the time-of-day could be created as an automation or in Node-Red.

[Roving-Ronin]

HI Peter,

RedEnergy atm, on standard TOU plan with peak/shoulder/offpeak, best price (for my area), but alas no App/API to pull data from.
Given this I end up using SA as the source for electricity import/export/generation, and have an 'entity tracking the total costs' (daily), but need the actual imported/exported units to call and multiply by the applicable tarrif that applies for that time period.
Unfortunately from looking at all the sensor entity data coming from SA, it appears for import/export/generation its all in Wh (not watts or kWh), hence my query if it would be possible to add an alias for these sensors (or a script , that simply convert them into watts or kWh, so they can be used in other applications/calculations?

[PeterH24x7]

You shouldn't need the conversion as the Energy module handles the conversions for you. A simple solution is to create 2x Helper sensors (see Settings > Devices & Services then the Helpers tab). Using "Create Helper" create "Number" helpers em_general_price for the general price and another em_fit_price for the feed-in price (assuming you have solar-PV) - see images below.

Note the icon naming is confusing - from my perspective import should point away from the grid, and export towards the grid.

Next for each time of day change in price (e.g. 12am off-peak, 6am shoulder, 10am off-peak, 3pm peak, 9pm shoulder) create an automation (see Settings > Automations & Scenes). See image below for help.

You can then configure the em_general_price and em_fit_price in the Energy configuration under the Grid Consumption and Return to Grid sections as "Use an Entity with Current Price" and it should work as expected.

Note, if the RedEnergy rate changes at 9pm, then you may wish to set it to change just a little later but before the next 5m read (e.g. 9.04pm) so that the kWh between 8pm and 9pm are all correctly accounted for at the previous rate.

[Roving-Ronin]

If I'm following this correctly, you then end up with a single 'em_general_price' that is the per kWh tarrif. So you then don't have any peak / off peak / shoulder being applied.

I've just added the code into the energy tarrif yaml to do the W --> kWh conversions, see: https://github.com/Roving-Ronin/Home-Assistant/blob/main/packages/energy_tariff_TOU_solar_analytics.yaml It also adds all the automations etc for changing the billing rates at set times and different rates etc.

[PeterH24x7]

The em_general_price (and em_fit_price) would change value per each of the time-based automation as shown above. You've nonetheless identified another means for implementation as below. While not a specific use for me, I do like the idea of having cumulative daily and monthly $ outside of the Energy module and for making Energy retailer price comparisons.

[PeterH24x7]

I should add that I do nonetheless have sensors in kWh and kW that are used for display purposes. Rather than code in YAML, I've simply implemented the conversions in Node Red.

[Roving-Ronin]

So your doing the same yourself (needing/wanting kWh) ;-) But why do it this way, that then requires installing and maintaining another software package, when it can all simply be done 'natively' with a few basic lines of code in HA. As per my original thought, it would seem easier to just add it to your SA integration, making it available to everyone and also keeping this code in the one place for all things SA related. Anyhow see above post with the link, when I get time I also have to see if I can get a TOU + Demand tariff working, as I personally wanting to see about using SA app to run the costings for power from the current plan I'm on, whilst then running HA Energy Dashboard with power costs for another plan (TOU with Demand) to allow comparing costs/savings for a period, before seeing if its worth changing plans.

[PeterH24x7]

You make a fair point regarding integrating the conversion into the base code. My original SA integration focus was only to provide the base-level functionality. My main hesitation for providing the Wh to kWh conversion as a float means it will likely need rounding to some decimal point for display purposes and/or I'd otherwise be reticent to round on conversion for sake of losing 2 to 3 decimal points of accuracy in any downstream calcs.

[Roving-Ronin]

But all your calculations are based upon the Wh from SA API, whilst any kWh conversion is to support 'add-ons', such as the billing tariff calculator, therefore your data would not end up 'suffering' from rounding off decimal points. :-)

[PeterH24x7]

Hi @Roving-Ronin - HNY!!!

The conversions do otherwise create a near duplicate data set in the HA database. I would like to think there's a smarter way so the data is only converted and rounded when required. Nonetheless, here's the additional code I'm trialling (tagged onto the existing).

As a bonus, it includes a new SA API get of expected Wh solar generation (days total to the current hour - matching the data found on the SA portal's Production tab - the grey graph bar). You will note some comments regarding the timestamp setting - maybe it should be "now" rounded down to the last hour - e.g. 2023-01-03 09:55:38 becomes 2023-01-03 09:00:00. Thoughts?

Let me know how you go.

# -----------------------------------------------------------------------------
#
# Solar Analytics - get daily cumulative expected energy data.
# Used to report today's total expected generated energy to the most recent hour (this is not a forecast).
# Updated every 60 minutes.
# Added 2-Jan-23 - initial version.
#
  - platform: rest
    name: sa_energy_generated_expected_data
    resource_template: https://portal.solaranalytics.com.au/api/v2/site_data/{{ states('input_text.sa_site_id') }}?all=false&gran=day&losses=true&power=false&trunc=false&tstart={{ now().strftime("%Y%m%d") }}&tend={{ now().strftime("%Y%m%d") }}   
    username: !secret sa_username
    password: !secret sa_password
    authentication: basic
    value_template: >-
      {{ as_timestamp(now()) | timestamp_custom ('%Y-%m-%d %H:%M:%S') }}
# The rest get timestamp is only the current date - rather use the current date-time of the get.
#      {{ as_timestamp(value_json['data'][0].t_stamp) | timestamp_custom ('%Y-%m-%d %H:%M:%S') }}
    json_attributes:
      - "data"
    scan_interval: 3600

  - platform: template
    sensors:
      sa_todays_energy_generated_expected_total:
        friendly_name: Total Energy Generated Expected
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_energy_generated_expected_data' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_energy_generated_expected_data.attributes.data[0].energy_expected | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_energy_generated_expected_total' ) }}
          {% endif %}
        icon_template: mdi:solar-power
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_todays_energy_generated_expected_total' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_energy_generated_expected_data.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_energy_generated_expected_total.time_stamp" ) }}
            {% endif %}

#
# Convert Solar Analtics Watt-hour and Watt measurements to kilo-Watt-hours and Watt-hours conversions.
# Added 2-Jan-23 - initial version.
#
# Energy conversions
  - platform: template
    sensors:
      sa_todays_energy_consumed_total_kwh:
        friendly_name: Total Energy Consumed - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_energy_consumed_total') | float / 1000 }}"
        icon_template: mdi:home-lightning-bolt-outline
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_energy_generated_total_kwh:
        friendly_name: Total Energy Generated - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_energy_generated_total') | float / 1000 }}"
        icon_template: mdi:solar-power
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_energy_generated_expected_total_kwh:
        friendly_name: Total Energy Generated Expected - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_energy_generated_expected_total') | float / 1000 }}"
        icon_template: mdi:solar-power
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_air_conditioner_total_kwh:
        friendly_name: Heating Cooling Energy - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_air_conditioner_total') | float / 1000 }}"
        icon_template: mdi:hvac
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_electric_vehicle_total_kwh:
        friendly_name: Electric Vehicle Energy - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_electric_vehicle_total') | float / 1000 }}"
        icon_template: mdi:car-electric
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_hot_water_total_kwh:
        friendly_name: Hot Water Energy - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_hot_water_total') | float / 1000 }}"
        icon_template: mdi:shower-head
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_stove_oven_total_kwh:
        friendly_name: Stove Oven Energy - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_stove_oven_total') | float / 1000 }}"
        icon_template: mdi:stove
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_energy_imported_kwh:
        friendly_name: Total Energy Imported - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_energy_imported') | float / 1000 }}"
        icon_template: mdi:transmission-tower-export
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

      sa_todays_energy_exported_kwh:
        friendly_name: Total Energy Exported - kWh
        unit_of_measurement: "kWh"
        value_template: "{{ states('sensor.sa_todays_energy_exported') | float / 1000 }}"
        icon_template: mdi:transmission-tower-import
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing

# Power conversions
      sa_consumption_power_kw:
        friendly_name: Power Consumption - kW
        unit_of_measurement: "kW"
        value_template: "{{ states('sensor.sa_consumption_power') | float / 1000 }}"
        icon_template: mdi:home-lightning-bolt-outline
        device_class: "power"
        attribute_templates:
          state_class: measurement

      sa_generation_power_kw:
        friendly_name: Power Generation - kW
        unit_of_measurement: "kW"
        value_template: "{{ states('sensor.sa_generation_power') | float / 1000 }}"
        icon_template: mdi:solar-power
        device_class: "power"
        attribute_templates:
          state_class: measurement

      sa_import_export_power_kw:
        friendly_name: Power Import Export - kW
        unit_of_measurement: "kW"
        value_template: "{{ states('sensor.sa_import_export_power') | float / 1000 }}"
        icon_template: mdi:solar-power
        device_class: "power"
        attribute_templates:
          state_class: measurement

# -----------------------------------------------------------------------------

[Roving-Ronin]

Hi Peter,

With 3p I only have CT's for solar and grid monitoring, so can't test the oven / aircon etc... but assume they should work if the others do.

IMHO wondering if the "# Power conversions" are really needed, as these are momentary values that are constantly change to show the 'now' value of them, and given this wondering if anyone will really use them (unless they have a card to show 'this moments' data) versus the other sensors that are used longer term to track long term energy import/export etc.

Seperate thought, have you considered adding unique_id for your sensors, such as:

sensors:
  sa_todays_energy_consumed_total:
    unique_id: sa_todays_energy_consumed_total
    friendly_name: Total Energy Consumed

Personally I actually add this into your integration, as its just handy to be able to then be able to do things in the entity view, such as typing in my own (display) name for that entity. Also handy versus other integrations where you want to fix something up and HA blocks doing so, with the no unique_id warning (e.g. This entity ('sensor.sa_data_by_5min') does not have a unique ID, therefore its settings cannot be managed from the UI).

Will keep an eye upon sensor.sa_todays_energy_generated_expected_total as waiting for it to still update atm. Assuming since its now dark, this won't update till tomorrow (Wed)

[Roving-Ronin]

Expected solar seems to be working also.

• energy_bom: 0
  energy_consumed: 12533.0726
  energy_expected: 34075.4822576555
  energy_generated: 36036.5711
  energy_shading: 0
  t_stamp: '2023-01-04'

[Roving-Ronin]

Hi Peter,

I keep on noticing that whilst sensor.sa_energy_generated_expected_data is receiving updates, that sa_todays_energy_generated_expected_total (and the kWh conversion) are constantly showing errors as status = Unavailable.

[Roving-Ronin]

forgot to also ask, is there any documentation upon what data the SA API makes available ? I note on their app, they have data for how many kWh and what tariff rate (i.e. peak / off peak / shoulder) have been imported. Just wondering if they publish that via REST, that would allow adding sensors to track this kWh and time billing periods also (allowing use for triggers for other things, and adding each tariff period to energy dashboard to then see the breakdown in HA.

[PeterH24x7]

Hi @Roving-Ronin I'm away at the moment so will only respond in brief until the weekend. The SA public app can be found via the following link. I have found it to be somewhat limited and ended up deciphering the rest get calls as used on their website. As such some of the gets I use are not official nor supported. This includes the get for the expected generation. I am not sure why it might be failing sometimes.
https://api-docs.solaranalytics.com/OpenAPI-Specs/sapublic-openapi.yaml

[Roving-Ronin]

Hi Peter,

Pending testing it does what is promises, it appears this need to convert from Wh to kWh has been removed with the release of 2023.2
See: https://www.home-assistant.io/blog/2023/02/01/release-20232/#other-noteworthy-changes

that mentions "Got an energy sensor in Wh, but you’d like it to be kWh? You can now change the units of energy sensors in the entity settings."

[PeterH24x7]

Hi @Roving-Ronin -

Thanks for picking up the Wh to kWh (or other energy unit) conversion in the latest HA release - a timely feature. Unfortunately it's only for energy at this time and the power W entities still need their own conversion to kW. To change entity settings I've also had to add "unique_id" (as you suggested above) to each entity. Lastly I've learnt that if the "state_class: measurement" is omitted from the entity attributes then the history is not collected. Everything seems to be working as expected.

I will test the code below for a week before I publish a new release. If you can test also and/or let me know if there's anything further to include (functionality, comments or otherwise) it would be appreciated. Thank you for your contributions.

Rgds, Peter

Edited to fix a minor cut-copy error in kW conversion entities.

# -----------------------------------------------------------------------------
#
# SOLAR ANALYTICS integration for Home Assistant Energy Monitoring
# 
# Developed by Peter Hormann and with thanks to Glen S and Roving-Ronin for their contributions.
#
# Created: 7-Jan-2022
#
# Last updated: 2-Jan-2023 (THIS IS BETA CODE FOR TESTING)
#
# Updates: 
#     16-Jan-2022 - added power reporting (last 5 minute average).
#     16-Jul-2022 - enabled more accurate and more frequent 1 minute power reporting
#                 - added 5 minute energy updates for all channels
#                 - moved sa_site_id to secrets.yaml.
#     11-Aug-2022 - added some error checking to deal with daily energy total errors when the data get is 'unavailable' or 'unknown'
#                 - removed "force_update: true" - where the data get may be 'unavailable'
#                 - removed "state_class: measurement" and "device_class: energy" for rest platform sensors (not applicable)
#     2-Feb-2023  - added new "Total Energy Generated Expected" sensor to provide daily cumulative expected energy (as per the Solar Analytics portal).
#                 - added kW sensors as conversions of their respective W conterpart (note: not required for energy entities as of HA 2023.2).
#                 - added "unique_id" to each sensor entity to enable HA based settings changes.
#
# This code is provided as-is and without any warrantee or guarantees. 
# Further public contributions and enhancements are welcomed.
# 
# Installation: 
#   1. Copy this yaml file to the HA config directory.
#   2. Include this file name as a package in the HA configuration.yaml. 
#      For example -
#        packages:
#          pack_1: !include solar_analytics.yaml
#   3. Define sa_username, sa_password and sa_site_id (e.g. 36304) in the secrets.yaml file.
#   4. After first run, review the attributes sa_data_by_5min to identify the 
#      device specific channel names and update the sa_todays_... xyz sensor to suit.
#   6. Add the new energy sensors from 4. above to the HA Energy Manager as "Monitor 
#      Individual Devices". Go to HA settings and then search for “Energy Configuration” 
#      to make the changes.
#   7. Also in HA Energy Configuration, enter the details for
#      > Grid consumption - as sa_todays_energy_imported
#      > Return to grid - as sa_todays_energy_exported
#      > Solar production - as sa_todays_energy_generated_total
#   8. If all working is correctly, the Energy dashboard should start populating data within 
#      a couple of hours.
#
# Reference for more information and updates:
#   https://github.com/PeterH24x7/-Solar-Analytics-integration-for-Home-Assistant-Energy-monitoring
#
# -----------------------------------------------------------------------------


#
# Define the Solar Analytics site_id value is required in URLs used in gets below - e.g. 36304. 
#   See the Solar Analytics user portal to find your site id or see the collected sa_site_list attributes as defined below.
#
input_text:
    sa_site_id:
      initial: !secret sa_site_id


sensor:

# -----------------------------------------------------------------------------
#  
# Solar Analytics - get the site details associated with the given user account login.
# Updated every 24 hours.
#
# note: assumes only a single device per account, there could be a second device (e.g. replaced device due to fault/upgrade) at $.data.[1]
#
  - platform: rest
    name: sa_site_list
    resource: https://portal.solaranalytics.com.au/api/v3/site_list?hardware=true&capacity=true&subscription=true
    username: !secret sa_username
    password: !secret sa_password
    authentication: basic
    value_template: "{{ now() }}"
    json_attributes_path: "$.data.[0]"
    json_attributes:
      - "e_status"
      - "fault_class"
      - "fault_id*"
      - "has_pv"
      - "mer_status"
      - "overall_status"
      - "retailer_user"
      - "s_cli_site_name"
      - "site_id"
      - "site_inactive"
      - "capacity"
      - "devices"
      - "sub_type"
    scan_interval: 62400

# -----------------------------------------------------------------------------
#
# Solar Analytics - get the site status for the specified site_id.
# Updated every hour.
#
  - platform: rest
    name: sa_status
    resource_template: https://portal.solaranalytics.com.au/api/v3/site_status/{{ states('input_text.sa_site_id') }}
    username: !secret sa_username
    password: !secret sa_password
    authentication: basic
    value_template: "{{ value_json['data']['mer_status'] }}"
    json_attributes_path: "$.data"
    json_attributes:
      - "dashboard_status"
      - "event_id"
      - "event_list"
      - "fault_status"
      - "mer_percentage"
      - "mer_status"
      - "mer_text"
    scan_interval: 3600

  - platform: template
    sensors:
      sa_dashboard_status:
        friendly_name: "Dashboard Status"
        unique_id: sa_dashboard_status
        value_template: "{{ state_attr('sensor.sa_status', 'dashboard_status') }}"
      sa_mer_status:
        friendly_name: "System Status"
        unique_id: sa_mer_status
        value_template: "{{ state_attr('sensor.sa_status', 'mer_status') }}"
      sa_mer_percentage: 
        friendly_name: "PV Performance"
        unique_id: sa_mer_percentage
        value_template: "{{ state_attr('sensor.sa_status', 'mer_percentage') }}"
        unit_of_measurement: "%"

# -----------------------------------------------------------------------------
#
# Solar Analytics - get 5 minute energy data.
# Used to calculate today's cumulative total energy for consumed, generated, imported and exported energy as used by the HA Energy module.
# Updated every 5 minutes.
# Note: the previous version calculated sa_consumption_power, sa_generation_power and sa_import_export_power (as an average over 
#   5 minutes) are now directly sourced using get sa_live_site_data sensor further down below.
# 15-Jul-22 - added trunc=false to include decimal components of 5 minute date (default is true). 
#    Also added air conditioner, EV, hot water and stove-oven energy loads as shown in the attributes of sa_data_by_5min. 
#    These channels should be added/edited/deleted to match the specific device set-up.
#
  - platform: rest
    name: sa_data_by_5min
    resource_template: https://portal.solaranalytics.com.au/api/v2/site_data/{{ states('input_text.sa_site_id') }}?all=true&gran=minute&trunc=false&power=false&tstart={{ now().strftime("%Y%m%d") }}&tend={{ now().strftime("%Y%m%d") }}   
    username: !secret sa_username
    password: !secret sa_password
    authentication: basic
    value_template: >-
      {% set most_recent_sensor_data = value_json['data'] | rejectattr('energy_consumed', 'equalto', None) | list | last %}
        {{ most_recent_sensor_data.t_stamp }}    
    json_attributes:
      - "data"
    scan_interval: 300

  - platform: template
    sensors:
      sa_todays_energy_consumed_total:
        friendly_name: Total Energy Consumed
        unique_id: sa_todays_energy_consumed_total        
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_5min.attributes.data | rejectattr( 'energy_consumed', 'equalto', None ) | sum( attribute='energy_consumed' ) | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_energy_consumed_total' ) }}
          {% endif %}
        icon_template: mdi:home-lightning-bolt-outline
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_energy_consumed_total.time_stamp" ) }}
            {% endif %}

      sa_todays_energy_generated_total:
        friendly_name: Total Energy Generated
        unique_id: sa_todays_energy_generated_total
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_5min.attributes.data | rejectattr( 'energy_generated', 'equalto', None ) | sum( attribute='energy_generated' ) | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_energy_generated_total' ) }}
          {% endif %}
        icon_template: mdi:solar-power
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_energy_generated_total.time_stamp" ) }}
            {% endif %}

      sa_todays_air_conditioner_total:
        friendly_name: Heating Cooling Energy
        unique_id: sa_todays_air_conditioner_total
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_5min.attributes.data | rejectattr( 'load_air_conditioner', 'equalto', None ) | sum( attribute='load_air_conditioner' ) | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_air_conditioner_total' ) }}
          {% endif %}
        icon_template: mdi:hvac
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_air_conditioner_total.time_stamp" ) }}
            {% endif %}

      sa_todays_electric_vehicle_total:
        friendly_name: Electric Vehicle Energy
        unique_id: sa_todays_electric_vehicle_total
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_5min.attributes.data | rejectattr( 'load_ev_charger', 'equalto', None ) | sum( attribute='load_ev_charger' ) | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_electric_vehicle_total' ) }}
          {% endif %}
        icon_template: mdi:car-electric
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_electric_vehicle_total.time_stamp" ) }}
            {% endif %}

      sa_todays_hot_water_total:
        friendly_name: Hot Water Energy
        unique_id: sa_todays_hot_water_total
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_5min.attributes.data | rejectattr( 'load_hot_water', 'equalto', None ) | sum( attribute='load_hot_water' ) | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_hot_water_total' ) }}
          {% endif %}
        icon_template: mdi:shower-head
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_hot_water_total.time_stamp" ) }}
            {% endif %}

      sa_todays_stove_oven_total:
        friendly_name: Stove Oven Energy
        unique_id: sa_todays_stove_oven_total
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_5min.attributes.data | rejectattr( 'load_stove', 'equalto', None ) | sum( attribute='load_stove' ) | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_stove_oven_total' ) }}
          {% endif %}
        icon_template: mdi:stove
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_stove_oven_total.time_stamp" ) }}
            {% endif %}

      sa_todays_energy_imported:
        friendly_name: Total Energy Imported
        unique_id: sa_todays_energy_imported
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {% set energy = namespace( imported = 0 ) %}
            {% for sensor_data in states.sensor.sa_data_by_5min.attributes.data | rejectattr('energy_consumed', 'equalto', None) if sensor_data.energy_consumed > sensor_data.energy_generated %}
              {% set energy.imported = energy.imported + sensor_data.energy_consumed - sensor_data.energy_generated %}
            {% endfor %}
            {{ energy.imported | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_energy_imported' ) }}
          {% endif %}
        icon_template: mdi:transmission-tower-export
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_energy_imported.time_stamp" ) }}
            {% endif %}

      sa_todays_energy_exported:
        friendly_name: Total Energy Exported
        unique_id: sa_todays_energy_exported
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
            {% set energy = namespace( exported = 0 ) %}
            {% for sensor_data in states.sensor.sa_data_by_5min.attributes.data | rejectattr('energy_generated', 'equalto', None) if sensor_data.energy_generated > sensor_data.energy_consumed %}
              {% set energy.exported = energy.exported + sensor_data.energy_generated - sensor_data.energy_consumed %}
            {% endfor %}
            {{ energy.exported | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_energy_exported' ) }}
          {% endif %}
        icon_template: mdi:transmission-tower-import
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_5min' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_5min.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_energy_exported.time_stamp" ) }}
            {% endif %}

# -----------------------------------------------------------------------------
#
# Solar Analytics - get live per minute power data - added 9-Jul-22.
# Used to generate most recent power information.
# Updated every 30 seconds (changed 24-Oct-22 to improve power management responsiveness).
# Note: this is not a published API 'get', but is used by the SA portal to display minute to minute power for a site.
#
  - platform: rest
    name: sa_live_site_data
    resource_template: https://portal.solaranalytics.com.au/api/v3/live_site_data?site_id={{ states('input_text.sa_site_id') }}&last_six=true
    username: !secret sa_username
    password: !secret sa_password
    authentication: basic
    value_template: >-
      {% set most_recent_sensor_data = value_json['data'] | list | last %}
        {{ as_timestamp(most_recent_sensor_data.t_stamp) | timestamp_custom ('%Y-%m-%d %H:%M:%S')}}
    json_attributes:
      - "data"
    scan_interval: 30

  - platform: template
    sensors:          
      sa_consumption_power:
        friendly_name: Power Consumption
        unique_id: sa_consumption_power
        unit_of_measurement: "W"
        value_template: >
          {% if states( 'sensor.sa_live_site_data' ) not in ("unavailable", "unknown") %}
            {% set most_recent_sensor_data = states.sensor.sa_live_site_data.attributes.data | list | last %}
              {{ most_recent_sensor_data.consumed | int }}
          {% else %}
            {{ states( 'sensor.sa_consumption_power' ) }}
          {% endif %}
        icon_template: mdi:home-lightning-bolt-outline
        device_class: "power"
        attribute_templates:
          state_class: measurement
          time_stamp: >
            {% if states( 'sensor.sa_live_site_data' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_live_site_data.state }}
            {% else %}
              {{ state_attr( "sensor.sa_consumption_power.time_stamp" ) }}
            {% endif %}

      sa_generation_power:
        friendly_name: Power Generation
        unique_id: sa_generation_power
        unit_of_measurement: "W"
        value_template: >
          {% if states( 'sensor.sa_live_site_data' ) not in ("unavailable", "unknown") %}
            {% set most_recent_sensor_data = states.sensor.sa_live_site_data.attributes.data | list | last %}
              {{ most_recent_sensor_data.generated | int }}
          {% else %}
            {{ states( 'sensor.sa_generation_power' ) }}
          {% endif %}
        icon_template: mdi:solar-power
        device_class: "power"
        attribute_templates:
          state_class: measurement
          time_stamp: >
            {% if states( 'sensor.sa_live_site_data' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_live_site_data.state }}
            {% else %}
              {{ state_attr( "sensor.sa_generation_power.time_stamp" ) }}
            {% endif %}

      sa_import_export_power:
        friendly_name: Power Import Export
        unique_id: sa_import_export_power
        unit_of_measurement: "W"
        value_template: >
          {% if states( 'sensor.sa_live_site_data' ) not in ("unavailable", "unknown") %}
            {{ (states.sensor.sa_consumption_power.state | int) - (states.sensor.sa_generation_power.state | int) }}
          {% else %}
            {{ states( 'sensor.sa_import_export_power' ) }}
          {% endif %}
        icon_template: mdi:transmission-tower
        device_class: "power"
        attribute_templates:
          state_class: measurement
          time_stamp: >
            {% if states( 'sensor.sa_live_site_data' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_live_site_data.state }}
            {% else %}
              {{ state_attr( "sensor.sa_import_export_power.time_stamp" ) }}
            {% endif %}

# -----------------------------------------------------------------------------
#
# Solar Analytics - get hourly cumulative expected energy data for the day.
# Used to report today's total expected generated energy to the most recent hour - a time lagging report of expected, and not a forecast.
# Notes: this is not a published API 'get', but is used by the SA portal. 
# The get also retrieves the daily total for the most recent hour for generated and consumed energy; not required given 5 min updates of the same above.
# Checked every 30 minutes for changes in the last hour.
# Added 24-Jan-23 - initial version.
#
  - platform: rest
    name: sa_data_by_hour
    resource_template: https://portal.solaranalytics.com.au/api/v2/site_data/{{ states('input_text.sa_site_id') }}?all=false&gran=day&losses=true&power=false&trunc=false&tstart={{ now().strftime("%Y%m%d") }}&tend={{ now().strftime("%Y%m%d") }}
    username: !secret sa_username
    password: !secret sa_password
    authentication: basic
    value_template: >-
      {{ as_timestamp(now()) | timestamp_custom ('%Y-%m-%d %H:%M:%S') }}
# The rest get timestamp is only the current date - rather use the current date-time of the get.
#      {{ as_timestamp(value_json['data'][0].t_stamp) | timestamp_custom ('%Y-%m-%d %H:%M:%S') }}
    json_attributes:
      - "data"
    scan_interval: 1800

  - platform: template
    sensors:
      sa_todays_energy_generated_expected_total:
        friendly_name: Total Energy Generated Expected
        unique_id: sa_todays_energy_generated_expected_total
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_hour' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_hour.attributes.data[0].energy_expected | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_energy_generated_expected_total' ) }}
          {% endif %}
        icon_template: mdi:solar-power
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_hour' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_hour.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_energy_generated_expected_total.time_stamp" ) }}
            {% endif %}

#
# Convert Solar Analtics Watt-hour and Watt measurements to kilo-Watt-hours and Watt-hours conversions.
# Added 24-Jan-23 - initial version.
#
#  - platform: template
#    sensors:

# Energy conversions - DELETED
# No longer required as of HA 2023.2 - unit can now be selected as part of entity settings. 
#   Supports energy only, not power.

# Power conversions
      sa_consumption_power_kw:
        friendly_name: Power Consumption - kW
        unique_id: sa_consumption_power_kw
        unit_of_measurement: "kW"
        value_template: "{{ (states('sensor.sa_consumption_power') | float / 1000) | round(2) }}"
        icon_template: mdi:home-lightning-bolt-outline
        device_class: "power"
# Use of state_class results in history being collected and the creation of a near duplicate data set in the HA database.
#        attribute_templates:
#          state_class: measurement

      sa_generation_power_kw:
        friendly_name: Power Generation - kW
        unique_id: sa_generation_power_kw
        unit_of_measurement: "kW"
        value_template: "{{ (states('sensor.sa_generation_power') | float / 1000) | round(2) }}"
        icon_template: mdi:solar-power
        device_class: "power"
#        attribute_templates:
#          state_class: measurement

      sa_import_export_power_kw:
        friendly_name: Power Import Export - kW
        unique_id: sa_import_export_power_kw
        unit_of_measurement: "kW"
        value_template: "{{ (states('sensor.sa_import_export_power') | float / 1000) | round(2) }}"
        icon_template: mdi:transmission-tower
        device_class: "power"
#        attribute_templates:
#          state_class: measurement

# -----------------------------------------------------------------------------

[Roving-Ronin]

Have updated with the above, I can't test the oven/EV/hot water / aircon sensors, having 3p and using all CT for import/production.

I do note that the sensor.sa_todays_energy_generated_expected_total retains an issue of 'The state class '' of this entity is not supported.'
Given this number may go up and down during the day, and definitely drops down/resets between days, I don't think "state_class: total_increasing" is the correct class to be using. My understanding is that is more for amounts that are supposed to fovered accumulate (i.e. keep increasing only). Hence using "state_class: total" that can go up and down, is probably more applicable here?

[PeterH24x7]

Wondering where you see the "state class of this entity is not supported" error/issue?

I've simply set it up the same as the "Total Energy Generated" sensor which is what the expected sensor is trying to predict to the current hour. Both of them accumulate throughout the day (not go up/down) and then reset at midnight. If I change the latter to 'total', then I should also change the others which nonetheless seem to work okay with HA EM.

See the image example of the two in my HA set-up below. Does yours look the same?

[PeterH24x7]

Ahhh ... found it in the system logs. Still the 'warning' indicating it's not strictly increasing doesn't seem true from what I've seen - i.e. it grows by the hour until the end of the day.

[PeterH24x7]

I've just changed the sa_todays_energy_generated_expected_total and the sa_todays_stove_oven_total to "total", rather than "total_increasing". Let's see what happens over the next 24 hours.

[Roving-Ronin]

I usually see it in Developer Tools --> Statistics, as the easy to go to area to check anything is wrong.
I don't have the 'Oven' sensor, but that one seems strange.... given it only consumes you'd expect it to be a total_increasing.

[PeterH24x7]

However like the other "sa_todays_...etc" energy sensors, they all reset at midnight, so based on my reading of the link below I do agree with your assessment that the state_class should be "total". Will test as above to ensure nothing breaks, then change the others and continue testing.

https://developers.home-assistant.io/docs/core/entity/sensor/#available-state-classes

[PeterH24x7]

Hi @Roving-Ronin - so today the results purely from a sensor "total" perspective look the same as "total_increasing".

However, the HA EM interprets the total differently and doesn't see the midnight reset to zero as a start of a new meter cycle, rather a negative energy usage. As such our Stove Oven Energy yesterday at midnight reached 0.21kWh for the day, and today to the moment it has reached 0.20kWh with EM reporting -0.1kWh as a relative net decrease - and not 0.20kWh as expected.

https://developers.home-assistant.io/docs/core/entity/sensor/#available-state-classes

This behaviour does seem to be as described by the "Sensor Entity" state_class definition. While "total_increasing" does generate a warning, it does seem to work okay compared to "total" and as such I'm inclined to leave the code as is above. See image.

Thoughts?

[Roving-Ronin]

Given I only have production and consumption (and that uses all my 6 CTs) I can't say re the oven. But as a device that is consuming energy (and never producing like a solar panel / battery) I would think it should be a 'total_increasing'.

The sa_todays_energy_generated_expected_total is something that can randomly go up and down (forecast in morning for sun and 100kW, then sudden clouds / rain and updated forecast drops to 10kW) and this should be class 'total'.

I've run the sa_todays_energy_generated_expected_total as class 'total' and it works fine.

BTW have you ever seen SA publish data for sa_todays_energy_exported_compensation ? It keeps showing up in the entities, yet it then says "This entity is no longer being provided by the energy integration. If the entity is no longer in use, delete it in settings."
Seems strange as SA do have this data, as it shows in their SA portal...so where is it / how come never shows in HA / via the API?

[PeterH24x7]

"sa_todays_energy_generated_expected_total" (expected) and its peer "sa_todays_energy_generated_expected_total" (actual) are both hour-by-hour cumulative generated energy in kWh that reset at midnight. The two are shown together in the chart on the SA Production page (https://my.solaranalytics.com/au/production/). I feel if one is total_increasing then so should the other.

As a sensor only, I would expect "sa_todays_energy_generated_expected_total" to work as either a total or total_increasing. However, things like the HA EM clearly don't understand total for other sensors such as my SA stove-oven, hot-water, heating-cooling and EV-charging kWh. As such I think for consistency it's best left as is despite the warnings (which maybe need review on the HA side?).

"sa_todays_energy_exported_compensation" and "sensor.sa_todays_energy_imported_cost" are news to me and the sensors must come from the EM; they appear to match the imported and exported energy costs as shown below. Never used them, but useful to know about and I'll add them to the documentation for the SA integration. Both appear to be hidden entities.

Looks like the revised code above stands as-is for the time being.

[PeterH24x7]

Maybe a bonus sensor here ...

(post edit 8-Feb-23 - fixed state_class mistake.)

# -----------------------------------------------------------------------------
#
# Home Assistant Energy Management extra - sa_todays_energy_total_net_cost
# HA EM automatically creates two entities respectively derived from the sa_todays_energy_imported and sa_todays_energy_exported
#   > sa_todays_energy_imported_cost - cost of imported energy
#   > sa_todays_energy_exported_compensation - revenue from exported energy
# This new entity provides the net cost (imported cost minus exported revenue)
#
#  - platform: template
      sa_todays_energy_total_net_cost:
        friendly_name: Todays Energy Total Net Cost
        unique_id: sa_todays_energy_total_net_cost
        unit_of_measurement: "AUD"
        device_class: "monetary"
        icon_template: mdi:cash
        value_template: >
          {{ (states.sensor.sa_todays_energy_imported_cost.state | float) - (states.sensor.sa_todays_energy_exported_compensation.state | float) }}
        attribute_templates:
          state_class: total_increasing

# -----------------------------------------------------------------------------

[PeterH24x7]

And maybe another bonus or two ... for those exposed to variable import unit rates and FIT rates - e.g. Amber.

# -----------------------------------------------------------------------------

      sa_todays_energy_import_rate:
        friendly_name: Todays Energy Import Rate
        unique_id: sa_todays_energy_import_rate
        unit_of_measurement: "$/kWh"
        device_class: "monetary"
        icon_template: mdi:cash-plus
        value_template: >
          {% if (states.sensor.sa_todays_energy_imported.state | float) != 0.0 %}
            {{ ((states.sensor.sa_todays_energy_imported_cost.state | float) / (states.sensor.sa_todays_energy_imported.state | float)) | round(3) }}
          {% else %}
            {{ 0.0 }}
          {% endif %}
        attribute_templates:
          state_class: measure

      sa_todays_energy_export_rate:
        friendly_name: Todays Energy Export Rate
        unique_id: sa_todays_energy_export_rate
        unit_of_measurement: "$/kWh"
        device_class: "monetary"
        icon_template: mdi:cash-plus
        value_template: >
          {% if (states.sensor.sa_todays_energy_exported.state | float) != 0.0 %}
            {{ ((states.sensor.sa_todays_energy_exported_compensation.state | float) / (states.sensor.sa_todays_energy_exported.state | float)) | round(3) }}
          {% else %}
            {{ 0.0 }}
          {% endif %}
        attribute_templates:
          state_class: measure

# -----------------------------------------------------------------------------

[Roving-Ronin]

Hi Peter,

Seperate issue, but just realised the sensors that I have for pulling gas m3 (via a reed switch using pulse_meter), with recent HA updates are now timing out when restarting HA, leading to them default to zero then reading the existing reading when it becomes available and adding that to whats already stored.. end result restart HA and the "Gas Meter Reading - m3" readings all double.
I know you had this issue previously with SA, just wondering how did you fix it ?

Here's the sensors I have, that read an ESP32 with the reed switch, being 'sensor.gas_meter_reading'. These sensors then apply the gas retailers 'correction factor' to come up with their 'corrected m3' reading and that is then mulitplied by 38.29 to convert from m3 to MJ.

---

Based upon sensor in ESP device being configured as type PULSE meter.
Uses code from SgtBatten and also from https://community.home-assistant.io/t/using-home-assistant-to-calculate-my-energy-bill-using-data-from-my-solar-inverter/344913/1

template:
  - sensor:

Takes sensor called 'gas_meter_reading' from the ESPHome device. Based upon the meter recording in 0.01m³ increments (10L)
The correction factor is the factor the retailer applies to the meter reading, to allow for temperature affecting gas volume.

      - name: "Gas Meter Reading - m³"
        unique_id: gas_meter_reading_m3
        state: "{{ states('sensor.gas_meter_reading') | float(0) * 0.9775 }}"   # Change 0.9775 to your retailers CORRECTION FACTOR
        unit_of_measurement: "m³"
        icon: mdi:meter-gas-outline
        device_class: gas
        state_class: total_increasing

Takes the above sensor 'gas_meter_reading_m3' and applied the 'heating value' as determined by the retailer, to convert from m3 to MJ.

      - name: "Gas Meter Reading - MJ"
        unique_id: gas_meter_reading_mj
        state: "{{ states('sensor.gas_meter_reading_m3') | float(0) * 38.29 }}"   #Update 38.29 to your retailers HEATING VALUE
        unit_of_measurement: "MJ"
        icon: mdi:meter-gas-outline
        device_class: energy
        state_class: total_increasing

Any assistance / advice appreciated.

[PeterH24x7]

No sure about what's causing your gas mis-read. Per the code above, I try and do some basic error checking before assuming the http get data is valid. If not valid, then both the last known good state value and timestamp value are retained.

      sa_todays_energy_generated_expected_total:
        friendly_name: Total Energy Generated Expected
        unique_id: sa_todays_energy_generated_expected_total
        unit_of_measurement: "Wh"
        value_template: >
          {% if states( 'sensor.sa_data_by_hour' ) not in ("unavailable", "unknown") %}
            {{ states.sensor.sa_data_by_hour.attributes.data[0].energy_expected | int }}
          {% else %}
            {{ states( 'sensor.sa_todays_energy_generated_expected_total' ) }}
          {% endif %}
        icon_template: mdi:solar-power
        device_class: "energy"
        attribute_templates:
          state_class: total_increasing
          time_stamp: >
            {% if states( 'sensor.sa_data_by_hour' ) not in ("unavailable", "unknown") %}
              {{ states.sensor.sa_data_by_hour.state }}
            {% else %}
              {{ state_attr( "sensor.sa_todays_energy_generated_expected_total.time_stamp" ) }}
            {% endif %}

[Roving-Ronin]

Peter,

Talk of the devil... running HA 2023.2.2 and noticed that I have bugger all readings on the Energy Usage graph, until it hit 10-11pm and then it showed the full days import / export / consumption till that point in time, and the readings aredouble the actual readings that SA has.

Haven't touched HA all day, just went to update to 2023.2.3 when I sat down and noticed this. Have you noticed the same?

[PeterH24x7]

I didn't get double readings, but did stop receiving data from 13.55pm yesterday. Not sure why. After waiting an hour I power-cycled my SA device at 3pm and all resumed normally excepting the data gap. It happened a few weeks ago too. The data on the SA portal also stopped for the period, but then was backfilled when the device came online again (presumably it was buffered somewhere). It happened a few weeks ago too and I was concerned my SA device has data transmit/receive issues. Maybe not if you've had similar probs.

Here's my day's hour-by-hour energy chart from HA EM with the lost 2pm to 3pm kWh included in the 3pm to 4pm slot.

Here's the power output in my HA Grafana charts - as you can see the missing data was straight-lined.

[PeterH24x7]

In short the code performed as expected. Without the unavailable/unknown detection in the past the readings for the missing period would be quite random. Now the daily tally remains intact.

[PeterH24x7]

Hi @Roving-Ronin
The new code is now published. I think this discussion can be considered closed. Happy to start a new one.
Thank you for your contributions.
Chrs, Peter