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.

Hi @cylex, Could you please update to the latest firmware? Version 1.7.0b1 introduced a number of fixes for the BLE code examples. You can check what version of firmware that your device is currently running by using the commands from the REPL import os os.uname() Thanks! Alex

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

@Shaun Thx so much Shaun, i will try this out. Will let you know how it goes. thx again, Jeroen

@YazIdo I think this may be an error associated with an accumulating number of open sockets. I got the same OSerror: 23 after running the MQTT example for the 8th time and beyond. A soft reset does not clear this, but powering on/off does clear it - and it works again, at least for the first 7 times. I fixed this problem by adding one line at the very end of the MQTT example. client.disconnect()

@mkbenon You're welcome, I just gave you some hints, glad that you manage yourself (best learning method). :o) Also please note that MQTT example script changes WLAN antenna mode for external (WLAN.EXT_ANT). If your LoPy setup has the external antenna - that's OK, but if not you should use default internal antenna (WLAN.INT_ANT).

@robert-hh @livius thank you so much!

@Cristi You can definitely do this, however you will need to write a simple protocol to talk to the different devices and associate an ID to each of them. Here's a link to some documentation that will help you get started - https://docs.pycom.io/pycom_esp32/pycom_esp32/tutorial/includes/lora-nano-gateway.html Let me know if you need any more support! Thanks, Alex

@daniel said in LoRaWAN MAC Battery Level: @bmarkus setting the battery level is not yet implemented, but this is a small change that we can have ready for the next release. Cheers, Daniel Sounds good, thanks :)

@robert-hh Thanks for the snippet. I can confirm that it seems to be a problem with my windows machine. I can now connect to the LoPy in STA mode via telnet and ftp (with my linux machine). Thanks for all the suggestions!

Today, With the release of "1.7.3.b1" version lora seems to communicate on OEM L01 modules after much hardware and software testing ...... regards

@gertjanvanhethof said in LoPy as LoRaWAN Basestation?: @bmarkus Yes that is correct. Only a LoRa Nano-Gateway is possible. This is not compliant with LoRaWAN. But for development and without a full compliant gateway this is ok. So you can develop LoRa Nodes which connects to your own Nano-Gateway. It is OK, but the original subject of the topic is "LoPy as LoraWAN Basestation?" Using LoRa radio layer you can make great things with other protocols, see http://www.waziup.eu/ as an example building network with SX127x devices and gateways only. But not LoraWAN.

@bucknall While one LoPy is sending and getting ACK, if I turn ON another LoPy it stops the communication (there is a collision), so, what can I do to avoid that collisions?

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

@jmarcelino Thanks for the quick reply. Yes, I'm in US915, and setting it to 3 does solve the issue. Now to figure out how to view what I'm sending from the LoPy to the mLinux Conduit gateway... :-/