As the other topic mentions, you can use UART to connect between the STM32 and Wipy controllers. I don't think we have any ready made examples, but the code should not be very complicated. Something like below should do #init UART while True: if uart.any(): input = uart.read() uart.write(output)

@Roberto-Duca yes, you need to use only the frequency chosen on the gateway. Note that the network may (and probably will) send it’s on list of channels and frequencies after the join, so ideally you should configure the network to only send that single frequency (don’t know if you can do that on TTN), or you will have to reset the list of channels after the join (or rather before each transmit). Also I believe the nano-gateway only listen on a single DR, so likewise, you should restrict your node to that single DR (both for join and subsequent traffic). Remember that a nano-gateway is just there for a bit of testing, it’s by far not a real LoRaWAN-compliant gateway.

@GregS Caution: I now believe that the only reason that code works for me is because it uses DR0 for the join requests, which is in violation of the regional parameters for Australia, which say to use DR2. I.e - I am too far away from a gateway. As I have said in another thread, the proper way of joining using OTAA is actually working for me, when get closer. (I don't know WHY that code uses DR0, but I don't really care - it's not code I will be using any more)

Doh! I think I know what's going on - I am simply too far away from a gateway, and the only way I can get a connection is to violate the minimum data rate spec for join requests (which is 2 for Australia).

@Vinicius-Pinhatari-campos What version of the firmware are you using? How are you powering the LoPy4? Problems on boot are often related to a power source which can't provide enough current for the peaks which happen during boot or wake up.

Just btw, I got the Module to Module example to work by changing the socket calls in the Node A code to blocking - looks like it's a timing issue.

@Simon-RAPP Wake-up from Deep Sleep is a power on cycle. After that, you have to re-instantiate all devices.

@d-alvrzx , thank you for your prompt response. The board isn't cheap, so I'm always afraid of damaging something...

@jcaron I've read updated documentation in https://lora-alliance.org/wp-content/uploads/2020/11/RP_2-1.0.2.pdf [image: 1629706152807-0a0d62fa-27fd-4836-8fa2-196b24eb1904-image.png] , it says AS923 have dwelltime limitation. So I think uplinkdwelltime value keep 1. is it right?

Hi assia, did you solve the problem ?

@KenM said in urequest.post gives me an OSError: Network card not available: api/v1/ thanks lot .it is working...

@g0hww Sounds like a nice setup & you're right, if I change the ip address in Atom settings I can find the lopy on the home wifi network, so much nicer than wifi direct via the ad hoc.

@hamza-charhour how is it not working? What do you expect it to do, and what does it actually do? What are you trying to connect with? How? What happens?

@Gijs Thank you for the reply. I've done a lot of studying but networking is not my strong suit. (That's why I went with pycom development boards to take care of networking) If I set up a stand alone lora mesh network with WiFi and LoRa, then disable the WiFi, how is the LoRa network authentication done? In a Pymesh network, is the connection to the network raw and the OTAA just an encryption for the message? I was hoping to connect up networks like a typical WiFi network with a password. Is this possible on a LoRa network? If it is, how can I do it? Do I have it all wrong and the authentication is similar to WiFi? Thanks.

@d-alvrzx the ESP32 has various sleep modes with various possibilities for wake up sources. The lowest power modes are indeed quite limited by design. IIRC the Pycom firmware uses ext1 wake up. You’ll find details of the different wake up sources of the ESP32 in the ESP IDF docs: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/sleep_modes.html

@jcaron Thanks for reply. I'm using a private network with Chirpstack and Laird gateway. Yes I know not to use Class C when in deepsleep. Our network is not used in winter (vineyard irrigation) and during this down time we want to sleep our nodes to save battery drain as we have low solar radiation in winter also. We are therefore not sending/receiving messages when in deepsleep. We have been successfully running Class C with 60 nodes for over 2 years, our only issue has been battery life which we are now trying to address. I will try and capture gateway log and post back here. Thanks

@livius Obviously this is only an option if you want to use a device which you already have purchased. Otherwise it is easier to take any plain vanilla ESP32 board. You can also use the LoRa chip of the LoPy. You just have to tell from the source code which pins are used for the communication to the chip.

Option to turn off the radio and have various features?