Hi, I've replied on your other thread about the same topic, so this is just for reference for anyone that finds this in the future. Nanogateways are generally pretty outdated these days. 8 channel gateways are so much cheaper than they were a few years ago few people are using nanogateways. There was a big update to the TTN API around a year ago, and I think they removed the legacy packet format, and Pycom haven't updated to it as so few people are using them. Unfortunately this means it is unlikely you will get this working.

@robert-hh I changed P8 to P9 and it works great! Thank you so much!

@tomstoffen I just briefly read your message. The first thing is TTN have their own fair use policy, so when sending a message every 5 seconds you will deplete your air time very soon. Depending on your payload size, you should be fine if you send a message every 15 minutes (that's what I've tested), maybe even every 5 minutes should be OK. from this page: https://www.thethingsnetwork.org/docs/lorawan/duty-cycle.html Finally, on The Things Network’s public community network, we have a Fair Access Policy that limits the uplink airtime to 30 seconds per day (24 hours) per node and the downlink messages to 10 messages per day (24 hours) per node. If you use a private network, these limits do not apply, but you still have to be compliant with the governmental and LoRaWAN limits.

@suad_m5 As a LoPy (and hence a nano gateway) can only listen on one channel at a time, it is not LoRaWAN compliant, and only devices that are configured to use that single channel will be supported. It is not a generic gateway, it's just a tool to make quick tests without a real gateway around. This does not mean only LoPys can be used. If you can configure your device to only use the channel you configured on your nano gateway, it should work. This is however not possible on many devices.

@robert-hh Thanks ! I finally did it ! Thanks a lot

@jmarcelino Thank you that appears to be correct! I get my push and pull acks now.

@nojava4u if your gateway is connected, you should see in it's log lines like: [1194454.555] Pull ack [1194479.579] Push ack [1194479.579] Pull ack [1194504.623] Pull ack [1194529.418] Pull ack If you do not get that, then either your gateway cannot connect to the the TTN server (unlikely), or your gateway is not (properly) registered. For that, follow the instructions at: https://docs.pycom.io/chapter/tutorials/lora/lorawan-nano-gateway.html, starting with "Registering at TTN". Besides that, you will ever see messages being received by your gateway. I see them here too, at my nanogateway about once every 30 minutes. At my fully compliant gateway I'm receiving these every two minutes. Looking at the content, it looks like noise, even if I do not understand the statistics behind that. At a triggering preamble length of 40 bit and a data rate of 5670 bit/s, there should not be a random match more often than once every 3 years.

I follow the tutorial, checked config many times but my gateway seams to be still offline.. look stuck at the same place you where then posted this question. do you remember the things you've made different that made it work?

Having the same issue. Just getting "Pull hack" "Push hack", but gateway not showing up in TTN. Trying to follow the official tutorial, with no changes.

@Thosch42 This tip from Robert should fix your red light: https://forum.pycom.io/topic/1343/solved-lopy-bricked-red-led/3

@blackansible Try this modification in your nanogateway.py code: https://forum.pycom.io/post/8290

@berpast awesome I updated my project with your solution and it is working perfectly.

@jmarcelino OK I will try this in order to get more information when a crash is happening. To what I've seen I'm not the only one having similar issues.

you can find the code that is working right now for TTN US here on my GitHub I also made a guide on my blog