Hi everyone, I’m having serious overheating issues with my new PiVistation 5 Hawkeye (Raspberry Pi based). Basically right out of the box, the CPU temperature jumps above 80°C within seconds of plugging it in — even without any streaming services running or anything. The fan just spins at maximum constantly and the device gets so hot I’ve been shutting it down out of fear of damaging it. It’ll hit 85°C almost immediately. I followed the setup instructions at docs.arducam.com for the PiVistation 5 series, so I’m pretty sure everything is set up correctly. Has anyone else run into this? What should I be looking at?
That does sound unusually hot. One thing that’s caught a few people with the PiVistation 5 — the camera-streamer service has some video streaming modes enabled by default that can hammer the CPU pretty hard. Could you try disabling the camera-streamer service and see what happens to your temps? Also worth running htop or top while it’s hot to see which process is eating up the CPU cycles. Let us know what you find.
Okay, so I disabled camera-streamer and it helped a bit — the temperature dropped below 80°C, but it’s still sitting around 74°C at idle which seems way too high. And if I enable libcamera_net just for periodic snapshots (not even streaming), it climbs back up to around 82°C at idle. So disabling camera-streamer isn’t really solving the core problem. Something else is going on here. Any ideas on what to check next?
Thanks for testing that — 74°C at true idle is definitely still abnormal. Let’s dig a bit deeper. Here’s what I’d like you to try:
-
When the temperature is high, run
toporhtopand look specifically for any processes related to libcamera_net or other camera services. Take note of what’s using the most CPU. -
For a clean test: completely stop the libcamera_net service and just let the Pi and camera sit fully idle for about 15-30 minutes. No snapshots, nothing. See where the temperature settles.
-
Then try enabling libcamera_net again but with a much lower snapshot frequency — say once every 5-10 minutes — and observe how the temperature responds.
That should help us narrow down whether it’s libcamera_net itself or something else in the stack.
Alright, I think I found the real culprit. I ran htop and it turns out it’s not libcamera at all — there’s a “discovery” service that’s pegged at 100% CPU constantly. I’ve attached screenshots below showing the discovery service maxing out a core, while libcamera’s CPU usage looks completely normal when it’s running on its own.
Here’s the kicker: I disabled both camera-streamer and libcamera, leaving ONLY the discovery service running, and the CPU stays at 100% and the temperature still shoots up to 80°C in under a minute after plugging in. The discovery service alone is enough to overheat the whole device.
To recap what I’ve observed so far:
- Camera-streamer off, discovery still running: ~74°C idle
- libcamera_net on, discovery still running: ~82°C idle
- Everything off except discovery: 100% CPU, 80°C in seconds
- libcamera alone (presumably with discovery too at the time): normal CPU usage
So the discovery service seems to be the real problem here.
Great investigation — that nails it down. The discovery service is designed to scan for other sub-devices on the network, but it looks like in this case it’s getting stuck in a loop or polling aggressively and eating an entire CPU core non-stop. That explains the rapid overheating even with everything else disabled.
Here’s what to do next:
- Stop and disable the discovery service entirely.
- Then start only libcamera_net (or camera-streamer, one at a time) and observe temperatures over a few minutes.
With the discovery service out of the picture, you should see a significant temperature drop fairly quickly. Let me know what you get.
Progress! Here’s what I found after disabling the discovery service:
- Discovery disabled, only libcamera running: temperature drops to around 60°C. That’s a huge improvement and actually usable.
But there’s a new wrinkle:
- Discovery disabled, only camera-streamer enabled: rapid overheating comes right back, CPUs hit 100% again. So camera-streamer also has issues on its own.
Also, I noticed something weird with the UI — the camera settings were visible initially but after switching over to libcamera and then back to camera-streamer, the settings disappeared entirely from the web interface. They’re just gone now, regardless of which mode I switch to. Screenshots attached.
So summary:
- Discovery service = confirmed bad, disabling it helps massively
- camera-streamer still causes problems even without discovery
- libcamera mode seems to be the stable path (~60°C)
- UI lost its camera settings somewhere along the way
Thanks for the thorough testing — that’s really helpful for tracking this down. It sounds like there are actually two separate issues in play: the discovery service going rogue (which we’ve confirmed), and camera-streamer having its own CPU utilization problems on this hardware revision.
The disappearing camera settings in the UI is also a known quirk that can happen when switching between service modes — it’s related to how the backend reconfigures itself.
We’ve actually just released a new optimized software image specifically for the PiVistation 5 Hawkeye that addresses these exact issues — the discovery service behavior, camera-streamer CPU usage, and the UI settings persistence. I’ve sent you the download link and flashing instructions via private message. You’ll want to use the Raspberry Pi Imager to flash it onto your SD card.
Give that image a try and let us know if it resolves everything — based on what you’ve found, it should.