I’m looking for practical examples of when to add “Applications” in ChirpStack.
[The documentation for v4 explains applications as “a collection of devices with the same purpose / of the same type. Think of a weather station collecting data at different locations for example.”]
I’m wondering if someone could provide additional examples. The strongest reason I see to have multiple applications is when different Integrations are needed for a collection of Devices. Since I only have one Integration at this time, I’m trying to figure out if all of my Devices should really be in one Application, or what other reasons I would have for separating them.
The only other reason besides having different integrations I would consider using multiple applications for is to organize devices better if you plan to use the grpc api often, as many of the API calls are application specific. For example I am designing a third party portal to add/view devices from chirpstack and in that case it is easiest to have an application per client, so then when they click to view their devices it can be done with a single listDevices call and no further sorting on the portal side.
Keep in mind we can only do this because the only integration we are using is the MQTT integration which is global to all applications. If we had to set up the integration for each new client/application, it would no longer be practical and we would do them all in one application.