Separating sensors by Installation with Service Profile

Viewed 40

We are currently using Chirpstack v3 but are soon going to upgrade to Chirpstack v4. Some Gateways should only be allowed to talk to certain sensors and it seems like this is possible by enabling Private Gateways and Configuring the Installation, that contains these sensors, with the same service profile.

Is Service-profile and Private gateways still a feature in Chirpstack v4?
Is there a better way to do this or a best practice we could refer to?
Can these Sensors still talk to other gateways or are they also locked to the gateways activated with Private Gateways in the same service profile.

1 Answers

The service-profile has gone, but you can make gateways private per ChirpStack v4 tenant, such that devices of Tenant A can only be reached by the gateways of Tenant A...

Thank you very much for the information!

I'm guessing it's the other way around as well? That Gateways of tenant A can only be reached by devices of Tenant A?

Correct. Downlinks will only go to the gateways of Tenant A. There is also an option to only make downlinks private. That way, a gateway can provide coverage to all tenants, but downlinks will sent through gateways of the same tenant.