# Cannot connect new The Things Kickstarter Gateway to V3

**URL:** <https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066>\
**Category:** TTKG - The Things Kickstarter Gateway\
**Created:** [June 23, 2021, 9:45pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066 "2021-06-23T21:45:43Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![rbrightwell](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/rbrightwell/32/35697_2.png) [@rbrightwell](https://www.thethingsnetwork.org/forum/u/rbrightwell)\
**Post date:** [June 23, 2021, 9:45pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/1 "2021-06-23T21:45:44Z")

</div>

Hello all,

This is my first post in the community, so bear with me and please let me know if my etiquette doesn’t meet community guidelines. I’m also new to the world of LoRa and cloud services in general, so this has been a bit of an uphill journey for me.

I’m trying to set up The Things Kickstarter Gateway (Note: NOT a TTIG) to a The Things Stack Community Edition-hosted console (NAM1). I’ve followed the steps outlined at [The Things Kickstarter Gateway Registration](https://www.thethingsindustries.com/docs/gateways/thethingskickstartergateway/) several (read: dozens) of times, but have been unsuccessful in setting up my gateway on the console. I am able to connect to the WiFi, but am unable to activate past that. In my most successful runs, I cycle between the WiFi setup stage (one LED solid, one slowly blinking) and the activation stage (two LEDs solid, one slowly blinking).

The only thing I can see that I didn’t quite follow in the instructions was the addition of a tenant ID after my gateway ID. However, anytime I try to put this into the configuration page, I get an error (see below).  
 ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/b/1/b1abd9dd5f7d7d1336a4290d20acb7e92611e993.png)  
 ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/e/1/e1ed381c17c3908e72b839c45274c868a2a15e9a.png)

My gateway is brand new and out of the box. I also downloaded the most recent firmware to make sure it was up to the 1.0.8 standard. I’ve also tried a couple different console setups and WiFi networks and have met the same problems each time. Alls to say I don’t think this is a hardware or console issue; I believe it is purely a configuration problem. However, I am finding no help in the documentation understanding what I am doing wrong. Can anyone in the community help me figure this out?

