How do I make the camera show up in the fluid interface?
Unfortunately, the only way is by using custom firmware
yeahďźďź if you want to monitor the printer status outdoors, the app is a very convenient option.
The app doesnât work in LAN mode
Eh? The app does work in LAN mode. As long as youâre on the same local network.
(Doesnât help on the go, ofc.)
In the way Simon described, outdoors which I took to mean remotely, I donât think it does?
You can use vpn for that.
Ah I see. Yeah, my bad!
Maybe he meant your back porch. 
Here is the way to get camera feed to show up on Fluidd: Discord
Basically go to settings, camera, add new
You DO NOT need Custom Firmware for this
I ended up using the custom firmware, since in their infinite wisdom, snapmaker did not implement the hardware video encoding support present on the CPU they used. This is why the FPS is so low. On the community firmware, itâs 30fps and the CPU doesnât even get strained.
Works like a charm! Thanks much
That prompts a download of the snapshot rather than actually showing the image in the Fluidd interface 
I ran into the same issue. I wanted the stock U1 camera to actually display as a live feed in Fluidd rather than downloading the snapshot, so I ended up building a small MJPEG bridge that runs directly on the U1.
It uses the stock Snapmaker camera service, requires no external computer or custom camera firmware, starts automatically after reboot, and Iâve tested the install/recovery process on my U1.
UPDATE: v1.0.1 is now available and is the recommended release. It adds automatic recovery if the U1 stock camera monitoring session stops updating. See the v1.0.1 update below for hardware test results.
I posted the project and instructions here:
GitHub:
Hopefully this solves the issue you were running into.
Update: the watchdog testing passed and v1.0.1 is now released.
I completed the hardware testing on my U1 and observed four consecutive automatic recoveries.
The issue was that the U1âs stock camera monitoring session could stop updating after running for a while, while the Fluidd bridge itself continued running. That left Fluidd displaying the last camera frame.
v1.0.1 adds an automatic watchdog that monitors /tmp/.monitor.jpg. If the image stops advancing for 15 seconds, it requests camera.start_monitor again through the U1âs existing local MQTT interface. Recovery attempts are rate-limited to once every 15 seconds.
Importantly, the recovery does not restart unisrv, Klipper, Moonraker, or the printer. It simply asks the stock camera service to resume the LAN monitoring session.
After each of the four test interruptions, camera frames resumed automatically without manually restarting the printer or unisrv.
v1.0.1 is now the recommended release and supersedes v1.0.0.
GitHub:
https://github.com/Dr-Hack-N-Sniff/Snapmaker-U1-Stock-Camera-Fluidd
If anyone tests it on another U1, Iâd still be interested in your firmware version and status.sh output if you encounter any issues.
Thatâs interesting, because that is exactly what I was getting when I had Fluidd display the camera using the Paxx firmware.
v1.0.2 is now available.
I spent quite a bit of time testing the interaction between the Fluidd camera bridge and the stock Snapmaker camera system on my U1. This release improves coexistence with Snapmaker Orca, the Snapmaker mobile app, and Fluidd, and adds recovery handling for failed stock-camera sessions.
Testing included an approximately 6-hour print, repeated Snapmaker Orca/mobile camera use, automatic recovery testing, and a controlled failed-session recovery.
During one recovery test, the camera session in Snapmaker Orca failed. v1.0.2 detected the short failed WAN session and released the LAN monitor so the stock camera could completely shut down. That full shutdown took about 6 minutes on my U1.
After the reset completed, I started the camera from the Snapmaker mobile app, which established a fresh camera session. The camera then worked in both Snapmaker Orca and the mobile app, while the Fluidd camera also remained available.
Release:
If you test it, please let me know which combination youâre using â Fluidd, Snapmaker Orca, mobile app, or all three â and whether you encounter any camera failures.
Works, but the image is only updated when the app is open (doesnât need to be vieuwing the camera). If I have no app open, every request to /server/files/camera/monitor.jpg returns the same old image