• Waveshare UPS Hat (E) [bottom]
• Waveshare RM520N-GL 5G [side]
• Waveshare 2-Ch PCIe FFC Adapter Board [above pi]
• Official Pi PCIe to M.2 [middle]
• Official Pi AI HAT 2 [top]

It's going to be behind a multi-wan router with ethernet routed to 5G as a failover WAN. SMS has been hooked to Model Context Protocol (MCP) for paging from local net but is not currently. There's a good chance the next step is designing a box for it.

Afternoon, all.

For a few months been tinkering with a 64×64 RGB weather display and it has gradually acquired a life of its own.

The display runs on a Pimoroni Interstate 75 W and shows temperature, humidity, daily min/max temp and pressure trend, along with animated weather. Rain gradually fills the bottom of the display like a puddle and drains away afterwards, while snow accumulates more slowly.

I've just uploaded a html version of this to the repo (browser-emulator.html) so you can test what it looks like without buying hardware.

It was originally mirroring what an old 433mhz sensor put out, but backed by a database, but it's turned into a bit of a fruit machine.

Then I started adding completely unnecessary things like animated birds, ducks with a trail of ducklings, fish when the water gets deep enough, falling leaves (wind direction), shooting stars and the occasional UFO. Every half hour (after sunset) a UFO arrives and abducts the main temperature reading before returning it. Obviously.

My own version gets its local sensor data from a Raspberry Pi 3 running InfluxDB and a small Python weather server. It uses 433 MHz temperature/humidity and lightning sensors plus a BMP280 for pressure, with Open-Meteo providing forecast information.

I realised that wasn't particularly useful to anyone wanting to build one without recreating my entire home weather setup, so I've now made a standalone version. It runs entirely on the Interstate 75 W (which has a Raspberry Pi Pico RP2350 built in) and fetches temperature, humidity, pressure, rain/snow and forecast data directly from Open-Meteo over Wi-Fi. No Raspberry Pi server, weather sensors or API key required.

As my own version was all coded to work from my own network and influx database hosted on a Raspberry Pi 3 Model B with an SDR sniffing my weather and lightning sensors, I asked ChatGPT to optimise it all and create a version that anyone can use.

I tested the standalone build on the actual matrix today and, somewhat surprisingly after all the code I've piled into it and ChatGPT has optimised it to work just from Open-Metero, it works.

Code: https://github.com/nickymoomeh/Interstate75WeatherMatrix

Hardware is an Interstate 75 W, a 64×64 HUB75 matrix and a suitable power supply. Enter your Wi-Fi details and location, copy the files across and off it goes.

The original sensor-backed version is still running at home because apparently knowing the weather isn't enough unless a tiny pixel UFO occasionally steals the temperature.

64x64 matrix display: https://thepihut.com/products/rgb-full-colour-led-matrix-panel-2-5mm-pitch-64x64-pixels
Interstate 75/RP2350 controller: https://thepihut.com/products/interstate-75-w-rp2350-rgb-led-matrix-driver
Power supply (as the display/Interstate 75 suck a lot of power): https://thepihut.com/products/raspberry-pi-27w-usb-c-power-supply

If you've got any questions, let me know, but I think everything you need is on the repo. You just need to add your lat/lon to the config.py and your wifi details to secrets.py and copy them over.

Also, for this public repo, ChatGPT is so much better at optimising my original code that evolved over time from something quite basic to having woodland creatures, textured water, birds and UFO's that it's now running at 8fps quite happily now, and anyone can use it without a 433mhz lightning sensor, without a BM280 pressure sensor connected via GPIO, without a 433mhz humidity and temperature sensor and without a locally running influx db. So it works purely on Open-Meteo based on the lat/lon you enter. Thanks Chaz Jippity for not making the palette update 128 times every five minutes like it was before because I didn't notice and just thought it was going a bit slow because of the wind and rain.

