micropython-lib VS log2ram

This is the current version of my code (excuse the mess it's become..), adapted from https://github.com/micropython/micropython-lib/blob/7128d423c2e7c0309ac17a1e6ba873b909b24fcc/micropython/bluetooth/aioble/examples/temp_client.py

STM32WB55 running MicroPython sounds like it'd suit. Should be fine for the power budget and aioble gives you one of the best BLE libraries on any platform. Documentation is generally good, though BLE is a little light (with some good examples and an active Discord channel!).

Pico (non-W) doesn't have upip (or mip, as that replaces upip now) or urequests because it doesn't have internet access required by them. In theory, you can download urequests from: https://github.com/micropython/micropython-lib/blob/master/python-ecosys/urequests/urequests.py or build your own MP image with it enabled. I don't know if it'll work as you want it to but it's worth a try.

Using SD-card on ESP8266 was more challenging. upip.install('sdcard') does not work.

But ChatGPT truly helped and suggested I find it in Github.

https://github.com/micropython/micropython-lib/blob/master/m...

I don't think there's a mip list command or something like that. So your best bet is to look at the subdirectories in https://github.com/micropython/micropython-lib for a list of installable packages.

Do give it another try if you get a chance; I'd be genuinely interested in hearing about your experience. Be sure to check out the awesome list and micropython-lib if you're looking to fill gaps. There are still many holes but they're rapidly being filled in.

Reducing logging, logging to ram and writing to the sdcard once a day helps longevity a lot, especially with quality sd cards.

99% of the time it's the verbose logging of application servers that is the culprit of sdcard failures.

https://github.com/azlux/log2ram

I always use this: https://github.com/azlux/log2ram

If you've got other issues then it's quite likely that lots of small writes from logging and similar has worn out the SD card, mounting the SD card as read only or installing log2ram could prevent it happening to another SD card.

> writing permanent its log files and swap partition

If this is the problem, the solutions are no swap and log2ram https://github.com/azlux/log2ram

I also noticed that Armbian logs to a ramdisk. I didn't investigate the implementation and if its contents survive a reboot.

The only real problems for me are that the SD card will eventually fail no matter what (I mean, much sooner than a SDD or HDD) and that there are basically no Pis at sale at a reasonable price. As a platform it is nearly dead.

For Pi-hole, I have an Rpi Zero with $10 Usb-to-Ethernet adapter, SD-card barely written (with Log2Ram) to avoid wear. Running about 3 years now almost unattended (besides security updates).

In addition to the other helpful suggestions you’ve received, look into using Log2Ram. It does what it sounds like, puts log writes in ram and then writes them to disk on a slower cadence that doesn’t work your SD card that much.

https://github.com/azlux/log2ram

Log files are a bit trickier. I want these to stick around between reboots, so just storing them on a ramdisk wouldn't really work. Thankfully, log2ram solves this problem. Written primarily for Raspberry Pi machines, it works fine on x86-64 laptops. This stores /var/log in RAM but will sync the contents to disk from time to time, ideal for our needs.