Okay seems like i fixed it or rather mitigated it. After a lot of testing out and recording my results i noticed that the EAGAIN Error did happen only about 30% of the time and that i just gut unlucky in assuming that it happened particularly more often using a different power source. Secondly, the EAGAIN Error only happened when the joining process took a long time. I assume that this does something that causes a faulty state in the Lopy4. This 30% Error chance could be reduced to about 10% by setting the Datarate to 5 during sending. s.setsockopt(socket.SOL_LORA, socket.SO_DR, 5) After this i also increased the Datarate during joining by using lora.join(activation=LoRa.OTAA, auth=(app_eui, app_key), timeout=0, dr=5) I havent done extensive testing after this, but the error has not occured ever since. Thank you again @jcaron!

That is some odd behaviour, can you contact me at support@pycom.io to sort this out?

@Gijs Honestly I think the Pycom documentation is seriously lacking in versioning. At the very least, new features / methods / options should be clearly marked as "introduced in version XXX". This would save a lot of time and energy for people trying things that are in the docs but are not in the version of the firmware they are currently running. Likewise, breaking changes should be documented.

@robert-hh Thanks alot for this quick answer!! The LED was active, even thought my inital code disabled the LED. It started after my first aproch updating the firmware and erasing the filesystem. Save booting the LoPY did not help (btw. nice button!). As metioned, only erasing the filesystem did not do it. What help in the end was checking the RESET boxes "CONFIG partiton" and "NVS partition" Thanks to all!

@robert-hh Thanks it works! :)

Another addition I want to make: I have been working on different frequency plans and found this: https://github.com/TheThingsNetwork/gateway-conf. I believe the frequency plan you want to use for the Pygate is in here as well. You can copy it directly and add the following items at the bottom: "gateway_ID": "XXXX", "keepalive_interval": 10, "stat_interval": 30, "push_timeout_ms": 100, "forward_crc_valid": true, "forward_crc_error": false, "forward_crc_disabled": false Let me know if that works better for you! Gijs

@robert-hh I ordered some A3144's and they are working excellent. Once again, thank you very much for your help!

@Gijs said in I2C Error & Duple COM Port Connection resume examples: Hi, A basic (flaw / feature) of COM ports is that you are not able to connect to it with multiple programs. When the Arduino software is connected to the port, you are not able to access it using the VScode editor. In VScode, you can prevent the Pymakr plugin from trying to connect / autoconnect by clicking all commands in the lower Pymakr toolbar, followed by the 'disconnect'. To solve your issue, you can try to access the fipy using another tool like putty or the Arduino serial terminal. Another way you can try to access the terminal output is through pybytes. Hope that solves your issue! Gijs Thanks for this - much appreciated!

Hello Gijs, thank you for the hint. The Gateway ist now running and needs only some individual additions :) [image: 1595346680996-60cd82d5-176c-4cc0-b1c7-00b7a269512e-image.png] Best regard Stefan

@Gijs said in Cannot login to pybytes web site: @LordLucan said in Cannot login to pybytes web site 8 ball pool: i, I've just created an account on the pybytes website. I can login to the site but cannot get very far because I cannot verify the account. I'm not receiving any emails Sorry to hear that, Were you able to solve the issue in the meantime? I know we are currently having issues with the signup procedure, where you do receive a confirmation email, but the link throws a 500 error. You are able to circumvent that by following the forgot password procedure. Let me know! Gijs That's good to know! Thank you!

@Gijs It seems that your code worked with mode=machin.WAKEUP_ANY_HIGH. I had to comment out the while loop, unless it would get stuck there every time!

After I followed that forum post I woud get another error. E (389) esp_image: image at 0x10000 has invalid magic byte

We got the same issue, while we can read the NFC tag content with any Android devices

@ahmadelmasri Do you know if the data consumed from the subscriber in the way you describe is encoded in a specialized binary format? I just tried to send a signal and using mosquitto_sub client from Paho I am getting non-readable data. I am calling mosquitto as follows: mosquitto_sub -v -h mqtt.pybytes.pycom.io -u <user> -P <token> -t 'u<token>'

@jg_spitfire That's the way TTN decided to send the downlink message in the RX2 node. The LoRa spec says: The RX2 receive window uses a fixed frequency and data rate. The default parameters are 869.525 MHz / DR0 (SF12, 125 kHz) Using SF9 is told by the TTN server to the node with the OTAA join accept message.

i'm having a dou't wether we will use lopy4 as a access factor or can we use this as a wifi hub that may be connect to computer after which can it's used as a usb dongle

@adi-canja USB-SDR is USB Software Defined Radio (a tool like this one https://www.passion-radio.fr/recepteurs-sdr/rtl-sdr-r820t2-248.html ) that allow you to view if something is send by your device (or not) around 868.130Mhz (Sigfox central frequency) That is worse than a spectrum analyser but it's cheaper :-) If something is sent correctly (2 second time on air, 500ms idle repated 3 time) then it's a coverage problem or an antenna problem, have you try another uFL cable+another antenna ? Have you try to go outdoor to do a tx test ? (Even if your network operator say you are in a good coverage area it's better to check it by yourself?) Have you any event on sigfox backend ?