Jeroen,
I saw the same option twice. See the picture.
Regards,
Ad
Which option?
New test version, hope this one stays running now. v3.13.34
The bottom two are the same?
Zet batterij in Nul etc
Nope it says “opladen” and “ontladen” biiiig difference 
zero_charge_only
zero_discharge_only
1 Like
sorry i’m blind 
No worries, was a late night (or early morning) here missed out code problem that I assumed was there, but it wasn’t.
1 Like
@Jeroen_Tebbens running version 3.13.36 now and that one seems stable.
Thank you for your confirmation.
Hi Jeroen. Running version .37. Many crashes, sorry.
Nothing is changed on my side, running via websocket. CPU usage 20%. I switched the app off for the time being.
thks
1 Like
Hi John, sorry and this is getting frustrating. On one end I fix the websockets with other users having crashes and timeouts. I waited a day, no crash dumps or diagnostics and now there are new ones. Drop me a diagnostic please.
No problemo, 9bca1fd9-e689-4c5f-bd3b-06c1a611a729
I have set the app to run.
Got and fixing now
1 Like
Try v3.13.38 just pushed to test should fix the websocket cleanup that caused null references (crash).
Thanks. Installed it, I will watch it 
Good, websocket is fast but the amount extra checks is insane to keep it stable.
And if there is just a short hickup in the connection the fun starts.
I’ve added extra logging so I could pin your problem easier. Hope it stays ok now.
Sorry. App crashes and restarts now automaticly, shall I send a diagnostic? Or wait for more crashes?
Yes sent it. See if I can get your case solved. I only have 1 battery and 1 p1 so my websocket traffic isnt that much.
8266bcbd-a378-4392-a963-d9dcbe6443ab here you go
No automatic restart now.
update 15:26 crash and restart automatically
