Like this: https://venus.local/gui-v2/?download=vrm
2 Likes
3 posts were split to a new topic: V3.70 issue when adding mods that add relays
I can’t seem to find this info but are Virtual Switches (like Toggle Switch) visible in VRM (or will they be at some point)?
@mpvader, do you have any thoughts on a timeframe of when V3.70 will be released officially? I have a customer application about to go live that will have some neat uses for virtual switches, but not wanting to load a Beta FW version on a customers device.
Quando paratus est 
Hi @thewiep not yet, but yes they will be. Can’t give any dates wrt when that will be - but its being worked on already.
1 Like
November is the goal, but as usual - when the release can be made depends on a lot of factors - hence this is hard to project / make definitive.
Matthijs, et-al
I upgraded to -41 this morning…..A nice to have enhancement for the Levels GUI would to have NMEA Tank Levels include what tank they are for/from. I was super impressed when I connected my Cerbo to my NMEA2K network how quickly you picked up the tank level info but without the specifics of which tank they are for.
I recognize this is not a functionality that everyone wants/needs and not urgent to me just trying to make you aware if possible for future GUI cleanup/enhancement. IDK how each vendor puts their tank data on the wire (I use all Maretron) but I can see the N2K PGN 127505 is probably the Fluid Levels you pickup and display but unfortunately that doesn’t include a label or description field to tell you where it came from. It appears in the Maretron ecosystem they send PGN 130818 separately that has the label info and you’d have to marry it back to the Fluid Level PGN to get the right labels.
In my case above I have port/starboard water and fuel tanks and only one Blackwater Tank so the generic works fine for Blackwater. It looks like the Fluid Instance field in 12705 is the common field to map to Data Instance in 130818 to get the Label: detail…..
Scott in Sunny/FL aboard M/V MARIAH
1 Like
Did you changed something in the battery life algorithm in the latest beta? Last two days it was cloudy and batteries only got charged to 60-65% every day. The active soc limit stayed at min. SOC level (20% in my case). Two weeks ago the algorithm worked normally under similar conditions.
If I understand correctly, active SOC raises about 5% when reaching min. SOC and plus 5% when battery doesn‘t get charged to at least 85% every day?
@mpvader Will there be any additional improvements to dess in 3.70?
I have a SolarEdge 17K inverter that is no longer reporting the correct total production for a day. Reverting to version 3.66 and everything is back to normal. I have tried version 3.70~35-41
Edit: The SE-inverter is running an old firmware 3.2537.0. It has been working perfectly up to now. Current production looks ok, but produced energy is very low compared to SE app.
Another site that I have access to is using a newer SE-inverter (without display), and is running venus os version 3.70~35 without any problems.
Sorry I can’t give you more precise information.
I really welcome the improved integration of the Shellys, thank you for that!
It would be really great if you could assign them another role in the console, such as PV inverter instead of standard grid meter, and also the phase to which they are connected. For example, I have a Shelly Plus 1PM that is connected to L2 in the house installation, but my Victron system is only single-phase and therefore connected to L1. This would eliminate the need to use Node-Red and the virtual device.
2 Likes
It might be a good idea to add a message to the v3.70~44 changelog about the VRM-API changes, with reference to what changes may break current use of the API.
For us VRM-API 0.3.3 breaks the use of installation stats. Reverting (there is a first for everything I guess)
See also: Node-RED DESS implementation issues with 15 minute pricing - #37 by dfaber
I also would appreciate if SignalK could be updated to 2.15+. So it’s possible to use canboat/visual-analyzer.
3 Likes
Bonjour,
Depuis plusieurs version, il y a un bug d’affichage sur la partie “Intégration - E/S physiques”. Bug présent sur VenusGX, OctoGX et CerboGX.
Cordialement,
Totally right! Apologies, I missed that change when compiling the v3.70~44 changelog.
Is being added.
1 Like
In 3.70 ~45 it doesn’t work to set position for the Shelly 3EM pro. I didn’t test with ~44 - I.e when setting AC input as position its back to unknown when back in setup screen.
This when the Shelly is reporting over websocket since it sits in another vlan compared to the Cerbo.
/Kaj
Im also waitnig for this one….. and the latest SK release is already 2.16