Fixed now
1 Like
Super thanks !
1 Like
Hi Kjetil, The app crashes periodically. But then it starts up again and works for a while, this happens almost every minute.
Sends log.. 85992c03-08fb-4da2-9eba-33c237ac299f
“CPU warning limit reached”
same thing happens on my 2 different heat pumps
thanks for this report and I have a fix for this that I will release later today
1 Like
New version out now
Thanks Kjetil, it seems stable now 
1 Like
Hey, started to use the app 2 days ago, was going to build my own setup instead of using the existing connection to Tibber. The one from Tibber could really do the job since I have floor heating and no radiators. This works so much better at least as it looks for now.
To the question: I installed the AP without using curve to set the temperature. It’s switched inside of the melcloud application now so right now I’m using curve.
Do I need to reconfigure the application to get rid of the old data?
Do I need to do any changes to the actual curve on the heater?
Thanks in advance and for a cool app.
Hi, great app!
I have a geodan and was wondering if it’s possible to fetch and log the flow/return and brine in/out values? Unless I’m missing something that’s already there.
I’ve been using the app for more than two weeks and I like it, especially the subtle changes how it manages the hot water optimization. This brings me to the question of what would be the optimal way to get the system to heat the water tank to +53 every other day in the afternoons?
There isn’t a card for the water tank temperature in the app flows. If I do it through the melcloud does the Optimizer override the target temperature and starts dropping it every hour?
Hi Jari,
Great to hear that you’re noticing the subtle behavior in the hot water optimization — that means the learning model is doing its job.
Regarding forcing the tank to +53°C every other afternoon: that kind of fixed, manual scheduling goes directly against how the learning algorithm is designed to work. The Optimizer continuously adjusts the target temperature based on consumption patterns, weather impact, and efficiency models. Introducing a hard rule like “every other day at 53°C” would interfere with the adaptive logic and reduce overall performance.
For that reason, this type of implementation will not be added to the app.
If you set the temperature manually in MELCloud, the Optimizer will detect the change and gradually steer the system back toward its calculated optimal setpoint. It won’t instantly override it every hour, but it will correct it over time to maintain the learned efficiency balance.
The intended approach is to let the system learn your hot water usage pattern and raise temperatures automatically when needed rather than forcing fixed intervals.
Thanks again for the feedback — it’s highly appreciated.
1 Like
This is not possible
Thank you for the response. Now that you mentioned, I pulled the hot water pattern data and you’re right, it does show the pattern of my usage. I didn’t know that this can be only seen through the widget. Excellent work. A donation coming.
1 Like
Great that it is working as intended
Another question concerning daily produced power meters. Those don’t seem to align with Melcloud values. I created a virtual device that calculates daily produced power, but the values optimizer offers are not realistic. Is there a reason for it and how those values are calculated?
Yes that is a display bug but I have not fixed it as it is only display and do not do any for the optimisation.
I might fix this one day by as all time have been spent on the optimisation I have left this for now.
1 Like
Thank you for the response. Just an observation about those values; to get the calculated produced daily energy value from Melcloud, I needed to calculate those through Total produced energy values. Even in the original Mecloud app the daily values are bizzare and insight values those values produced do not align with reality.
