# Monitoring shelly plug s

**URL:** <https://discourse.nodered.org/t/monitoring-shelly-plug-s/73023>\
**Category:** Share Your Projects\
**Tags:** node-red-dashboard\
**Created:** [1 January 2023 13:59 UTC](https://discourse.nodered.org/t/monitoring-shelly-plug-s/73023 "2023-01-01T13:59:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [2 January 2023 10:13 UTC](https://discourse.nodered.org/t/monitoring-shelly-plug-s/73023/5 "2023-01-02T10:13:00Z")

</div>

> [@juntiedt](#):
>
> However I will put some logic in my node but it will take some time.

Have a look at this topic, it may give you some ideas how to resolve it.

> [@Understanding Shelly aenergy vs apower for daily power consumption?](https://discourse.nodered.org/t/understanding-shelly-aenergy-vs-apower-for-daily-power-consumption/72331/19):
>
> Calculate it before writing to the database. Save the reading to context, then when another reading arrives compare it with the previous reading to determine how much energy has been used between those times, and write that to the database, and then save the current reading to context, etc, etc. You can determine and deal with the device being reset because the current data would be less than the previous. To then read it in influx, just sum the values over whatever time period that you wish…

---

_[View the full topic](https://discourse.nodered.org/t/monitoring-shelly-plug-s/73023)._
