Region issue - remove region by default

I am testing a small balloon that floats in the stratosphere, with some children. My LORA device can work with ranges of 868 to 930 hmz

I have a problem, I do not know where the balloon is, and I do not know if the Chirpstack configuration can be made to admit all the frequency ranges, without having to select one by default. For example, if the balloon is near Korea or Japan, I don’t know how to make Chirpstack admit both frequencies instead of only one.

Any idea?
thank you in advance

Chirpstack should be able to accept frequencies from any region enabled in the Chirpstack.toml file as long as the corresponding regional configuration file (i.e eu868.toml) is properly configured. Although you may need to test, or perhaps someone else can speak to, whether the device has to rejoin whenever it switches frequencies (off gut I would say it would need to reconnect to let Chirpstack and the device “agree” on some of the regional parameters for that area).

Another important factor is what is receiving the LoRa signals from the balloon? Do you have a network of gateways spread out to receive the messages across multiple borders? Or maybe you will be following it with a gateway type device of your own?

As whatever is receiving the balloon’s messages will obviously need to be listening to the correct bands, but it also needs to forward the correct MQTT topic prefix.

1 Like

I know that Chirpstack accepts frequencies of any region but what I want to know is whether it is possible that by default I listen and admit any frequency, without having to change the region or frequency of the device.

As far as I understand, modifying the configurations files should do the trick

The gateway send a json that include the frequency, then chirpstack checks if that frequency is included in the frequency file, if not, it drop the packet

It may require some testing, but it should be possible.

Notice that what you are asking is not an usual deployment of a LoRaWAN device network, I don’t believe that the protocol was designed to support moving end-devices.

nevertheless, as Liam said, I think that there are other technical problems that are, probably, harder to solve, as the end-device move from a region to another, the gateway and the end-device should be able to change their frequencies

As Marcos said, the solution here is probably to create a new region file that would accept any of the frequencies the balloon might travel in.

1 Like

Thank you for your answers!