- Newest
- Most votes
- Most comments
Thanks guys, the root issue was actually that I was using AWS CLI 1.2 and needed to upgrade to V2. After that, I did get the issue with string vs integer and resolved. My gateway is now beaconing.
Hi! Is this on an existing Gateway or are you getting this error while creating a new Gateway? If you are trying to enable beaconing on an existing Gateway, please note that this functionality is only available when creating a new Gateway. If the latter, please post the exact command you are issuing to create the Gateway and beaconing parameters.
Cheers.
Hi. The beacon.json you've pasted produces the following error:
Parameter validation failed:
Invalid type for parameter LoRaWAN.Beaconing.Frequencies[0], value: 923300000, type: <class 'str'>, valid types: <class 'int'>
Invalid type for parameter LoRaWAN.Beaconing.Frequencies[1], value: 923900000, type: <class 'str'>, valid types: <class 'int'>
If you remove the quotes around the frequencies, your gateway should be created. No problem for me at least, and no sign of the error your original question mentioned.
you can see it doesn't appear to receive any bcning router_config, as I get no log messages regarding it
To see the router_config message, you need to enable XDEBUG logging in station.conf. Example log message:
2024-05-07 00:54:45.421 [AIO:XDEB] [4|WS] < {"msgtype":"router_config","NetID":null,"JoinEUI":null,"region":"AU915","hwspec":"sx1301/1","freq_range":[915000000,928000000],"DRs":[[12,125,0],[11,125,0],[10,125,0],[9,125,0],[8,125,0],[7,125,0],[8,500,0],[-1,0,0],[12,500,1],[11,500,1],[10,500,1],[9,500,1],[8,500,0],[7,500,1],[-1,0,0],[-1,0,0]],"sx1301_conf":[{"radio_0":{"enable":true,"freq":917200000},"radio_1":{"enable":true,"freq":918200000},"chan_FSK":{"enable":false},"chan_Lora_std":{"enable":false,"r
2024-05-07 00:54:45.421 [AIO:XDEB] [4|WS] . adio":0,"if":300000,"bandwidth":500000,"spread_factor":8},"chan_multiSF_0":{"enable":true,"radio":0,"if":-400000},"chan_multiSF_1":{"enable":true,"radio":0,"if":-200000},"chan_multiSF_2":{"enable":true,"radio":0,"if":0},"chan_multiSF_3":{"enable":true,"radio":0,"if":200000},"chan_multiSF_4":{"enable":true,"radio":0,"if":400000},"chan_multiSF_5":{"enable":true,"radio":1,"if":-400000},"chan_multiSF_6":{"enable":true,"radio":1,"if":-200000},"chan_multiSF_7":{"e
2024-05-07 00:54:45.421 [AIO:XDEB] [4|WS] . nable":true,"radio":1,"if":0}}],"protocol":0,"regionid":0,"bcning":{"DR":8,"layout":[3,9,19],"freqs":[923300000,923900000,924500000,925100000,925700000,926300000,926900000,927500000]}}
Thanks Greg! I was just coming back to comment on this same thing. I have reported the issue with the documentation and it should be addressed soon.
Cheers!
Relevant content
- asked 4 years ago
- asked a year ago
- asked 2 years ago
{ "Description": "My LoRaWAN gateway", "LoRaWAN": { "Beaconing": { "DataRate": 8, "Frequencies": ["923300000","923900000"] }, "GatewayEui": "a1b2c3d4567890ab", "JoinEuiFilters": [ [ "a272bd6167b90000", "a272bd6167b900ff" ] ], "NetIdFilters": ["000000", "000001"], "RfRegion": "US915", "SubBands": [2] }
}
And the command:
aws iotwireless create-wireless-gateway --name "Beaconing Gateway" --cli-input-json file://beacon.json