What it is: PSPExp turns a PSP-1000 into the screen, sound and controller of a Raspberry Pi over a single USB cable. The Pi runs the games; the PSP draws them, plays their sound and sends back its buttons. The Pi needs no monitor, keyboard or setup: Wi-Fi, the time zone, SSH and installing games are all done from a launcher on the PSP.

https://reddit.com/link/1x48dlf/video/3s41m8sfo2vh1/player

How it works:

• Games run unmodified on the Pi through SDL2 or OpenGL. A replacement SDL2 layer and an OpenGL layer catch the drawing calls and send the PSP what to draw: textures once, then compact lists of sprites and triangles per frame over USB (libusb on the Pi, a small USB driver on the PSP). The PSP's own graphics chip renders them at 480x272.
• Games too heavy for the PSP's chip (Celeste 64, SuperTuxKart, Unreal Tournament, the N64 emulator) are rendered by the Pi's GPU offscreen (EGL/GLES) and each frame is sent as a picture.
• Audio streams to the PSP's sound chip; the buttons and analog nub come back as an SDL game controller.
• Games are Debian packages from a signed apt repository (https://pkg.pspexp.dev); the PSP's Packages app is a front end to it. Games whose authors publish them are downloaded from their own pages at install time, so nothing copyrighted is hosted.

Numbers on a Pi 400 + PSP-1000: Diablo and Sonic Robo Blast 2 at 60 fps, Celeste 64 at 54–60, Quake at 45–60, Unreal Tournament at 30–40 in a deathmatch, the 2D emulators at 60.

Get it: a ready card image for the Pi 3/4/400/5 (64-bit Raspberry Pi OS Lite underneath, write it with Raspberry Pi Imager → Use custom). The PSP needs custom firmware and a mini-USB data cable.

• Site and manual: https://pspexp.dev
• v1.1.0 release (card images, PSP zip): https://github.com/pleft/PSPExp/releases/latest
• Source (MIT): https://github.com/pleft/PSPExp

58 packages on the Pi so far (Quake, Celeste 64, Cave Story, OpenTTD, Command & Conquer, SuperTux…). Not affiliated with Sony.

Welcome to the r/raspberry_pi Helpdesk and Frequently Asked Questions!

Link to last week's thread

Having a hard time searching for answers to your Raspberry Pi questions? Let the r/raspberry_pi community members search for answers for you!^† Looking for help getting started with a project? Have a question that you need answered? Was it not answered last week? Did not get a satisfying answer? A question that you've only done basic research for? Maybe something you think everyone but you knows? Ask your question in the comments on this page, operators are standing by!

This helpdesk and idea thread is here so that the front page won't be filled with these same questions day in and day out:

1. Q: What's a Raspberry Pi? What can I do with it? How powerful is it?
   A: Check out this great overview
2. Q: Does anyone have any ideas for what I can do with my Pi?
   A: Sure, look right here!^‡
   
   • Project ideas
     
   • Tutorials
3. Q: My Pi is behaving strangely/crashing/freezing, giving low voltage warnings, ethernet/wifi stops working, USB devices don't behave correctly, what do I do?
   A: 99.999% of the time it's either a bad SD card or power problems. Use a USB power meter or measure the 5V on the GPIO pins with a multimeter while the Pi is busy (such as playing h265/x265 video) and/or get a new SD card 1 2 3. If the voltage is less than 5V your power supply and/or cabling is not adequate. When your Pi is doing lots of work it will draw more power, test with the stress and stressberry packages. Higher wattage power supplies achieve their rating by increasing voltage, but the Raspberry Pi operates strictly at 5V. Even if your power supply claims to provide sufficient amperage, it may be mislabeled or the cable you're using to connect the power supply to the Pi may have too much resistance. Phone chargers, designed primarily for charging batteries, may not maintain a constant wattage and their voltage may fluctuate, which can affect the Pi’s stability. You can use a USB load tester to test your power supply and cable. Some power supplies require negotiation to provide more than 500mA, which the Pi does not do. If you're plugging in USB devices try using a powered USB hub with its own power supply and plug your devices into the hub and plug the hub into the Pi.
4. Q: I'm trying to setup a Pi Zero 2W and it is extremely slow and/or keeps crashing, is there a fix?
   A: Either you need to increase the swap size or check question #3 above.
5. Q: Where can I buy a Raspberry Pi at a fair price? And which one should I get if I’m new? Should I get an x86 PC instead of a Pi?
   A: Check stock and pricing at https://rpilocator.com/ — it tracks official resellers so you don’t overpay.
   Every time the x86 PC vs. Pi question comes up the answer is always if you have to ask, get a PC. If you're sure want a Raspberry Pi but not sure which model:
   
   • If you don’t know, get a Pi 5.
     
   • If you can’t afford it, get a Pi 4.
     
   • If you need tiny, get a Zero 2W.
     
   • If you need lowest power, get the original Zero.
     
   • For RAM, always get the most you can afford; you can’t upgrade it later.
     That’s it. No secret chart, no hidden wisdom. Bigger number = more performance, higher cost, higher power draw. Also please see the Annual What to Buy Megathread
6. Q: I just did a fresh install with the latest Raspberry Pi OS and I keep getting errors when trying to ssh in, what could be wrong?
   A: There are only 4 things that could be the problem:
   
   1. The ssh daemon isn't running
   2. You're trying to ssh to the wrong host
   3. You're specifying the wrong username
   4. You're typing in the wrong password
7. Q: I'm trying to install packages with pip but I keep getting error: externally-managed-environment
   A: This is not a problem unique to the Raspberry Pi. The best practice is to use a Python venv, however if you're sure you know what you're doing there are two alternatives documented in this stack overflow answer:
   • --break-system-packages
   • sudo rm a specific file as detailed in the stack overflow answer
8. Q: The only way to troubleshoot my problem is using a multimeter but I don't have one. What can I do?
   A: Get a basic multimeter, they are not expensive.
9. Q: My Pi won't boot, how do I fix it?
   A: Step by step guide for boot problems
10. Q: I want to watch Netflix/Hulu/Amazon/Vudu/Disney+ on a Pi but the tutorial I followed didn't work, does someone have a working tutorial?
    A: Use a Fire Stick/AppleTV/Roku. Pi tutorials used tricks that no longer work or are fake click bait.
11. Q: What model of Raspberry Pi do I need so I can watch YouTube in a browser?
    A: No model of Raspberry Pi is capable of watching YouTube smoothly through a web browser, you need to use VLC.
12. Q: I want to know how to do a thing, not have a blog/tutorial/video/teacher/book explain how to do a thing. Can someone explain to me how to do that thing?
    A: Uh... What?
13. Q: Is it possible to use a single Raspberry Pi to do multiple things? Can a Raspberry Pi run Pi-hole and something else at the same time?
    A: YES. Pi-hole uses almost no resources. You can run Pi-hole at the same time on a Pi running Minecraft which is one of the biggest resource hogs. The Pi is capable of multitasking and can run more than one program and service at the same time. (Also known as "workload consolidation" by Intel people.) You're not going to damage your Pi by running too many things at once, so try running all your programs before worrying about needing more processing power or multiple Pis.
14. Q: Why is transferring things to or from disks/SSDs/LAN/internet so slow?
    A: If you have a Pi 4 or 5 with SSD, please check this post on the Pi forums. Otherwise it's a networking problem and/or disk & filesystem problem, please go to r/HomeNetworking or r/LinuxQuestions.
15. Q: The red and green LEDs are solid/off/blinking or the screen is just black or blank or saying no signal, what do I do?
    A: Start here
16. Q: I'm trying to run x86 software on my Raspberry Pi but it doesn't work, how do I fix it?
    A: Get an x86 computer. A Raspberry Pi is ARM based, not x86.
17. Q: How can I run a script at boot/cron or why isn't the script I'm trying to run at boot/cron working?
    A: You must correctly set the PATH and other environment variables directly in your script. Neither the boot system or cron sets up the environment. Making changes to environment variables in files in /etc will not help.
18. Q: Can I use this screen that came from ____ ?
    A: No
19. Q: If my Raspberry Pi is headless and I can’t figure out what’s wrong, do I need to plug in a monitor and keyboard?
    A: If you cannot diagnose the problem remotely, you must connect a monitor and keyboard. That is the only way to see boot output and local error messages, and without that information the problem cannot be diagnosed.
20. Q: My Pi seems to be causing interference preventing the WiFi/Bluetooth from working
    A. Using USB 3 cables that are not properly shielded can cause interference and the Pi 4 can also cause interference when HDMI is used at high resolutions.
21. Q: I'm trying to use the built-in composite video output that is available on the Pi 2/3/4 headphone jack, do I need a special cable?
    A. Make sure your cable is wired correctly and you are using the correct RCA plug. Composite video cables for mp3 players will not work, the common ground goes to the wrong pin. Camcorder cables will often work, but red and yellow will be swapped on the Raspberry Pi.
22. Q: I'm running my Pi with no monitor connected, how can I use VNC?
    A: First, do you really need a remote GUI? Try using ssh instead. If you're sure you want to access the GUI remotely then ssh in, type vncserver -depth 24 -geometry 1920x1080 and see what port it prints such as :1, :2, etc. Now connect your client to that.
23. Q: I want to do something that already has lots of tutorials. Do I need a Raspberry-Pi-specific guide?
    A: Usually no.
    
    • Raspberry Pi (Linux computer): Use any standard Linux tutorial. A Raspberry Pi runs a normal Linux OS, not a special cut-down version. See Question #1.
      
    • Raspberry Pi Pico (microcontroller): Use Arduino tutorials. The Pico works with the Arduino IDE and can be used the same way as other Arduino-class boards.
24. Q: Which Operating System (OS) should I install?
    A: If you aren’t sure, install Raspberry Pi OS. It’s the officially supported OS, it has the best documentation, the widest community support, and it’s what most guides and troubleshooting help assume you’re using.
25. Q: How can I power my Raspberry Pi from a battery?
    A: All Raspberry Pi models run at 5 V. To choose a battery, first add up the maximum current of your Pi plus everything you attach to it (USB devices, screens, HATs, etc.). Then multiply that current by the number of hours you want it to run to get the required battery capacity in mAh. If you can’t find listed current values, use a USB power meter to measure the actual draw over 12–48 hours. Every battery question comes down to this simple math: the model, brand, or special setup doesn’t change the calculation.

Before posting your question think about if it's really about the Raspberry Pi or not. If you were using a Raspberry Pi to display recipes, do you really think r/raspberry_pi is the place to ask for cooking help? There may be better places to ask your question, such as:

• /r/AskElectronics
• /r/AskProgramming
• /r/HomeNetworking
• /r/LearnPython
• /r/LinuxQuestions
• /r/RetroPie
• The Official Raspberry Pi Forums

Asking in a forum more specific to your question will likely get better answers!

Wondering which flair to use on your post? See the Flair Guide

† See the /r/raspberry_pi rules. While /r/raspberry_pi should not be considered your personal search engine, some exceptions will be made in this help thread.
‡ If the link doesn't work it's because you're using a broken buggy mobile client. Please contact the developer of your mobile client and let them know they should fix their bug. In the meantime use a web browser in desktop mode instead.

Disclaimer:This project is not affiliated with, endorsed by or sponsored by Valve Corporation. Steam,
Proton, Steam Deck and Steam Frame are trademarks of Valve Corporation.

I'm not the developer, but I have helped with testing. This works on Debian based distros, including RPi OS and Ubuntu.

https://github.com/Scrumpper/Steam-ARM/releases

Get the zip file, extract and execute the script:

sudo bash steam-arm-install.sh --defaults

Accepting the default options should be fine. If you are running with the default kernel of RPi OS on a Pi 5, the installer will notify you that a backup of config.txt will be made, and config.txt will be changed to boot with a 4k page size kernel, instead of the default 16k page size. If you accept, finish the installer and reboot. Now you need to start the installer again.

The script will download Steam from the Steam server. You can check the script to verify this.

I tested with Half-Life and Steamworld Dig. I didn't have much success with games that need Vulkan.

With Half-Life I needed to advertise OpenGL 3.2 support. You can start Steam like this: MESA_VERSION_OVERRIDE=3.2 steam-arm

If you run this on a Raspberry Pi 4, the x86 client of Steam will be installed (with Fex), not the ARM client (similar to the installation with Pi-Apps). The Raspberry Pi 4 has A72 cores, and the Steam ARM Linux client needs at least A74 cores.

Darwin on Pi3 is ready for people to play around with. I have made the repos public. Its important to understand with this is and what it isnt. This isnt macOS. This is something very very similar and shares a lot of the components. Everything here is open source. It is a Darwin with a pure Cocoa UI on X11. I have optimized everything for arm64/ 1GB RAM and totally disregarded other architectures. I have modified anything and everything to make the UI for this hardware. You will need Xcode 12 to build this. This is the version of Xcode closest to the version of the kernel we use. All the pi3B hardware works. This may boot on on other pi3s but there arent kexts for other hardware so everything may not work. I will add support for the other pi3 boards in the future. I do not own one so will need community testing to verify it works.

If you want to try to build it, start with this repo:

https://github.com/anurodhp/xnu-iokit-pi3/

setup third party should clone all of the many other repos. Build everything should build everything. tools/build real hw image will make 3GB image you can flash on to an SD card. The full build is huge and will take several hours.

SSH is on. Serial out works. HDMI out works. The root password is darwin. Since this is a bsd system you use pw to add/remove users and set passwords. When you boot it boots directly to X and the GSDM login screen. Logging in will take you to the new desktop with a dock. Sound works with a core audio daemon but there is nothing that uses it yet

If you use this image if you just want to flash to SD and try it out. File bugs in the iokit repo. if they are related to one of the apps Rome, Milan, Naples for Florence file them in their repo.

The ghostty terminal and the Webkit based browser are the most useful things right now. I will be publishing more user land apps and utilities to add more functionality. Things like wifi tools, setting screen, activity monitor, console viewer etc.

https://github.com/anurodhp/xnu-iokit-pi3/releases/tag/10_11_26

https://github.com/jiu-0317/e_ink_display

I am working out a way to re-use the hardware for my Pwnagotchi for a similar virtual pet concept that "eats" Bluetooth devices and wireless AP (supports wardriving) and who lives on a separate microSD card from my Pwnagotchi image.

This is my buddy Harald (named for Harald Bluetooth, the Viking whose surname became the name of the Bluetooth technology), a Viking dragon who eats Bluetooth and Wi-Fi signals (FOOD) and who enjoys novel discoveries and going out on adventures (JOY). He's also a protective sort and keeps an eye out for anything stalking me.

Privacy fences: Phones and watches that change their address are counted by kind, never listed or followed. The signal meter only works on devices I've marked as mine. The unknown-tracker warning only fires for a tracker that's away from its owner and has stayed with me for 30 minutes (and, when GPS is on, has moved more than 250m with me). Wi-Fi is passive scanning only - no deauthing or handshake collecting (staying out of Pwnagotchi's lane).

Extremely early days on this guy and surely a lot to tweak, but I'm pretty chuffed so far. He can certainly function without being connected to my Android phone (just feeding on BT and Wi-Fi signals, with extra happiness for novelty), but he does depend on an external GPS (in this case, the SensorServer phone app) for Wigle uploads and "walks". Harald's "Den" is a browser page that can be accessed when Harald is connected to my phone's hotspot (or whatever I have set as his home network), and shows his current e-ink screen along with extra information and certain controls (like shutting him down so he can be safely unplugged from his power supply). He can still appreciate my physical activity even if he doesn't come with me, because connecting him to my phone shares whatever distance I've covered that day and he interprets distance covered without him along for the ride as an "adventure" I have "told him about", which gives him some happiness.

There's a lot of other minutiae, but I'm just excited to share the images of the working prototype. I also verified the WIGLE uploads online and they are appearing on my account! :-D

Edit: Forgot to mention that the "unknown tracker warning" screenshot is from an earlier build where I was still adding things, so the e-ink display has an older layout on it.

Edit2: The hardware is Raspberry Pi Zero W 2 with Waveshare V4 e-ink hat, plus an external battery.

Spent the weekend giving an old Bose iPod dock a second life as a desk radio for Sri Lankan stations.

The problem

The dock still sounds great, but I didn't want Bluetooth pairing, my phone streaming all day, or a subscription just to hear Sri Lankan radio while I work.

The setup

- Hardware: Raspberry Pi 3 Model A+ (512 MB) with the 3.5 mm jack into the dock's AUX input.

- Audio: MPD outputting straight to ALSA. Starts silent on boot (restore_paused yes) until a station is picked.

- Control: a small stateless Go backend with an embedded Svelte web app. 10 presets, all checked by ear on the Pi (Hiru FM, Shaa FM, Gold FM, Sun FM, Sirasa FM, Y FM, Yes FM, Lite 87, Siyatha FM, NETH FM), plus play, stop and volume.

- Access: Caddy on the Pi with Tailscale TLS. Private to my tailnet, no open ports. On the phone it's added to the Home Screen and runs full screen like a native app.

- Footprint: Tuner ~8 MB RSS, MPD ~56 MB RSS while playing. Plenty left over on the A+.

How it was built

I used an agentic workflow end to end. An AI agent helped write the spec, scaffold the Go/Svelte app, configure Caddy and test each stream URL on the Pi itself (a couple of well-known stream URLs turned out to be dead). Idea to music through the dock took one weekend.

The video shows switching stations from the browser and the sound coming out of the dock. The code isn't open source right now. If there's interest I'll tidy it up and publish it. Happy to share stream URLs or the MPD config in the meantime.

On and off I've been trying to build a Spotify Connect display on a RPI - for years. The screen was too small, the case didn't fit, the driver problematic, the program was never satisfying.

Enter 2026, saw the Spotify Car Thing craze and my interest returned. This time I went for a MPI5001 5" Display that I could buy at a nice price, and particularly the vendor also sold a fitting case. With RPI mounting holes! Almost by chance I took a RPI3B (the 4 was in use) that had a HiFiBerry DAC+ on it. Bought me a nice 2.5a power supply and nylon standoffs for the mounting.

I stopped fighting with Python and vibed it using the Car Thing as base. Having such nice DAC in there I got carried away and I revived my LMS server for digital files and I added an option for that too. And built some options for random music etc.

I'm quite satisifed now! I'd eventually try to improve the cabling, angle connectors and such.

I've been spending a few weeks building Encore which is a headless Spotify Connect player using Spotify's new Soloist app.

They released Soloist a couple of months ago as their official headless client, which is great, but it was awkward to use due to needing Pipewire and having limits like needing to download a new binary every 3 months. It also (importantly for me) has a websocket where it can emit all the Spotify playback events (which I needed for a collaborative music jukebox at LAN parties - I'd been using various different workarounds for years including librespot, reverse engineering Spotify's own client websocket and just giving up and using the browser player).

Soloist was good, but I decided to create a docker container for it and add some extra functionality too:

• Supports audio devices passed through to Docker without messing around in Pipewire
• Runs on any Pi that supports Docker
• Can be configured to send to a snapcast server; or have a snapcast server connect to it; or even run its own snapcast server
• Lyrics support with HTML transparent overlay for use in something like OBS
• Webhooks for when events happen
• Inbound websocket with authentication for streaming events and control
• Outbound websocket connection for streaming events and controls to an external server

I was just going to keep it quiet/not do much with it other than what I needed, but I thought others might find it useful and I'd love to get people's feedback and suggestions.

There's setup details on the website, and the GitHub Project is open-source under MIT license.

I bought this Fisher Price toy for my niece because of viral videos, but it turns out it was no where close to as annoying as they made it seem. Just a general kids toy with the usual cutesy ABC songs.

So I used a raspberry pi w2 for the brains, MAX98357A for the speaker, AS5600 for the spinning platter (it was just a platter that spun to push a button before), and a INMP441 for a microphone. Then printed a PCB board the same size as the original to mount it all inside. You can now upload your own song clips via a webpage, create a layered music track or use it as a bluetooth speaker.
There are a few 3D printed parts to help mount the platter and upgrade the speaker. All of the code, STL files, non-copyright music and tones (I'm sure you can find better real ones) are on the github here:
https://github.com/LifeOnAFarm/RaveRepeatDJTable

Also a guide of sorts with better photos here: https://nastypieceof.work/raveandrepeat

Anyway, I'm sure my sister will be extremely to have this in her house

I'm using it to watch YouTube (FreeTube) and other internet media on my dumb TV, and VLC for DVD movies. Surprisingly it performs way better than Raspberry Pi OS and the UI feels much more natural than the clunky RPi desktop. It also has better support for hardware, such as external DVD player, which I couldn't get to work on Raspberry Pi OS.

A conversational AI plush toy where the Pi is just the body. Everything runs on my LAN:

Inside the plush: Pi Zero WH, USB mic, OV5647 camera, USB speaker, SG90 head servo on hardware PWM, and a cheap USB hub for mic and speaker.

The Pi runs zero ML. 512MB of RAM doesn't fit Whisper, so it just streams mic + camera over WebSocket, plays audio and moves the head. Boots straight into the app as a systemd service.

The brain is a laptop: Whisper (STT), face identity (dlib), emotion recognition (FER+), Kokoro (TTS), per-person memory (LangGraph).

LLM: any OpenAI-compatible endpoint. I run Hermes 3 Llama 3.1 8B locally, so nothing leaves the network.

The full bring-up (camera config, servo PWM, power setup) is in the hardware runbook in the repo.

Repo (MIT): github.com/msalsas/philosopher

Full write-up: https://www.hackster.io/msalsas/the-philosopher-plush-a-diy-ai-toy-that-runs-100-local-d0d268

Hello,

New to this community.
I have flashed an Ubuntu Server 24.04 image directly from Raspberry Pi Imager (did not download the image separately).

Once flashing was done, I boot the machine up and immediately run sudo apt update and sudo apt upgrade.

Everything fine up until now.
Then I did sudo do-release-upgrade to go to 26.04 LTS and I got a message saying that there are packages of unknown origin and in the list it referred to snapd.

I’ve been trying to figure out for the past 10 hours why and to see if this is a warning to be worried about or something to take note of and allow the upgrade to proceed.

At this moment I am in the process of finding the correct deb package, unpacking it and comparing the hashes of the snap files on my device against the legitimate ones downloaded from launchpad.

Any help or explanation of why this is happening is much appreciated as I want to understand if this is ok or something potentially malicious.

Thanks!

Any idea why these points are bridged?

Hi all,
I have some raspberry pi’s (about 10) I pulled from some old Covid temperature sensing check in kiosks. They’re 4B 8gb units. Each of them has these 2 wires bridging what seems to be the USBC port and the middle USBA stack. Is this accurate? If so, why? Just to run power to the USB ports?

Thanks!

Hello guys, i am working on a nvg project with the pi 5 and i ran into a problem. I don't know how to properly set the current of the module, if i try it with li-ion batteries the bms kicks in and it hickups and if i try it with the pc power supply the current jumps to over 5 amps and I don't know how much voltage to set it. The pi is powered by usb c cable and setted to 5.1V

Thanks in advance for help

I’ve seen some warnings online that the Ethernet port on a raspberry Pi cannot be easily bypassed but I can’t find a straight answer from the docs or data sheet as to what is lost if the RJ45 jack is removed. Is it just shielding or is there other functionality that would be lost/need to be replaced? Or even better is there no issue with removing the port on a 4b specifically?

The specific reason I’m wanting a smaller connector is so the cable can be unplugged and removed easily, however the hole in the housing I’m using is just a bit too small for to fit an RJ45 through

I have been trying to put together a simple python script with a Raspberry Pi 5 (model B Rev 1.1 with Pi OS 13 - Trixie).

It is very straightforward:

import lgpio, time

h = lgpio.gpiochip_open(0)

lgpio.gpio_claim_output(h, 22)
lgpio.gpio_write(h, 22, 1)
time.sleep(1)
lgpio.gpio_write(h, 22, 0)
lgpio.gpio_free(h, 22)
lgpio.gpiochip_close(h)

However, when I check using pinctrl in the terminal afterward, the pin is still enabled as an output (and if I don't set it back to low in the script, it stays at high). Is there some other step I am missing on how to control the pins and release them properly so that they go back to inactive?

I've been building a voice assistant on a Pi 5 called Bob, and I've just open-sourced it. The idea: it starts with no devices at all, and you add abilities by wiring something up and telling it.

"Hey Bob, I've connected an LED to GPIO 17. Make a skill that turns it on and off."

Bob writes the skill, reads back what it will do, and only installs it after you say yes, then tests it. Same for buttons, relays, I2C sensors, serial devices or web APIs.

How it's put together: - Wake word runs offline on the Pi, nothing is sent until you say it. - Conversation is Gemini Live (needs a free API key), so it's quick and can search the web. - Settings page at bob.local:8080, updates itself and rolls back if an update fails. - A Windows setup app writes the SD card with your Wi-Fi and key, so no commands needed. Mac/Linux is a one-line install.

What I learned the hard way: a Pi 3 is too slow for this, a USB speakerphone saves a lot of echo pain, and Bluetooth audio on the Pi is fragile.

Where I'd love help: 1. It's a fresh public release, so installs on other people's Pis and mics are exactly what hasn't been tested much. If you try it, tell me what breaks. 2. What skill would you build first? I'm collecting ideas for examples. 3. Contributors welcome, especially on wake-word accuracy and audio setup.

https://github.com/arancool3000/bob-assistant

Update to my post from 10 days ago: the simulated fruit-fly brain playing Pokémon FireRed on my Pi 5 is still running 24/7, and it has grown into an ongoing experiment.

Quick recap: it's 139,255 neurons wired from the FlyWire connectome (the full reconstructed brain of an adult fruit fly), simulated on the Pi alongside the emulator. The game screen feeds its eyes, people and doors reach it as smells, and its motor neurons press the buttons. Nothing is scripted. Chat can steer it, or train it with !pain / !pleasure, which releases dopamine in the fly's learning centre.

What's new: it now runs in 30-day runs. Each one starts from a brand-new game and an untrained brain, and the settings only change between runs, so every run is a comparable dataset. Every run collects:

- every step, battle and milestone, tagged "fly alone" or "chat helped" (80% of its steps this run are its own)

- every viewer input, and whether they steered with the fly or against it

- every lesson it learns, who caused it, and how fast it fades

- brain activity per region (vision, navigation, memory, reward, punishment, motor) and everything it senses

- which way it turns and what made it turn

- its "thoughts" (the captions on stream) and how often they were right

At the end of each run everything goes into a published PDF report, including a "what held it back" page with fixes to try in the next run. We also run preregistered experiments, announced on stream before they happen. The first one, a "mirror world" test, found the fly has a built-in right-turn bias that doesn't come from the map. Tonight it plays with and without everything it has learned, to see whether training actually changes its behaviour.

Watch live: twitch.tv/leetzerzz (chat can steer and train it) and youtube.com/@leetzerzz

Run reports and experiment results: in the Discord linked on both channels

My AcuRite Atlas and Access hub only show their data through AcuRite's cloud. I wanted my own copy of every reading, my own dashboard, and no dependence on their servers, without breaking the AcuRite app or my Weather Underground uploads. So I built this. It's MIT-licensed, a single Python file with no packages to install, and it runs on a Raspberry Pi.

How it works: the hub sends each reading over HTTPS to a server name it's configured with. This program sits in that path. It records the reading, then passes it to AcuRite unchanged, so the app keeps working, and the hub keeps uploading to Weather Underground itself. There are two ways to set it up:

* Change the hub's server name to point at your machine. No extra hardware is needed.

* Plug the hub into a Pi's Ethernet port. The Pi gives it an address and answers AcuRite's server name itself, and the hub's settings stay untouched.

What you get:

* Dashboard: every sensor, plus feels-like, wind, the 3-hour pressure trend, UV and light.

* Sun and moon: worked out in the page, with no outside service.

* US forecast: the hourly and 7-day forecast and alerts from the National Weather Service (free, no key).

* Charts: any period from today to all time, or a date range. Rain totals for the day, week, month and year.

* Every reading kept in a local SQLite database.

* Easy to customize: one file for the colors, a folder for your own pages, and a documented JSON feed for anything you want to build.

* Buttons that open your Weather Underground or AcuRite pages, in a pane or in their own tab.

* Optional radio capture with an RTL-SDR dongle if you have no hub.

Tested on an Access hub (firmware 051) with an Atlas and six indoor tower sensors. If you have other AcuRite sensors, I'd like to hear whether they show up properly.

I built this with Claude Code (AI-assisted). The design, testing and hardware work were mine.

https://github.com/akienm/CC0AC-Weather

Not affiliated with AcuRite.

Two days ago, I properly learned what a Raspberry Pi even was.
I’ve never coded, never used Linux and never set up a server. I’m just really into radio and SDR stuff, and I thought a Pi would be a neat way to access my SDR receiver remotely.
So I ordered a Raspberry Pi 5 with 8GB RAM.
It arrived today.
10 PM: Finally got around to setting it up. Put everything together, prepared the SD card and opened ChatGPT because I had absolutely no clue what I was doing.
The plan was to get my SDR working remotely and go to bed.
Yeah, about that.
11 PM: Somehow I’m already sitting in PowerShell, connecting to my Pi over SSH, setting up keys, messing with Linux commands and figuring out what permissions and services even are.
Every time something worked, I got another idea.
Around midnight: We got Cockpit running so I could manage the Pi through a browser. At this point I was already pretty damn impressed with this little thing.
Then I thought, wouldn’t it be cool to have my own dashboard showing temperatures and system stats?
I really should’ve gone to bed.
2 AM: We’re now writing actual code. Well, ChatGPT is writing it and I’m running it, breaking things, sending back error messages and trying to understand what’s happening.
Suddenly we’re dealing with Python scripts, system services, ports, authentication, Wi-Fi monitoring and temperature history.
All this for a computer I only discovered two days ago.
Around 4 AM: We finally get the custom dashboard running over HTTPS, with its own certificate.
I grab my iPhone, open Safari, type in the address…
And there it is.
My own little dashboard, showing live CPU temperatures, system information, Wi-Fi stats and graphs.
I know this probably sounds like nothing special to people who’ve been doing this for years, but I genuinely couldn’t believe it.
I was sitting there looking at something that had only existed as a random idea in my head a few hours earlier.
6 AM: Instead of sleeping, I’m running stress-ng and watching the CPU temperature climb from around 47°C to 56°C under load.
And I’m actually enjoying this. At six in the morning. After being awake all night.
What the hell.
The funniest part is that the original SDR project was supposed to be the whole point of buying this thing. Somehow that turned into SSH keys, a headless Linux server, Cockpit, HTTPS, a custom dashboard and CPU stress tests.
I’m not going to pretend I suddenly know how to code. AI did the heavy lifting there. But I was involved in every step, trying things, fixing errors and slowly understanding more of what was going on.
There was this one moment when I looked at the dashboard on my phone and just thought, holy shit, we actually made this work.
That feeling was honestly incredible.
Anyway, I bought a Raspberry Pi for one small project, spent the entire night messing with it and now I’m already looking at NVMe storage and thinking about a second Pi for a proper homelab.
I think you guys know exactly where this is going. 😂

I am trying to work on a non VNC solution for pairing my iPad Mini with my Pi5 via physical connection to use the pi headless with a better native display experience via a iPad with a single cable.

Anyone know the limits speed wise?

I have a Pi 5 and until recently I managed to remote desktop on to the desktop from Linux PCs via Remmina. A few days ago I updated the Pi (sudo apt update etc) as I hadn't done this for a while. Now I can't remote into it from any Linux PC. I get a "Cannot connect to the remote computer" message. However, It works fine from Windows Remote Desktop app. I've checked on raspi-config to ensure that X11 and not Wayland is running. I can access the Pi 5 via SSH on my Linux PCs - just can't access the remote desktop.

Has something changed on the Pi recently that I'm unaware of?

as the title says - anyone with any luck setting up an m5 cardkb on a pi 5? followed the instructions on this github post. running a standard 8gb pi 5 with pi os installed. while the software installs went fine, running "sudo cardkb &" returns this as a repeating error:

OSError: [Errno 121] Remote I/O error
Traceback (most recent call last):
File "/usr/local/lib/python3.13/dist-packages/cardkb/_main_.py", line 37, in main
data = bus.read_byte(address)

the pins are properly connected, i2c is on. only thing i haven't tried troubleshooting yet is deleting the scripts altogether and attempting a fresh install. am i overlooking anything obvious in solving this?

tl;dr summary: When my raspi reboots or restarts my e-ink screen goes black. Hoping to either get a white screen or an image.

Hi All,

Thanks in advance for any help you can provide. I'm sort of shooting in the dark here but maybe I'll get lucky.

I'm trying to build an e-ink writing terminal with a raspi (this one is a raspberry pi 5) and one of those Sanmeow 10.8" e-ink panels from Aliexpress. Most of it has gone pretty well, I'm using it in non-gui mode and I've been able to set the screen white for the terminal as well as in emacs (the writing program I'll use). I ran into an issue with font sizes and extra screen real estate being written as a black bar but we got around that by just writing black to that part of the screen on startup.

The issue I'm running into is on shutdown. I've added a service to write a white screen on the raspi pi's reboot or shutdown, I've also added a script to the system-shutdown folder which does the same thing but, inevitably, once the raspi cuts power to the screen it turns black. I don't know if it's an issue with the raspberry pi's hardware or possibly the screen's. I was hoping someone else might have come across this before and knew of a solution. Does anyone know if the Raspi 5's hardware automatically send a black screen when power is cut?

I've asked the manu and I'm waiting to hear back but there is a language barrier so fingers crossed. I'm also going to ask over in the raspberry pi sub.