[Feature request] Split energy totals

[analystcmyk]

TLDR :

Add energy used to separate total variables, based on timeslots. eg. LowTarrifTotal between 00:00 and 07:00, HighTarrifTotal between 07:00 and 00:00

Situation :

• We share a house (3 floors) with multiple people.
• We have a single main energy contract, and one monthly bill for the total energy consumption.
• We have an OpenBeken Energy meter installed per floor
• We have no home automation, only an MQTT broker
• Electricity supplier gives 3 tariffs groups : low, mid, high

1. Weekend : low, 00-24
2. Monday - Friday : low 00-08
3. Monday - Friday : mid 08-10, 14-18, 22-00
4. Monday - Friday : high 10-14,18-22

Issue :

Calculating real costs per floor is a nightmare, to be energy efficient you want to promote low tariff usage.

Those responsible for splitting the bill have no way to distinguish between different tariffs.

This means a lot of owners just take the average price per KWh.

This is problematic :

• it is unfair : you pay for a neighbor running heating all day while you try to do your washing in the weekend.
• it removes any incentive to be energy efficient.

Proposed :

A variant of SetupEnergyStats that allows for split totalcounters

In this situation it would mean that each meter will have 3 additional total power used variables. ( low, high, mid)

example : SetupEnergyTotalGroup [TotalGroupName] [starttime][endtime] [WeekDayFlags] eg.

SetupEnergyTotalGroup "LOW" 00:00 08:00 0xff;  // all days
SetupEnergyTotalGroup "MID" 08:00 10:00 0xFC; // weekdays

All TotalGroup values should be available via MQTT.

Possible issues :

• How to prevent overlap ? At any time only one TotalGroup can be active.

Remarks :

• Alternatively you might use multiple addRepeatingEvents() to set the total, with a command like SetTotalgroup = "MID";
• Looking at the examples below, I don't know how seasons could be included. It might be an idea to include startdate-enddate
• Hourly prices would be even more precise, but a lot of more work. See https://app.preciodelaluz.org/
• apart from time-of-use structures, there a lot more ways to differentiate : https://en.wikipedia.org/wiki/Electricity_pricing#Rate_structure

Some examples of time-of-use pricing schemes:

• The UK has a time-of-use pricing scheme known as Economy 7, where electricity is cheaper during off-peak hours (usually from midnight to 7 am).
• In France, there is a time-of-use pricing scheme called Tempo, where electricity prices vary based on the season and time of day. The year is divided into three seasons (white, blue, and red) with different pricing tiers. During weekdays, electricity is more expensive during peak hours in the evening, and cheaper during off-peak hours
• Italy has a day/night tariff scheme called Fascia Oraria, which divides the day into three periods: peak, off-peak, and night.
• Germany has a time-of-use pricing scheme called SLP (Standard Load Profiles), where electricity prices vary based on the time of day and the season. The day is divided into multiple time blocks.

[analystcmyk]

Other scenarios :

• we have a shared office with 2 people : one only works at monday and friday : at the end of the period we calculate the bill

[analystcmyk]

Not part of this feature request, but related:

// totalgroup "mary" is created, start with 0
SetupEnergyTotalGroup ADD "mary" 

// totalgroup "john" is created, start with 0
SetupEnergyTotalGroup ADD "john" 

// add all energy used now to totalgroup named "john"
SetupEnergyTotalGroup SET "john"

 // delete the totalgroup "john"
SetSetupEnergyTotalGroup REMOVE "john";

This would allow dynamically setting the total, (checkout, checkin) for example you just send the name of the total via MQTT

Maybe this is already possible with existing scripting