@james-matthews Depends what you mean by "idle". In Pytrack-assisted deep sleep it should be somewhere in the range of 10-20 µA. Once you wake up the ESP32 and/or radios whatever the Pytrack uses is drowned in the consumption of those. Note that in my experience, keeping the accelerometer active for wake-on-fall/tap/movement already brings power draw to several hundred µA rather than a few dozen as expected (but that was on the Pysense, and I haven't much investigated the cause for the issue since). I expect the GPS to be a lot more power-hungry, though there are probably standby modes and the like.

hi @stefan85e, Short between G28 and 3V3 it's for safe-boot (booting without executing micropython scrips or loading previous OTA firmware). This is not required. Let's simplify and isolate problems. upload scripts with Atom Here make a simple print("hello") , no UART usage, yet; it should work usage of UART class. Here if you just want to output messages, print() method should be enough. UART 0 is already indirected to P0/P1, thru print(). The second UART (#1), it's for communicating with another device connected to the Expansion Board (not with the USB/FTDI chip).

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.