-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENHANCEMENT]:DHW-Temperatur adjustable with Scheduler #120
Comments
thats a good idea. thanks !!! |
Done in v23.05 |
Hi Rüdiger, :) |
Thanks for your ultra-fast response and reaction!! I will try within the next days an will report- not so fast as you...;-) |
V23.05 imported and deployed: will see if setting of DHW will work tonight. One feedback already: if you try to change the temperature of dhw SP in scheduler again, the window for adjusting don't open again: you have to choose any other action again first and than choose again dhw setpoint to get to the window to adjust the temperature... |
In system log set setpoint DHW is visible- but no reaction of heatpump or in heishamon ( TOP 9: Target Temp DHW) - will have a look within next days and report here.. |
For changing the temperature in function block "pupup" in flow "WP_Scheduler" I had to add some parseInt -e.g.: |
Is your feature request related to a problem or use case? Please describe.
I use your Nodered Flow V23.0 since 4 weeks- first off all: thank you very much for your work!!!
I would like to reduce setpoint for DHW to shift operation time from night to day- because of higher outside temperatures and therefor better cop. I didn’t find a solution with the scheduler…?
Another question concerning the code: there are nodes (complete!) which are not looking at the end of any other node- in my imported flow: is that ok?
Describe the solution you'd like
A clear and concise description of what you want to happen.
Setpoint DHW in scheduler…
Thanks and have a nice holiday!
Greetings
Rüdiger- lower Saxony, Germany
The text was updated successfully, but these errors were encountered: