# OpenEnergyMonitor development plan discussion

**URL:** <https://community.openenergymonitor.org/t/openenergymonitor-development-plan-discussion/26789>\
**Category:** Organisation\
**Created:** [29 September 2024 08:20 UTC](https://community.openenergymonitor.org/t/openenergymonitor-development-plan-discussion/26789 "2024-09-29T08:20:06Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![TrystanLea](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/trystanlea/32/31_2.png) [@TrystanLea](https://community.openenergymonitor.org/u/TrystanLea)\
**Post date:** [22 September 2024 08:55 UTC](https://community.openenergymonitor.org/t/openenergymonitor-development-plan-discussion/26789/10 "2024-09-22T08:55:00Z")

</div>

@djh interesting point about half hourly alignment, all the work I have done on half hourly has been aligned with the clock, I thought that would be a requirement to make half hourly settlement possible?

@borpin yes down sampling would be an emoncms core feature. Will consider min/max/mean when I look at this.

@grod55 I would like to do more work on the multi account management module but Im afraid per node user permissions is not a level were going to get into at least for the foreseeable future. Im aware this side of things can get complicated fast from previous attempts.

Alerts are a much needed feature!

@Andre_K +1 for tank temperature, though it needs sensor distance from top of the tank and distance from top of coil really to make comparisons between systems easier.

---

_[View the full topic](https://community.openenergymonitor.org/t/openenergymonitor-development-plan-discussion/26789)._
