TUYA TS011F_plug_1

[DanielSzym11]

The problem

Would it be possible to add an energy measurement entity for the TUYA TS011F_plug_1 smart socket that would reset itself to zero every 24 hours? This is needed to apply the condition in automation that energy > 0.1 on a given day. At this moment, this energy is adding up, it can of course be reset to zero, but it requires manual intervention in the Z2M console of the device and sending a reset command. If I do not have zero energy and the values add up and are above 0.1, the automation can turn on and perform actions, even though it shouldn't. It's about sending a message about the end of washing, but there was no washing. It sees that Power = 0 and Energy > 0.1 for over 1 minute and performs automation actions.

What version of Home Assistant Core has the issue?

2024.1.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

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

[mib1185]

Hi @DanielSzym11

You may be interested in the Utility Meter integration. But this sounds like a request for support? We use GitHub for tracking issues with Home Assistant Core itself, not for providing support. If you are in need of support, you should try our Community Forum or join our Discord chat server.

Thanks! 👍

[ChristophCaina]

I would also use a Utility Meter in this case, as mib1185 already mentioned... there's no need for additional entities directly on the device level - the integration should only provide the entities and information sent by the device itself.

[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.