Comments (26)
I think it is a bug.
It might be fixed in current version (JUST pushed out) beta v22.27
https://github.com/edterbak/NodeRed_Heishamon_control/tree/beta-1
If you can check this version and pay special attention to this, that would be awesome :)
THanks for the reporting !!
from nodered_heishamon_control.
I think it is a bug. It might be fixed in current version (JUST pushed out) beta v22.27
https://github.com/edterbak/NodeRed_Heishamon_control/tree/beta-1
If you can check this version and pay special attention to this, that would be awesome :)
THanks for the reporting !!
I did the flows update as described in the instructions and set test sterilization on the pump. However, after sterilization, the pump still switched to heating mode.
Is it possible that I have incorrectly added the room temperature sensor and it is affecting the incorrect operation of the pump after sterilization?
I didn't make any more changes.
from nodered_heishamon_control.
Ah, Im looking now at the code.
it is not a bug.
It is just not programmed as you and I thought it was.
I will have a look if it is doable to change. (it is complex in interaction with other functions... need to see...)
from nodered_heishamon_control.
I think I fixed it on my end. Did a testrun, and it worked. ofcourse the proof is in the pudding, so after upload/release the bughunting can start.
from nodered_heishamon_control.
Can I try it or do I have to wait for a new release?
from nodered_heishamon_control.
It is in current upload, v22.28
https://github.com/edterbak/NodeRed_Heishamon_control/tree/beta-1
from nodered_heishamon_control.
I tried force sterilization. The problem remained the same - after sterilization, the pump switched to heating mode.
Before sterilization, "only DHW" mode was activated.
from nodered_heishamon_control.
Maybe we are talking about two different things.
How do you enabling the sterilisation ?
Through the scheduler or home dashboard?
from nodered_heishamon_control.
Sterilisation is normally set on the heat pump's dashboard. This time I enabled the "force sterilisation" function in the app for testing.
from nodered_heishamon_control.
Ghehehe... Yes.
In node red dashboard, you also have a scheduler. In here, you can set a time and an action.
I have been fixing this. Hahaha... Miscommunication.
I will look at that toggle on the home screen.
You could try the NR scheduler as a replacement for the wallmounted unit scheduler. It is bigger and more flexible
from nodered_heishamon_control.
Yesterday I set up the "scheduler" function in the app:
This is what I found this morning:
from nodered_heishamon_control.
Are there schedules in the controler still active with heat only?
Can you post a screenshot of the RTC page?
Are you sure the operating mode was different befor the schedule?
from nodered_heishamon_control.
Did i correctly see you use not direct mode but compensation curve? (Should not be a problem, but nice to see) i have not used that myself. Only quick testing. On the Dutch forum nobody uses it too. I have had very little feedback on this part. Good to see it being used
from nodered_heishamon_control.
It's been a few weeks since I've had the heating off and only the water heating on. That's why I raised this issue only now. In winter, when both heating and water preparation were turned on, switching to "only heating" after sterilisation did not cause any problems, but now the situation is not very good.
Yes, the pump is set to work according to the compensation curve.
I don't put any shedule settings in the pump or the app. Yesterday, just for testing, I set the sterilisation schedule in the app.
from nodered_heishamon_control.
Could you check if you have a value here:
and a little further down you could see "F_stored_next_operating_mode"
Normally, this variable should not be found.
Only during sterilization run, I expect this variable to contain the operating mode that was active befor the sterilization.
So if you cnt find it, it is good. (when not in a sterilization run)
from nodered_heishamon_control.
Found it.
The root cause is that variable "TOP4_Operating_Mode_State" is empty when the sterilization run is started.
The current value of TOP4_Operating_Mode_State should then be stored in "F_stored_next_operating_mode".
Now, F_stored_next_operating_mode is empty.
When the sterelization run ends, I send out the task to the broker to change the operating mode to the value of F_stored_next_operating_mode. But because this is empty, it sends out the value 0 (zero) which is Heat Only.
To solve this.
Can you post a screenshot of these stored variables.
It could be the variables are actually empty.
It could be the variables are not empty, but not stored correctly under the "file" local storage.
Have you arranged the persistent data folder and settings.js correctly?
See the text on github under installation:
A - Persistent data folder.
B - Adjust settings.js.
from nodered_heishamon_control.
As you mention F_stored_next_operating_mode is empty, now i remember two weeks ago scheduled Force DHW
in nodered dashboard, DHW was done but when it finished it active heat mode. Suspect the same behavior "it sends out the value 0 (zero) which is Heat Only".
The first blue area is when DHW force scheduled cycle, the second purple area is compressor runnig in Heat mode, when DHW force finished and previous state (DHW_only) was not restore. Compressor running is drawed in purple. I noticed why is on heating mode where it was at DHW_only mode.
from nodered_heishamon_control.
I have HA Node-Red Addon installation.
I checked the A and B settings and everything is as described here:
https://github.com/edterbak/NodeRed_Heishamon_control/tree/main/HomeAssistant
When sterilization is not enabled, I did not find the parameter F_stored_next_operating_mode.
Meanwhile, the parameter:
When I turn on manually from app force sterilization:
"F_stored_next_operating_mode" doesn't exist anyway.
I also noticed another nuance - when I manually turned on Force sterilization in the app, I can't turn it off later in the app.
I only turned off sterilization on the pump dashboard.
from nodered_heishamon_control.
Ok. Let me digest this ..
The toggle on home screen is different than the schedular function. The toggle does not set F_stored_next_operating_mode.
Ill make it similar soon.
from nodered_heishamon_control.
I have rewritten the Sterilization code part now.
The toggle on the dashboard is the same as doing a scheduled sterilization.
I have tested it 3x now.
Toggle on: Heat only >> HEAT+DHW, + Sterelization = 1
Toggle on: HEAT+DHW >> Heat only, + Sterelization = 0
Toggle on: Auto(2) >> Auto+DHW(6), + Sterelization = 1
Toggle on: Auto+DHW(6) >> Auto(2), + Sterelization = 0
It should be ok now.
I will upload a version, version 22.29, in a minute
@albertoanta
The Force DHW option is a different topic.
BTW, the toggle does not mean. force a dhw run.
The toggle means, throw away efficiency during a dhw run. I want hot water fast.
Forceful is the better choice of name I would say.
At least, this is what I understood from it.
from nodered_heishamon_control.
Good news!! After installing version 22.29, the pump returned to DHW mode after force sterilization.
Now I will wait until Monday, when the regular sterilization will be done.
Weekly sterilization is set on the pump dashboard. Should it work with this setting or do I need to set the scheduler in the app?
from nodered_heishamon_control.
Good news indeed. Thanks.
If you only use the nr schedular, that is sufficient. You do not need the schedules steril task on the wall controller
from nodered_heishamon_control.
Problem solved
from nodered_heishamon_control.
supurb. thanks for confirming !! :D
from nodered_heishamon_control.
supurb. thanks for confirming !! :D
Hello again,
Could you please help in one more place?
I wanted to make an automation in node-red so that towards the evening, while the sun is still shining and the solar power plant is still producing electricity, the heat pump will heat the water.
The script activates "Force DHW" in the heat pump, but returns to "Heating only" when finished.
The solar power plant works independently, it is not connected to the heat pump and only the script controls the pump according to the sensor of the solar power plant.
Maybe this place can be fixed to return to the previous mode after Force DHW?
from nodered_heishamon_control.
Hi,
Could you close this issue and make a new one?
the issue is solved here. It was about sterilization mode, and not force dhw.
In the new thread/issue, I do like to have more info on your scenario.
How are you triggering exactly the force dhw. in detail.
What script, what does it do.
What is the state befor the script fires.
etc..
You can share the node (select + export) or use screenshots as well to make it clear what you are doing.
Regards.
from nodered_heishamon_control.
Related Issues (20)
- [BUG]: Scheduler conditions not shown after reboot HOT 2
- [BUG]: [error] [function:COOL function] ReferenceError: msg3 is not defined HOT 1
- [BUG]: Scheduler not functioning with 23.06. HOT 1
- DegreeDays - question HOT 2
- [ENHANCEMENT]: Anti-Theft request HOT 6
- [ENHANCEMENT]: various ideas HOT 2
- [ENHANCEMENT]: Support for Zone2 and Buffer tank HOT 8
- Settings memory HOT 2
- dashboard and pump work according to custom room temperature sensor HOT 31
- [BUG]: Softstart jumps between 2 temperatures HOT 3
- RTC power trigger dT question HOT 3
- [ENHANCEMENT]: table with supported Heishamon versions on Github. HOT 17
- [ENHANCEMENT]: Delay for outside Temp-Sensor HOT 4
- [ENHANCEMENT]: Panel integrated temp sensor as trigger HOT 4
- [BUG]: Tsp sometimes jumps to "set water temperature" and not applying "custom functions" HOT 3
- [ENHANCEMENT]: after auto DHW heat, pump is on for heating HOT 4
- [BUG]:V23.09: text heat,dhw,cool status missing HOT 2
- [ENHANCEMENT]: Softstart and Night reduction HOT 6
- [BUG]:Delay-Node missing? HOT 4
- [ENHANCEMENT]: Using S0 of Heishamon for calculating efficiency HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nodered_heishamon_control.