I noticed there just seem to be no way of configuring a gateway region via the chirpstack UI so that one can spread out gateways coverage to multiple sub-regions (i.e: us915_0, us915_1, etc.) for environments with high device density or crowded frequencies, even though it appears to be possible according to this documentation page.
Indeed, the only way I found to have different sub-regions is to use the correct mqtt prefix by the mqtt-forwarder, which happens to match the region_config_id as configured in chirpstack. However, it kind of defeats the possibility to reconfigure the concentratord channel planes remotely via gateway region assignment.
In V3, it seems that such a thing was made possible through the use of gateway profiles, which I assume it was then possible to reconfigure a concentratord channel plans by switching gateway profiles (I can only assume this was possible since i’ve never tried V3).
Is there a reason why gateway profiles was removed from V4, thus making the gateway region assignment rely 100% on the gateway local configuration rather than a global configuration via chirpstack? Is there something I am missing here?
Is it possible to make sub-regions assignment possible entirely remotely, without having to change the gateway local configuration (making the mqtt-forwarder publish on a specific pre-defined mqtt topic prefix)?
Best regards,