Hi
Anyone an idea why I have an analog tank sensor on vrm instance 20 sitting?
and furthermore my Fronius is as well on vrm instance 20. And two times. I have no idea why ...
Thank you
asked
VRM multiple device entries and Fronius two times
Hi both,
The Fronius as well as Tank input being on ID aka VRM-instance 20 is not a problem. These instance numbers need to be unique per class of product (battery monitor, inverter, tanklevel, and so forth).
Its normal, and common, to see overlap.
With regards to the other reported issue, seeing the Fronius twice in the list, that looks indeed to be a bug in the visualisation in the Device list. I'll get that fixed, most likely will be soon; ie a few days, maybe a week. I don't expect there is any harm in that, other than seeing it twice in the Device list on VRM.
All the best, Matthijs
Got my Symo two times as well... Maybe because it has two trackers?
This was already reported by me several weeks ago and was taken by Victron as a case.
Unfortunately, the problem wasn't solved when my CerboGX broke, now I'm waiting for a replacement but the summer vacations don't help speed up the process.
What an interesting coincidence.
I also have two duplicate entries of my Fronius Symo inverter.
Possible that come Victron technician or Victron employee can take note of this issue?
Yes my issue was the duplicate entry of a fronius inverter in device list in VRM,
At the time, @kevgermany ask for my VRM id and transfer the case to Victron who enabled remote access on my system.
Since then I have never heard of this problem, but as I said in the meantime, my CerboGX was in the group of CerboGX's that fail on power up and it broke, I guess then Victron no longer has access to this problem.
Interessting - it seems to be always id 20 - and in my case the fuel level sensor is as well on id 20
someone an idea how to open up a case with victron?
Also happening to my Fronius installation, and I have a few more coming up. What is the fix for this? @kevgermany ?
In my case, they popup alternately, not at the same time. This is confusing to the API integration we have with VRM!
