I’m sorry, but we’ve had good weather here over the last few days, and the heat pump has only run a hot water cycle at night—around 3 AM.
I wasn’t awake then to toggle Debug on “Main” and stop it immediately afterward.
I considered building a flow to trigger this, but I don’t know of a way to toggle Debug on “Main” and generate a diagnostic report automatically.
Here are the timestamps for the hot water cycle that ran overnight:
2026-09-27 02:03:50 status: 15004 Hot water
2026-09-27 03:06:54 status: 15002 Stopping
2026-09-27 03:07:54 status: 15003 Off
Unfortunately, there was no heating cycle during this period.
It seems we are reaching a cross roads here. From what I can tell consumption and allocation works, but we don’t get any production values. In itself that isn’t a big deal, it just means production and COP won’t work. You’ll still get per device allocation in homey energy.
Before assuming your heat pump doesn’t provide production data, I’d like to check whether the gateway is returning current values.
Could you compare these before and after one normal hot-water cycle?
On the heat pump’s own display, look for the heat-meter/produced-energy totals. Photograph the values and labels, if available.
In QModMaster, read these using your existing zero-based setup, function 03, two registers each:
Hot-water production: 44298 → address 4297
Heating production: 44300 → address 4299
Repeat after the cycle finishes, allowing a few minutes for any delayed update. Please send the raw register words and approximate timestamps.
The latest values received by my app were 352.5 kWh for hot water and 26,660.4 kWh for heating.
If the pump’s display increases but Modbus stays unchanged, that points towards the Modbus/gateway path. If neither increases, we’ll know to look at the pump’s heat metering instead.
If you cannot find produced-energy totals on the display, just let me know—no need to change any settings. No new app build or diagnostic report is needed for this comparison.
This is a free translation of the display:
Accumulated energy consumption
Heating 56791.8 kWh
Hot water 3093.4 kWh
Ventilation 2797.8 kWh
Apart from that, there is nothing in the heat pump’s own display or menu system indicating anything about produced energy.
Readings from QModMaster;
Hot-water production: 44298, address 4297, value 3525 0
Heating production: 44300, address 4299, value 4460 4
These values match the “latest values received by the app” that you specified. So, I assume the heat pump handles the generated energy and stores it in the Modbus registers as described above, but doesn’t display these values on its own display.
I’ll get back to you with new readings for 4297 and 4299 once a cycle has finished, so we can see if the figures change.
Here are the timings for the hot water cycle:
2026-09-28 13:23:04 status: 15000 Starting
2026-09-28 13:24:04 status: 15004 Hot water
2026-09-28 15:25:12 status: 15002 Stopping
2026-09-28 15:26:12 status: 15003 Off
No heating cycle occurred during this period.
Readings from QModMaster:
Hot-water production: 44298, address 4297, value 3525 0
Heating production: 44300, address 4299, value 4460 4
This means the figure for hot water hasn’t changed, even though a hot water cycle ran. It would be a shame if it didn’t update…
Could it be that it is aggregated on a daily basis?
I’ll keep taking readings for 4297 and 4299…
Hmm – I’ve just been informed that the F730 lacks a flow meter, meaning it cannot calculate the energy produced. For registers 44298 and 44300 to work, the EMK 300 accessory needs to be installed.
However, there should be a workaround involving a calculation – I am looking into this further…
Thank you for all the work you’ve done on the app!
I’m now looking forward to experimenting with the setups we’ve got working and seeing if I can switch from the cloud-based solution (via MyUpLink) to a purely local one.
I’d also like to make a correction: after speaking with Nibe installers and Nibe customer support, I’ve confirmed that it isn’t possible to install an EMK 300 on an F730. Nor is there any other established solution. In other words—there is simply no way to extract energy production data from an F730. That leaves you with the options of either “building” a custom solution yourself or simply replacing the heat pump. Neither option sounds particularly appealing…
However, it is apparently possible to perform a calculation using other registers and time as a factor. I’ll leave it unsaid how good or effective this solution is, but if you’re interested in implementing one as an experiment - let me know!
Yesterday, the heat pump started running in heating mode—previously, it had only been producing hot water.
I can therefore see the values on the heating side starting to change.
If you’re interested, I’ve been logging a few parameters since October 1st.
Thnx!
Correction: Unfortunately, there was an error with “Experimental: Current power Heating” in the logging, so please disregard its values. It is incorrectly displaying “Experimental: Current power Hot water” instead.
I’m currently migrating my Homey Advanced Flows from the discontinued Nibe S-series app to Nibe Live for my NIBE S735.
There are two functions I’m currently missing in Nibe Live:
1. Night cooling (Nattsvalka) – On/Off
I need an action card to enable and disable Night Cooling from a Homey Flow.
According to the NIBE S-series Modbus register list, Night Cooling is available as: Holding Register 227 – eMbHolding_eU8NightCooling_0
2. Trigger when Heating Offset changes
The old Nibe S-series app has trigger cards that can detect when Heating Offset becomes greater than or less than a specified value. I cannot find equivalent trigger cards in Nibe Live.
For my automation, an even more useful and convenient solution would be a single trigger:
“When Heating Offset changes”
Ideally, the trigger should also provide the new Heating Offset value as a tag.
I don’t actually need to know in the trigger whether the value increased or decreased. I mainly need my Advanced Flow to run whenever the Heating Offset changes; the Flow can then use the current/new value for the following actions.
Would it be possible to add these functions to Nibe Live?
They would allow me to complete my migration from the old Nibe S-series app to Nibe Live.
I can look at these, should be straight forward.
In terms of heating offset, can you confirm which heating offset you refer to? My first thought was the heat curve but that’s never set by the pump itself I believe so not fully understanding the use case there.
@Stefan_Fors After some contemplating I decided to move the whole ventilation cluster to the main device instead. It makes sense since its per definition shared across most other functions (eg heating, cooling primarily). This is now live in test on version 1.4.7.
This may mean your night cooling flow (if you built it) may need redoing.
FWIW I can highly recommend using the homey MCP and let claude/chatgpt do those kinda thing, its almost frictionless.
It’s strange that you couldn’t see the file—you’ve managed to access previous files, after all.
Since the previous file contained an error anyway, I’ll try again with a new one.
Let me know if it doesn’t work—in that case, I’ll have to try something else.
By the way, I’ve noticed that the following parameters haven’t changed at all:
Nibe Hot water Energy delivered (we know the reason for this)
Nibe Heating Energy delivered (we know the reason for this)
Nibe Main Experimental: Idle energy (consistently shows 0.1)