Certainly something that I’d like to have a go at publishing when I get my ASHP (hopefully through the summer).
I don’t think there is enough real world data out there for folks to see.
Yes, there are some people sharing the odd screenshot and monthly summaries, but I’d like to be able to share all the data I can. As I hope my installation would be a good one. LOL.
I could possibly go down the public web server route too, host it somewhere or other.
My other thought was maybe influx/grafana combo which I’m familiar with through my energy-stats site.
But you wouldn’t get the cool ‘cop in window’ etc.
I’ve recently discovered PVOutput.org, and am now pushing my solar generation / consumption / etc data to it. It’s very well suited to collecting and aggregating PV data over long periods and displaying it publicly.
It would be handy if there was something similar for heat pump performance data…
I would like to do so. But I’m using a home-grown approach so sharing emoncms is not an option for me. That said, I have a script that saves electrical input and heat output daily (and by implication COP). Such scripts could be adapted to send the data to a server we could all access.
Hello all. Apologies in advance if I am violating the etiquette of the forum with this post! My name is Jane Wilson, I’m the COO at Hildebrand. We have a number of members of the HA community using our Glow CAD with MQTT for their local energy management. Thank you for choosing our solution.
We are about to launch the Glow Heat Pump Community - a BEIS grant funded initiative to support getting the concept from idea to reality - to help consumers and installers make better informed decisions based on using data (energy consumption and building fabric - getting an HTC figure from internal temperature sensor and consumption data) to understand 1) if your home is ‘heat pump ready’ and 2) if the HP (post installation) is running as efficiently as it could. The intention is that we overlay this with a Case Study database - so that consumers can look up the experience of ‘someone like me’ before they make their investment. There will be tools for installers as well, and a similar community element.
If you’d like to contribute your experience, please let me know. If you think there is information we could host that would be useful to this community, again, let me know. We will be open sourcing much of what we develop. One of our goals is to support an accessible heat pump database as well - with pre- and post- installation performance data within the context of the physical environment the device operates within.
HTC is a way of determining the maximum heat loss of your property by using a combination of fuel used to heat the home and the average daily outside temperature. Usually using data over a period of the heating season.
It’s a term I go into depth on in my “What Size Heat Pump” article.
@mjr - the web site will be designed to support everyone, from complete beginners to experts
@Zarch - thank you for explaining what the HTC is.
We will be working with this solution, independently tested by UCL as part of the SMETERS programme, SmartHTC Technical Specifications - Build Test Solutions - using our soon to be launched environmental sensors that will measure temperature and humidity.
Hi Brian - our partners, Build Test Solutions, do need to make a living and have spent many years of building PhD level expertise to develop and refine that algorithm. To reassure you, it isn’t something they intend to charge a lot of - probably in the single digit pounds.
The input required is three weeks of energy consumption data, three weeks of an internal sensor temperature readings and, obviously, capturing external temperature for your nearest weather station.
That feels a bit offensive to the openEnergyMonitor developers (and all commercial FOSS developers), who do need to make a living and have spent many years building their expertise, yet really open source their system instead of holding it to ransom.
That’s not the biggest worry. It’s what happens if they go bust or get bought out? I’ve contributed to too many efforts, projects and initiatives that are no longer even much of a memory.
I’ve not yet been able to ask the other owners of the heat pump, but before I do, may I ask if this is open to openenergymonitor users who don’t use HA, and would we have to buy the Glow CAD or is that covered by the grant funding? And would we need to get a weather station or could the heat pump external sensor readings be used?
Would I be able to participate if I was already collecting this data with my own hardware?
The How it works page suggests that I would be able to. I am put off by the setup fee though.
Thanks for posting, good to hear that your initiative is progressing, this is with Nathan from @BetaTeach who posted above I assume?
Great to hear that you are at least making your part open source, could you share more details on that?. It will be good to compare notes and findings of our two initiatives! best of luck!
Yes, Nathan is one of our Consortium Partners - go with the best!
We’ve already open sourced the models behind our smart tariff (ToU) comparison tool - developed last year which are on observablehq. What we need to do is add live tariffs but the whole market has changed a lot in the last 18 months… as we all know. That tool will help people to understand the Total Cost of Ownership and how different tariffs could be helpful (depending on their choices).
As the project evolves, we’ll see what we can Open Source - as sometimes things are proprietary (still trying to get to the bottom of the database of heat pump characteristics). Do stay in touch and thank you.
Gosh, sorry for asking “one eternity later” @Timbones but I haven’t really investigated the auth. In your opinion is it better / easier / safer to use one approach rather than the other? It sounds as though you might be happier with it using the read version of API key?
For personal use, requiring login is fine, but if I wanted to share it publicly then it would need to use the read key. Many (all?) of built-in emoncms apps use read keys.
Given that I’m already sharing via MyHeatPump app, it’s not hugely important to me to be able to share the MMSP app. Probably only useful for comparing two MMSP systems.
Some people may have privacy concerns about sharing live data publicly, so the addition of a “delayed” option could be useful, as @TrystanLea suggested in his opening post on Sharing heat pump data.
I’ve also started sharing my ASHP data in the same was as @Trystan by using Emoncms to sync our local data to emoncms.org, this allows us to share all data without the risk of sharing live data:
@glyn.hudson thanks; it’s fascinating to see someone else’s data who has a very similar heat pump, seems Samsung is a fairly exclusive club at the moment.
I’m interested in the behaviour seen on say Friday 7th October (and others) but especially between 18.00-19.30 where it runs for 5 minutes and then (I think) just runs the pump(s) for 3, then repeats the cycle. My 16kW has this behaviour too and it seems strange but more efficient to do this than to run constantly at the energy levels either side of the episode.
Do you know what’s going on?
Is it okay or something I should try to tune out?
Cheers!
Edit: p.s. your link to your emoncms page is incorrect but I knew what to do
