Adjust region based on blockchain #193
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Appears to save some space
madninja
force-pushed
the
madninja/chain_region
branch
from
d988c49
to
7974549
Compare
Co-authored-by: Jeff Grunewald <jgrunewald@helium.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This sets the gateway to follow the asserted lorawan region by following the regions through the associated gateway-service.
The helium-gateway cli adds a new
regioninfo argument which will fetch the currently set region for the gateway.Note
The region setting in
settings.tomlwill be used as the initial setting until a region update is received from the chain. This means that if the hotspot is never location asserted on chain the region will remain set to the settings.toml value.The info region command will return the default setting if no chain setting is asserted or found