@jcaron Just to clarify something from our use case: In our experience using the same frame counter is not a problem with our private instance of a TTN server. How we do it now is that we restore from nvram and save it immediately after. This is so we don't need to think about it again. I understand ADR will not work for us here, but it is still a lot easier and spares us from some logic with exception handling and still keeping the session and avoiding a new join. We also do not need to receive responses. We are basically using it as a makeshift abp connection, as our setup and back-end does not support abp. Having a function that restores the session without erasing it would actually be quite nice for our case. This, as far as I understand it from TTN, does also work for the public TTN network, but I have not confirmed this. Is there some way of getting all connection details down in a file so we could save it to an SD card instead? This would actually allow us to quite efficiently create devises and manage the things for our system.

@jcaron I have two antennas which perform more robust. One, which looks similar, but is 22 cm long (18 cm up from the hinge). That one shows a nice current profile, peak in the middel of the "active" section and going down to almost zero towards bot sides. The other is a home-brew ground plane antenna, along a recipe from the ttn forum, which also work pretty well. Both are not very sensitive to touching the xxPy and moving. Compared to these the PyCom antenna performs between 6dB and 16 dB, depending on placement and touching. I have my xxPY built into a aluminium box with the antenna connector at the shorter side. The PyCom antenna shows some current at the connector, which explains the sensitivity to touching. Picture: GP antenna on FiPy in a box, built from a SMA connector an 1.5 mm wire. Tip wire it 82mm, the radial are 86 mm.

Hi, Yes, it seems to be the same issue. When can I expect a fix for this? Any work around? any other api to check new data arrival at UART? Regards Sameer

@robert-hh I finally got a new probe, and I was able to confirm on an oscilloscope that it is no longer sending the 'Ping' after awhile.

@sameerchouksey Did you try this example https://docs.pycom.io/chapter/tutorials/lora/lorawan-otaa.html ? Especially: # make the socket blocking # (waits for the data to be sent and for the 2 receive windows to expire) s.setblocking(True) # send some data s.send(bytes([0x01, 0x02, 0x03])) # make the socket non-blocking # (because if there's no data received it will block forever...) s.setblocking(False) # get any data received (if any...) data = s.recv(64) print(data) Also try to upgrade FW to 1.17.x (lorawan have changed to 1.0.2 spec).

@smbunn It's still a single step to change the LoRa region but now you can either fix it in firmware configuration, or use the region= parameter. I recommend always the region parameter going forward. The firmware method was added more so existing code without the region parameter wouldn't break.

How do your calcs compare with m=lora.stats() print('TxTime(ms)',m[7])

@jmarcelino We have already added the file mqtt.py, and main.py is blank Thank you

Thanks @seb and @jmarcelino for testing purposes what is the cheapest way to setup an indoor gateway? @jmarcelino I've just added sigfox to home-assistant btw https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/sensor/sigfox.py

@grtvhecke said in How to know to which LoRa Nano-Gateway the LoPy Connects: do you need to check in code the device and send an ack or not depending to this ID Yes

@sameerchouksey do you know if the network is sending MAC commands to the device? If so there could be acknowledgements to send back, which would reduce the max available packet size. Not sure if those ACKs have priority over the payload though.

@obladio I'm not sure if the Raspberry Pi code works in the current form, it's been a while since I tried it - almost as long as that code has been sitting there unchanged (1 1/2 years) but maybe it does. I do know downlinks are not supported at all in that code which is what TTN is really annoyed about - in the past gateways without downlinks were blocked from participating in TTN https://www.thethingsnetwork.org/forum/t/resolved-some-single-channel-gateways-stopped-working/6529 and https://www.thethingsnetwork.org/forum/t/the-future-of-single-channel-gateways/6590/72 I'd recommend using a single channel gateway which supports downlinks, such as the LoPy with nano-gateway code or some of of the suggestions on that 2nd thread I linked. If you want to use the Raspberry Pi code you have I guess you have to do some tests to understand if it's currently working.

@imasd I was noisy an so I drove over to the HLK place. And indeed, at that spot there is a good sensitive antenna on the top of a 5 story building. The antenna looked like the TaoGlas Barracuda, pretty long. And other short wave antennas. So the person seems to know what she/he is doing.

@robert-hh I want to remove the time.sleep and just focus on checking if the packed is sent before sending more so I can max out the send and recv part...

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

@Lonefish Do you actually have a valid IP connection between the FiPy and the server? The topic of the subject talks about LoRa, but you can't perform HTTP requests over LoRa, you need to go through a gateway for that.