Hi all,
this is Jan Rosenow and I’m a heat pump policy expert. I would like to contribute to openenergymonitor and share my heat pump data. But I have zero experience with any of the programming languages and need help. Can someone explain how I go about sharing my data for a NIBE F2040 heat pump?
Thanks!
Hello Jan, good to hear from you on here! What monitoring do you have on the NIBE at the moment? I know there’s the Nibe Uplink and I can help you record the data from that, but it’s usually quite limited and not enough to create a full heatpumpmonitor.org dashboard.
Do you have a heat meter? The NIBE heat pumps I’ve helped monitor dont seem to have integrated heat metering? as far as I have been able to tell… I only have limited experience with NIBE so there may be configurations Im unaware of.
@Zapaman and @dMb have probably got the most experience of Nibe here and may be able to help guide us in the right direction.
A lot of the systems on heatpumpmonitor.org have our 3rd party modbus electricity monitoring and mbus heat metering monitoring package Level 3 Heat Pump Monitoring Bundle (emonHP) - Shop | OpenEnergyMonitor this gives the most detail and best accuracy but does of course come at an expense and requires an electrician, plumber/installer to fit. You may well have components of this already in place e.g a heat meter that could be used as part of this?
Welcome Jan,
As Trystan says, it’s great to see you joining this community and we’re happy to help you share your data.
The NIBE systems monitor quite a lot of operational parameters and (assuming they’re given an Internet connection) they send those to the NIBE Uplink servers, primarily to drive their smartphone App. A good approach for reporting those parameters is to interrogate the NIBE Uplink API every couple of minutes and pull back a selection of readings to supply to the MyHeatpump app that underpins the HeatpumpMonitor site. That ‘interrogate the NIBE Uplink API’ step needs a script of some sort; I have some examples written in the Python scripting language.
However, that’s not the full story because the NIBE systems do not have built-in Electricity Consumption (input) or Heat Generation (output) meters - so those need to be installed separately. If you already have those that’s great but if not the first step will be to investigate options for retro-fitting suitable metering - using something like the Heat Pump Monitoring Bundle Trystan mentioned.
Your F2040 is the outdoor unit, right? You presumably also have an indoor controller, something like an SMO 20, where you configure the settings? That’s the combination @prwv has on his installation.
(I have an F1145 GSHP where the controller is integrated into the compressor enclosure, all indoors.)
David
Hi Jan great to see you on here.
Yes NIBEuplink is a great starting point. Also Yes I have a very similar set up F2040-6 with SMO20.
You would probably need to set up a Raspberry Pi to capture the Uplink data and push that yo EmonCMS. The flow / return temperature data should be available. Also Compressor Frequency and Circulation Pump % parameters can be useful. FInally if the outside temperature should be available and the room sensor data if you have that sensor.
This data forms a really useful starting point.
I know it’s a few months since the last post but I too am an SMO 20 / F2040-12 user. I installed mine 9½ years ago, and back then open energy monitor was a lot newer and I think there weren’t any Nibe users to hack scripts with.
Anyway, long story short - had my first real interruption of heating (2 weeks over Christmas !) repaired without root cause identified by replacing most of the electronics in the F2040. This has renewed my interest in logging data in a way I can remotely access, and also my PV setup as might add a 2nd array when I do the loft.
I’ve also got a no longer offered Nibe solar thermal setup that I wondered if I could log, as I’m considering switching it from East to West facing.
Hi there
Since the start of the thread I’ve joined the community with my Nibe f2040-16 and SMO40. I don’t yet have a heat meter installed but log all possible parameters from Nibe uplink. I use the excellent python scripts from @dMb but have modified them a little to add some derived data (eg delta T) and also read in some Independent temperature sensors which I’ve attached to various bits of pipe work to help diagnose some ongoing issues. The script then publishes this data to emoncms for analysis.
The data has proved really useful to fix a lot of my problems and performance issues, there is a whole thread on that which has been dormant for a month but I’ll update in due course. Using this data to see how my 2040 performs in this cold spell is insightful too.
I’m happy to share my scripts but I’m not as organised as @dMb so don’t have a GitHub and blog post to cover what I have done.
Sorry to hear you had to have some repairs, mine is now 4 years in and I’m looking at having some sensors changed due to major defrost problems and high temperature alarms. This has all come from data insights!
I am running an S1156, also curious about what I can and can not do. System seems to have power read out for the compressor but no heat/output parameter. Also looks like nibe /uplink have split their subscription between real time remote setting, and historically data.
Hi - I have a NIBE F2040 12kw and SMO20 and have been having short cycling, high temp alarms and defrosting issues from installation back in 2022. I’d be interested to hear from other NIBE users on their experiences over the past few weeks of cold & damp weather too.