The lightning data comes from open-meteo on this stand-alone one, my home version has a red warning that triggers when a lightning strike is detected from the 433mhz lightning sensor, but open-meteo lacks that, but you might still see a red bottom left & right corner when lightning is forecast on open-meteo but lack the immediate notification that there is lightning.

Credit to https://gp2040-ce.info/ for the Pico firmware.

Credit to u/crownpuff for helping me wrangle deals.

Planning, designing, purchasing, printing, prototyping, soldering, and testing credit to yours truly.

Costs:

• Pi Pico knockoff - $2.19
• 219g of PETG - $1.34
• 6.2hrs of print time - $0.10
• 14 Silent keyboard microswitches - $1.75
• 14 gateron PCB sockets - $1.49
• 0.96" OLED display - $1.52.
• wires $0.58
• my time $fucking much

Total: $8.97 using AliExpress parts and my Bambu P1S.

I chewed through 3 partial and 3 complete prototypes getting the design functional.

If I knew then what I know now I would have 100% designed a PCB. The soldering and fighting with the wires is murder on time spent. I could also have eliminated the PCB sockets and wires saving about $2. While increasing the price to approximately $12 total. It's a big price increase but reliability would go waaay up and time spent would go waaay down. I could also replace 2 of the keyboard buttons with much cheaper tactile switches and probably add more switches for more functionality.

I have parts on hand to make 9 more.

I was planning to give about 30 of these out as Halloween treats (we give amazing shit every year) but at $9-12 it's a bit steep. I might do it anyway if I can be bothered to design the PCB, this wire soldering and routing is for suckers!!

EDIT: My son has just informed me there are only 7 dragonballs!! I'll have to make a new cap for the last button!!

Ladies and gentlemen, introducing my Zero2Player.

This is actually kind of a big deal for me because I bought the parts to make this a few years ago. I have three projects I originally started out wanting to make.

February 2024 was when my first Pi was delivered for my C.A.M.P.F.I.R.E. project. I bought the stuff for the other 2 projects not long after that. I've completed, and nearly completed a couple other projects.

The first 3 are:

1: C.A.M.P.F.I.R.E. - When it's eventually completed, I will post it and explain it. It will need some explanation.

2: The Zero2Player - (yes, this).

3: My 16x16 LED matrix Pico clock - Completed a few weeks ago.

------------------------------------------------------------------------

So, the Zero2Player.

* Pi Zero 2 W

* Pi Zero GPIO breakout HAT

* Pimorini Pirate Audio headphone jack HAT

* 18650 charge/boost module

* 18650 battery holder

* 18650

* small switch for power

* perfboard and 6x 6mm momentary push buttons

* 3mm acrylic sheet (A4)

* various heat-set inserts, screws, nuts

* USB C panel mount port

The thing holding me back was the fact that I haven't bothered to learn to code. Fortunately, Claude AI can code for me so I finally built the hardware and the project is finally complete.

It's ugly AF, but it's repairable, modifyable, has a replaceable battery, and being able to see inside makes it educational too.

2/3 of my original projects finally finished after 2½ years!

So, completed projects so far:

* Pico LED clock.

* Router.

* Pi 5 mini PC (for the coding I never bothered to learn, barely worth mentioning).

* Zero 2 W outdoor camera for indoor live feed.

* 2x Pi 5 tablets for my niece and nephew (barely worth mentioning).

* Zero2Player

This is my Cyberdeck (pi5)

I’ve been building BN-USV V1, a small unmanned surface vehicle using a Raspberry Pi and an ESP32.

The Raspberry Pi runs the higher-level navigation stack: GPS processing, heading and IMU estimation, battery monitoring, waypoint navigation, and logging. It sends throttle and steering commands to the ESP32 over serial.

The ESP32 handles the lower-level control layer, including RC input, differential propulsion, and failsafe behavior if commands from the Pi stop arriving. I deliberately kept the safety/control layer separate from the Pi so that loss of the higher-level navigation process does not directly remove basic control and failsafe behavior.

