Dual total energy counter

[lk29]

Perhaps someone has already described the method.

How to display three total energy meters

1 - 23:00:00-06:59:59
2 - 07:00:00-22:59:59
3 - the sum of the first and second

[wjohn007]

I had a similar requirement.
I was looking for a solution to display the hourly and daily consumption of electrical energy.
Tasmota provides the raw data. The graphical display should also be implemented under the Tasmota UI.

I defined a new Button "Historical data and statistics" in the main-menu.

Tasmota forwards the raw values ​​to thingspeak.

Thingspeak saves the data, aggregates it as desired and generates a graphic that Tasmota can integrate via iframe. (scripting is required)

This gives you the following representation, for example:

I'm pretty sure that this will also meet your requirements.

John

[lk29]

beautiful but redundant and requires third-party service.

For this I can use mqtt or homeassistant.

I’m looking for a simple solution to take into account the total consumption but divided by time (night and day tariff)

[wjohn007]

For tasmota-only solutions berry-script my be helpful.
John

[lk29]

do you have examples?

[lk29]

For tasmota-only solutions berry-script my be helpful.
John

Use esp8266ex
Berry scripting not supported:(

Make custom!
I'm trying

[sfromis]

More generally, a reason why Tasmota does not facilitate doing what you'd like to do is that the deliberately rudimentary web UI is not intended to be used as a "device dashboard" for daily operation, which is instead expected to be handled in your backend platform with much better resources available.

[lk29]

But if there is a “web interface”, then why not use it to the fullest? In my project I would like to maintain minimal dependence on third-party software.

[sfromis]

Because Tasmota was designed for ESP8266 with very limited resources, the priority was ability to handle controls and sensors, not a flexible web UI. There are reasons why the "M" in the "Tasmota" name means "MQTT" 😉

To be clear, I'm not trying to say what you "should or should not", merely explaining the principles not including being a standalone server with rich features for growing a "device dashboard".