Sorry but need more information. Diagnostic and a screenshot of the websocket tab in app settings.
Okido, herewith
I reinstalled Battery policy, no difference
2d016da4-7117-4dbd-bcc3-3da7a2b81f18
═══════════════════════════════════════
HomeWizard WebSocket Diagnostic Report
═══════════════════════════════════════
Generated: 2026-03-13T16:52:42.981Z
── Device: 5c2faf35c624… ──
Connected: YES
Snapshot age: 203s (13-3-2026, 17:49:19)
Reconnect attempts: 0
Messages: 10199
Measurements: 246 ok / 7108 dropped
System: 10 ok / 0 dropped
Batteries: 118 ok / 1008 deferred
Reconnects: 9
Handler errors: 0
Last connected: 2026-03-13T16:45:17.032Z
Last disconnected: 2026-03-13T16:45:09.694Z
Handler timing (max): meas=93ms sys=101ms bat=25ms
Handler timing (last): meas=1ms sys=101ms bat=1ms
Reconnect rate: 0.1/min (9 in 7202s)
── 
No anomalies detected ──
── Event Journal (last 20) ──
13-3-2026, 15:43:16 close [5c2faf35] WebSocket closed
13-3-2026, 15:44:34 open [5c2faf35] WebSocket opened
13-3-2026, 15:45:02 close [5c2faf35] WebSocket closed
13-3-2026, 15:45:14 open [5c2faf35] WebSocket opened
13-3-2026, 16:00:06 close [5c2faf35] WebSocket closed
13-3-2026, 16:00:17 open [5c2faf35] WebSocket opened
13-3-2026, 16:15:02 close [5c2faf35] WebSocket closed
13-3-2026, 16:15:14 open [5c2faf35] WebSocket opened
13-3-2026, 16:30:06 close [5c2faf35] WebSocket closed
13-3-2026, 16:30:16 open [5c2faf35] WebSocket opened
13-3-2026, 16:45:06 close [5c2faf35] WebSocket closed
13-3-2026, 16:45:17 open [5c2faf35] WebSocket opened
13-3-2026, 17:00:06 close [5c2faf35] WebSocket closed
13-3-2026, 17:00:17 open [5c2faf35] WebSocket opened
13-3-2026, 17:15:11 close [5c2faf35] WebSocket closed
13-3-2026, 17:15:26 open [5c2faf35] WebSocket opened
13-3-2026, 17:30:12 close [5c2faf35] WebSocket closed
13-3-2026, 17:30:25 open [5c2faf35] WebSocket opened
13-3-2026, 17:45:06 close [5c2faf35] WebSocket closed
13-3-2026, 17:45:17 open [5c2faf35] WebSocket opened
═══ End of report ═══
thanks that was what i was looking for.
i did a test and it is working
I’ve uploaded v3.13.60 how this works better for you.
Sorry, it didn’t.
I just updated Homey and restarted, perhaps it helps.
What I see from the CPU usage, in the night of 13-3 it goes up, perhaps update 3.13.59?
I can’t see at what time the update of the HW app was done though. Battery policy had been uninstalled for weeks (from the moment you solved the last high cpu usage)
Update 22:16, in the night of 12-3 the higher load starts I suppose
Weird, must be energy (apiv2) websocket issue.
Need to enable debug somehow to see what goes on your end. I will a setting for the energy device so you can enable it hopefully we can find the problem.
I pushed v3.13.61 to test. Check how that goes.
If you still face issues toggle the debug mode in the settings of the energy_v2 device and sent me the diagnostics. Make sure you turn it off then else the debug by itself will be an additional CPU problem.
Still high so to see, debug on, here websocket info and diag
65c497d1-3d0d-4309-8f12-502289366626
═══════════════════════════════════════
HomeWizard WebSocket Diagnostic Report
═══════════════════════════════════════
Generated: 2026-03-14T11:13:44.238Z
── Device: 5c2faf35c624… ──
Connected: YES
Snapshot age: 17s (14-3-2026, 12:13:27)
Reconnect attempts: 0
Messages: 606
Measurements: 21 ok / 577 dropped
System: 2 ok / 0 dropped
Batteries: 2 ok / 0 deferred
Reconnects: 1
Handler errors: 0
Last connected: 2026-03-14T11:05:53.750Z
Last disconnected: 2026-03-14T11:05:44.186Z
Handler timing (max): meas=154ms sys=1ms bat=1ms
Handler timing (last): meas=1ms sys=1ms bat=1ms
── No anomalies detected ──
── Event Journal (last 20) ──
14-3-2026, 08:15:05 close [5c2faf35] WebSocket closed
14-3-2026, 08:15:18 open [5c2faf35] WebSocket opened
14-3-2026, 08:30:06 close [5c2faf35] WebSocket closed
14-3-2026, 08:30:19 open [5c2faf35] WebSocket opened
14-3-2026, 08:42:41 slow_handler [5c2faf35] measurement took 1300ms
14-3-2026, 09:30:06 close [5c2faf35] WebSocket closed
14-3-2026, 09:30:20 open [5c2faf35] WebSocket opened
14-3-2026, 10:55:45 slow_handler [5c2faf35] measurement took 260ms
14-3-2026, 11:00:07 close [5c2faf35] WebSocket closed
14-3-2026, 11:00:18 open [5c2faf35] WebSocket opened
14-3-2026, 11:08:23 slow_handler [5c2faf35] measurement took 357ms
14-3-2026, 11:15:07 close [5c2faf35] WebSocket closed
14-3-2026, 11:15:18 open [5c2faf35] WebSocket opened
14-3-2026, 11:38:05 close [5c2faf35] WebSocket closed
14-3-2026, 11:38:17 open [5c2faf35] WebSocket opened
14-3-2026, 11:54:45 close [5c2faf35] WebSocket closed
14-3-2026, 11:54:55 open [5c2faf35] WebSocket opened
14-3-2026, 12:03:02 open [5c2faf35] WebSocket opened
14-3-2026, 12:05:41 close [5c2faf35] WebSocket closed
14-3-2026, 12:05:53 open [5c2faf35] WebSocket opened
═══ End of report ═══
Can you spam me a few diagnostic reports as it is only showing measurements per second so I probably need to throttle it there. I have 2s now but seems somehow that is still to heavy for your case.
Here you go
aa749258-15c2-448e-bc4e-86801bc1a59c
4107da99-fb4a-4683-8e6c-9dc35c99648f
37e15361-c280-4997-a55e-0455a783f17a
fcad994f-b666-4270-90e8-7ad396e554e9
768dcb57-f650-4520-b33b-3ed912b59114
f0764c60-012f-40ff-a2a8-0234dcea2816
5c87a63f-7661-4058-9f9e-3965169fa3c8
a7d3d097-f96b-450e-b812-182407559c66
═══════════════════════════════════════
HomeWizard WebSocket Diagnostic Report
═══════════════════════════════════════
Generated: 2026-03-14T11:39:03.747Z
── Device: 5c2faf35c624… ──
Connected: YES
Snapshot age: 227s (14-3-2026, 12:35:16)
Reconnect attempts: 0
Messages: 1891
Measurements: 54 ok / 1813 dropped
System: 5 ok / 0 dropped
Batteries: 6 ok / 2 deferred
Reconnects: 4
Handler errors: 0
Last connected: 2026-03-14T11:30:13.794Z
Last disconnected: 2026-03-14T11:30:05.785Z
Handler timing (max): meas=208ms sys=81ms bat=778ms
Handler timing (last): meas=1ms sys=81ms bat=1ms
Reconnect rate: 0.2/min (4 in 1462s)
── 
ANOMALIES ──
[5c2faf35] Slow batteries: 778ms
── Event Journal (last 20) ──
14-3-2026, 10:55:45 slow_handler [5c2faf35] measurement took 260ms
14-3-2026, 11:00:07 close [5c2faf35] WebSocket closed
14-3-2026, 11:00:18 open [5c2faf35] WebSocket opened
14-3-2026, 11:08:23 slow_handler [5c2faf35] measurement took 357ms
14-3-2026, 11:15:07 close [5c2faf35] WebSocket closed
14-3-2026, 11:15:18 open [5c2faf35] WebSocket opened
14-3-2026, 11:38:05 close [5c2faf35] WebSocket closed
14-3-2026, 11:38:17 open [5c2faf35] WebSocket opened
14-3-2026, 11:54:45 close [5c2faf35] WebSocket closed
14-3-2026, 11:54:55 open [5c2faf35] WebSocket opened
14-3-2026, 12:03:02 open [5c2faf35] WebSocket opened
14-3-2026, 12:05:41 close [5c2faf35] WebSocket closed
14-3-2026, 12:05:53 open [5c2faf35] WebSocket opened
14-3-2026, 12:17:12 close [5c2faf35] WebSocket closed
14-3-2026, 12:17:22 open [5c2faf35] WebSocket opened
14-3-2026, 12:17:56 slow_handler [5c2faf35] batteries took 778ms
14-3-2026, 12:18:19 close [5c2faf35] WebSocket closed
14-3-2026, 12:18:32 open [5c2faf35] WebSocket opened
14-3-2026, 12:30:02 close [5c2faf35] WebSocket closed
14-3-2026, 12:30:13 open [5c2faf35] WebSocket opened
═══ End of report ═══
I will make the throttle update for your energy_v2 customizable.
I think in your case that is the problem. Where 2s seems ok but to heavy in your case.
So you can modify it to 3s or higher and see if that lowers the cpu.
Hmm, changing the interval to 4, 5 of 6 doesn’t change much. When I close the Homey app Slimladen voor Marstek… the cpu load goes down (just after 13:10). Changing the interval up or down: the load stays between 10 and 20%.
I restarted the other app and again more load (just after 13:30). Changes in the interval gives no big differeces in the load. After restart Homey and switched off HW app and Slim laden app they stay on 20% and 10% load?? Weird…I will restart everything again and look what will happen.
What?! SlimLaden had impact on my app? Damn not ok.
I have removed the HW app from Homey and installed version 3.13.58. I reinstalled all hardware frome HW again. The cpu load is now between 0-10%. That’s oké. I will monitor for some time and then start the Slim laden app. It’s now installed and 0% cpu load. I will let you know what happens.
Thanks awaiting your feedback but wasted several hours on this learning that an other app has impact on my app that way is not cool.
I want to rule things out, therefor gone to regular versions. Perhaps it can be a Homey issue (because the cpu load stayed though stopped app(s). When everything is working (looks like it now) I will update the apps step by step to see where it goes wrong. I’ll keep you posted.
First update: the Slim laden app is now on the test version, no extra load.
Second update: Slim laden to production version, HW app to test version: no extra cpu load (execpt when installing new versions)
Third update: both apps on test version: normal CPU load
Very strange…you have seen the graphics with high cpu load, also a crashed Homey Pro. very weird. Perhaps something remains after an update? Now a clean install but I don’t prefer that 
having to add all my hardware…
Or, it’s something within the Homey Pro, restarting didn’t help though.
I hope thing will stay normal.
Sorry for the inconvienence, thanks for your time
App by itself is low cpu, its the devices / hardware that gathers metrics and communication.
