You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
My customer wants to deploy this solution to Brazil.
The Frequency plan is AU915-928 and is not yet supported by this starter kit.
Describe the solution you'd like
Add the support for AU915-928 Frequency plan.
Describe alternatives you've considered
We are using separated LoRaWAN concentrator that support this frequency plan.
Can we jus add the router config for AU915-928 frequency plan to the Concentrator twin ?
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Thank you for the feature request. As discussed orally, we will try to have a spike branch on this feature soon supporting only basic functionality (upstream messages). Formal integration with the Starterkit will be harder as we do not have the hardware required to test physically those frequency ranges.
If you have some option where we could run some end to end test in places that supports this frequency plan that would tremendously help with the quality and implementation we can deliver.
We have a poc of AU implementation on this feature branch. Based on our tests, it looks it works for upstream/downstream and join requests. Please keep in mind, this is PoC state and do not meet the quality of the rest of the kit. If you find issues please let us know!
Is your feature request related to a problem? Please describe.
My customer wants to deploy this solution to Brazil.
The Frequency plan is AU915-928 and is not yet supported by this starter kit.
Describe the solution you'd like
Add the support for AU915-928 Frequency plan.
Describe alternatives you've considered
We are using separated LoRaWAN concentrator that support this frequency plan.
Can we jus add the router config for AU915-928 frequency plan to the Concentrator twin ?
Additional context
N/A
The text was updated successfully, but these errors were encountered: