Good point, we could add some text to the effect of, we recommend asking asking the installer if they are happy for the system to be listed.
@Vinny good points, including that information in notes makes a lot of sense.
We are working on an upgraded backend for heatpumpmonitor.org to include these fields and many of the others raised before around system boundaries etc. Hopefully have something to show soon!
Looking good Trystan. Iāve already asked my installer and theyāve very happy to be listed.
One thought about the tick boxes at the bottom of that screenshot; would it be worth providing (links to) definitions of terms like Buffer and Low Loss Header? Maybe you have that covered elsewhere on the page, especially if weāre including details of system boundaries where we need everyone to be using the same definitions.
I have a two-pipe Buffer (on the flow side, which purely adds volume) and a four-pipe Low Loss Header (which does hydraulic separation for three emitter circuits, each with their own pumps) so I would plan to tick both boxes (although my Buffer doesnāt actually do hydraulic separation, so maybe that would be wrong).
Maybe using terms like Two-Pipe Buffer versus Four-Pipe Buffer would be clearer - or maybe that would cause more confusionā¦
Is it possible to automatically add weather data if people put their postcode into the heatpump app?
Almost like a default addition to the data collected.
Many of the installs on the big list arenāt showing outside temp data and I feel this is very important to show when trying compare performance between units.
Is there a free weather data stream that could be used?
In my install I provide the outdoor temp from a probe connected into the heatpump hat, but obviously not everyone is going to go to those extremes.
With our APIs, you can get data for any location on the globe: minutely forecast for the two hours, hourly forecasts for one week, current weather, and history for the 40 years back, with a vast range of meteorological parameters. All these remarkable products are available for free with up to 1 million calls per month. For those who are looking for a bigger service, we provide several paid subscriptions and a range of historical products.
Although the page at the link above says 1 million calls per month for free, this page:
says 1,000 calls per day, which should still be sufficient.
With the amazing recent chatter on Twitter about hot water performance, iām wondering how it could be possible to isolate just DHW performance of the heat pumps on the list?
I know weāve talked about this before, but it seems more relevant than ever. And Iām keen as anyone to understand my own performance to try and improve it.
Could some hardware be created to somehow know when the diverter is in hot water mode?
Or can we use a CT clamp or something?
Iām just thinking about a generic way that would work on all installs, regardless of make/model etc.
Many of us could isolate pumps watts in a feed cos we monitor that stuff via extra emontx etc, but thatās pretty hacky and not for your average installer to want to mess with. Itās almost like we need an out of the box way of doing it?
Some systems already do this (though I donāt know how many), so the data aggregation could be provided with an extra feed to indicate heating or DHW, and provide analysis of that data from those systems where it available.
Ecodanās Melcloud, for example, provides 0/1 values for each circulation pump, as well as separate energy readings for heating and hot water. So I can setup a 2nd āMy Heatpumpā app that only shows hot water: Emoncms - app view (compared to my primary one that has both).
Does the data youāre reading direct from Vaillant via eBus have any flag or register for DHW? This is how I do it for my Samsung, thereās a modbus register for the position of the 3-port valve.
What 3-port valve have you got? Does it have a built-in microswitch? e.g the Mut Meccanica Tovo SV does, but a standard Honeywell does not.
The fallback solution would be to attach a CT around the 3-port valve live or neutral cable, this solution will work for everyone but requires extra monitoring hardware e.g emonTx V4, emonVS voltage sensor and 20A CT. The power used by the three port valve will be very small, so it needs a very accurate monitor, I donāt think the old emonPi with a 100A sensor would be good enough.
Hi I am wondering whether it would be worth allowing the annual energy performance to be displayed as kWh/m2 in the same way as āproperty infoā columns? That way both sets of data would be displayed as like for like.
Probably a silly question but for the dashboard, when referring to āHeat Demandā is this just for space heating or also for hot water?
I can see the benefit of both options but to allow for an apples to apples comparison would it be possible to either ask for both fields or to clarify which is required?.
Alternatively while it would require some additional scraping of data, for UK based users could you not ask for the EPC URL and pull the property type, city, floor space, heat demand directly from there?
Hello @KnightPhoenix, good question, it should be both and could be clarified. The monitored data is both so as you say making sure the heat demand figure is both is needed for a apples to apples comparison.
It would be interesting to collect data for EPC heat demand and subsequent heat demand as calculated in the heat loss survey. Thatās a good idea to try and pull in data from the EPC database.