Has any one setup a MotionEye server to feed to PrusaConnect?  

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

I wrote https://nvtkaszpir.github.io/prusa-connect-camera-script/ which can be used with various streaming options, I'll add details how to make it work with motioneye, probably using ffmpeg.

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

Thank you, I'll add that to my project list.

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

ok I've added sections for MotionEye, https://nvtkaszpir.github.io/prusa-connect-camera-script/config.for.camera.motioneye/
Tested on my Rpi4 (took more time to set the motioneye on new os due to libcamerify), snapshot is the easies to do it.

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

Thank you for your effort.  I'll try to get to this soon.  It will take a while for my 77-year-old brain to sort all this out.

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

I'm using the latest(but very old) MotionEye OS .img file - how did you use new OS and install motioneye?

Just asking I don't want to break my setup running the script - I'll use a different SD card and try with the new OS if you can tell me how to get motion eye running on the new OS

RE:

I used official raspberry os system (Debian 12 Bookworm) on Rpi 4, then followed motioneye github docs how to install it - such as adding fhanges to pip config systemwide which would break other packages, then install motioneye via pip, and so on. Also AFAIR i had to fix pip config because it ended in having duplicated lines 😉

But it was still lacking, thankfully not much change was required. I just needed to  change systemd exec command so it starts with libcamerify. More details are already on github issues or libcamerify docs.

So the systemd service is now

ExecStart=/usr/bin/libcamerify /usr/local/bin/meyectl startserver -c /etc/motioneye/motioneye.conf

root@hormex:~# cat /etc/systemd/system/motioneye.service
[Unit]
Description=motionEye Server
After=network.target local-fs.target remote-fs.target

[Service]
User=motion
RuntimeDirectory=motioneye
LogsDirectory=motioneye
StateDirectory=motioneye
ExecStart=/usr/bin/libcamerify /usr/local/bin/meyectl startserver -c /etc/motioneye/motioneye.conf
Restart=on-abort

[Install]
WantedBy=multi-user.target

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

I'm trying install motioneye on a clean "lite" version of trixie but it wouldnt work, I'll try bookworm here shortly but I feel like I'm missing something. Am I suppose to install motion first then motioneye?

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

Hey so I finally got motionEye up on the lastest distro of trixie and by a miracle I actually got your script running, I have 2 cameras but only the second camera connects. is this limited to just a single camera? my prusa tokens match up and each camera has their own fingerprint - heres what my redacted snapshot.env looks like

PRINTER_ADDRESS=127.0.0.1

PRUSA_CONNECT_CAMERA_TOKEN= REDACTED

PRUSA_CONNECT_CAMERA_FINGERPRINT= REDACTED

CAMERA_DEVICE=/dev/null

CAMERA_COMMAND=curl

CAMERA_COMMAND_EXTRA_PARAMS="--max-time 5 'http://192.168.1.5:8765/picture/1/current/' -o "

PRINTER_ADDRESS=127.0.0.1

PRUSA_CONNECT_CAMERA_TOKEN= REDACTED

PRUSA_CONNECT_CAMERA_FINGERPRINT= REDACTED

CAMERA_DEVICE=/dev/null

CAMERA_COMMAND=curl

CAMERA_COMMAND_EXTRA_PARAMS="--max-time 5 'http://192.168.1.5:8765/picture/2/current/' -o "

RE:

my script runs with only one camera, so if you have two then you need two separate instances of the script.

looking at those configs:

CAMERA_COMMAND_EXTRA_PARAMS="--max-time 5 'http://192.168.1.5:8765/picture/1/current/' -o "
CAMERA_COMMAND_EXTRA_PARAMS="--max-time 5 'http://192.168.1.5:8765/picture/2/current/' -o "

Do you mean you have two different cameras under motioneye available under different URLs (/1 and /2) ?
Which instance fails?
What does it show in the logs for the failing one?

Make sure to doublecheck fingerprint env var per each.

Also check if you can get the real image dump from the url via ffmpeg/ffplay

RE:

Yes, actually ended up figuring it out which was a miracle. While your website/github was quite detailed it seemed geared more toward other programmers which I definitely am not but I can stumble around enough I sometimes get lucky 🤣  - I actually thought about posting  a separate thread with step by step instructions for others who are like myself are not as good. Yeah, really like the script tho, I repurposed a rpi4 that was running octoprint with 2 USB webcams but when input shaping and pursa connect came out it kinda made octoprint irrelevant so I changed the rpi4 over to motionEyeOS but it wasnt being updated.

Now I have a fresh install of trixie lite running motionEye and both USB cameras now upload to prusa connect thanks to your handy script. Its handy to pull up the Prusa App for a quick glance but can still also check motionEye livestream via VPN or dyndns+portforwarding(pick your poison) - pretty slick

RE: Has any one setup a MotionEye server to feed to PrusaConnect?

motioneye nowadays has some issues with being quite old code, so I switched to mediamtx (in advanced setups https://nvtkaszpir.github.io/prusa-connect-camera-script/stream.mediamtx/) for the live stream and recording