Four months ago I showed my retro-futuristic Pi camera here. Today it's fully released - firmware, print files, assembly manual. Build your own SATURNIX
https://redd.it/1urysi6
@r_raspberry_pi
https://redd.it/1urysi6
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit: Four months ago I showed my retro-futuristic Pi camera here. Today it's fully released…
Explore this post and more from the raspberry_pi community
DroneAware community network update: 160 sensors and 1.6 million Remote ID detections
https://redd.it/1ut0n1b
@r_raspberry_pi
https://redd.it/1ut0n1b
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit: DroneAware community network update: 160 sensors and 1.6 million Remote ID detections
Explore this post and more from the raspberry_pi community
Issues with connecting to Raspberry Pi Connect
Hi all. I am completely new to RPI, I only just got my first one (Raspberry Pi 4B 1GB) mostly to experiment and try to learn.
I am now trying to use Raspberry Pi Connect as I don't have a monitor cable for it. The RPI is connected to my network, I am able to control it from my PC, and it pings outside the network (I've tried google.com and raspberrypi.com with success). It also displays as online on connect.raspberrypi.com.
However, when actually trying to connect to it, whether by screen share or remote shell, nothing happens. It stalls at "Waiting for response from raspberrypi".
$ rpi-connect doctor returns the following:
Screen sharing is supported by this version of rpi-connect
✓ Wayland compositor available
✓ Screen sharing services enabled and active
✓ Communication with Raspberry Pi Connect WebSocket server
✗ Communication with Raspberry Pi Connect API - Please check your connection to the internet.
Further diagnostics will be available once communication with Raspberry Pi Connect API is successful.
✗ Some checks failed
I am honestly not entirely sure where to go from here. I haven't been able to find a solution to this anywhere else - does anyone have any idea what I can do to fix this?
https://redd.it/1usk4nn
@r_raspberry_pi
Hi all. I am completely new to RPI, I only just got my first one (Raspberry Pi 4B 1GB) mostly to experiment and try to learn.
I am now trying to use Raspberry Pi Connect as I don't have a monitor cable for it. The RPI is connected to my network, I am able to control it from my PC, and it pings outside the network (I've tried google.com and raspberrypi.com with success). It also displays as online on connect.raspberrypi.com.
However, when actually trying to connect to it, whether by screen share or remote shell, nothing happens. It stalls at "Waiting for response from raspberrypi".
$ rpi-connect doctor returns the following:
Screen sharing is supported by this version of rpi-connect
✓ Wayland compositor available
✓ Screen sharing services enabled and active
✓ Communication with Raspberry Pi Connect WebSocket server
✗ Communication with Raspberry Pi Connect API - Please check your connection to the internet.
Further diagnostics will be available once communication with Raspberry Pi Connect API is successful.
✗ Some checks failed
I am honestly not entirely sure where to go from here. I haven't been able to find a solution to this anywhere else - does anyone have any idea what I can do to fix this?
https://redd.it/1usk4nn
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit
Explore this post and more from the raspberry_pi community
FsFAT library has 7 recognised security issues
There are a series of security issues raised with the FatFS* module that may impact you if your Pico / Pi uses the C module / Micropython and people have access to the media (sd card / drive) or, in some vulnerabilities, you use OTA updates.
Please note that runZeroInc state: No attacks using these bugs had been reported as of the July 1 disclosure date.
Library source: https://github.com/runZeroInc/vulns-2026-fatfs-chance
Errors found: https://securityaffairs.com/194808/security/seven-bugs-in-fatfs-put-iot-and-embedded-devices-at-risk.html
Video demonstration: https://www.youtube.com/watch?v=E0A7IrJtpUY
* For those who do not use this module (quote from here):
>FatFs is a generic FAT/exFAT filesystem module for small embedded systems. The FatFs module is written in compliance with ANSI C (C89) and completely separated from the disk control layer. Therefore it is independent of the platforms and storage devices. It can be incorporated into small microcontrollers with limited resource, such as 8051, PIC, AVR, ARM, Z80, RX and etc.
It is very handy if you are logging data directly to an SD card for example as the results can be read directly by a Mac / PC / Linux box without having to connect the collection device to a network.
https://redd.it/1utgzfz
@r_raspberry_pi
There are a series of security issues raised with the FatFS* module that may impact you if your Pico / Pi uses the C module / Micropython and people have access to the media (sd card / drive) or, in some vulnerabilities, you use OTA updates.
Please note that runZeroInc state: No attacks using these bugs had been reported as of the July 1 disclosure date.
Library source: https://github.com/runZeroInc/vulns-2026-fatfs-chance
Errors found: https://securityaffairs.com/194808/security/seven-bugs-in-fatfs-put-iot-and-embedded-devices-at-risk.html
Video demonstration: https://www.youtube.com/watch?v=E0A7IrJtpUY
* For those who do not use this module (quote from here):
>FatFs is a generic FAT/exFAT filesystem module for small embedded systems. The FatFs module is written in compliance with ANSI C (C89) and completely separated from the disk control layer. Therefore it is independent of the platforms and storage devices. It can be incorporated into small microcontrollers with limited resource, such as 8051, PIC, AVR, ARM, Z80, RX and etc.
It is very handy if you are logging data directly to an SD card for example as the results can be read directly by a Mac / PC / Linux box without having to connect the collection device to a network.
https://redd.it/1utgzfz
@r_raspberry_pi
GitHub
GitHub - runZeroInc/vulns-2026-fatfs-chance
Contribute to runZeroInc/vulns-2026-fatfs-chance development by creating an account on GitHub.
Fast (responsive) OS version?
Been quite some time since I touched anything Pi, and recently started a project with a 3B+. Installed the 64-bit RPi OS. Why does it feel slow (takes time to load up apps, select menu options, etc) to me (once booted up) ?
Ultimately, I need a basic desktop environment, Wifi, Python (which I can install later), and gcc... is there a better (faster, more responsive) OS for this?
Thanks!
https://redd.it/1uu57bw
@r_raspberry_pi
Been quite some time since I touched anything Pi, and recently started a project with a 3B+. Installed the 64-bit RPi OS. Why does it feel slow (takes time to load up apps, select menu options, etc) to me (once booted up) ?
Ultimately, I need a basic desktop environment, Wifi, Python (which I can install later), and gcc... is there a better (faster, more responsive) OS for this?
Thanks!
https://redd.it/1uu57bw
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit
Explore this post and more from the raspberry_pi community
I put my thermal receipt printer on the internet — strangers can now print messages onto my desk
Inspired by aschmelyun's ping-receipt project, but I rearchitected it for my setup: the website is a dependency-free PHP app on ordinary shared hosting that queues messages into SQLite, and the Pi runs a single-file Python agent (stdlib only, no pip installs) that polls outbound over HTTPS every 5 seconds and prints via raw ESC/POS to /dev/usb/lp0.
What I like about the split: the Pi never accepts an inbound connection — no port forwarding, no tunnel — and if the printer is off or out of paper, messages just queue and print when it comes back.
Hardware: a generic POS-80 thermal printer (\~the cheapest 80mm USB one you can find) + a Pi 4. Linux exposes it as /dev/usb/lp0 with zero setup, which was a relief after discovering macOS has removed raw printing entirely.
Each receipt prints: timestamp (my timezone), sender IP, city-level geolocation, distance from my desk, the sender's local time, browser/OS, and a native ESC/POS QR code that opens a map pin of roughly where the ping came from. There's a live map at https://ping.garethvjones.dev/map.php
Fun ESC/POS lessons: my "48 columns" assumption was wrong until I measured the dashes (42 vs 48 chars/line matters), native QR via GS ( k worked first try on the clone printer, and ASCII art survives if you hard-slice lines instead of word-wrapping them.
Try it: https://ping.garethvjones.dev — plain ASCII only, rate limited, be nice.
https://redd.it/1uton42
@r_raspberry_pi
Inspired by aschmelyun's ping-receipt project, but I rearchitected it for my setup: the website is a dependency-free PHP app on ordinary shared hosting that queues messages into SQLite, and the Pi runs a single-file Python agent (stdlib only, no pip installs) that polls outbound over HTTPS every 5 seconds and prints via raw ESC/POS to /dev/usb/lp0.
What I like about the split: the Pi never accepts an inbound connection — no port forwarding, no tunnel — and if the printer is off or out of paper, messages just queue and print when it comes back.
Hardware: a generic POS-80 thermal printer (\~the cheapest 80mm USB one you can find) + a Pi 4. Linux exposes it as /dev/usb/lp0 with zero setup, which was a relief after discovering macOS has removed raw printing entirely.
Each receipt prints: timestamp (my timezone), sender IP, city-level geolocation, distance from my desk, the sender's local time, browser/OS, and a native ESC/POS QR code that opens a map pin of roughly where the ping came from. There's a live map at https://ping.garethvjones.dev/map.php
Fun ESC/POS lessons: my "48 columns" assumption was wrong until I measured the dashes (42 vs 48 chars/line matters), native QR via GS ( k worked first try on the clone printer, and ASCII art survives if you hard-slice lines instead of word-wrapping them.
Try it: https://ping.garethvjones.dev — plain ASCII only, rate limited, be nice.
https://redd.it/1uton42
@r_raspberry_pi
ping.garethvjones.dev
ping — where the pings come from
A live map of everywhere the receipt printer has been pinged from.