Yes you can, just dont hammer (ie short polling interval) from both ends.
Thanks, leave the polling interval at the default setting, so I’ll go ahead and add them to Home Assistant as well.
Sorry to hear, drop me a diagnostic report.
Try (if possible) to sent it before you think it will crash.
Got a large refractor here in alpha locally that changes the battery policy behavior so need to check it is related or maybe solves the memory problem.
New test version v3.15.11 pushed
- ExplainabilityEngine memory fix
- Refractor battery policy plannings method
Hi Jeroen, question/observations after the update of last night.
Webcam data of the P1 meter tile has changed.
Webcam date of the Battery Policy tile is missing.
Significant lees Time line information and it apears the Battery Polici tile status indicator is not correct.
=== HomeWizard Battery Policy — Support Info ===
Tijdstip: 2026-04-14T10:09:44.202Z
— Batterij —
Aantal: 3 Capaciteit: 8.06 kWh
Max laad: 2400W Max ontlaad: 800W
SoC nu: 79% Modus nu: zero_charge_only
— PV —
Capaciteit: 6500W Geleerde slots: 0/96
PR instelling: 0.75 PV actief: true
— Instellingen —
Beleidsmodus: balanced Tarieftype: dynamic
Strict min/max: true
Max laadprijs: €0.150 Min ontlaadprijs: €0.160
Min SoC: 10% Max SoC: 100%
Efficiëntie: 0.78 Cycluskosten: €0.075/kWh
— Laatste policy run (v3.15.11) —
Tijdstip: 2026-04-13T22:45:01.337Z
Prijs: €0.268 SoC: 29% Huidig verbruik: 7258W
Scores: laden=0 ontladen=0 behoud=0
Beslissing: discharge → zero_discharge_only
Break-even: €0.106 Gem. kostprijs: €0.051
Optimizer: discharge
Prijsrange 12h: €0.250 – €0.373
Yes sorry, its a bit dodgy but you are also on test/beta which is now also used to troubleshoot memory crashes from other user.
The P1 webcam drawing moved to the battery-policy as it makes more sense to have it to “smart” charging and forecast PV etc. Further the “smart charge” from Homewizard information will be visible there in the future.
Great, thanks for the update. I know I’m on the beta version but like to share my observations, don’t know if they are (future)features, bugs or my own misunderstanding. Happy with your work, that’s for sure.
I deployed new test version hope that one is better.
Apologies for posting my question in the wrong thread. It might not be the app’s fault, but who knows, maybe someone knew the answer to my question. I didn’t know that this thread is only for questions to the app developer. My apologies again; I will open my own thread.
Sorry has nothing to do with my app. Sounds more about Homey Energy and or the decimals / round used in Homewizard Energy app.
But totally unrelated to my app.
No problems with test but is it safe to install the stable version over the test version?
Yes, actually it’s the only way to revert the app version.
But you can lose new functionality;
In case you don’t encounter any issues, you’d best just continue to run the test version, until Jeroen announces to publish the test version as stable.
OK yes that reminds me to stop auto-updating and wait for the stable. Not easy with 2-3 updates a day sometimes 
Sorry, I am trying to fix a memory problem for a user that keeps crashing regularly.
Sadly I can only provide updates via test/beta version method.
So yes, either install the stable version (with the risk of loosing added features in the new version) or disable auto update and manually update when you like.
Next week I take a break and I will stop updating this app.
It means “Dynamic Programming” its a main procesw handling dynamic prices, weather, solar forecast, solar production into a “planning”.
This is the main process running every 15min to adjust the planning for the different modes the battery must do (charge, discharge or standby)
When I change the temperature in the Homewizard app (Heatlink) from, say, 16 degrees to 17 degrees, the set temperature jumps back to 16 degrees after about 5 to 10 seconds. If I do it again, it stays at 17 degrees.
I have a few flows, and I have to run them twice.
The first time, the temperature does indeed change in the app on the Heatlink, but then jumps back to the old temperature. If I run the flow again, it stays correct.
Until a few updates ago, I never had any problems with this.
Can you tell if something is wrong?
I only see connection issues with the water meter and the P1 meter.
But when I look at the live view, I always see the water meter running right away.
But that’s not what this problem is about.
0c0d99f4-1b6d-4e2a-9f37-4eb56de2c409
I made this one, but it’s useless—I used the wrong app. Sorry.
eb5b1aa5-3931-4454-ab63-3bc95f1de7e1
Translated with DeepL.com (free version)
