Ok, but then better just wait, test, and see 
.
Thanks @mpvader. You folks are doing an amazing job with this platform and outstanding UI, so looking forward to when you can fit this integration. Thanks again.
3 Likes
Good day all, per just now we’ve made v3.70~39 available for public testing.
Its mostly about (small) improvements to the switch controls in the New UI. Further details in the change log above.
Have a good weekend! Matthijs.
2 Likes
I was testing peak shaving and it works (EM540 grid meter).
But I do see strange things happening in VRM.
Picture “grid metering → Inverter/charger”
Picture “grid metering → external meter”
Is this a bug in VRM?
I am running Venus beta 3.70~39 on ekrano gx with Large firmware set.
I have enable Node-Red and SIgnalk. Node red works fine, but SIgnalk web interface is not working. (I.e. cant connect to the URL).
I have toggled signalk off and on a few times and also rebooted the Ekrano with no luck.
Is this a known issue? Any fixes available?
THanks,
Alex
On v3.70-39: My Shelly EM50 that is used to measure the power for my heat pump does not show the power consumption at all. It is listed as product „Expansion IO“ in VRM while a Shelly Plug is listed as AC Meter.
just installed official Venus OS release 3.66, VRM seems to be the same as I select external meter, so none 3.70~39 bug but bug in VRM.
Hello. Did for someone broke the MQTT in the NodeRed ? For some reason i can not recieve/send to either external broker or internal . Using MQTT in and Out nodes. It was working approximately 10 days ago. I have 3rd party EVSE to mqtt and virtual MPPT(DC) . Thoose work okay . When i send data from external source. If i send from node red it stops working due to timeout.
I’ve been wondering the same thing albeit on a 3-phase mains with only a single phase MultiPlus system with both an em540 (L1, 2, 3 grid) as well as a current coil (L1 but at same location as the em540: directly at the mains). What I see is that no matter what settings I try, I cannot get the system to recognize that there is a 3 phase load before the MultiPlus (as AC loads) and and only a 1 phase load after the MultiPlus (as essential loads). In this specific configuration L2 and L3 of the 3 phase load will show op on the AC load panel and the L1 component of the 3 phase load will show up on the essential loads panel. Even when specifically setting the MultiPlus only to support loads on AC-out. I just can’t wrap my mind around why this is or how to change this. I thought about removing the current coil or placing it not at mains in but after the 3-phase charger connection but then the MultiPlus L1 25A max regulation won’t work anymore in case of a failure of the em540.
What I would expect, and need, is to only see the MultiPlus L1 AC-out load on the essential loads panel. And then the L1, 2, 3-phase load on the AC loads panel with Shore loads displaying AC loads plus the MultiPlus L1 AC-in loads (this I need to check to be correctly calculated)
Basically with no loads on AC-out and the multiplus not charging the house/boat battery, I’d need to see essential loads to be zero. And the L1, 2, 3 of the 3-phase propulsion battery charger as AC loads. But it doesn’t, I see L2 and L3 as AC loads and L1 as essential loads.
The use case knows only three states (and the ‘Optimized’ ESS states have been tested as well with the same result):
- Shore connected, MultiPlus in passthrough/inverting (ESS external control, mode 3). Inverting automatically when the L1 of the 3-phase AC loads plus the MultiPlus L1 AC-out combined go over the set L1 maximum of 25A.
- Shore connected, MultiPlus charging (ESS keep batteries charged, mode 2). And again automatically throttling charging or even inverting to safeguard the mains L1 25A limit.
- Shore disconnected, MultiPlus inverting (ESS mode 2 or 3 makes no difference)
When shore connected, the 3 phase load concerns the propulsion battery charger that is set to max out the available mains fusing 3 x 25A.
It is therefore essential to have the MultiPlus manage the mains L1 load not to exceed that same 25A, which it does by the way, by throttling down it’s own charger and/or use the house/boat bank for inverting to deliver power to the essential loads to protect the mains L1 fuse.
Only when the propulsion battery charger starts to throttle down when its battery is almost full Is the MultiPlus allowed to use the available ‘headroom’ of the 25A mains L1 fuse to support the essential loads and/or charge the house/boat battery bank.
Technically this does work right now, but the way those loads are displayed on the AC loads and essential loads panels are just not in line with the actual power distribution. By the way, selecting ESS mode 2 ensures all phase are controlled independently, the MultiPlus should not attempt to compensate any imbalance in the 3 phase propulsion battery charging system with energy from the house/boat battery!
And although I didn’t test for it explicitely, I do wonder what is going to happen if there is a malfunction in the 3-phase load section, specifically an overload of L1. In that case, with the MultiPlus set to only support loads on AC-out, it should definitely NOT try to supply (upto an additional 20A of) power to L1 on the input side. Instead the 3 x 25A MCB on mains(shore) in should trip as intended.
PS, sorry to have to ask but I can’t do it myself: if deemed not to be a beta test topic, could a moderator please be so kind to fork of a topic specifically for discussing the ‘support all loads versus support only essential loads and AC loads versus essential loads display panel’ situation.
PPS, for those curious about using ESS on a boat with removable shore mains: in front of all the onboard AC wiring sits a large 3-phase relay with it’s coil wired to N-L3 of the shore connector. This relay disconnects instantly when shore power is unplugged, mitigating the small but present risk of having a ‘hot’ L1 pin on the shore connector for the few seconds it may take the multiplus LOM detection to kick in and disconnect L1 AC-in.
Hey all, v3.70~40 is available for testing, a few fixes - details above.
Thank you! I’m going to sound like a broken record, so I apologize: but is on the road map for 3.70 to allow users to disable Peak Shaving completely?
In our ESS / DESS system, when SOC is scheduled to stay “flat” (consume from grid), the FET bridges remain active and the system still chases loads.
This consumes ~500-600W on our system with 4x 10k Quattros. Disabling Peak Shaving would save us ~180kWh per month, assuming the system could go into true standby mode when scheduled to consume from grid (similar to when the system is at min SOC).
The same applies when using the ESS “Scheduled Charge Levels” (without DESS), when the system is sitting at the scheduled charge level.
I know you all have been busy so thanks for the attention.
“If/when I have some spare time” (crazy busy here these days) I’ll continue my quest to find the most elegant way to put a Multiplus or Quattro in pure Passthrough mode, where the input is connected to output via the internal relays but all the power electronics are off.
1 Like
I have added a Shelly 1PM gen 3 to the Cerbo GX and when selecting the position, in this case “AC output” , it only reverts to “Unknown” Is this a known bug or still under development?
Hi @HcGrande , noted; we’ll make sure this is fixed.
1 Like
Hi @HcGrande
I have added a Shelly 1PM gen 3 to the Cerbo GX and when selecting the position, in this case “AC output” , it only reverts to “Unknown” Is this a known bug or still under development?
Thanks for reporting, this will be fixed in a coming beta release.
Regards,
Rein
1 Like
Good day all,
Herewith a heads-up of changes, including a breaking one, which are coming up for the Virtual switches:
Overview of the changes
- The virtual switch nodes will support 1 switch only. It will no longer be configurable to create 4 virtual switches out of one node.
- The “Group” field, which is already available via the UI now, and allows to organize multiple switches together for the user on the same “card”, will also be configurable in the Node-RED flow. Which makes it faster to set-up, especially when developing a flow and copying that from one system to another.
- Same for the “Custom name” field.
- Outputs will be added to the Virtual switch nodes, eliminating the need to add switch nodes separately, cleaning up the canvas.
Impact on existing flows:
- Existing flows will continue to function in general after the update, ie. they won’t stop functioning in their entirety.
- Flows where multiple switches (Switch 1, 2, 3, 4) are configured in a single virtual device, only Switch 1 will remain visible in the UI. Switches 2, 3 and 4 will no longer be visible. Put differently: switches 2, 3 and 4 will be ignored; and also their configuration will no longer be accessible from the Node-RED flow editor.
How to prepare:
To avoid any issues, you can already now create separate virtual switches in your flow. And as long as you create one Virtual switch per node, then you are good.
Here is a small screenshot:
Conclusion:
This change will come in one of the next beta releases. If you have auto- update enabled for beta releases, plan accordingly. We’ll mention this as part of the change log when this is included.
1 Like
Hi all
Great to have virtual devices now. I use especially the virtual battery.
I’m not sure where to ask for improvements, but it would be great, if the virtual battery as well would provide
/System/MaxCellVoltage
/ConsumedAmphours
/AllowToCharge
/AllowToDischarge
InstalledCapacity
Thank you
wohlfeil
Hi all, per just now, v3.70~41 for public testing.
Changelog above, mostly gui-v2
Agree, see:
