@sheriff-fatman 

has a meltdown when it has to adjust slightly at 5°C and starts cycling

I have a similar sort of issue, although at a slightly higher OAT
I decided to try a the following approach, where actually i'm going to push a slightly higher flow temperature after that problematic OAT - which will help heat dissipation through my rads and match my units minimum power output at that higher OAT to reduce cycling

Unlike the stock MELPump Firmware, for Home Assistant Firmware users there is no automatic update feature on the adapter currently due to some technical challenges with the hardware variations - you will need to keep an eye on the releases from time to time.
The reason i mention it is that in v6.5.5 the +/- Offset options became a retained parameter, in the unlikely event that your adapter does restart or have a power outage.

from the weather curve setting of 35°C to one of 47.25°C

This could be part of the Auto Adapt "learning", which some form takes place every time you swap from one operation type and back to AA 
There is adjustment of compressor frequency as the Flow Temperature and Setpoint converge to try and tune the overshoot i have observed from the data:

One immediate issue I'm having is that the curve is resetting itself whenever the screen is closed, even after the settings have been saved.  I woke up to see it had defaulted back to the pre-set curve, and have just re-created my version, only for it to be reset again when I left the configuration screen.

Presumably a bug of some kind.

Posted by: @sheriff-fatman

↑

One immediate issue I'm having is that the curve is resetting itself whenever the screen is closed, even after the settings have been saved.  I woke up to see it had defaulted back to the pre-set curve, and have just re-created my version, only for it to be reset again when I left the configuration screen.

Presumably a bug of some kind.

I reviewed some device logs and there is a mistake in the JSON schema being sent by MELPump so the adapter is not taking any action on it.

Posted by: @f1p

↑

I reviewed some device logs and there is a mistake in the JSON schema being sent by MELPump so the adapter is not taking any action on it.

I'd switched to Auto-Adaption mode pending a fix, which has been eye-opening (perhaps a post to come on that later) but I've just had to switch MelPump control off for now as the two modes seem to be fighting each other at the moment, as per screenshot below.

Posting here for info @f1p as part of general bug-reporting during beta testing.

@sheriff-fatman Yes, that's a good point - this conversation is related only to the Beta feature of the onboard compensation curve

Further to that, I think this mode switch/fight is potentially a graphical representation in the App only which may not actually occur on the pump (cross check in Home Assistant or on the Main Controller)

Posted by: @sheriff-fatman

↑

One immediate issue I'm having is that the curve is resetting itself whenever the screen is closed, even after the settings have been saved.  I woke up to see it had defaulted back to the pre-set curve, and have just re-created my version, only for it to be reset again when I left the configuration screen.

Presumably a bug of some kind.

I think this was resolved last night, it was for me anyway

@majordennisbloodnok Hi, great write up. I am a subscriber of Melpump. last Oct i let Havenwise control my heat pump, but im coming off that now, My question is, does anyone know do i do anything in Melcloud so that it sits there whilst i use Melpump to control my heating and heat water please? ie so the HOP takes instructions from Melpump and not the Melcloud app please

@boycey Hi. Im not a Melcloud user so I might be missing something, but why would you want to keep Melcloud when you have Melpump? The dongle attached to the board for Melpump allows the Melcloud adapter to be plugged in too.

@boycey 

Are you using the MELCloud Adapter with MELPump or have you put in the dedicated MELPump Adapter?

Posted by: @boycey

↑

@majordennisbloodnok Hi, great write up. I am a subscriber of Melpump. last Oct i let Havenwise control my heat pump, but im coming off that now, My question is, does anyone know do i do anything in Melcloud so that it sits there whilst i use Melpump to control my heating and heat water please? ie so the HOP takes instructions from Melpump and not the Melcloud app please

Posted by: @bontwoody

↑

@boycey Hi. Im not a Melcloud user so I might be missing something, but why would you want to keep Melcloud when you have Melpump? The dongle attached to the board for Melpump allows the Melcloud adapter to be plugged in too.

@bontwoody's right, @boycey, with a couple of provisos.

As you know, you have two choices for how Melpump gets its data - either from the Melcloud API or via a little adapter gizmo.

• If you want Melpump to get data via the Melcloud API, you absolutely have to continue using the Mitsi wifi adapter to talk to Mitsi's cloud systems. Moreover, in that scenario, both Melpump and the Melcloud app will be changing data in Mitsi's cloud and so the heat pump will see any changes as coming from Melcloud anyway.
• If you want Melpump to get data directly from the heat pump, you'll need that little adapter gizmo. As @bontwoody mentioned, and as I expect you're already aware, that gizmo has two sockets on it so that you can daisy-chain both it and the Mitsi wifi adapter and have both adapters sharing their data with their respective destinations. Moreover, the gizmo is designed to share the data with up to two separate destinations so that you can get it to interact with Melpump as well as, for instance, Home Assistant. In this case, Melpump, Home Assistant and Melcloud are all independently capable of receiving information from and sending commands to your heat pump.

The important thing to remember is that Melcloud is designed right from the start to be sharing control since it also expects you can make config changes via the little wallbox display unit supplied with the FTC. As a result, Melcloud doesn't care if the heat pump is receiving instructions from elsewhere; all it cares about is that when those instructions are carried out the new state of affairs is reported back to Melcloud by the Mitsi wifi adapter. The same logic applies for the little adapter gizmo used by Melpump and, indeed, Melpump itself; it recognises instructions could come from somewhere else and it's fine with that as long as any settings changes are reported to it.

All this is a long winded way of saying you don't need to do anything in Melcloud if you're using Melpump. I don't use Melpump but I do use the little dongle thingy along with Home Assistant, and both Melcloud and Home Assistant are rubbing along perfectly well with each other.

The area I happen to disagree with @bontwoody about is the idea of not keeping Melcloud. That's purely because I hate the idea of locking myself into anything, hence why I continue to maintain the Melcloud connection even though I'm not using it for control any more. However, mine is not the only opinion with merit and so if you do choose to stop using Melcloud altogether then all you need to do is unplug the Mitsi wifi adapter from the pass-through socket of the Melpump adapter gizmo thingy. @f1p, we really need to come up with a snappier name for your creation.

Does that help?

@majordennisbloodnok has a clear explanation above,

What I was referring to—and the reason I asked about the adapter—is that situations can occur where multiple sources have the potential to perform write operations to the FTC. I fully understand that this can be difficult to diagnose when you have MELCloud native schedules, MELPump Automation, and Havenwise all potentially modifying and adjusting parameters even simultaneously.

This may be irrelevant to your situation, however for users of the adapter may be interested to know of this lesser-well known feature.

There are some special service codes i added, primarily for troubleshooting. Since my adapter works as an active broker, it is possible to enable a feature where any write requests originating from the MELCloud adapter are not passed on to the FTC. This effectively makes MELCloud "Read-Only."

There are various scenarios where this feature is useful: it can help isolate which third-party application a change is originating from, and for the cyber-security conscious, it provides the peace of mind of knowing that only they can write to their unit.

@f1p Hi, I have the mistsu wifi adapter for melcloud and the app, and then melpump working via the melcloud account, i think that's how it works, so if i set my schedules etc up in melpump, what do i need to have the melcloud app set to so it doesn't confuse melpump?