@rolandvs said in Is the time in the RTC preserved after hard reset w/o power down?: If true it makes the use of the RTC sort of worthless in situations where you want to keep time with an attached battery without the possibility to use Wi-Fi to NTP your time like with LoPy or SiPy... It doesn't solve the original issue, but you can update time without network connection using GPS receiver, e.g. on the pytrack extension board.

@chriseb Which firmware version are you using? The latest release 1.17.3.b1 seems pretty stable.

You need to close the file as soon as the write is complete. If the unit shuts down while the file is open there's a good chance to corrupt the flash. This will erase the flash when it reboots.

@jmarcelino Great, then work is being done :) Thanks for the reply!

@ledbelly2142 Not yet, I did read somewhere here that the battery voltage is connected to ADC pin 16 so it should be possible. Hoping for an example that can report it as a Battery percentage. I'd like to have the following Topic structure on my LoPy's MQTT topic: lopy/ip lopy/probes/1 ... lopy/probes/4 lopy/battery lopy/rgb lopy/oled/1 ... lopy/oled/4 lopy/ble Cant think of any more yet. Still not sure how i'll go with my plan of 4x SPI Type K temp probes and 4x 128x32 OLEDs as they are SPI as well and require more than just a CS per screen. Reporting on the Battery topic would be things like percentage when it hits internal warning levels.. but with the view to using deep sleep it would probably report on wake up. Also a notification when its charging if at all possible would be nice. I changed the IP topic and paylod to this btw client.publish(topic="lopy/ip", msg=wifiaddress) And on the far end I use Node-red to append to the front: "LoPy Booted with IP: " + msg.payload; *node red function code - not micropython And send the string to Pushover for a push notification on my phone. I've also mapped the on board button to do a machine.reset() so I can carry it around, hit reset then get a notification on my phone if it connects to WiFi (good for range testing).

This listing (**********) has been removed, or this item isn't available. Please check that you've entered the correct item number Listings that have ended 90 or more days ago won't be available for viewing. Remove this?

@ozeta hiiiii friends your problem like your application is not stop run again continuously i mean right in their one solution you have taken one jumper wire put it on your board 3v3 and G28 then orange led is blinking than you remove your jumper wire. here current execute method is stopped (main.py) .

The issue was posted on github.

Question 1: that is correct, the payload is still encrypted. Question 2: this has been discussed before here. I would like to refer you to Pierre's blog here.

@robert-hh, the method function very well, thank you

@sjp770 SPI is a bus system. In a star configuration you can connect several slave devices to one master, as long as the (capacitive) load is not exceeded. But you need a CS for each device. If D/C is needed, you may be able to share it. If devices have active feedback pins like an Alarm pin, that has to be connected too to a separate I/O.

Hi @sslupsky, Which version did you install? This specific issue has been fixed (at least I can't reproduce it and there have been numerous updates in the past year). We know about an issue in 1.26.1, which caused some issues with Pymakr. You can follow this post for more info.

@bigboy20769 I see at least two options: call the respective init methods in a try block call os.uname and check the type of module

@jcaron The issue has been worked out and it works quite well now! Thanks a lot!

Have just got a lopy and a pytrack myself and fully agree that this would be an instant buy for me, though covering the gps antenna would probably be a bad thing.

@jmarcelino I solved it. I have used an old firmware version on my gateway. I guess I missed this one module when updating all others. After updating I can set the TX power up to 20 dBm without getting any errors. Thanks for your help! Kind regards Pascal

@jalperin This works to restore RTC after pysense go-to-sleep. py.setup_sleep(sleepsec) pycom.nvs_set('gtsSec',sleepsec) pycom.nvs_set('ttSec',time.time()) py.go_to_sleep() rtc = RTC() ttSec = pycom.nvs_get('ttSec') # time.time() previous value if ttSec: gtsSec = pycom.nvs_get('gtsSec') # go to sleep seconds # reset clock to prior saved time plus length of sleep (both in seconds) rtc.init(time.gmtime( ttSec + gtsSec )) else: # Initialize your wifi, then rtc.ntp_sync("pool.ntp.org") # rtc.ntp_sync("23.239.26.89") while not rtc.synced(): time.sleep(1) Since I can't distinguish awakening from reset, I am currently setting ttSec manually before running code. pycom.nvs_set('ttSec',0)