Which PGNs are required for digital switching modules to appear?
Hello!
Per just now, v3.60~86 available: stability fixes.
2 Likes
Hi, that is not public at the moment. For now the focus is on making the feature work with industry partners.
Later/soon I’ll consider the details on making the protocol available.
Matthijs
The toggle to temporarily disable Dynamic ESS is still broken in v3.60~86 
See: V3.60 - DESS toggle switch disappears
2 Likes
Are you able to make it available to Victron dealers?
Also in the beta, I still experience this issue:
Often in the morning the grid is been used for ac loads which is more expensive than selling less in the evening to support loads until pv power is sufficient.
I have a workaround of lowering the minium soc during the night and rising it during the day, but that is not a real solution.
6 Likes
A small comment regarding the screens, the order is different from one to the other. It would be nice if it was the same.
5 Likes
I agree. I mentioned this a few months ago but it’s not been addressed
I put it in the “annoying but not life threatening” pile.
On my brief page Alternator is on the top and the solar is underneath.
If I pull out the sidebar on the brief page they are the opposite way round
On my overview page Solar is on top and Alternator is underneath.
Presumably inverting them on the Brief page would unify the views.
2 Likes
I believe I found a Node-RED bug on the latest beta ~86
‘Dynamic ESS’ node,
‘Venus settings’, ‘Actiive restrictions for schedule x’
as well as for
‘Venus system’, ‘Active restrictions’
The return values 1 and 2 are acting opposite of what is set in VRM DESS
EDIT: as workaround I simply assume the node’s values list is wrongly worded, with the value 1 and 2 ‘description texts’ swapped around. But while testing, I notice even without any restrictions in VRM, these nodes provide erratic values while VRM DESS sells to grid: 2 (Batter to grid flow is restricted) which contradicts what is actually happening.
Hi! v3.60~87 is now available for public beta testing.
Fixes one small bug in info shown for managed batteries
New gui v2 is really great, but I would like to add the following comments
I would really like to have bars instead of gauges in the brief page. The bars could also have different colours insted of all blue.
For those who have the Safiery StarTank sensor, it would be nice to have the temperature displayed in the environement tab
Maybe a stupid question, but how does one get rid of the “Firmware integrity: Modified” status ?
Context: I just upgraded a Venus GX from v3.60~87 to v3.60 Stable and the above message seems persistent.
So far I’ve tried “Reinstall latest stable firmware”, switching from the Large image to the Normal image and combinations of those actions but the “Modified” status remains.
I’ve resorted to downgrading to the v3.55 Normal image, upgrading to v3.60 Normal and it still says Modified, even after “Reinstall latest stable firmware” at that stage.
Disclaimer: in the past I logged in over SSH to this device but SSH was disabled again afterwards.
Edit: maybe this is a cosmetic bug in the release for beaglebone (Venus GX), as my updated Cerbo makes no such complaints but had SSH enabled in the past as well.
As of the latest beta v3.60~87, my primary battery monitor disappeared so the battery percentage was 0%. It suddenly reappeared a few hours later when I went into devices to see what was happening. Now I can’t scan for firmware updates from VRM. Just hangs there. Never had this with any previous beta releases.
With v3.60 officially released today, I suspect the servers to be a little bit busy 
No worries, it’ll be back available again soon.
Hello all! Today we’ve released v3.60 as an official release.
Thanks all for your feedback and help. Its been crucial in getting it all done.
We’ll soon start another cycle.
In case of any possible issues in v3.60, please follow the same guidelines as usual.
Have a good evening, Matthijs
14 Likes
Thank you and the team for all the effort made! Installed this afternoon without any problems.
3 Likes
Congrats and shout-out to the dev team. This was the first beta we’ve been actively testing from start to finish and I’m impressed by the collaborative process and results. Looking forward to the next beta, this time we’ll be ready to share our list of issues, feature requests and potential bugs right from the getgo.
1 Like
Could be indeed, perhaps the method now used to check if the file system is ‘tainted’ doesn’t work on the file system used in the Venus GX. Though I thought they were there same.. Anyway, we’ll look into this.
EDIT: confirmed. a test Venus GX that I have access to, which for sure is not modified, has the same issue.
#1473
1 Like
Sorry for only discovering this on release day.
Good thing it’s only a cosmetic bug that will undoubtedly be one of the fixes in v3.61
Still a big thumb up for an intense testing path and successful release ! 
1 Like