@gabrielapb You could try the following: save the current timestamp to NVS before going to sleep on wake-up: retrieve the saved timestamp from NVS retrieve the "remaining sleep" from the Pysense using pysense.get_sleep_remaining current timestamp is approximately saved + sleep interval - remaining Note this won't get you a very precise time (as it doesn't take into account boot time, and I'm not sure of the accuracy of the Pysense clock), and the offset to the real time will increase with the number of sleep periods, but it's helpful to have at least of rough idea of the time until you can get the actual time through other means. The alternative is to use the module's deep sleep rather than the Pysense's deep sleep, but that may not be possible depending on your actual use case.

Seems like this is related to WIFI in some way. When turning off WIFI (pycom.wifi_on_boot(False)) problem goes away. I am not using WIFI in any way, but maybe powerlines or WIFI accesspoint makes my W01 panic? This is the application I have been running during the test: from machine import Pin import utime LED.append(Pin('P3', mode=Pin.OUT)) while True: LED.value(1) utime.sleep_ms(100) LED.value(0) utime.sleep_ms(100) I havent been able to decode the core dumps, can I send them to someone for investigation? This forum didn´t allow me to post it here.

I’ve experienced similar issues when using MySQL databases. What you’re experiencing can most likely be linked to some kind of server problem. That’s what it’s boiling down to most of the time. One of my clients was having a real bad time with his database and I identified the faulty server as being the culprit behind most of the issues. Once we switched him up to a cloud server all of the connectivity problems were gone. Also, you could try using a service like Aiven for MySQL. With that you can connect appliances to your databases with ease. I hope I could help you, and you figure out the problems.

Hey. Could you try reflashing the latest firmware. Including using the checkbox to wipe flash. And reupload and try the code again. Thanks

@paul-thornton The timing is rather critical. Couldn't you extend the time window for updating to let's say 30s?

@paul-thornton Just did. :)

@SiMoS-IoT Thanks. Given the state of Pycom documentation and the large quantities we are going to need we have decided to build our own solution, so the power feed issue will go away. I really like the approach to power Pycom have, but the fact we can't get any documentation on how it functions, other than a few system calls, means we can't take it into production. I'll probably still keep using it, but only for interests sake.

An effort to bring all documentation inline is ongoing at the moment and things should be clearer going forward. We are aware of a few conflicting pieces of information that need clearing up. Ill pass along the feedback about schematics being made available to the public.

@martinnn Full ACK.

HI Mellow, I would be very interested to find how you did this.

@rskoniec On the gnd pin is a ground connected from a ldr, on the 3 volt pin is the ldr connected and the analog signal is converted to a digital signal to pin 3. The Pysense isn`t connected to the external board with the ldr when I was trying to upload the code. Now is there only ten headers soldered to the Pysense. I used a pair of female headers for the gnd and 3 volt pins and maile headers for the sensor pins

@manel Hi, have you tried doing a power cycle? If it still doesn't work, try updating the firmware and checking the "Erase flash file system" box.

You can use an FTP client (like FileZilla) to see and transfer files on the flash drive of your device via a static wifi (e.g. have your device and laptop connected to your home wifi) or by using your device as an access point (connect your laptop to the device wifi). https://docs.pycom.io/gettingstarted/programming/ftp

@robert-hh but i dont see the mqtt integration in my console ?

@sslupsky AFAIK, the enable pin is not accessible.

Hi @martinnn, Thanks for noticing, I've forwarded it to the team and we'll work on that. These shortcuts work in Atom, but they clash with VSCode's shortcuts.

@StijnK setup_sleep() is a function contained in the pycoproc.py library, and according to its code the maximum value is 2^24 - 1. So the maximum sleep time you could set is 16777215 seconds, which is about 4660 hours (more than six months). Here is the code of pycoproc.py in Github: https://github.com/pycom/pycom-libraries/blob/f848adcfb937e7b7bbc5f78db95840fa26dabe11/pybytes/pysense/lib/pycoproc.py#L24