Nearly perfect!!! great Job
BUT : yesterday I created the same virtual switches , and today I see placeholders
and in the device the new types are missing.
one more idea: is it possible to make the setpoint more generic? like by adding a unit for setpoint for switching heatpump when PV is above this setpoint
I like this new switch types 
Greetings from Austria
Leopold
After updating to 3.70-37 my solar connected to the multi RS was only producing around 18watt when it should already been more than that.
Checked all my node-red node’s feeding in to grid was on allowed and PV was enabled. I’m not running DESS. Just ESS with battery life. I often disable charging in the morning and with the previous versions the Multi RS connected solar would feed in to the grid. But now it looks like something is changed in that with this version and the PV would not generate. Enabling charging and the pv started generating again. Not sure if this is a fix, bug or a future. Would be good to know how to feed-in the solar on the multi RS to the grid with charging disabled.
Update:
Downgraded to 3.70-35, but the problem existed, went to the official version and still the same. So went back to the node-red flows, found out that enable feedback was somehow disabled but only showed state connected. Didn’t disable it my self. Injected enabled went back to 3.70-37 and problem was gone.
hi @GadingeL , pls confirm on what version you are seeing that Placeholder label. I expect that it is some earlier version, or maybe you are using a plug-in like dbus-serial battery, and that is the reason.
In v3.70~37, clean install, it all works fine here.
Noticed, we’ll fix that, thank you
Yes, there is a generic slider coming.
Thanks, you are right, did a new installation and now it works!
A possible problem with DVCC max charge handling after upgrading from 3.62 to 3.70~37 beta.
I have an unsupported config. Basically an asymmetric multi II split phase in a 3 phase environment. 
So I run the 2 parallel Multi II 3000 on L1 from a Cerbo, and the single Multi II 3000 on L3 from an rpi. Both run Dynamic ESS. The rpi uses MQTT to get grid meter, battery data and DESS schedules from the Cerbo.
Originally, I ran a DcSystem on the Cerbo to reflect the Dc charge/discharge of Multi on L3, which works for DVCC but dynamic ESS doesn’t adjust for DC activity, so I had to make several mods to delegate/dynamicESS.
I recently converted that to an emulated MultiRS running on the Cerbo, reflecting activity of the Multi II and a Fronius Primo on L3. This allowed me to drop mods from delegate/dynamicESS, which sees it as PV activity.
Installing 3.70~37 to see if it would help with an additional Multi, or MaxDischarge management, which it doesn’t, I found that maxcharge management also stopped working due to the delegate/dvcc change to update.values in class InverterCharger, which now uses PV current iso Dc/Current. This was for better distribution of maxcharge across solarchargers and inverterchargers when required, but has the effect of driving maxcharge to zero for the vebus multi. So the battery either didn’t charge enough, or charged too much. I fixed by removing the new overlay. I will need to check on the new distribution code, but I don’t recall ever seeing my solarchargers at anything other than max, even when dess inhibits feedin due to negative price.
Looks to me like this code will not work in a mixed vebus multi and MultiRS environment. I’m not sure if that is actually supported, although it seems to be in delegate/dynamicESS, but likely an unusual use case. I will either fallback or do my own mod, but thought I would report it in case it was supposed to work.
Smart IP43 Charger not showing correctly. It shows Instead as an inverter/charger with an AC load connected that doesn’t apply in this case. It also shows as OFF when the charger is actually ON. Tapping on it takes your to the charger page. Shore power not showing at all. Thanks.
this is a printscreenshot stable version but with the v3.70-37 it is permanently this fault in Node Red (lost connection …)
Can this please be solved?
Because of this plugin I’m waiting for 3.70 & SK 2.16: @canboat/visual-analyzer
I am somewhat concerned about the integration of Shelly switches. We have installed more than 75 on the vessel so far, with a further 15–25 to follow.
The integration into VenusOS shall enable reliable and quick switching, and the UI need to allow free grouping for visualize them plus there is the request for switching of groupings (one virtual switch and n physical switches).
Any thoughts about?
Do you have a Multiplus in your system?
If so, something does seem off.
If not, I believe this has been my experience with the Smart IP43 all along — not sure what’s different now from what you’re describing.
I don’t have a Multiplus, I just have a Smart IP43 Charger that somehow shows as an inverter/charger with AC loads that don’t apply, shows as OFF when it is indeed ON, and doesn’t show shore connection.
Unfortunately this is the expected behavior for a system without a Multiplus, and only a Smart IP43. Victron does not treat the Smart IP43 as seriously as the Multiplus, for example they don’t support DVCC.
Oh, that is disappointing. All this beautiful functionality in Venus OS, and Victron’s flag smart charger is not supported correctly. It will be nice to get a response from Victron please, about your plans to display this charger correctly after all this time. Thanks @silvercreek for your response, and to Victron in advance.
Hi @Sdb , can you share the vrm url and enable remote support so someone can login and check?
Hi, absolutely that is the plan. But it has and is taking quite a while unfortunately.
Hi @h4i5j6 have you tried what is there now? Switching of groupings will require you to work in Node-RED.
and afaik, it all works (in the beta)
Matthijs
389794 - tunnel set open
This afternoon installed other Browser (Firefox) and since then no problems anymore.
I have gutfeeling that there is a link with losses off internet (quality-packet lost-etc) not sure off course.
I am working local and the local network is ok (0 packet losses) still I get more troubles when the internet is not stable.
I am not the only one having this problem there are several topics about it.
Unfortunately, beta testing is impossible at the moment. As we are at sea until 1 week before the Metstrade starts and only have a single Ekrano production system with deep SK integration to two navigation PCs with Timezero, I avoid beta or “too fresh” versions on all systems.
Therefore, at the moment I can only contribute what needs to be considered from our perspective.
No Node-RED, but Mediola AIO Creator Neo.
