I can confirm now that updating via USB/Serial is definitely possible... if you are adventurous you can try the command I posted here otherwise it might be worth to wait a few more days for pycom to release an official upgrade package.

@abilio Ah. Did not realise it was writeable :) It works fine now ! Thanks.

Ah, this piece of information was missing. The version with the print P10 was from the wipy - the loopy is either less powerful, or not yet optimized.

@bartvrancken you are right, the information delivered by Pymakr isn't enlighting, as it does only say "join" and "leave".

@matamune Thank you very much for your detailed post. It will be really helpful to improve the tool.

i can confirm the issue seems to be resolved

This is really starting to get ridiculous with PyCom ... deploying a much awaiting firmware update with ABP and then not providing any kind of documentation updates To help my fellow coders out, i figured out some items: lora = LoRa(mode=LoRa.LORAWAN, sf=7, tx_power=14) lora.BW_125KHZ lora.CODING_4_5 Now what the ABP auth tuple should be i haven't figured out. But note again that PyCom did not even fix the TTN OTAA issues

After looking at the ESP-idf files, RTC may confusingly be an acronym for "real time coprocessor". If this is true, how does the lopy keep time?

@daniel, I got it working using the code example that @DarkHawk posted here. I only added a line wlan.ifconfig(config=('192.168.2.5', '255.255.255.0', '192.168.2.1', '8.8.8.8')) before nets = plan.scan(). When I compare the few lines of code I cannot really see the difference. I'm not sure, but the only logical explanation would be a typo in the ssid or password. Of course I confirmed them several times... Only issue left is the DNS but that you know about already.

@LonTech thanks, let's see how it will be supported by the machine module.

@peter thx this also worked for me now, the other example from the lopy documentation somehow did not work for me, so thx for sharing.

@peter That is correct. At the moment, Pymakr detects when your device is not up to date with the latest version (only when connected to the internet), then redirects you to download the update manually. We are currently working on integrating the full update feature inside Pymark as well, so expect this in one of te next updates.

Hi @bmarkus, thanks for your question This is on the roadmap but there is no definite date for it yet.

Hi j_c_meyer, Not yet on our webshop, but maybe soon. We'll keep you posted. Cheers, Daniel

Thanks indeed! Latest information is that it might be gateway related because some other people are experiencing the same issue. Now patiently awaiting the ABP capable firmware and docs :-)

@LoneTech nice, should be easy to use this directly in the auth setup so one doesn't have to hardcode the DevEUI

@bmarkus Hi, The regulator on the board can handle up to 1.2A but as the LoPy chips also need to be powered it is good if you do not exceed 500mA

Hi leogaggl, I see... I'll check with our forum guru. We have to avoid spamming... Let's see how to improve it and make it easier for new users. We'll get back to you shortly. Cheers, Daniel