š¢ Rilasciata #DietPi 9.15 che introduce diverse novitĆ tra cui:
* Script di Aggiornamento a #Debian #Trixie
* Supporto #OrangePi 3 non-LTS
* Gestione Migliorata dei Pacchetti #Unbound
* Supporto#GRUB Esteso
* Client #Moonlight Sbloccato
š qui la release note completa: https://dietpi.com/docs/releases/v9_15/

Last chance to express your voice about 32-bit #ARM on #openSUSE? Take the survey now https://survey.opensuse.org #ARMv7 #RaspberryPi #BeagleBone
A Dual-Screen Cyberdeck To Rule Them All - We like cyberdecks here at Hackaday, and in our time weāve brought you some pretty... - https://hackaday.com/2025/07/30/a-dual-screen-cyberdeck-to-rule-them-all/ #raspberrypi #cyberdecks #cyberdeck
#cyberdeck #DIY #raspberrypi #hacking
Okay, Bravo. This is fucking excellent. Well done.
I had the idea that writing to the SDCard for 250ms every few seconds was a bad idea
That is how long it took for SQLite to insert 1 row in 4 databases, roughly 80ms times 4
(I have four databases because the daily DB, the day before, the day after, and the huge all-time database)
So instead, I added a CSV buffer: incoming readings are appended to a flat file instead of immediately SQLite, and every 5 minutes, one of the nodes takes a hit to commit the CSV into the databases
The CSV append operation takes a few ms, usually 2ms but sometimes 5ms, so I'm happy about this part
The CSV to SQL operation takes about 8s when all 10 nodes are up (50 measurements to 4 databases), so that's a tad slower than I'd want but it happens once every 5 minutes so I guess that's ok?
(every SQL insert now takes about 40ms and there is probably still room for improvement)
And now I can keep a console with watch cat buffer.csv which is great, and more readable than my server logs
Here is a sequence of four batches as a demo (first CSV field is a timestamp, second is the node ID, and the rest are air quality readings from the BME680)
#diy #AirQuality #RaspberryPi #SQLite

I updated a bunch of stuff in the project, especially split the single database that was getting way too big for SQLite + microSD to handle gracefully (more than 30s) and I updated the README with new screenshots
Iām now storing my sensor readings in two database files:
This way, the daily databases are kept small, which makes querying them fast (mostly for the pretty graphs), and I also still have a giant single database for offline statistics (should I need that)
Reiserouter mit dem #raspberrypi
https://raspithek.de/projekt/reiserouter-mit-dem-raspberry-pi/
I just added documentation to the README for my DIY mesh network of air quality sensors
Comments are welcome! This is still just a personal project
https://github.com/GuillaumeRossolini/griotte
#iot #esp32 #esp8266 #RaspberryPi #arduino #mesh #AirQuality
Raspberry Pi NAS with OpenMediaVault
https://peertube.wtf/w/kRvpspH3TVqeW2xEcAHJ5p
I need to change the storage mechanism
Iām doing backups of my readings database from the Raspberry Pi Zero to my PC, and what used to take 4 MB of space early on (in September) now takes 60 MB
Obviously even with indexes, SQLite canāt be expected to read this from flash storage to present my graphs in a timely manner
I guess I can double store: once in a daily database I can use to present my graphs, so that SQLite only ever has to read from tiny databases, and a second time in a single database meant for larger analysis (off the rpi)
The migration will be painful š
I should kick off this thread with Archimedes, the #owl #CompanionBot in the first pic! Made him for #BayArea #MakerFaire in May '18, with a #RaspberryPi brain, then updated in '21 with an #Arduino for motor control.
I've been working on smaller versions since then ā including Nano'Medes here, with #origami wings ā and plugging away at the new "Prince Stolas" version. Both use my Companion Core PCB (more on that soon!) š¦š¤šāØ
V1: https://www.hackster.io/glowascii/archimedes-the-ai-robot-owl-325ff5
V2: https://www.hackster.io/glowascii/archimedes-2-robot-owl-familiar-2348ef

Attached is a video of the #esp32 happily blinking its payloads across WiFi networks to the #RaspberryPi Zero, for storage in the #sqlite database
Thousands of readings per day (about 1300 each sensor so far, today), all sensors being within 15 readings of each other, Iād call that stable
Iām happy to notice that when a board fails, it eventually recovers on its own (it takes several hours, though)