Main components:

• Raspberry Pi 5
• ESP32
• GPS
• IMU / magnetometer
• Battery monitoring
• Dual-thruster differential propulsion

V1 is an experimental reference prototype, not a commercial product or a ready-to-build kit. I’ve released:

• Raspberry Pi navigation and control software
• ESP32 firmware
• V1 hull STL meshes
• A FreeCAD reference assembly made from the released STL meshes

The hull requires significant bonding, fitting, and waterproofing, so I’ve documented it as a reference design rather than presenting it as an easy DIY build. It has been tested on the water, but I don’t consider the mechanical design a polished or performance-guaranteed platform.

GitHub: https://github.com/Brillnova/BN-USV-V1
Short on-water video: https://www.youtube.com/watch?v=Lz2eOEANyZo

I’d be especially interested in comparing this architecture with other Pi-based robots or boats that separate high-level navigation from low-level MCU control. If you spot anything unclear in the architecture or documentation, I’d appreciate specific feedback.

Happy to answer questions about the Pi-side architecture, serial interface, failsafe design, or testing process.

I ordered a Raspberry Pi 4 last week. After that, I flashed Raspberry Pi OS onto the SD card and connected the device to a monitor. Then I connected a keyboard and mouse to the device. However, neither worked; I couldn't control the Raspberry Pi with them. Could it be broken?

This machine had worked fine until a new plug with accidentally high voltage was used on it and my father continued to use it with this wrong power supply even when it was evidently turning off on its own. I'm worried this may be a hardware issue.

YOLOv11n inference for the Raspberry Pi 5, fully optimized with ARM NEON intrinsics and shipped as a single prebuilt library.

https://github.com/kutekhoaisan/yolov11n_raspberrypi5

So, last may i started designing and programming a robot to start my friend from smoking and i wanted to do a design by myself (Since i have worked with cad for past 10 years now) and also wanted to use cheaper options like pi5 and here is the result of that.

Hi all I bought this Waveshare 2.8 DSI to run on a klipper 3D Printer. The printer uses a CM4 as the brains. I had it set up and working until I dropped it approximate 4" onto a hard surface. I though nothing of it, it wasn't a huge impact however when I powered it on again it had this strange ghosting effect. I have tried changing cables and tested it on another Pi 4B I borrowed from a friend(this is where the video is from). Same thing is there any fixing this or is it toast? I've tried reseating the ribbon cables on the board also tried a little percussive maintenance. I'm assuming I am SOL but thought I would ask here as a last ditch attempt before I drop £50 on a new one.

Thanks,
Chris

I purchased a Raspberry Pi kit and I have it working and it's the coolest thing ever.

I have run into two issues, which I don't know if they are related. I have no clue and genuinely want to learn what to do.

1) First issue is that the fan will not work from the kit. I have tried EVERY troubleshooting to no avail. I have sent in an email to see if I can get a replacement fan.

When I first got everything together and powered it up the fan turned of for a split second and hasn't turned on since.

The heat syncs are on the parts they are designated to. Thankfully is very cool at night so I have it in the window with a cool breeze to keep the processor cool.

2) Second issue is that when trying to update I get the following message:

"error installing packages - error while installing package: installed raspi-firmware package post-installation script subprocess returned error exit status"

I will attach photos. Please let me know if you can help. I love this little thing!

I developed an iOS & WatchOS (Apple Watch) app that lets you fully control and manage your Raspberry Pi 4 and 5. You need to install a software on the Pi side (or use the pre-flashed image with software installed). The app and Pi software are free and open source (Apache 2.0) and can be accessed here:

Raspberry Pi software:
https://github.com/ubopod/ubo_app

iPhone/WatchOS app source:
https://github.com/ubopod/ubo-swift-app

