I was happy to read about that fix in V3.80~22.
But since install, some spikes in VRM for ‘AC-Loads’ go even higher (>15.000 kWh in one hour) and there seem to be more of them. Today already 3 of them.
These spikes are only visible in the System Overview Graph on VRM, nowhere else.
I have indeed several FINDER meters attached via Modbus via Virtual AC-Loads in Node-Red on OS-Large.
But i’m not aware on how you include their values into the AC-Load graph in VRM.
In fact, i would really like to exclude some of the meters to be included in your VRM data at all, as they were never meant to serve for such purpose.
Maybe i also need to tell that these meters do NOT sum up to the main AC-Load that Venus OS calculates for the system it is in, but can be lower OR higher!
So, can you please elaborate in detail on that error and the general data flow please, so i know the root cause and may do temporary workaround or whatever?
Thanks! I installed the ~27 and will report again.
I’ll try the ‘initialize with defaults’ also if it does not help. Yes, i can imagine that when it intializes with e.g. 0kWh consumption, BUT has values at all, it is used somehow by Victron, seconds before i fill in values via Modbus. Resulting in an instant big spike. Sounds plausible at least. Maybe i disable that setting at all on all virtual meters/loads.
Victron should still explain, how they use the values of my virtual loads! And how they distinguish ‘AC-Loads’ from ‘Base load’. Because in my case, my virtual devices also contain visualization of electrical circuits that have nothing to do with the system where the victron parts sit in…
Let me start by explaining that we actually don’t like filtering these bad energy values. Ideally these bugs should be fixed at the source, not filtered for later. This was not a bug that was fixed, rather it is an attempt at working around bugs in other places.
The problem is that there are just too many third party products that play fast and loose with energy counters.
In this case, you see the spike because your energy meter briefly returns to zero, and jumps back up to the total. This is interpreted as a counter wrap.
My Finder Meters are tracked and filtered now for Zero values, but they were not the problem.
I went back to older OS and could reproduce it when “Start with default values” was ON.
So now i filter possible zero values before accidentally writing them on to the virtual AC-load.
Next, I disabled “Start with default values”.
And in addition, i start them “not connected”, but send a msg.connected=true once i gave them a complete dataset.
Only thing, once again (old problem), all this shuffled again the IDs (100,102, etc) of the Virtual loads. Thus, my tracked VRM values of the last months are shuffled and broken AGAIN.
(If victron could just give an option to FIX these IDs manually…)
In GUI-V2 there is a way via “Settings > VRM > VRM Device Instances” to set a fixed ID for “Device Instances”. Have you tried this?
It must be possible - with one exception - a “MultiPlus-II”.
It’s not possible to set a fixed ID for a MultiPlus-II this way - does anyone know a way for a “Fxed-MultiPlus-II-ID”?. In VRM there are 7 IDs for the MultiPlus-II. I have to restart often multiple times to get the correct one for consistent VRM-Datapoints. But with more than one “Changing-Device-ID” a restart as a workaround is difficult.
Under “Settings > VRM > VRM Device Instances” you can change SOME IDs, but the Virtual Meters and Loads are not even listed there.
In VRM itself you can’t change it, too.
So this stays a problem…
