All my loads and PV are on MP2 AC input 1. However, system data shows all PV power being on ACIn2. The system works but it seems like a minor data visualization/handling bug. This is with the latest beta 72.
Problem:
Other possibly relevant screens and settings:
Since 3.60~71 my problem Cerbo keeps losing connection with CG EM340 Grid Meter seems to have dissappeared. Was this problem related to VM-3P75CT Meter disconnecting frequently (addressed in ~71)?
Yes! Good to know it works well now
I installed 3.60-72 today specifically for the Orion XS dvcc issues. And it is working correctly.
Was able to charge battery from solar battery without it showing as alternator and doubling in DC load readout. It didn’t overvolt either.
Thank you!
I installed 3.60-72 yesterday and had some unexpected behaviours which forced me to roll back to latest stable.
System is
1st problem: The AC1 grid lost alarm got triggered every 2-3 min or so
2nd problem: CERBO touchscreen started fliggering and very slow response
3rd problem: System reboots
After roolback all is working
Hi @SFH , thanks for the report. Is it ok if we login?
I see that the system (found it via your email address) is offline now - would it be possible to have it online again?
Would be great to have a look at the logs.
Matthijs
Certainly. Give me 45 min and i will be on the boat
Perfect. I’ll send you an email - to avoid spamming everyone here on the community with the logistics
Hi all, available for public testing per just now: v3.60~74.
Highlights:
Thanks for all your reports! Getting closer & closer
Upgraded to v74. Issues seem to be fixed. Running flawless for a couple of hrs
Hey, small amendment: The feature that allows to control a relay on battery cell temperature was part of my announcement; but that was too early / one of the parts needed to make that work is missing. To be continued in a next beta.
Grid Setpoint in ESS doesn’t work anymore with DESS enabled in 75. It did work in 69.
Still works for me on ~75 Large.
Then there is something that can cause grid setpoint to become inactive in combination with dess and it doesn’t happen all the time.
Hi all, two extra updates:
1. SmartSwitch video
Make sure to watch this video by Energy Solutions, whom in detail explain all the options of the new Switch pane in combination with their 4 channel DC SmartSwitch:
2. Controlling a battery heating system with a GX
And secondly, one addition to the v3.60~75 changelog is that its now possible to have a GX relay controlled by battery cell temperature. Perfect for a heating system in combination with the Lithium NG batteries - without having to configure it in Node-RED.
To configure this, go to the usual menu where temperature rules for relays are set. That menu now also shows battery (cell) temperature:
Any update on the Multi RS grid feed in limit bug? (Victron Multi RS 6000 limited to 5000W (20,6A) grid feed in when using external current sensor? - #31 by vaursechs)
The most probable case I can see in my crystal ball is “they’re working on it” 
Throughout the v3.60~beta there have been many and fast intermediate releases and fixes.
Now that we’re approaching the final v3.60 release, you can expect less intermediate releases with more time between them.
The main reason is that all new features have been added and most small bugs and “quick fixes” have been handled, but now the more serious release-critical bugs still need some work.
And unfortunately those need more time than the average obvious quick bugfix.
My gut feeling tells me that this week probably won’t see a major bugfix release but by end of May / beginning of June there’s likely to be a first Release Candidate.
Hi all, available per just now: v3.60~76.
It fixes all open issues with the recently added “Virtual switch” feature in Node-RED.
Would be great if you could test that; any feedback here please: Beta V3.60~69 onwards Virtual switch feedback and loss of settings on reboot - #24 by ADT.
And also this changes the underlying generic code of many nodes: thorough testing & feedback welcome.
Thanks!
Hey all, can I ask you to as much as possible post reports and such in the relevant topic, rather than having them all here in the main Venus OS beta topic that has then changelog?
Doing that saves me time in explaining my colleagues where to read to get a good picture of the possible issue in their area of responsibility; and saves them time as well.
So, in short: if you see an issue, see if there already is a v3.60 related thread in this category; if not, make one.
Replies that can go here are is general feedback, not needing further back and forth, for example positive feedback that an announced feature works well for you 
.
We’re keeping an eye on the whole Venus OS beta testing category. Not just this post.
Thanks!
Let me start with a compliment you devs are doing great work actively working with us beta test customers here on this forum.
Then a suggestion towards your request to keep the back and forth out of the main thread for topics that you deemed fit to move to a separate thread, maybe you could add a list of those moved topics right next to the changelog in the first msg where, I assume, everybody will have look anyway with every update. An index of sorts to provides better visibility for all of us as well.
