v2.2.5 has been released to production. During this sprint the team also launched Helium Roaming Services. LoRaWAN network providers can learn more about how to leverage Helium coverage here.
The ability to export and import complete Organizations was added as well as a number of backend community reported issues. Users can migrate their Organization from a Console instance hosted by one provider to another or to their own hosted version of Console. Note Data Credits are not transferable and will not be migrated. For more information check here.
Important: The Multiple Packet feature has been updated to accurately reflect the amount specified by user configuration regardless if they’re uplinks or initial joins.
Full list of this sprint’s implemented features and fixes:
(Note: a closed issue does not mean the team took action, for example the issue could have been a duplicate or no longer relevant).
Open source users
Check the readme for instructions on how to use prebuilt Console images.
Important: the seed nodes in the
.env-router template need to be updated. Check the
.env-router template file, and copy the value of the
ROUTER_SEED_NODES env var to your local
New open source users should follow Option 1 listed in the readme and use
docker-compose-quay.yamlas the template for their docker-compose file.
Existing open source users can update their existing docker-compose file and replace the lines for just the “console” section with the updated lines in the latest
docker-compose-quay.yamlfile. If something does not work, simply revert your changes back to the
docker-compose-quay.yamlfile an issue here.
Database migrations will still happen automatically when using the hosted Console image.
Additional technical documentation.
The team’s focus in the coming weeks (usual disclaimers apply):
- Microsoft Azure IoT Central integration
- Scaling out roaming services
- Preferred Hotspot selection