Values from IAM sensors get stuck and dont revert to 0

[Eskot11]

---

name: Bug report
about: Create a report to help us improve
title: 'Values from IAM sensors get stuck and dont revert to 0 when power stops'
labels: bug
assignees: ''

---

Describe the bug
While the ENVIR operates correctly for whole of house sensor (but of course this never drops to 0), the 3 IAMs I am using maintain the last value stored in them rather than reverting back to 0 when power stops, they change correctly as demand rises and falls however it sometimes sticks at a value when the device (pool pump) stops, this means the log file continues too log the Watts the high value.

To Reproduce
This happens every day and requires a reboot to clear the 'stuck' value

Expected behaviour
I would expect the Watts value to revert back to 0 once it stopped receiving info for > 5s

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop/Server/Device (please complete the following information):
Raspberry Pi, 3b
HACS

• Version of the Custom Component installed? 0.2.4
• Model of the Current Cost Device ENVIR

Additional context
Add any other context about the problem here.

Logs
No errors appear in the logs - the Envir continues to work perfectly its only the IAM sensors that dont

Please set the Current Cost Custom Component's logging level to debug and provide relevant logs section from Home-Assistant.
To Enable debug logging level, add this to your configuration.yaml and restart:

logger:
  default: error
  logs:
    custom_components.currentcost: debug