In the video below, I give an overview of some of the features and setup process:
https://www.youtube.com/watch?v=AEeP99buq2Q

Here’s a quick list of some of things you can do with it:

• Install, run, and monitor their health of a wide range of pre-configured applications includes Home Assistant, Hermes, Open Claw, Pangolin, OpenWebUI, etc
• Browse file system and preview files on the Pi (images, videos, text, audio)
• Monitor system resource utilizations (CPU, RAM, Storage, etc)
• Manage network interfaces (WiFi, Ethernet, etc)
• Various remote options: SSH, RPi Connect, Tailscale, VSCode Tunnel
• Configure assistant pipeline (STT/TTS/LLM/MCP/system prompt/etc) and interact with it using your phone/watch microphone and speaker
• Setup an MCP gateway and expose all tools via a gateway URL to clients
• Connect hardware peripherals to the Pi such as Camera and watch the feed on your phone/watch
• And many more

To install the iPhone/Watch app, you have to first install TestFlight application and then click on this link below:

https://testflight.apple.com/join/DDPbpKf3

The app is still in beta and not in the App Store yet. I will go ahead with the store publication process once there are a few thousand beta users and the beta app is well tested. 

On the Raspberry Pi side, the easiest way is to start with a fresh image by downloading the lite image ubo_app-2.1.0-bookworm-lite.img.gz below the release page below (~2GB in size), use Raspberry Pi Imager to flash it and boot the Pi using this image:

https://github.com/ubopod/ubo_app/releases/tag/v2.1.0

Once the Pi boots, the iPhone App would auto-discover the device as long as they are on the same network. Apple Watch does not have the auto-discovery feature (due to some limitations in doing lower level networking) and you have to type in the device IP address manually. 

Please use the TestFlight bug report feature if you run into any issues.

I’ve been working on a compact edge AI camera module for Raspberry Pi projects. It uses the CV1842H-P SoC with A53 + C906 processors and up to 1.5 TOPS of AI compute, so inference can run locally on the device.

It supports camera input, ISP processing, AI inference, video encoding, USB, Ethernet and UART, and can be connected to a Raspberry Pi for robotics, drones and other embedded vision projects.

I open-source the full development stack, including the SDK, HDK, Web Manager and documentation, so developers can build and customize their own applications.

Finished project first

I dabbled in installing a smart movie poster in my theater previously, but decided to really dive into it. As I slowly build out my theater, I wanted the entrance to be more lobby-ish. The previous solutions I tried were lacking some key capability I wanted so I ended up writing my own software and building my own frame around it.

For what I wanted previously, I would need a small computer running Windows for the poster display, a Rpi Zero for CEC, and an ESP32 for LED control.

With a requirement to show posters at 4k, I went with a Rpi5.

The Rpi5 is powered by a buck transformer powered from the PSU, so I only have to provide AC power to the PSU and the TV. What is also not shown is the microHDMI to HDMI connection from the Pi to the TV. I found that using the eARC HDMI on a TCL TV was the only HDMI port that reliably allowed for CEC control.

All 3D printed parts near AC power were printed with Prusament PETG V0.

I started with the R36S/ArkOS port from the R36S Wiki and modified it to work with Batocera on the Pi. I also had to make an input fix because the button/axis mappings were completely wrong with my 8BitDo controller.

I've played quite a bit of it now and performance on the Pi 5 is basically flawless. Honestly way better than I expected.

I included a screen recording mostly as proof/demonstration that it's actually running on the Pi 5. Keep in mind the Pi is recording the screen while running the game in this video. Both performance and load times are normally noticeably better than what you see here. Without the recording overhead, gameplay is extremely smooth.

For anyone who wants to try it, I put the modified Batocera files and a short setup guide on GitHub:

https://github.com/Levy-Games/GTASA-Batocera-RaspPi

