Maybe it’s best to remove the daily aggregation, as it’s not nearly as useful as I thought it would be. Keep things simple, eh?
1 Like
Sure will do that.
Hi - very impressed with all the work on heatpump monitor, and I like the graphs in particular. Adding to your (no doubt) long list of ‘nice to haves’ could you add the design flow temperature as a ‘colour coding’ on the graphs. Since this will influence the sizing of radiators you might guess that this would be a significant impact. I guess fairly obvious but it would be useful to see.
Thanks @JackHolly good idea, I’ve added it to the issue list: Comparisons of performance vs design flow temperature · Issue #25 · openenergymonitor/heatpumpmonitor.org · GitHub
1 Like
I’ve moved the grid profiles and aggregation posts to a separate thread here so as not to have too many different topics in parallel: https://community.openenergymonitor.org/t/heatpumpmonitor-org-grid-profiles-and-aggregation
And another thread for other heat pump trials: HeatpumpMonitor.org: Other studies and comparisons
2 Likes
Any chance you could add - Heat output versus flow temp on the compare graphing tab?
Here is mine via XLS
Wondering if it might be worth replacing these columns on the front page with a single fabric efficiency figure expressed in kWh heat demand/m2?
Which would look like this:
Does that remove too much useful information from the list? those columns would be accessible via the expand for further info button…
is it a worthwhile change?
2 Likes
I guess in the context of a prospective heat pump purchaser casually looking at the dashboard and hoping to find a ‘match’ for their own property, a single figure for Fabric Efficiency is probably more difficult to relate to than the existing, more descriptive columns.
Having said that, for a more ‘technical’ audience, I do like the normalised efficiency metric…
Thanks @dMb I’ve added an option to show this view for now with a checkbox at the bottom of the page, I’ve also included kwh/m2 electric for interest.
2 Likes
This is really useful - thanks!
1 Like
1 Like
I’ve just turned my heat pump off at the isolator switch because I’ve not needed any heating since 3rd April and DHW is consistently being covered by the diversion of excess solar PV generation. I’ll turn it back on in Autumn.
My NIBE F1145 GSHP consistently draws 1.1 kWh per day (about 45 W) when in ‘standby’ (with no pumps running) so that’s money and carbon I don’t want to be wasting. This explains why my system’s 30-day COP is so bad but my daily cost is so good.
I want to ensure I don’t mess up the long-term stats on HeatpumpMonitor though:
-
The Heat Meter and Electricity Meter are still reporting ‘real’ readings so that’s all good - they’re just showing no electricity consumption and no heat output.
-
A potential issue is the temperature readings - those are sourced from NIBE Uplink and since the heat pump is switched off it’s not sending any updates. The way I report the data to emoncms means I’m effectively sending the last ‘real’ reading (from 09:00 today) repeatedly - and will continue to do that all summer.
- I could use an alternative source of Outdoor temperature and report that instead; same for Indoor temperature
- I could report the heat meters’ view of Flow and Return temperatures (rather than the heat pump’s), I suppose
Is that worth worrying about though? If the heat pump isn’t running do the temperature readings actually matter?
hi all… my first post in this thread.
I’ve a samsung 16kw gen6, self installed (thanks glyn hudson for your video, I did watch as part of my planning). I’m monitoring it via modbus into esphome then into home assistant. I’m pushing the data as feeds into an instance of emoncms running on a debian VM in azure. emoncms heatpump app is running and shows my data.
at the moment my emoncms’s http server is locked down so only I can get to it from my static IP at home, I’m not going to unlock this to the world until I have a handle on the “make public” part?
I’m a bit puzzled about how the “make app public” button works and what is actually required from the point of view of open ports, web server configuration etc? I couldn’t find docs about this part, can someone perhaps explain? I only want to make the performance data as shown by the app public, not my entire emoncms front end, login page etc.
Also couple of feedback points about the install docs which I followed here:
https://docs.openenergymonitor.org/emonsd/install.html
I tried Ubuntu 18LTS, Ubuntu 20LTS, and debian 11 azure market place images. All failed with PHP not found errors. I’m no dev , far from it, but I was able to deduce that it was looking for PHP8.1 and couldn’t find it and had no way to get it. I was eventually able to get it working (after multiple iterations, easy in azure by just blatting the vm and starting again) by using debian 11, and adding the repository for PHP8.1 according to this: https://computingforgeeks.com/how-to-install-php-on-debian-linux-2/, installing PHP8.1 manually , then letting the emoncms scripts do their thing. perhaps something about PHP8.1 should be added to the emoncms install document and/or script?
cheers
Ian
I’d like to add the flow rate to the app, as I have this data. but I don’t see it in the heat pump app config parameters, do I need a different version?
my admin page info says the below (installed today)
Components: Emoncms Core v11.3.0 | App v2.6.10 | Dashboard v2.3.3 | Device v2.2.2 | Graph v2.2.3 | Backup v2.3.2 | DemandShaper v2.2.2 | Postprocess v2.2.7 | Sync v2.1.4 | Usefulscripts v2.3.10 | EmonScripts v1.6.13
One option is to set up an account at emoncms.org (@TrystanLea can sort one out for you) and then sync your heat pump data to that account. This will save you having to expose your personal instance to the web.
I would be cautious about switching off the unit at the isolator, there’s a warning again this in my Samsung heat pump user manual:
Best to keep the isolator switched on to maintain power to the unit and just switch off demand for heating or DHW at the controller if not needed. This will also have the advantage of maintaining the monitoring.
Thanks Glyn. I’ve checked both the Installer and User manuals for my NIBE system and they don’t include a warning such as you have for your Samsung unit, so maybe my system is more tolerant of having the power off. I’ve turned it off for months before with no issues.
For now I’ve switched it back on at the isolator but off on the controller. I’ll keep an eye on the electricity consumption in that mode (but from a quick check it’s back to constantly drawing 45W).
1 Like
yes I did look into that and got as far as registering for an account at emoncms.org. I was even prepared to contribute a nominal fixed amount to the run costs. But once I saw it was charged per feed rather than per instance, I baulked. there are quite a lot of feeds needed to do this properly , some of the feeds are purely the results of mathematical operations on other feeds, which is irritating to be charged for, and that number goes up every time another data type is added (RoomT, FlowRate). Given that I’d be contributing my data to the public good out of altruism, and probably all manner of commercial entities will be able to get value out of that data, it rather sticks in the craw to have to pay to be able to contribute it!
I did have a look at those instances on heatpumpmonitor.org who are using self-hosting, they are all exposing their emoncms login front end, which is one critical vulnerability or brute-force away from trouble on their home networks. I’m not saying that the devs here don’t take care, nor am I saying that those people have set weak passwords, but that is not something I wish to take any risk with at all on my home network, which is why I looked at azure hosting. I was really hoping there’d be a way to just publish the public app, perhaps on a different port.