@terrypacker said in Multiple devices on one transport:
But we also all creating many local devices in case you want to use them in different data sources.
I'm not sure what you meant here.
If it helps, I really only need a LocalDevice at all because that seems to be what's required by the library for communicating with RemoteDevices. I will be not be populating the shared or multiple LocalDevices with additional objects.
My original plan was to have one LocalDevice per network adapter that might be used. For most systems this would mean just one LocalDevice.
Is there any reason to have multiple LocalDevices (which I assume requires its own device number each) if I'm not going to be actually exposing any objects?
I'm essentially only interested in reading from or writing to other BACnet devices on the network.