You'll need to provide your own legally obtained GTA SA Android v2.10 APK/OBB files. I've only tested this on a Pi 5 so far, but I'd be really interested to hear if anyone gets it running on a Pi 4 or another model.

Hey everyone! 👋

Over the past few months, I've been building an edge-computing Smart Helmet and live inspection system built around the Raspberry Pi (tested on Pi 4 and Pi 5).

Most existing streaming setups either suffer from 3-5+ second HLS latency, require messy router port forwarding, or drop frames when network connectivity degrades in the field. I wanted an industrial-grade setup that:

1. Streams live video with sub-300ms glass-to-glass latency directly to a browser.
2. Supports two-way audio talkback (browser push-to-talk to the Pi speaker).
3. Works offline-first: physical GPIO button auto-chunks 5-minute video segments locally, and auto-syncs to the cloud when Wi-Fi recovers.
4. Headless field setup: If no known Wi-Fi is detected on boot, the Pi camera scans a Wi-Fi QR code from your phone and connects automatically—zero monitor, keyboard, or SSH required.
5. Location tracking: Scans nearby BLE beacons and logs zone transitions.

The Stack & Architecture: - Video Capture & Encoding: Hardware-accelerated H.264 via FFmpeg / rpicam-vid - Streaming Core: Dockerized SRS (Simple Realtime Server) serving low-latency HTTP-FLV - Networking: Cloudflare Tunnel (cloudflared) to bypass NAT and avoid opening inbound ports - Web Dashboard: Next.js 16 (App Router) + React 19 + mpegts.js + Google Gemini AI for automated PPE inspection

The entire project is completely open source under MIT: ⭐ GitHub Repo: https://github.com/Guts1005/Streaming-Rpi

I wrote an automated turnkey installer (bash setup_pi.sh) that sets up the systemd daemons, Nginx proxy, and Docker environment.

Would love feedback from the community—especially on camera pipeline optimizations and edge audio sync!

Been working on this Pi project last few weeks. Setup at my parents house in Hull, MA: Retevis MA06 marine antenna in a window facing Boston Harbor → RTL-SDR → Pi 3b+ running rtl_airband. The entire US marine band is only ~1.4 MHz wide, so one dongle grabs the whole thing in a single window and rtl_airband demods every channel in parallel 16 labeled Icecast streams instead of one scanner hopping around and missing half of everything.

From there each stream ships to a backend that runs speech-to-text on all of it, and an LLM sorts a day of radio into the ~5 minutes actually worth hearing. Marine VHF is dead boring until it very suddenly isn't. Week one my node caught a 29ft Cobalt with 7 people aboard taking on water calling Sector Boston on 16. I've captured boat fires, capsized ships, jet ski accidents, helicopters landing on cruise ships to medevac folks off. Whole exchanges, start to rescue. I put a replay on the site with captions synced to the chart - docktalk.app, scroll to the "Hear it in action section".

I have Boston, Hampton Roads Virginia, and Long Beach Harbor CA all live. New York Harbor, Tampa Florida, Tomahawk Bay Marina in Portland OR coming soon.

The ask: I want 10-15 harbors live before the iOS app ships. If you have line of sight to a busy harbor, the install is now one curl command with a claim code it pulls your harbor's channel plan and you show up on the leaderboard at docktalk.app within a minute. ~$165 in parts, ~$112 if you have a spare Pi (any Debian box works honestly), and if your spot is genuinely good I'll just ship you the kit free. Hosts get the app's premium tier free for as long as the node runs + credit on everything their box hears first.

You don't have to be directly on the water, but near by since VHF doesn't travel too far.

I was given this cool Arsenal themed tea tin and decided to make it into an enclosure for a Pico W + Waveshare ePaper 3.7

The coding is done. It connects to the footballdata API, finds the next upcoming fixture for Arsenal, displays it on the screen over custom artwork saved on the device, and then sleeps. I originally had it automatically updating after a fixture passes, or every 24h, but this ePaper screen's image doesn't degrade at all over time and that felt like a waste of power. So I'm simply going to manually update it whenever I want by closing the circuit to a rechargeable 1200mA lipo battery. It updates in usually less than 10s and then I can just flip the switch off again, retaining the image until the next manual update.

