Hello ChirpStack team,
We have a client deployment where a single property (tenant) contains gateways operating in different LoRaWAN regions.
Scenario:
The property is primarily US915
Some gateways at the same property support AS923
Each gateway supports only one region
The requirement is to retain the existing frequency plan and add the additional frequency per site, without impacting existing gateways or devices
We understand that:
A single gateway can operate in only one region
A single tenant/property can support multiple regions, as long as each gateway is bound to the correct region configuration
Questions:
Is the recommended approach to maintain separate region configuration files (e.g., region_us915_x.toml and region_as923_x.toml) and assign the appropriate region_id per gateway?
Are there any known constraints or caveats when running US915 and AS923 gateways under the same tenant (e.g., downlink scheduling, ADR behavior, or gateway-bridge considerations)?
For Basic Station deployments, is region selection best handled entirely via the gateway configuration, or are there additional ChirpStack-side settings recommended?
Is there any supported way (or future roadmap) for handling dual-frequency gateways, or is per-gateway single-region configuration the only valid approach?
We want to ensure this configuration aligns with ChirpStack best practices and avoids issues such as CRC failures, excessive downlink retries, or join instability.
Any guidance or references to official documentation would be appreciated.
Thanks in advance.
