I am experiencing a situation where calls to VeDbusService fail. Specifically, the first call succeeds while subsequent calls fail with a path '/' already exists message in the traceback.
The service names are unique. In fact, I've made extremely simple service names as a test com.victronenergy.tank.foo and com.victronenergy.tank.bar and the second call still fails.
Splitting the VeDbusService in separate unix processes works fine. So it appears I can create at most one dbus service in each process.
Is there something I'm not doing right or is this a limitation of VeDbusService?
My application is to take what the NMEA2000 version of SeeLevel tank sensor system sends and split that out to separate dbus services. All SeeLevel information ends up in the same dBus object so each tank overwrites the sensor data for others. I have the system working with separate unix processes for each tank, but am wasting CPU cycles repeating the same data collection for each tank, then throwing it away if it is not for the right tank.