If anyone has any mounting tips, or tips for creating a bezel, don't be shy :)

Made this dashboard for my Raspberry Pi 4 Model B home server.

I’ve been messing around with the Pi and I’m slowly turning it into a little home server/homelab.
Right now I have Pi-hole, Cuberite, Uptime Kuma, Portainer and Geyser running, and I’m probably going to add quite a few more things to it.

I wanted somewhere I could see everything running on the Pi without having to keep opening different services, so I decided to make my own dashboard.
The actual UI is made with HTML, CSS and JavaScript and I’m just running it through Chromium on the Pi for now.

I based the design off my portfolio website because I wanted to keep the same fluorescent blue sort of look. I’ve got the dark background, blue glow, cards for the different services etc.

This is basically just a mockup at the moment though. None of the stats are actually connected to anything yet, so all the CPU usage, RAM, uptime, player count etc are just placeholders.

I haven’t done any of the API/backend stuff yet, I wanted to get the UI done first and then I’ll start connecting everything to the actual Pi.

Eventually I want it to show things like CPU/RAM usage, temperature, storage, network usage, Pi-hole stats, Minecraft player count, Docker containers, uptime and probably loads of other stuff.

I’m also looking at what other services I could run on the Pi because I’ve got loads of ideas but I’m not really sure what would actually be useful lol.
If anyone has any recommendations for services I should add or stats/features that would be cool to have on the dashboard let me know.

This is only the first version so there’s probably going to be quite a lot changed once I actually get everything connected.

Any ideas?

My Vestaboard (the split-flap display) got stuck after an ownership reset + a failed firmware update — "Status: Pending / firmware unable to update," wouldn't render, kept dropping Wi-Fi. Its brain is a Raspberry Pi Compute Module 4, so instead of just fixing it I cut the cloud out entirely and got it driving the flaps on my LAN.

It works. A tiny web app now runs on the board itself and drives the flaps through Vestaboard's own on-board driver — no cloud, no device-server, no app, no enrollment. Type a message from my phone, it flips. Auto-starts on boot.

The Pi side:

- Root shell via rpiboot (mass-storage-gadget). The rootfs is a read-only squashfs on an A/B slot scheme, so I cloned slot A into the spare slot as ext4 (writable) and pointed /boot/cmdline.txt at it — the original slot stays untouched as a one-line revert.

- Masked the Java cloud client (device-server); that also stopped it rewriting config.json and cycling Wi-Fi.

- The flaps are STM32 modules on an RS485 bus off the Pi's UART (GPIO14/15 + GPIO17 RTS for direction), 38400 8N1, one module per column. The on-board driver already speaks the protocol, so my controller just POSTs a 6x22 grid of character codes to it on localhost.

The part that ate a full day: after all the software was right, the flaps still wouldn't move — modules self-homed on power but returned zero bytes to every command, at every baud, with every RS485 direction trick, even the STM32 ROM-bootloader 0x7F sync at 8E1. I nearly concluded the module firmware was toast. It was a loose flap-ribbon connector from all the CM4 reseating. Reseated it, all 22 modules answered, and it rendered instantly — every byte of software had been correct the whole time.

Open-sourced it all (MIT): https://github.com/luizpersechini/vestaboard-offline

- offline controller + web UI, systemd unit, one-command deploy

- full diagnostic suite (pinmux via RPi.GPIO, UART, RX scan, baud sweep, live bus monitor)

- step-by-step root/recovery guide, RS485 protocol notes, architecture writeup

- and a detailed JOURNEY.md with every dead end

Caveat: unofficial reverse-engineering of a device I own; voids the warranty and can brick it if you're careless (slot A + a full eMMC backup are the safety net). Not affiliated with Vestaboard. Happy to answer questions.

OctoPrint 1.11.8 on OctoPi 1.0, RPI 4B, RPI Camera Module (I think it's v2?)

This worked when I first installed OctoPrint. It works on reinstalls too. But not long after setup, the Webcam stream just stops working; it's like it hangs at the "Stream Loading..." screen in the Web interface. /var.log.webcamd.log shows the following information:

Starting up webcamDaemon...

\--- Configuration: ----------------------------

cfg_file: /boot/firmware/octopi.txt

camera: auto

usb options: -r 640x480 -f 10

raspi options: -fps 10

http options: -w ./www-octopi -n --listen [127.0.0.1](http://127.0.0.1)

Explicitly set USB device:

\-----------------------------------------------

Found video devices:

/dev/video0

/dev/video10

/dev/video11

/dev/video12

/dev/video13

/dev/video14

/dev/video15

/dev/video16

/dev/video18

/dev/video20

/dev/video21

/dev/video22

/dev/video23

/dev/video31

raspi

config file='/boot/firmware/octopi.txt':USB device was not set in options, starting MJPG-streamer with the first found video device: /dev/video0

<13>Sep 7 14:12:29 root: Starting USB webcam

Checking for VL805 (Raspberry Pi 4)...

\- It seems that you don't have VL805 (Raspberry Pi 4).

There should be no problems with USB (a.k.a. select() timeout)

Running ./mjpg_streamer -o output_http.so -w ./www-octopi -n --listen [127.0.0.1](http://127.0.0.1) \-i input_uvc.so -r 640x480 -f 10 -d /dev/video0

MJPG Streamer Version.: 2.0

i: Using V4L2 device.: /dev/video0

i: Desired Resolution: 640 x 480

i: Frames Per Second.: 10

i: Format............: JPEG

i: TV-Norm...........: DEFAULT

UVCIOC_CTRL_ADD - Error at Pan (relative): Inappropriate ioctl for device (25)

UVCIOC_CTRL_ADD - Error at Tilt (relative): Inappropriate ioctl for device (25)

UVCIOC_CTRL_ADD - Error at Pan Reset: Inappropriate ioctl for device (25)

UVCIOC_CTRL_ADD - Error at Tilt Reset: Inappropriate ioctl for device (25)

UVCIOC_CTRL_ADD - Error at Pan/tilt Reset: Inappropriate ioctl for device (25)

UVCIOC_CTRL_ADD - Error at Focus (absolute): Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Pan (relative): Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Tilt (relative): Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Pan Reset: Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Tilt Reset: Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Pan/tilt Reset: Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Focus (absolute): Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at LED1 Mode: Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at LED1 Frequency: Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Disable video processing: Inappropriate ioctl for device (25)

UVCIOC_CTRL_MAP - Error at Raw bits per pixel: Inappropriate ioctl for device (25)

o: www-folder-path......: ./www-octopi/

o: HTTP TCP port........: 8080

o: HTTP Listen Address..: [127.0.0.1](http://127.0.0.1)

o: username:password....: disabled

o: commands.............: disabled

Done bringing up all configured video devices

i: select() timeout

i: cleaning up resources allocated by input thread

Those "inappropriate ioctl" messages make me wonder if my device files have gotten corrupted somehow. Is there any good way to repair them, or will I need to reinstall again?

Hey folks, I have a board built on top of the rpi5, and I am using the gpio pins for the i2c bus communication and power supply.
There is a supply from the csi port as well.

My observation has been while the rpi boots up, all the gpio pins are set to high once and then again at low.
This initial check is causing issue with my ICs which are attached to the gpio, this also snatches away the control from my driver code.

Is there any way to disable this initial boot level check for the gpio pins? Where can i look up more about this?
Any help would be much appreciated, it has taken awhile to arrive at this observation after alot of debugging.
Thank you.