Hi, As you see, the Lopy1 has 4MB of flash memory. All our newer products sport larger Flash memory as the firmware size is ever increasing with new features. The problem is that the files you are trying to upload will fill up the Flash to its maximum. You can either install one of the older (smaller) firmwares using the firmware updater tool, or do something with the mpy files. That is a pretty advanced procedure where you build your own firmware, there is some discussion around it in multiple places, I link one here: https://forum.pycom.io/topic/2686/requesting-manual-flashing-procedure/5?_=1597228804264

sadly it's the same... rst:0x7 (TG0WDT_SYS_RESET),boot:0x37 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:1 load:0x3fff8020,len:8 load:0x3fff8028,len:2140 ho 0 tail 12 room 4 load:0x4009fa00,len:19760 entry 0x400a05bc

@tomstoffen I just briefly read your message. The first thing is TTN have their own fair use policy, so when sending a message every 5 seconds you will deplete your air time very soon. Depending on your payload size, you should be fine if you send a message every 15 minutes (that's what I've tested), maybe even every 5 minutes should be OK. from this page: https://www.thethingsnetwork.org/docs/lorawan/duty-cycle.html Finally, on The Things Network’s public community network, we have a Fair Access Policy that limits the uplink airtime to 30 seconds per day (24 hours) per node and the downlink messages to 10 messages per day (24 hours) per node. If you use a private network, these limits do not apply, but you still have to be compliant with the governmental and LoRaWAN limits.

@hayesey I am looking for a SIM card NB-IoT enabled in the UK. Could you let me know how you get your SIM card, or where I can find one please?

@Scott-Basgaard Well at the time I'm pretty sure you could download what was called the "pybytes" firmware and modify it accordingly (with the patch above). But this particular problem was sorted out in a later version of the built-in pybytes library, at least for me. FWIW, back then you had to set the dns server with socket.dnsserver() before you did from network import LTE.

@jirkakrepl today there is no data displayed the last samples are from 3 days ago. if i have a pull size of 20 it says no recent data. the best thing for me with those line graphs is to select the time scale and it plots al the data points in between.

@dnear1 We deployed the fix now

Ive pointed the correct people at this thread. one of them should be able to answer soon :)

Heya, There is currently no system in place to export data. but one should be ready soon. Paul

@weingami Hi, I deployed hotfix and tested wifi, sigfox and lora connections. I correctly received the data. We need to test more things and there are a few more bugs, that we know and we're about to fix now.

@cirobr glad that got it fixed for you. Not sure if it was a case of overload. More just having time to develop rate limiting that never existed previously.

@protean Hi, when you click on "get location button", Device scans the wifi networks around and sends the result to Pybytes. Pybytes is using Google location API to figure out and the location.

@belal-chaudhary Can you confirm is your wireless network the standard wep/wpa-2 setup or does it use fancy certificate based authentication? Nothing strange going on Re Network proxy's like Eduroam/mobile providers are likely to have?

Just got around to getting back to this issue - thanks so much Xykon, problem solved! robert-hh: I did do erase during update yep, a few times, but eventually was solved with advice from the post above :)

Hi @klaus, Currently, you can only configure one WiFi network, and save multiple in the Pybytes console.

@jirkakrepl Thanks. I had worked this out.