Tasmota - state is not strictly increasing

[perseus177]

The problem

Warning in logs Entity sensor.pracovna_energy_total from integration tasmota has state class total_increasing, but its state is not strictly increasing.

Hardware - Blitzwolf SHP6 Firmware version - 13.1.0(tasmota) Sensor - Energy Total

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Tasmota

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tasmota/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:297
Integration: Senzor (documentation, issues)
First occurred: 8. decembra 2023 o 00:05:10 (2 occurrences)
Last logged: 9. decembra 2023 o 00:05:10

Entity sensor.pracovna_energy_total from integration tasmota has state class total_increasing, but its state is not strictly increasing. Triggered by state 240.788 (240.789) with last_updated set to 2023-12-07T23:00:01.500313+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tasmota%22

Entity sensor.chladnicka_energy_total from integration tasmota has state class total_increasing, but its state is not strictly increasing. Triggered by state 143.891 (143.892) with last_updated set to 2023-12-08T23:00:02.586314+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tasmota%22

Additional information

No response

[home-assistant[bot]]

Hey there @emontnemery, mind taking a look at this issue as it has been labeled with an integration (tasmota) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `tasmota` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tasmota` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tasmota documentation tasmota source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[perseus177]

Still same problemm

[RaynePhantasm]

I have the same problem with my tasmota devices. At midnight, the value of “energy_total” sometimes decreases.