Reversed WAR temperatures about nodered_heishamon_control HOT 13 CLOSED

Hi root2k,

what version of flow are you using. 21.00 stable? or a beta version.

from nodered_heishamon_control.

I have copied the content of the flows.json (flow date 2 months ago). I guess thats the stable version 21.00?
My Heisha heat mode is compensation curve and the outdoor temperature offset ist at 13 degrees.

What should I have to change, so that is working as it should?

from nodered_heishamon_control.

There is a newer version. try from this page.
it has a lot lot lot of fixes.
among one, the WAR issue you mention.

https://github.com/edterbak/NodeRed_Heishamon_control/tree/main-22-beta_2

from nodered_heishamon_control.

I have tried it, in this version the WP_MQTT flow is missing, but isn't really nessesary because it was just an overview of the topics, right?

In this version the WAR temperatures are displayed correct.
But the other thing I have recognized is, that there is no possibility to change the outlet setpoint.
On home screen there is just the actual outlet setpoint written but no possibility to adjust this like in the DHW part with arrows for up and down?

But it is still the same, I can't activate the nodered WAR as long as the pana is in compensation curve mode.
Need to be set to direct mode otherwise the nodered WAR function will be diasbled after 3 sec.

When will be this flow a stable version?

from nodered_heishamon_control.

The WP_MQTT flow is removed by Edterbak and was not nessesary, correct.

In compensation mode you can only shift the target setpoint right?
The Function RTC can shift depending on your custom levels and depending on the room setpoint.
If al function are disabeld (RTC, WAR) and you are in direct mode the Default water temp. will be used.

Would you like a manual shift control, or do I understand your question wrong?

from nodered_heishamon_control.

I explain it with more details ...
I didn't set my pana into direct mode on the remote controller before using this nodered flow.
That's why I'm thinking it isn't working well so far.
I thought that is not nessesary anymore, because edterbak has written in the changelog.
So this might be the issue why the WAR switch turns off 3 sec. after activating.

To the outlet setpoint correction, yes a manual correction would be nice (picture red marked). Like the DHW setpoint (picture marked green).

And the last thing is, I don't know if this is a bug or just the result why the WAR function isn't activated, I don't see any calculated temperature ...

from nodered_heishamon_control.

Hi root2k,

What you ask for is contradictory to my feeling. And if I actually am understanding correctly, impossible.

If you have your heatpump setup to use the compensation curve (this is indeed now possible), then:
1 - you cannot talk about a setPOINT. a setpoint is one defined point, not dependant on anything else.
2 - the panasonic compensation curve is determining the water setpoint depending on the temperature outside (the curve).
3 - the water temperature (heat) is controlled by the panasonic. 100%.* It is out of Node Red's hands.
4 - because of point 1+3, it is of no use to offer a button to increase/decrease a target temperature.
5 - the Panasonic is only using the panasonic outside temperature sensor. Only the sensor directly connected how pana expects it. So no homebrew sensor through Node Red.

*3 - only exception is the RTC function as Maarten mentions. It can shift the entire curve (in the panasonic) by -5/+5 degrees depending on the room temperature.

When using compensation curve, is of no use to activate the WAR function inside node red. It simply will not do anything. That is why I force it off after checking the heating mode.

The last point you made, yes, that might be a bug :) thanks for letting know. I will have a look at this later.

I hope I understand you correct, and what I write is a good answer to your question.

regards,

from nodered_heishamon_control.

Hi edterbak,

thanks for your response.
I may think we are not talking about the same thing in some points.
What I mean with the correction of the setpoint is the same thing you can do at the remote conrol of the panasonic.
There you can change the setpoint from -5 to +5.
That is, at the moment, an important tool for me because I'm struggeling since 3 years with a problem after dhw of the panasonic.
Let me explain, the compresor falls back to 0 hz after heating up the water tank. What I know is that it's sometimes a pana control problem. To wake up the pana for heating I'm doing a setpoint correction up to +3 on the remote control or the cloud modul, manually. That works for me and the pana is starting heating again. But If I use this flow, I can't do this any more.
Therefore I have to create a flow or something that the pana is doing this on her own, but don't know if this works together with your flow?

And to your last point activating the WAR mode is not nessesary, nice to know.
So that's normal behavior when using the WAR function, that nodered switches the WAR button auotmatically off, do I understand right?

Big thanks to your effort.

regards.

from nodered_heishamon_control.

root2k,

Ah, I understand now.
(Technically we call changing the setpoint you mean: 'shifting' the compensation curve up or down. But thats besides the point.)

I got thrown off a bit when the story went from a problem to problem solved (in newer version) whereafter it slided to new feature request. That last part was unclear.

Could you please make an issue with a new feature request for this?
To be clear. You write about two feature requests.
1 - the option to use the setpoint arrows on the dashboard to shift when in compensation curve mode.
2 - the function to automatically shift +3 for 30 seconds, after DHW cycle finished.

item 1 is a good one. Logical and easy to make I would say.

There might already be a request for item 2, but for item 1 I know there is none. Crazy when I think about it...

Many thanks. :)

from nodered_heishamon_control.

Design wise, I am thinking of the following solution with the motivation below. Kindly your thoughts.

The CURRENT dashboard is build up like this:
1 - You insert the target water temperature. If no other function below is active to override/correct (2 - 5) then that would endup below as final water setpoint at 6.
After it is sent to the heatpump and confirmed, it shows in the dashboard on the left section at 7.

Proposal for the new situation adapting for SHIFT:
1 - Depending on the Operating Mode (Direct or Compensation Curve) change the text of 1
Use the same up/down toggles in the same location for shifting the curve
2 - automatically disabled.
3-5 can still be used together with shifting
6 the final corrected shift will be shown here.

After it has been sent and confirmed the shift will be shown at 7

The labels on item 1, 6 and 7 should be made dynamic based on Direct/Compensation curve.

from nodered_heishamon_control.

Hi edterbak,

thank you for your reply.
Yeah I don't even know the right technically word, thanks for telling me. But it's excactly what I mean, shifting up and down of the compensation curve by using the setpoint correction.

I will make two feature requests when I'm done writing this message.

To your thoughts of the implementation of the shifting part: I think that would be nice if it works like you have written above.
But I thought, as you have written before, the disabling of the WAR function is automatically done right now when the user don't set the heatpump into direct mode?

So the WAR function will be disabled after shifting up or down of the compensation curve. But in case of the shifting correction, it would be cool to automatically set it back to 0 when the user enables the WAR function again. Do you have the same thoughts about this?

from nodered_heishamon_control.

:) Hi again.

Thanks for the requests!
I will respond in the respective issues. Thanks again.

Your suggestion about the WAR function is taken onboard as well.
I am thinking of graying out the text of the WAR (temp) ..... 0 as a whole too when in compensation curve.
Your right about the WAR function needing to show 0, or nothing maybe even.

from nodered_heishamon_control.

Fixed in 22.00

from nodered_heishamon_control.