It appears Output Power = 0kW because there was a DeltaT of 0 Which doesn't appear correct because it was 4C according to the data.
Like you say, i presume this is a timing/capture thing, in particular with the Home Assistant firmware which has different refresh rates for different parameters giving higher resolution when viewed there.
Just a note on the Thermo. Diff setting - it only applies in Auto Adapt. It appears you are in Compensation and therefore overshoot is only +1.0 This is the classic Flow Temp overshooting Flow Setpoint issue
The Ecodan was initially set to a +5/-5 tolerance, which is it's default option. I've subsequently adjusted this to +3/-7, but it still works around a 10°C tolerance around the flow temperature currently.
I wonder, @sheriff-fatman, if Mitsi have chosen to use a shared parameter between defrost cycle and freeze protection. If that were the case, we’d see a software-induced correlation rather than a physics correlation, but a correlation nonetheless.
“Curiouser and curiouser”, said Alice…
Frost Protect/Freeze Stat is an operation mode, where Defrost is a multi-stage status flag (however i only see two used).
In the firmware i inject defrosts to the Operation Mode status for easier viewing and understanding of users.
@robs Just to quickly fill in some of the gaps in the response, now that I have more time to post properly (I think the car moved about 10 metres in 30 minutes while sending the one last night, so I wasn't typing whilst moving but I didn't have the normal time to compose a post, and I didn't want to leave it unresponded overnight, given the time taken on your reply).
Just on this, as I'd spotted similar things with the output previously, there's an instant COP calculation of 3.63 in the same snapshot, which doesn't match the input and output figures, so I think there's probably an issue with how the output data is displaying from time to time. @f1p might be able to shed more light on this, as he makes and sells the dongle device, and liaises with the MelPump team, whom I believe are a separate entity. The dongle, as far as I recall, polls every 10 seconds so the 5 minute snapshots are summarising this data in some way, but this one is an example of where the output looks odd. The fact that the COP figure is non-zero suggests to me there's undisplayed data, and I assume its the output data where this manifests, based on the fact that it looks to be the obvious 'wrong' number.
No worries and hope you don't have to sit in traffic too often!
Is it possible to get Home Assistant to record data points more often than 5 mins? Every 1 minute would be good. Also, are some of the values averaged over the time period and others the current value at the time the data points were captured? That might explain some of the odd combinations of values.
From your earlier post, Phil has described the Thermo Diff setting and the 1C overshoot in another post. A conservatory would account for needing a 10kW heat pump but do you always heat the conservatory when you heat the rest of the house?
Just to clarify my point from yesterday evening's post, it's not the cycling itself that I'm querying, as I understand the general concept of what is going on and, like you, I have questions about how effectively the Ecodan is able to modulate down.
The databook says that your 10kW Ecodan can only modulate down to 3.5-4.0kW in mild temperatures (7-15C), but then it has the same compressor as the 12kW. For comparison the new 8.5kW can modulate down to 2.5-3.5 and the new 5/6/8kW Ecodans down to 1.8-2.0kW.
At slightly higher temperatures, as we experienced yesterday, it switches to idle for a period of time as part of the cycling process, which in turn increases the overall COP relative to it's output. I'm not sure if all heat pumps are designed to do the same thing, but in general terms cycling whilst constantly running is only something that seems to occur within a range of outside temperatures of 4-7°C.Below 4°C, it runs generally in equilibrium. Above 7°C it includes idle periods within the cycling loop, as it's doing currently, as shown below, and the idle periods are adding about 0.1 to the daily COP as per the summary stats, as there is still a diminishing delta T during these idle periods providing some heat output into the mix. Most of the data snapshots taken in your reply are at OAT of 9°C, and one of them looks to have picked up an idling period within this, so it's outside of the area where the freeze stat issue is occurring.
Heat pump cycling isn't sinusoidal, the ons and offs don't follow as a set period - the frequency of both is variable. One thing I have noticed with our Ecodan is that if the flow temperature gets too high and it cycles off then it is quick to restart but if the wireless remote stops the heat pump (e.g. because of solar gain) then the heat pump is slow to restart (the internal temperature needs to drop before the heat pump restarts). This difference could be the cause of your different types of cycling.
Your water flow rate doesn't seem very stable in the EmonCMS image above, Ecodans usually use constant flow rate pumps and so their flow rates don't vary much (see the example of our system below). Do you have TRVs or UFH thermostats opening and closing bits of the system?
If that's how the system will operate on weather compensation in warmer periods, then I can live with that, as it's going to be doing the same overall thing as the Havenwise control methodogy of having idle periods between 'blasts' of heat and the WC blasts based on flow temperature should overall be gentler and more consistent than those that were being driven by the internal room stats within Havenwise control. It seems a sensible way for the heat pump to run if it's unable to modulate down appropriately.
The bit that doesn't make logical sense to me, and which still remains unclear, is why there's a distinct pattern of behaviour within the small range of 4-7°C where the cycling activity is erratic at a specific temperature of 5°C, relative to the less frequent cycling around it, and why this behaviour improved via a change in the freeze stat protection settings.
In mild weather heat pumps need to cycle if they can't modulate down low enough, how the cycling is controlled is key to efficiency though.
Maybe a specific temperature at which the interaction of WC curve temp, heat pump flow temp overshooting and load/emitter output causes the most flow temperature overshoot cycling? But it could be a bug in Mitsubishi's software, with more mild temperatures forecast would you be willing to switch freeze stat off and see what happens in the 4-7C temperature range?
Is it possible to get Home Assistant to record data points more often than 5 mins? Every 1 minute would be good. Also, are some of the values averaged over the time period and others the current value at the time the data points were captured? That might explain some of the odd combinations of values.
In the Home Assistant firmware the data points are between 2s and 25s depending how important the values are, e.g. compressor frequency, flow, return temps are the most frequently refreshed
