Questions on Multi-Region ChirpStack v4 Deployment — AS923-1 and AS923-3 Configuration

Question

Hello everyone,

I’m currently new and am evaluating the feasibility of running ChirpStack v4 in a multi-region environment that supports both AS923-1 and AS923-3 simultaneously. I’d like to better understand the configuration requirements, potential risks, and recommended testing approach for such a setup.

I’ve outlined a few focused questions below to guide this discussion:

How does ChirpStack v4 handle region detection or auto-selection when both AS923-1 and AS923-3 are enabled in the same deployment, and what are the common issues or best practices to prevent devices from joining under the wrong regional parameters?
In multi-region (AS923-1 and AS923-3) setups, how does ChirpStack manage potential sub-band mismatches between devices and gateways, and are there known cases where overlapping frequencies cause uplink misrouting or packet loss?
When operating gateways in different AS923 sub-regions, is it recommended to manage them under one ChirpStack Gateway Bridge or separate configurations per region, and what configuration conflicts or region-mapping issues should be expected?
What is the most reliable approach to managing device profiles across AS923-1 and AS923-3 — separate profiles per region or shared configurations — and have there been compatibility issues affecting join procedures or downlink scheduling?
What practical test plan or validation checklist would you recommend to verify correct region handling, gateway operation, and end-to-end data flow when testing multi-region ChirpStack v4 setups across AS923-1 and AS923-3?

Orne Brocaar · Answer

When using ChirpStack, you should separate each region by its own MQTT topic-prefix. E.g. AS923-1 gateways would use as923/gateway/..., AS923-3 gateways would use as923_3/gateway/.... At the device-side, the correct region is configured in the device-profile.

In each region_XXXXX.toml configuration file, you make sure to use an unique MQTT topic-prefix, that matches your gateway configuration.

That way, when ChirpStack receives an uplink on as923_3/gateway/..., it knows it must be mapped to AS923-3.

In summary:

It detects by MQTT topic-prefix and it knows per device the correct region through the device-profile.
An uplink on an overlapping frequency will be discarded by ChirpStack because the region does not match the device region (device-profile).
As you need multiple MQTT topic-prefixes, each region needs a separate Gateway Bridge.
You need separate device-profiles per region.
I think the above should provide you with enough info to define a test-plan :)

Questions on Multi-Region ChirpStack v4 Deployment — AS923-1 and AS923-3 Configuration

1 Answers