@HenroRitchie If you have a single ESP32, machine.deepsleep() is sufficient. In combination with the Pycom expansion boards go_to_sleep() ensures proper deactivation of the respective sensors and set-up of the interrupt sources. It then switches off the power to ESP32. In summary, that results in a very low standby current - with the above side effect. Since the PIC on the expansion board also can control the EN (Reset) pin of the ESP32, it may pull that low before switching off the power. That may be a better solution than calling machine.deepsleep(), because it switches the ESP32 off immediately, and the PIC stays powered and therefore in a defined state during deepsleep.
Did you try with another USB cable?
Are you sure that you're using USB data cable not just charging USB cable?
Is there any dev file like /dev/tty.usb* after you connect PyTrack? (use Teminal to check that out)
Try on Windows machine maybe.
@dispatj Try the examples given... If it doesn't work, come back with details of what exactly you did (the code you used, as well as what you use to receive those beacons), what you expected, and what you actually got (including errors, logs, screenshots...).
It's 2019 now. In fact we're more than half way through 2019, and still it looks like the FiPy is useless for cellular in the UK.
In fact even though Things Mobile and Hologram offer 'IoT LTE sims', neither support NB-Iot or CAT-M1 LTE. So basically the FiPy can't be used some 18 months later.
I've just ordered a SIM7600E-H module from AliExpress instead :(