Configuring the gateway parameters in console.thethingsnetwork.org is not as important as it appears. Here in Australia the ‘thethings.meshed.com.au’ appears to apply arbitrary filtering on our gateways. It is the only router in this region (AU_915). so from time to time when this filtering is an issue we will swap to another router. We also don’t use thethings.meshed.com.au for applications much. because integrations are not as configurable, and we have to use a ‘special’ dashboard.
So the issue here is the “frequency plan” setting seems to only be for statistics. As is the “Router” configuration. It can be set to anything, it does not appear to mean much. When set to anything you can forward packets in anywhere. and by the Things Networks own documentation. A unregistered gateway will still work. but the packets it received will be stamped untrusted.
So back to the problem. When you use ttn.opennetworkinfrastructure.org as your router. All downlink packets are enqueued against the channel plan for EU_868. When this happens the gateways here in Australia to discards the transmission. Even though the gateways frequency plan is defined correctly in the dashboard. This lets me to believe that value is only for statistics.
60c5a8fffe74d372 >< 172.20.1.55 PUSH 207 :: {"rxpk":[{"tmst":1623936916,"chan":2,"rfch":0,"freq":917.200000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":8.5,"rssi":-70,"size":23,"data":"AETpAdB+1bNwEQFVAAAAAAGu+9RhEKQ="}]} ::
thethingsnetwork <> 52.169.76.203 PULL_RESP 213 :: {"imme":false,"tmst":1622032348,"freq":869.525,"rfch":0,"powe":27,"modu":"LORA","datr":"SF12BW125","codr":"4/5","ipol":true,"size":33,"ncrc":true,"data":"IAzxv/1dO/oMXS5B/Ke4zhfnBTYMQDboBpq0FuO2fphB"}} ::The only way to overcome this problem appears to use the correct router for the region. Which for AU_915 is the infrastructure hosted by Meshed. And I guess we will have to put up with the arbitrary filtering.
Working OTAA compatible TTN Routers
| au915.thethings.meshed.com.au | |
| router.au.thethings.network | |
| router.us.thethings.network | Make sure the gateway has min/max TX freq set. Does work-around meshed for OTAA |
| Router DNS Address | Region | Region |
| thethings.meshed.com.au | AUS | |
| router.au.thethings.network | AUS | |
| au915.thethings.meshed.com.au | AU915 915-298 | AUS/NZ |
| as923.thethings.meshed.com.au | AS923 – “AS1” 922-923 | AUS |
https://www.thethingsnetwork.org/country/australia/
| Router DNS Address | Region | Country |
| router.eu.thethings.network | EU433 and EU863-870 | EU |
| router.us.thethings.network | US902-928 | US |
| router.cn.thethings.network | CN470-510 and CN779-787 | China |
| router.as.thethings.network | AS923 | Southeast Asia |
| router.as1.thethings.network | AS920-923 “AS1” | Southeast Asia |
| router.as2.thethings.network | AS923-925 “AS2” | Southeast Asia |
| router.kr.thethings.network | KR920-923 | Korea |
| router.jp.thethings.network | AS923-925 | Japan |
| router.au.thethings.network | AU915-928 | Australia |
| ttn.opennetworkinfrastructure.org | EU433 and EU863-870 | Swizerland |
So ensure you set your router DNS entry to one that corresponds to the table above. Otherwise the things network appears to tell the gateway to TX on an out-of-band channel. and a misconfiguration on the end of the operator could mean transmitting on licensed spectrum. and potentially prosecution. Despite every other effort being made to be compliant.
I expect the only reason why the US router works is because the downlink channels match both AU_915 and US_915
thescobber 