I’m not sure you could do this on Flow temp alone.
The way it does the DHW runs is to slowly ramp the flow from the cold water temp, so say starts at10C all the way upto and past your DWH target. So that could be 70C in my Arotherm.
Thanks. All this discussion has made me consider if I can set my Boiler & Tank up in a quasi HP manner running it at much lower temperatures. My issue has always been DHW and needing to heat the tank hotter than 55°C to get decent DHW supply. This has been exacerbated by a new boiler that takes an age to reach a good output temperature (more efficient apparently). I think I have worked out the issue (after 10 years!) and how I can resolve it.
I also think I can trigger this boiler to run at different target temperatures as well (TBC) which might improve things further - effectively a heating and DHW cycle! This discussion has not just benefited ASHP users!
So I reckon we need to support a range of different strategies for deciding whether our system is doing Heating versus Hot Water - and yet we need to unify those in some way so the MyHeatpump app and HeatpumpMonitor can report on CoP values for Heating versus Hot Water across all the systems.
How about a ‘boolean’ Feed that shows 1 for Hot Water mode and 0 for Heating mode - and everyone decides for themselves how best to derive the right value?
Or 1 for Heating, 2 for Hot Water and 0 for Standby?
Would be hard to derive that from historical data though, which is the appeal of using something like a flow temperature threshold…
A CT around the cable supplying power to the 3-port valve would work for all systems, some 3-port valves even have a microswitch in them designed to be used to provide a signal for applications like this. I’m lucky I can read a boolean register via modbus from my Samsung heatpump which informs the position of the 3-port valves, I’ve used this to separate central heating and DWH in the monitoring.
Very nice! The new buttons look great. The cost comparison tool is very cool. Would it be possible to colour the cost green if it’s less than gas and red if it’s more than gas? This would make it very clear that most heatpumps on the site are cheaper than mains gas to run.
I do have a digital signal for DHW/Heating, so it could be left to users to find a way to tell the system as suggested by @dMb .
I wonder if you could also add, on the charts page, an option to do an average profile of all systems (possibly being able to select out GSHP/ASHP or some other paprameters that could be thought about - e.g. something on average ambient temperature or degree days) using something like the existing ‘Profile Explorer’ App. From a personal perpective I’m thinking that his could start to get quite useful from a policy/grid reinfrocement perspective when there are a few more systems on board, but it does also provide a way for people to compare their own system with the average in a more granular way. It may be a bit of big ask , but just thought it might be interesting. This is my ASHP profile… (not got a full Feb or Mar yet)…
I’d agree with 85% - I was going to quote the same study Glyn posted, but it’s quite old - 2009 - and with recent campaigns to get people to lower flow temperatures averages are likley to have gone up a bit, but 90% seems pretty hard to achieve!
Hi everyone. I’m a product manager at UK not-for-profit Icebreaker One, responsible amongst other things for the Open Net Zero net-zero data index.
We love HeatpumpMonitor and would like to index it but we’re having trouble finding the data behind the visualisations - our aim is to index the data itself to make it more readily available for people analysing it, rather than websites with tables or graphs.
Could someone point me in the right direction please, or tell me it’s not ready for that yet? With my “encouraging good data citizenship” hat on, I’d also recommend you publish a specific licence for people using the data on the site. The Creative Commons or Open Data Commons licences would be a good place to start (can’t link to them due to new user limitations on the forum). Happy to answer any questions about this.
We’ll need @TrystanLea and @Timbones to comment on the practicality of providing access to the underlying data.
The point about licensing was raised on a recent webinar discussing HeatpumpMonitor with a recognition that including Attribution for bare data is problematic and that a more permissive license might be appropriate - but the key thing is to declare which license applies.
We also discussed whether we would need the individual contributors to opt-in to making the data more widely available, which might need bottoming-out first.
Is your intention to mirror data on your servers? and what level of detail would you be seeking to mirror? e.g 10s data, daily summaries for individual heat pumps, 30 day data table comparison, annual?
Yes we need to sort and be clear on the licence as @dMb mentioned.