core icon indicating copy to clipboard operation
core copied to clipboard

Shelly Plus Plug S reports non-increasing value

Open davidrpfarinha opened this issue 1 year ago • 2 comments

The problem

I have a Shelly Plus Plug S which is collecting data from my desktop setup, so I can understand how much is it consuming. Today I noticed that I had an error saying that the value is not strictly increasing.

Entity sensor.pc_outlet_switch_0_energy from integration shelly has state class total_increasing, but its state is not strictly increasing. Triggered by state 27.245672 (27.245674) with last_updated set to 2023-10-16T01:46:59.581362+00:00. Please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+shelly%22

What version of Home Assistant Core has the issue?

core-2023.10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Shelly

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

davidrpfarinha avatar Oct 16 '23 18:10 davidrpfarinha

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of shelly 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 shelly Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


shelly documentation shelly source (message by IssueLinks)

home-assistant[bot] avatar Oct 16 '23 18:10 home-assistant[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.

hi @davidrpfarinha, please share diagnostic file for this device.

chemelli74 avatar Jan 21 '24 23:01 chemelli74

Hey @chemelli74,

I hope you are doing well. This happened a while back, and I don't recall seeing this again. Nevertheless, here you have the old diagnostics, and if you need the newest version, I can share it as well.

config_entry-shelly-d63e72238703ee99f2089a980a11b0e8.json.txt

davidrpfarinha avatar Jan 22 '24 15:01 davidrpfarinha

@davidrpfarinha , going to close this issue for now. If you see it again, please open a new one.

chemelli74 avatar Feb 03 '24 19:02 chemelli74