[BUG]: Tsp sometimes jumps to "set water temperature" and not applying "custom functions"

dennisbakhuis commented 7 months ago

Describe the bug While most of the time the system works nicely, occasionally (few times a day), the Tsp jumps from its corrected value with WAR and RTC to the value without "custom functions", which is of course much higher. This is only for a short while (few minutes) until it jumps back to the expected Tsp with all "custom functions" applied.

To Reproduce Pump: WH-MXC12J9E8 Heishamon: 3.1 NR-flows: 23.09 Mode: only heat Functions: WAR, RTC, Softstart

Expected behavior These jumps are not normal and make the pump start for short while. This is of course not what we want.

Screenshots I noticed it first in my hass dashboard to glance if all is ok (Here also Softstart is applied which adds the addtional wiggle):

This is also clearly seen in the NRui dashboard:

I do not see anything weird in the WAR temperatures in NRui:

Also nothing weird in the Thermostat temperatures:

Additional context

As the Softstart jumps in nicely, I got a hunch it is probably not that function.
What happens if one of the functions somehow fails and returns null? Does it then jump back to the "basic setpoint"?
I have problems with Heishamon and got a high MQTT reconnect rate (still need to put a ticket on that repo. While it is problematic, I do not think this problem is caused by this as the pump is set to this Tsp by mqtt (and turns on).

If it helps, here are my pump details: heatpump_data.txt

I would love to check/look for problems myself but not sure where to start. Also I am a bit reluctant to update the NRF to the beta one as @edterbak mentioned they are not so stable yet. Same with Heishamon (HM), as I am not sure if NRF 23.09 is fully compatible with HM 3.2.3

edterbak commented 7 months ago

This is a weird one. Never have I ever seen this behaviour. I will think about this more. Also seeing the calculated WAR SP is not changing in the graph, suggests it is not the WAR function.

Can you collect the RTC corrections ? Import this link-out node, and you can export the correction value to where you want it for that. Connect with a link-in node to [RTC Correction]

[
    {
        "id": "3f6602042d2dc015",
        "type": "link out",
        "z": "8c9d42231fd19d3c",
        "g": "a8ac5b148d851a6b",
        "name": "RTC Correction",
        "mode": "link",
        "links": [],
        "x": 3945,
        "y": 1460,
        "wires": []
    }
]

PS You are right. v23.09 is indeed not compatible with HM 3.2.3. Starting from beta v23.10 beta14 it is compatible.

edterbak commented 7 months ago

Is there any update on this issue? Is it still happening?

If not, please close the issue. Otherwise we should continue diggin in :)

dennisbakhuis commented 6 months ago

I am still investigating but December is not my best month in terms of spare time (-:

I have turned off the soft start function and have not seen any spikes. However, I also changed the whole network as I have many problems with Heishamon and MQTT disconnects. I have as hunch that this might be partly connected.

I first want to solve that the MQTT reconnects before I move on. I will also upgrade to 24.01 + heishamon 3.2.3 this weekend and see how that goes.

For now, lets close the ticket. I will open a new one if I have more information to offer.

edterbak / NodeRed_Heishamon_control

[BUG]: Tsp sometimes jumps to "set water temperature" and not applying "custom functions" #142