MicroPython Forum (Archive)

Very nice, thanks!

danicampora wrote: The RTC time is kept across power saving modes, so even after a DEEPSLEEP reset it will keep the correct time.

Thanks for the tip. I updated my boot.py to only set the RTC if the reset reason was POWER_ON or HARD_RESET.

I hacked up a module that gets time from the timezonedb.com, then makes it easy to sync your WiPy's real-time clock (RTC) to it. This is not that accurate because it makes no attempt to account for network latencies, but +/- a few seconds is fine for many applications. Note, this module has a horrib...

I tested sending through Yahoo's smtp server and it worked like a charm. >>> import smtplib >>> efrom = 'me@yahoo.com' >>> eto = 'you@gmail.com' >>> header = 'To: {} \nFrom: {} \nSubject: Email from my WiPy\n\n'.format(efrom, eto) >>> msg = header + 'Hi,\nThis is the WiPy emailing ;-)\n' >>> smtpser...

This is working well for me on 1.1.0. My boot.py is now happy and working well over telnet even when I want to Ctl-D to reset the board. Here it is, for people's reference: import machine import os import time from network import WLAN BAUD = 2457600 # fast when directly connected on NooElec PL2303 S...

+1 for a way to get the current wifi object. I was hoping to setup exactly what you suggested where you don't drop the connection across soft resets.