Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider allowing nocca in production builds #180

Open
adriansmares opened this issue May 31, 2023 · 0 comments
Open

Consider allowing nocca in production builds #180

adriansmares opened this issue May 31, 2023 · 0 comments
Milestone

Comments

@adriansmares
Copy link

adriansmares commented May 31, 2023

The AS923 regions (AS923-1 and AS923JP) enable CCA even if the gateway does not have the required CCA hardware. This is problematic as in Australia the AS923 region can also be used, and these gateways sometimes lack CCA hardware. Currently such gateways stay in a reconnection loop as they fail to initialize CCA.

Historically our LNS used the 'wrong' region (AS923). As this wasn't a supported region, it wouldn't activate CCA, but downlink would work. Since version 2.0.6 a 'correct' region name is required. Using either AS923-1 or AS923JP forces CCA to be enabled, and in turn reduces these CCA-incapable gateways to bricks.

In my view the LNS is aware of the CCA limitations of a particular gateway, and should be trusted to forcefully enable or disable CCA. Another option is for the gateway vendors to have station builds which explicitly avoid enabling CCA, but I don't think this is ideal as it forces them to have a station build per SKU.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants