# Using AS920-923 (AS1) in Australia instead of AU915-928, failed to connect end-device to TTN v3 **URL:** \ **Category:** Uncategorized\ **Created:** [April 19, 2022, 10:45am UTC](https://www.thethingsnetwork.org/forum/t/using-as920-923-as1-in-australia-instead-of-au915-928-failed-to-connect-end-device-to-ttn-v3/56556 "2022-04-19T10:45:22Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![PreetiDangol](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/preetidangol/32/35697_2.png) [@PreetiDangol](https://www.thethingsnetwork.org/forum/u/PreetiDangol)\ **Post date:** [April 19, 2022, 10:45am UTC](https://www.thethingsnetwork.org/forum/t/using-as920-923-as1-in-australia-instead-of-au915-928-failed-to-connect-end-device-to-ttn-v3/56556/1 "2022-04-19T10:45:23Z")
Hi, I have been trying to connect the end device (Strega Emitter) to the TTN v3 (Community Edition) and I am from Australia. On TTN v3 side I am using: Frequency Plan: Asia 920-923 Mhz (used by TTN Australia). Not using Frequency Plan: AU915-928 because my end device doesn’t support it. I have been using private LoRaWAN, configuring R3000 LG LoRaWAN Gateway as UDP Packet Forwarder. I have registered the end device from the LoRaWAN Device Repository. With OTAA activation mode and end device config ADR: off, DR: 2, Class: A operation. It appears, the end device doesn’t send uplink messages continuously. It sends a few periodic uplink messages and again performs a join procedure. Join procedure is not reliable. I have been continuously in contact with my end node and gateway supplier to check if there are any issues from their end. I have been constantly doing firmware updates and checking gateway logs. So far it seems like issues are not on their end. I have added extra channels in the gateway and TTS following the AS920-923 (AS1) frequency plan as well. I have confirmed the RX1 delay in the end device. The end device rewrites the Rx1\_delay as the value set in the desired RX1 delay. I believe I have checked the possible points of bugs. Does anybody have any insight why the join procedure is not being reliable? Is it because of the frequency plan: Asia 920-923 Mhz (AS1) and should I select a different frequency plan in the TTN v3 console? Is the issue associated with gateway? I have gone through some posts of forum as well but couldn’t get exact answer to my query. 2022-04-18T14:00:00Z ---
**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\ **Post date:** [April 19, 2022, 1:15pm UTC](https://www.thethingsnetwork.org/forum/t/using-as920-923-as1-in-australia-instead-of-au915-928-failed-to-connect-end-device-to-ttn-v3/56556/2 "2022-04-19T13:15:10Z")
> [@PreetiDangol](#): > > I have been using private LoRaWAN > [@PreetiDangol](#): > > On TTN v3 side > [@PreetiDangol](#): > > Frequency Plan: Asia 920-923 Mhz (used by TTN Australia) > [@PreetiDangol](#): > > should I select a different frequency plan in the TTN v3 console Some confusion here - you state you are using a private instance - why the references to TTN(V3 & associated infrastructure/console)? If private you can set you own band decision - just make sure its supported and same at both GW, NS & end node and h/w supports. If using TTN then you need to follow the TTN AU freq plan(s) Much discussed here: > [@Can Australian users agree on using a single frequency plan?](https://www.thethingsnetwork.org/forum/t/can-australian-users-agree-on-using-a-single-frequency-plan/17660): > > Or… Australia TTN Users why not just use AU915? And especially & more recently here: > [@Future Strategies for AU915 and AS923 in Australia](https://www.thethingsnetwork.org/forum/t/future-strategies-for-au915-and-as923-in-australia/44218): > > Australia operates in the 915MHz ISM band and is somewhat unique in that both AU915 and AS923 are both allowed to operate. With TTN about to launch the V3 server in Australian it’s an opportune time for the TTN Australian community to review how both systems can best co-exist going forward. The launch of the V3 server is a Break-Point where we have an unique opportunity to: learn from history, review what has changed since the first introduction of LoraWan, and look forward at the next round… Last time I looked whilst both continue I thought there was a growing concensus for AU915 but I guess been out of touch lately on that. As you say if your device doesnt support then maybe only AU923 an option - suggest double check with vendor(s) as may just be a firmware/config option vs major h/w issue.