This is a thread for feature requests and discussion relating to the rough development plan and change log available on the thread here: OpenEnergyMonitor development plan 2024.
I agree, but I suspect the devil is in the detail. The alignment of the thirty minute intervals might need changing for example. The obvious alignment is with the half-hour periods of a smart meter, but these periods are not aligned with a clock (exactly on the half-hours). There is a noticeable random delay added in each meter, AIUI, so it might need adjusting to match reality. Deriving the kWh figures from the power might be one way to do this.
1 Like
This would be good. Can this go into emoncms rather than just cloud?
Iāve asked many times for a means of aggregating down. For instance, I have long-term temperature data that Iād like to reduce to Max/Min/Avg and also be able to get a rolling figure for week/month/year.
Did automated trimming of Feeds ever appear? A daily ātrimā would be useful.
Can refining all the very old issues in GitHub be added into the roadmap as well - perhaps even fix some 
but at the very least just close as not happening.
1 Like
As discussed in past, Iād like to be able to assign access to nodes to individual users with permissions. Today a node is assigned to an account with either read, write, or disabled privileges. We have instances where some users only need read access to various nodes, whereas other users may require write access to the same nodes.
It would be helpful to have user permissions (or user roles) that are then granted access to various nodes. MongoDBās Access Manager is a good example (substituted Node for Project).
1 Like
Emoncms
It would helpful to have configurable alerts such as inactive feed notification, or values above/below expected thresholds, to help identify issues in unattended locations.
1 Like
Iād love to get DHW tank temperature as input to the heatpump app, if only for display purposes.for now. It could down the road be useful to compare DHW performance better as charging offsets etc. could be automatically determined from the data.
1 Like
I am supportive of a subscription plan at a reasonable cost.
I will be interested in how you will handle the existing credits (we have a sizable balance and this was one of the appealing features of emonCMS - the more we buy from the shop, we get credits for emonCMS hosting).
Perhaps one way to keep purchases separate from subscription plans is to offer discounts on future purchases of gear from the shop vs subscription top up credits. The current emoncms subscription credit is 20% of the purchase invoice price. How about creating a shop voucher for future purchases?
Alternatively, provide tiered subscription rates based on the number of feeds. If I purchase more gear from the shop, I will create more feeds, so a discount for having more feeds is somewhat like the credits we get today.
Of course, all this depends on the subscription rates you plan to introduce. The current rate of 1GBP per year per feed is reasonable for a small number of feeds, but it gets expensive with larger numbers. With my credits and current number of feeds, I have covered over 5 years of emonCMS use. Changes to the current model will impact my budget going forward.
Thanks for your thoughts on this @grod55 the primary goal of subscription or scheduled payment, is to make it administratively easier for users. We donāt envisage any significant movement in overall account costs at this point, perhaps a slight change in distribution of cost if higher resolution feeds are more expensive than lower resolution feeds, but nothing finalised yet. Interestingly the Ā£1/year per feed is now 20% cheaper than the Ā£1/year per feed when billing started in 2018 due to inflation according to Inflation calculator | Bank of England.
1 Like
Thanks. I appreciate the insight and glad you have been able to maintain the 1GBP price. Also understand that some feeds are more expensive.
@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.
Yes, definitely. I have a sensor at the top and in the middle and look at both. Are those distance measurements in datasheets of the cylinders?
September 22nd amendments to development plan:
Heatpump app:
Add button to recalculate daily statsAdd immersion heater feed option- complete.
Expand account authentication to make write apikey available for backend processes such as rebuilding daily data stats- different mechanism implemented for now a master key specifically for the route cleardaily, as many systems were not associated with an emoncms.org user login specifically.Implement mechanism for rebuilding daily stats for all accounts from HeatpumpMonitor.org-complete.Forum post about mirroring self hosted systems on emoncms.org- HeatpumpMonitor.org self hosted systems
1 Like
Something else Iāve seen mentioned in the past is to add the ability to add notes.
This would be useful to show when something about the system, its settings or the building itās heating happen. This would help explain changes in the performance of a system and help with those trying to keep track of tweaks they are making.
4 Likes
Iād like to see one additional COP button/grouping that is Full window - DHW. My rationale is that the āSpace heatingā looks only at times where the compressor is on and neglects periods where just the pumps are on when the heat pump is cycling. Taking this idea a bit further, maybe we could have an advanced view with check boxes on what to include in the shown stats. Something like
DHW CH Pump only Standby (pumps off)
Would then only include periods where the compressor is on for space heating and also the periods when the pumps are circulating the hot water between active cycles.
The existing buttons could just map to the appropriate selections of those check boxes, which would hence not impact usability for anyone thatās used to the way it currently works
1 Like
Edit: ignore was thinking this was hpm dev post
Idea for heatpumpmonitor.org
Would it be possible to add an āaverageā for each column (where applicable)?
My usecase: SPF/SCOP is only part of the story, I often add other data such as electricity consumption, room temperature, etc. to get a fuller picture when comparing systems. It would be really useful to add a mean average row for those columns where it is applicable.
Alternatively adding additional detail to the āTotalsā section for the added columns which would support average data.
1 Like
On each systemās dashboard view buy default it displays MY HEATPUMP at the top, this title can be edited by the user when configuring the app in Emoncms. However, would it be useful if this title by default displayed the heat pump make/model and location, like it dose on the system summary page. May be a useful identifier when comparing two or more systems side by side.
1 Like
@Lakee yes agreed! I was thinking about just this the other day, Im thinking of introducing a way to link a emoncms.org dashboard to a heatpumpmonitor system, this could allow the dashboard to load this information from HeatpumpMonitor.org.
This would be part of a āShare to HeatpumpMonitor.orgā button that would be available from the emoncms.org MyHeatpump app.
1 Like
Also, how about being able to filter by country/region/county etc - nice to be able to compare local systems in similar climates, as this can have an impact on ASHP performance - I think thatās only possible at the moment if itās part of the systemās location?
What about a āsubjectiveā evaluation of the location - exposed, sheltered, suburban, etc? This could have a significant effect, especially if the buildingās insulation is not up to modern standards.