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
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.
The text was updated successfully, but these errors were encountered:
The
AS923
regions (AS923-1
andAS923JP
) 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 eitherAS923-1
orAS923JP
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 astation
build per SKU.The text was updated successfully, but these errors were encountered: