I am considering getting the Heat Pump Monitoring Bundle from the OpenEnergyMonitor store; and just wanting to check if this is a good idea / necessary.
I am on a journey of decarbonising my home, and have managed to reduce my grid usage by 75-80% in the last 4 years. Through installing a ground source heat pump (12kW NIBE F1155), solar PV (k17Wp) and battery storage (3x Tesla Powerwall, 40.5kWh).
My NIBE has an external energy monitor, an “emlite EML M19 - ECA2”; and I subscribe to the NIBE Uplink premium data service. However, for some crazy reason (to save a few pounds a month on server costs??) NIBE scale down data over time, so there’s no accurate log of kWh usage on a historic hourly, daily, weekly or monthly basis. Their advice was to take a measurement every day. Which kind of defeats the purpose of having an external energy monitor and paying €49.50 plus VAT every year for NIBE Uplink!!
Has anyone got advice on how to access data from the emlite meter directly, or is the Heat Pump Monitoring Bundle my best solution?
I have an 8kW NIBE F1145 which is connected to NIBE Uplink (though I don’t pay for the premium History or Manage options) and I grab the instantaneous readings back from the NIBE Uplink API every 2 minutes, storing them in my own database. (Actually I publish them as MQTT messages so they’re in the same format as a range of other monitoring info which all gets stored in InfluxDB.)
The NIBE Uplink API is pretty decent; the main barrier to ease-of-use is their choice of OAuth2 as the Authentication mechanism so my webpage that Trystan linked above is mostly about navigating the OAuth2 handshake steps to get a valid OAuth2 token.
Give me a shout on here or leave a comment on the MarshFlattFarm page if you get stuck or have questions.
Hi David, I managed to follow most of your instructions; and got the OAuth2 working. However, when I get passed the NIBE login and captcha, I am getting the following error page, relating to the code in the callback index.php
@dMb Success! I added “php” to the top of index.php (so it read “<?php” instead of “<?”); and that resulted in the Authorization Code presenting correctly. Really appreciate this resource that you have produced. Agree with @borpin perhaps this could be made accessible for less technical people. I’m not a coder by any stretch of the imagination, and have totally winged this!
Me too! I am going to email NIBE about this. I really don’t understand why they can’t add on a “data storage” element to the NIBE Uplink premium service, if it is indeed server resource they are trying to save.