I’ve attached a copy of the UART debug I received during one of my configurations with areas of interest highlighted. This run was done with the credentials “swri-div-14-gnat-asset-tracker” and the network ID “[https://nam1.cloud.thethings.network/](https://nam1.cloud.thethings.network/)” over an Ethernet connection. Any help will be greatly appreciated!

[Attempts at Registration Forum.pdf](https://www.thethingsnetwork.org/forum/uploads/short-url/vytkiVdHDZCvO4fVbLjUFUzVr2y.pdf) (234.1 KB)

---

<div class="post-metadata">

**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\
**Post date:** [June 23, 2021, 11:16pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/2 "2021-06-23T23:16:54Z")

</div>

Check [Want to move my TTN Gateway to V3 - #9 by aberenyi](https://www.thethingsnetwork.org/forum/t/want-to-move-my-ttn-gateway-to-v3/48429/9) for instructions that worked for another forum user.

---

<div class="post-metadata">

**Author:** ![rbrightwell](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/rbrightwell/32/35697_2.png) [@rbrightwell](https://www.thethingsnetwork.org/forum/u/rbrightwell)\
**Post date:** [June 24, 2021, 1:46pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/3 "2021-06-24T13:46:32Z")

</div>

Thanks for the response. These were the instructions I was trying to follow. However, any combinations of my gateway key followed by an “@ttn” results in the “unexpected data sent to gateway” error I received above. I have tried using the tenant ID with two different API keys as well.

---

<div class="post-metadata">

**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\
**Post date:** [June 24, 2021, 1:52pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/4 "2021-06-24T13:52:32Z")

</div>

Please try with a smaller (less characters) gateway id. You might well be running into buffer size limits concerning the name used.

---

<div class="post-metadata">

**Author:** ![rbrightwell](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/rbrightwell/32/35697_2.png) [@rbrightwell](https://www.thethingsnetwork.org/forum/u/rbrightwell)\
**Post date:** [June 24, 2021, 4:19pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/5 "2021-06-24T16:19:17Z")

</div>

All,

Just wanted to post my resolution for anyone else with similar issues. There were several steps I had to take to find a solution to my problem.

1. I did in fact need a tenant ID (@ttn) for my gateway.
2. My original gateway ID was too long, and this was indeed why I got the “unexpected error” issue.

However, this was not the end of my problems. I was still getting the frustrating looping problem and rejected LoRa packets. I did finally manage to find some links tracing this back to a mechanical issue. This led to resolution #3:

1. Push my LoRa chip firmly into its socket – and pushed it even harder when that didn’t work

– to FINALLY get a working router.

Thank you for all the help Kersing and other members of the community for having the answers that support and the setup page did not. So much for a five minute activation.

---

<div class="post-metadata">

**Author:** ![jeroen2](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeroen2/32/44252_2.png) [@jeroen2](https://www.thethingsnetwork.org/forum/u/jeroen2)\
**Post date:** [September 1, 2021, 8:48am UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/6 "2021-09-01T08:48:05Z")

</div>

Am trying to migrate my old Kickerstarter GW to TTNv3. With the experience as you summed up in this thread I was hoping that it would go smooth. However it seems the gw is not connected

- The 3rd LED keeps blinking slowly (which means activating) - restarting the gw does not help
- Have Wiffi and ethernet connected
- Info ([http://192.168.1.68/info](http://192.168.1.68/info)) states the following

![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/8/e/8e58fa4a19187ba16fa2cb6715f188d9b79fec01.png)

![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/8/2/82ad147969de10e0a13b1d977c5f13edb647d04d.png)

So I am puzzled where the problem is?

---

<div class="post-metadata">

**Author:** ![jeroen2](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeroen2/32/44252_2.png) [@jeroen2](https://www.thethingsnetwork.org/forum/u/jeroen2)\
**Post date:** [September 1, 2021, 11:43am UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/7 "2021-09-01T11:43:47Z")

</div>

Finally the kickstarter gateway connects to the network (when I do not configure WiFi it ‘activates’).  
Now the 4 LEDs all light up.

However I see no LoRa traffic in the v3 console (while there is traffic flowing thru the air).  
Seems like a hw issues to me

---

<div class="post-metadata">

**Author:** ![bertrik](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/bertrik/32/35697_2.png) [@bertrik](https://www.thethingsnetwork.org/forum/u/bertrik)\
**Post date:** [September 1, 2021, 12:00pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/8 "2021-09-01T12:00:14Z")

</div>

I think I have a similar problem, everything looks good on the gateway info page, but no traffic at all showing on the TTN v3 console. Shows as connected but up/down counters are 0/0, there is a node nearby:  
 ![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/0/8/0828bfbe447f4074e652a0ce9f6ec777fd5bb92f.png)

---

<div class="post-metadata">

**Author:** ![jeroen2](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeroen2/32/44252_2.png) [@jeroen2](https://www.thethingsnetwork.org/forum/u/jeroen2)\
**Post date:** [September 1, 2021, 1:43pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/9 "2021-09-01T13:43:30Z")

</div>

Yes that is the same as I am seeing ([http://192.168.1.69/info](http://192.168.1.69/info))

![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/6/c/6cabba333876c82c9b01ea31257af47faf95ed65.png)

While in the console no traffic is seen

![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/8/d/8dc7b3310fcbccbe35b76245555c6708325dca70.png)

---

<div class="post-metadata">

**Author:** ![wolfp](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/wolfp/32/45304_2.png) [@wolfp](https://www.thethingsnetwork.org/forum/u/wolfp)\
**Post date:** [September 1, 2021, 1:53pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/10 "2021-09-01T13:53:19Z")

</div>

imho if the connection between the gateway and the TTS CE-server gets lost for more than 60(?) seconds this counter is reset to zero.  
Does your gateway send status messages every 30 seconds?  
With one of my gateways I observed that if the WLAN-connection gets lost even for a short time this counter is reset to zero.

---

<div class="post-metadata">

**Author:** ![jeroen2](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeroen2/32/44252_2.png) [@jeroen2](https://www.thethingsnetwork.org/forum/u/jeroen2)\
**Post date:** [September 1, 2021, 3:54pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/11 "2021-09-01T15:54:30Z")

</div>

After factory reset of the kickstarter GW I configured as described in lnks above.  
So I do not know it is is send every 30 secs. Never had issues on v2 so I am puzzled what the reason is 🙂

---

<div class="post-metadata">

**Author:** ![bertrik](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/bertrik/32/35697_2.png) [@bertrik](https://www.thethingsnetwork.org/forum/u/bertrik)\
**Post date:** [September 1, 2021, 4:39pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/12 "2021-09-01T16:39:59Z")

</div>

Well, at least the screenshot now shows “Gateway Card: 868MHz”, so it’s detected, and “config: correct” and “Broker connection: true”. This wasn’t the case in your earlier screenshot, so I think you’re heading in the right direction.

---

<div class="post-metadata">

**Author:** ![jeroen2](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeroen2/32/44252_2.png) [@jeroen2](https://www.thethingsnetwork.org/forum/u/jeroen2)\
**Post date:** [September 1, 2021, 5:15pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/13 "2021-09-01T17:15:17Z")

</div>

Yes @bertrik - it started working when I did not configure WiFi / to me it seems a weird problem 🙂

---

<div class="post-metadata">

**Author:** ![bertrik](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/bertrik/32/35697_2.png) [@bertrik](https://www.thethingsnetwork.org/forum/u/bertrik)\
**Post date:** [September 1, 2021, 6:30pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/14 "2021-09-01T18:30:49Z")

</div>

What a mess, I feel sorry for people who bought this gateway, and would not recommend it to anyone.

Like @jeroen2 I’m running from one weird problem into another:

- The screen shot at [The Things Kickstarter Gateway | The Things Stack for LoRaWAN](https://www.thethingsindustries.com/docs/gateways/thethingskickstartergateway/) shows old/misleading info, is not applicable for TTS CE
- On my best attempt, according to the internal info page of the gateway, things look OK: LoRa card detected, LoRa packets received, gateway claims to be connected to a network and is able to connect to the gateway server. However no data on the console and no evidence it is passing traffic from nearby nodes.
- However, after having enabled wifi, the “gateway card” status goes to “ND” (not detected?), no more packets coming in

Not sure anymore what to do, hopefully someone from TheThingsIndustries can look into this.

---

<div class="post-metadata">

**Author:** ![bertrik](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/bertrik/32/35697_2.png) [@bertrik](https://www.thethingsnetwork.org/forum/u/bertrik)\
**Post date:** [September 2, 2021, 11:38pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/15 "2021-09-02T23:38:47Z")

</div>

I finally got it working. I tried various things.  
The thing that finally made it work is to remove the “@ttn” from the gateway id, just enter the plain gateway id in as shown in the TTS CE console. This is in direct contrast to an earlier post from june 24 in this thread.

---

<div class="post-metadata">

**Author:** ![jeroen2](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeroen2/32/44252_2.png) [@jeroen2](https://www.thethingsnetwork.org/forum/u/jeroen2)\
**Post date:** [September 3, 2021, 1:00pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/16 "2021-09-03T13:00:27Z")

</div>

Thanks. That also worked for me. So do not use the @ttn behind the Gateway Id:  
(at least for the kickstarter gateway)

I am still not able to configure WiFi - \> after doing so it does not connect to ttnv3 anymore

---

<div class="post-metadata">

**Author:** ![tcottle0](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/tcottle0/32/40078_2.png) [@tcottle0](https://www.thethingsnetwork.org/forum/u/tcottle0)\
**Post date:** [October 24, 2021, 5:04pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/17 "2021-10-24T17:04:24Z")

</div>

So I thought I would leave this as a bread crumb for the next person trying to move their kickstarter gateway to V3

I started yesterday morning moving my gateway from V2 to V3. I read the background info and figured it would be a 15 min task. 6 hours later I was ready to chuck it into the trash bin. The GW is using 1.08 firmware, is US model (TTN-001-915-1.0) and is located in the US.

The issue is that it is stuck at the 3rd LED fast blink

I’ve read and reread all of the forum posts, reread the docs, reset the GW (full serial flash) numerous times, added and deleted gateway (using unique IDs each times), created and deleted API keys but no change

This morning I attached a HW serial monitor to inspect the GW messages. This line looks suspicious

CONF: Could not parse URL ‘nam1.cloud.thethings.network/’, fallback on default

I can ping [https://nam1.cloud.thethings.network/](https://nam1.cloud.thethings.network/) so it isn’t a DNS issue. In the end it was a missing “HTTPS://” in the on the setup page

![ttn setup](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/6/1/614f4a86af87bdeffa1f00198858bc19ed1d6e7c.png)

The source of the error was I was copying and pasting the link from the address setup page ([Addresses | The Things Stack for LoRaWAN](https://www.thethingsindustries.com/docs/getting-started/ttn/addresses/)). On that page all URLs are preceeded with https:// except the #$%^$&^% API endpoint links

![2](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/a/a/aac4d150f57aaab5e3b42b848b9eb40056787445.png)

Once that was fixed the gateway finally connected

---

<div class="post-metadata">

**Author:** ![cnoork](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/cnoork/32/45348_2.png) [@cnoork](https://www.thethingsnetwork.org/forum/u/cnoork)\
**Post date:** [October 25, 2021, 7:51pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/18 "2021-10-25T19:51:04Z")

</div>

I think all my configuration are now correct with all the info which is given here but still it isn’t working. It looks like the gateway card is not detected if I look to the info page. I have reinserted the card but this did not the trick. It is currently do a reboot after an uptime from 99 seconds. Has anyone a suggestion how to troubleshoot this?

![image](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/f/1/f13ef2fb5834e3ad6e8893c78660a5dd16d2f1db.png)

---

<div class="post-metadata">

**Author:** ![cnoork](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/cnoork/32/45348_2.png) [@cnoork](https://www.thethingsnetwork.org/forum/u/cnoork)\
**Post date:** [October 26, 2021, 6:27pm UTC](https://www.thethingsnetwork.org/forum/t/cannot-connect-new-the-things-kickstarter-gateway-to-v3/49066/19 "2021-10-26T18:27:48Z")

</div>

Here also the UART output…

> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
> \* The Things Network \*  
> \* G A T E W A Y \*  
> \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
> Firmware name: AmazingAckermann, type: 0, version: 1.0.8, commit: 846da98b, timestamp: 1574945235  
> Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298  
> Build time: Nov 28 2019 12:48:18  
> Reboot reason: 0x10  
> BOOT: (persisted info) 6F 72 72 65 01 03 DB 59 ED 3E FF 5D 48 F4 58 E5
> 
> WIFI: Entering state 0  
> WIFI: Entering SCAN state 0
> 
> MAIN: Initialisation complete  
> LORA: Changing state from 0 to 0
> 
> MAIN: Leaving state 0  
> MAIN: Entering state 1  
> FLASH: Magic bytes found: wifi config present  
> FLASH: Magic bytes found: activation data present  
> FLASH: Magic bytes not found: no stored FOTA data present  
> FLASH: Loading Firmware Data  
> CNFG: (Firmware HASH (sha256)) F7 4B 6E FA 9E 91 AE E4 2C 62 8E D2 50 1B 43 3C C0 69 36 41 AA 52 86 F7 67 0F 44 7A 6E FD 25 F2  
> FLASH: Loading WiFi Data  
> CNFG: WiFi SSID: Things-Gateway-001EC03AEF18  
> CNFG: WiFi key: \*\*\*  
> CNFG: WiFi conn\_type: 4  
> CNFG: WiFi sec\_type: 4  
> FLASH: Loading Activation Data  
> CNFG: Gateway ID: iotutrneude  
> CNFG: Gateway Key: \*\*\*  
> CNFG: Account Server URL: [https://eu1.cloud.thethings.network](https://eu1.cloud.thethings.network)  
> CNFG: Locked: true  
> CNFG: Locked first time: false
> 
> MAIN: Leaving state 1  
> MAIN: Entering state 2  
> INET: State change to 0  
> LORA: Initialisation complete  
> LORA: Changing state from 0 to 1  
> WIFI: Entering state 1  
> ETH: IP Address: 0.0.0.0  
> WIFI: Entering state 2  
> WIFI: Disabling modules  
> Head magic match void: trying to free an already freed block, ignore  
> WIFI: Entering state 3  
> WIFI: Enabling modules for server  
> WIFI: Entering state 6
> 
> \>WIFI: IP Address: 192.168.84.1  
> SNTP: State change from 0 to 1  
> INET: Gateway has Ethernet  
> INET: State change to 2  
> INET: Connected to a network, waiting for DHCP lease, checking validity with ping  
> CB: ETH: IP Address: 192.168.10.152  
> SNTP: State change from 1 to 2  
> SNTP: State change from 2 to 3  
> SNTP: State change from 3 to 4  
> INET: State change to 3  
> INET: Ping probe  
> INET: Error sending probe on WiFi  
> INET: Ping response from PIC32INT, set as default  
> INET: State change to 4  
> SNTP: State change from 4 to 5  
> SNTP: State change from 5 to 6  
> SNTP: State change from 6 to 7  
> INET: State change to 5
> 
> MAIN: Leaving state 2  
> MAIN: Entering state 3
> 
> CNFG: Load online user config state change to 4  
> HTTP: Close active socket 0  
> HTTP: Starting connection  
> LORA: Wait init complete, waiting for application.  
> LORA: Changing state from 1 to 2  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3815  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3620  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3601  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3601  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (188KB), free: 156KB
> 
> SCAN LENGHT: 0
> 
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3601  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3601  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB
> 
> SCAN LENGHT: 0
> 
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3601  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3589  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3589  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3589  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3589  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB  
> MON: SYS Stack size: 3959  
> MON: TCPIP Stack size: 3589  
> MON: APP Stack size: 4290  
> MON: LoRa Stack size: 3909  
> MON: heap usage: 183KB (190KB), free: 156KB
