After I rolled back to Stable 3.54, DESS settings became available and DESS is working.
After next setup of BETA 3.60~49 they disappeared again.
I desired to use this BETA due to the DESS fix:
Improve how Dynamic ESS reacts when actual consumption or solar production differs from forecasted. For example when there is more solar then expected, the updated algorithm will in many cases use that extra solar power to charge the battery, even if that would exceed the planned SOC level for the current hour. Instead of feeding that excess solar back into the grid for a low price, to later have to buy it back at a higher price.
Thanks for letting us know. I’ll dig into the cause tomorrow morning.
Mind sharing the vrm id (the number in the url of the vrm dashboard), so I know at which sites to look.
And I will give you a bit more details after my experiments on the last 2 days.
I have noticed that Dynamic ESS option in VRM Settings menu can appear and disappear after Cerbo reboot, like I rebooted Cerbo - it is absent, after next reboot it can appear, next reboot - disappear again.
In the Saturday morning I changed some settings and rebooted Cerbo dozens of times trying to find a cause. Unfortunately this black box attempts did not lead to a result.
After next reboot at ~noon I decided to postpone this experiments and wait when known issue with DESS will be fixed, I mean this one Cerbo not loading new DESS schedules.
That time Dynamic ESS option was shown in VRM Settings but DESS Status was Inactive.
After issue was fixed and my DESS switched to Status Auto I rebooted Cerbo and Dynamic ESS option disappeared again from VRM Settings menu and DESS Status switched to Inactive. It was Saturday evening, about 17:00 GMT.
And finally I rebooted Cerbo last time on Sunday morning - Dynamic ESS option appeared in VRM Settings after reboot and is shown by now. DESS is in Status Auto and working properly.
However I am almost sure, if I reboot my Cerbo again - it will disappear again with a very high probability.
Why and what is a reason - it is unclear for me, I did not find any connections with settings, including switching ON/OFF my external grid meter in the system (VM-3P75CT).
So, I hope you will find and fix this issue.
I can reboot my Cerbo by your request if it will be required to reproduce it.
Thank you for that info. It helps me to search in the right direction. I’ve been somewhat able to reproduced this. At least for short while. During the reboot, the dynamic ess setting disappeared as well on my own site. But it appeared again once the Cerbo had booted.
My current theory is that this only happens while the system is still starting up, so it recovers within a few minutes after rebooting. Can you confirm or dispute that?
I haven’t found the exact cause yet, but I am sure it has to do with the fact that the Dynamic ESS configuration itself moved from VRM to Venus in the beta branches. If it can’t reach the GX (yet), it is unable to synchronise the settings. There are some ways to get this to behave better, but lets first make sure that this is actually the issue.
One more thing that also comes to mind is that, with the 3.60~48 update, the number of schedules increased (to cater for future 15 minute schedules). That takes some time the first time it needs to create all of those schedules, causing the first boot to be quite slow.
I noticed this behavior within my experiments.
However I can’t fully confirm this, because after I rebooted Cerbo, as I wrote above, at 17:00 GMT on Saturday, the option is not appeared even on Sunday morning. I had to reboot Cerbo again to fix the issue. And only after reboot it appeared again. I tried this many times before and behavior is always the same.
So, after some reboots it not appeared again even after system is fully started and working.
Looking at the logging of your site, during that reboot, Dynamic ESS was completely switched off (or at least the system reported that).
Will need to discuss and check internally to see what options we have on improving this behaviour.
Not much. Other than that we deem the behaviour acceptable that the settings aren’t there directly after a reboot, but return when the system is running again.
The reason why your system went away for such a long time hasn’t been found, making it unreproducible.
This turned out to be a bug in choosing the right Multiplus. We’ve fixed that in the code and it will be part of the next beta Venus firmware.
Thanks @LiVi for reporting and having me test it on your system.
