I'm trying to understand how BACnet objects, specifically in my case Analog Inputs are addressed by consuming applications.
BACnet4J has a helper function which creates a new object id based on the type of object and the next available id. Ok, so let's say I have a analog input that I want to expose through BACnet4J. Each time my application is run, does that same analog input instance need to map to the same BACnet object id? Or do BACnet monitor applications form dependencies on other object properties?
To boil it all down, what information needs to remain immutable when my application is invoked to map the same analog input to a BACnet object so I behave like a traditional BACnet device to upstream consumers.