# NB-IoT device connecting using UDP **URL:** \ **Category:** Devices and Connectors\ **Created:** [January 22, 2022, 5:04am UTC](https://community.tago.io/t/nb-iot-device-connecting-using-udp/1006 "2022-01-22T05:04:17Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![system](https://yyz2.discourse-cdn.com/flex034/user_avatar/community.tago.io/system/32/24_2.png) [@system](https://community.tago.io/u/system)\ **Post date:** [January 22, 2022, 5:04am UTC](https://community.tago.io/t/nb-iot-device-connecting-using-udp/1006/1 "2022-01-22T05:04:17Z")
@Rob Young Hi All - great support so far in this community, thanks! So I have a NB device and have it successfully using MQTT to upload to [Tago.io](http://Tago.io). The problem I have is the MQTT connection seems very unreliable with regular failures and often consecutive failures prompting me to reset the device. As is, I’m not confident to deploy these devices into the field. I’m wondering if I can connect using the device default of UDP? Or maybe coAP? My understanding is I’d need a network and connector (which I’ve created) but I don’t understand how I configure the device’s firmware to connect. Device doco is here: [https://www.dragino.com/downloads/downloads/NB-IoT/NSE01/NSE01%20NB-IoT%20Soil%20Moisture%20%26%20EC%20Sensor%20User%20Manual\_V1.0.0.pdf](https://www.dragino.com/downloads/downloads/NB-IoT/NSE01/NSE01%20NB-IoT%20Soil%20Moisture%20%26%20EC%20Sensor%20User%20Manual_V1.0.0.pdf) The MQTT firmware settings allowed me to enter a token but UDP only asks for UDP Server and Port. What should I enter here? Thanks Rob ---
**Author:** ![system](https://yyz2.discourse-cdn.com/flex034/user_avatar/community.tago.io/system/32/24_2.png) [@system](https://community.tago.io/u/system)\ **Post date:** [January 22, 2022, 5:04am UTC](https://community.tago.io/t/nb-iot-device-connecting-using-udp/1006/2 "2022-01-22T05:04:17Z")
@Vitor Lima In order to use an UDP server with TagoIO, you would need to make and host your own UDP server. Here is a guide on how to create one using Node.JS: [How to create your own Network to integrate with TagoIO - How to - TagoIO Community](https://community.tago.io/t/how-to-create-your-own-network-to-integrate-with-tagoio/429) ---
**Author:** ![system](https://yyz2.discourse-cdn.com/flex034/user_avatar/community.tago.io/system/32/24_2.png) [@system](https://community.tago.io/u/system)\ **Post date:** [January 22, 2022, 5:04am UTC](https://community.tago.io/t/nb-iot-device-connecting-using-udp/1006/3 "2022-01-22T05:04:18Z")
@Rob Young Thanks Vitor. Seems like another rabbit hole of tech I’m probably going to struggle with lol. If I step back, is there a reason qhy the MQTT connection is so unreliable? Here’s a typical output from my terminal when the device wakes up to send data: _NSE01 NB-IOT Soil Moisture & EC Sensor_ _Image Version: v1.0.0_ _NB-IoT Stack : D-BC95-002_ _Protocol in Used: MQTT_ _[8316]NBIOT has responded._ _[9354]Echo mode turned off successfully._ _[10442]The IMEI number is:868411056759764._ _[11523]The IMSI number is:505013535346199._ _[13672]Turn on PSM mode successfully._ _Currently set frequency band:28_ _[15806]Signal Strength:13_ _[20540]_ **Upload start:0** \_\_ _[25576]remaining battery =3231 mv_ _HEX:fe 03 06 00 d2 06 7b 00 10 ad ce_ _[26766]water\_soil:2.10_ _[26793]temp\_soil:16.59_ _[26820]conduct\_soil:16_ _[37997]Failed to open the MQTT client network_ _[41548]Close ACK not received…_ _[44084]Close ACK not received…_ _[44120]Failed to close the port_ _[45156]_ **End of upload** \_\_ Sometimes it’s fine for several connections after a power cycle then it seems to fail repeatedly. Other times a full power cycle makes no difference. I don’t believe it’s an issue with the device or the network connection, more that the Tago server isn’t responding for some reason. Thanks Rob ---
**Author:** ![system](https://yyz2.discourse-cdn.com/flex034/user_avatar/community.tago.io/system/32/24_2.png) [@system](https://community.tago.io/u/system)\ **Post date:** [January 22, 2022, 5:04am UTC](https://community.tago.io/t/nb-iot-device-connecting-using-udp/1006/4 "2022-01-22T05:04:19Z")
@Vitor Lima Hi Rob, It seems we already solved that by ticket system, as it seems that you resetting the device fixed the issue, let me know if you have additional questions. ---
**Author:** ![plamrock](https://avatars.discourse-cdn.com/v4/letter/p/f07891/32.png) [@plamrock](https://community.tago.io/u/plamrock)\ **Post date:** [April 16, 2023, 12:49am UTC](https://community.tago.io/t/nb-iot-device-connecting-using-udp/1006/5 "2023-04-16T00:49:47Z")
@Rob Young I realise this is old but can you shed any light on your settings in the NSE01? I am trying to replicate using the NBSN95a wihch is effectively the same unit but am getting nowhere [AT+SERVADDR=mqtt.tago.io](http://AT+SERVADDR=mqtt.tago.io),1883 AT+CLIENT=??? AT+UNAME=Token AT+PWD= AT+PUBTOPIC=??? AT+SUBTOPIC=??? ---
**Author:** ![reiry01](https://avatars.discourse-cdn.com/v4/letter/r/bb73d2/32.png) [@reiry01](https://community.tago.io/u/reiry01)\ **Post date:** [December 5, 2024, 6:08pm UTC](https://community.tago.io/t/nb-iot-device-connecting-using-udp/1006/6 "2024-12-05T18:08:33Z")
same as me i well lost Tago, ist Schrott wenns kein echtes UDP oder coup mqtt geht einfach nicht forget Tago sorry