Camera not visible on Prusa Connect, but working on Prusa Link  

RE:

SAME BRO!!!

Wow, just installled my Pi Zero W with Camera THIS night; practically at the same time you posted. What a coincidence. Anyways, I vote bump, since I am at the same point with the same problem. Dunno if a (faster) Zero 2 W can help. There was a hint in the setup steps that the Zero W is too slow. But I would love to have multiple cameras in my Original Prusa Enclosure. Or just one working one for starters, so I can check my printer remotely while I am at work.

Mit besten Grüßen,

Lucas

RE: Camera not visible on Prusa Connect, but working on Prusa Link

same, have 3 printers and all cams just stopped working in connect, they are all working in link.

just says "The snapshot is not available" on newly imaged raspie, the other two just say image is older then 1 hour, last image captured "Snapshot time2/16/2024 4:03:28 AM"

makes it hard for folks to print, since these are all at a makerspace, and people start prints from home, they need to see status of bed before printing, and monitor their prints...

troubleshooting today, i re-imaged one of the raspberry pies (4), confirmed they are running latest version of image.

link for one i reimaged today

connect for the one i reimaged today

link for one of the ones i have not re-imaged

RE:

I am having the same issue! Earlier today my camera was working fine. All of a sudden, I get a black screen, or an error message. Does anyone know of a fix? Please help. I vote to bump this thread!

I am running a USB webcam connected to a laptop. When I follow the QR code to link the camera to Prusa Connect, my camera works live for 5-10 seconds then the screen turns black and says error at the top right corner. One time instead of the screen turning black, it turned a tinted purple color like the picture at the very top of this thread.

RE:

AFAIR people from Prusa said on Discord they had to disable images otherwise they would make other parts of the platform unstable, so they sacrificed images in order to make anything else working.

This was few days ago, though.

https://forum.prusa3d.com/forum/bugs-errors/camera-feed-no-longer-updating-in-prusa-connect-but-still-updating-in-prusa-link/#post-699682

RE: Camera not visible on Prusa Connect, but working on Prusa Link

Update for help diagnosing this issue:

When I use my iphone, camera always works on Prusa Connect. When I use a USB webcam connected to a laptop the problem always occurs. 

I tried using two different USB webcams. I tried restarting my computer. I tried using two different computers. The problem still does not go away.

Everytime I go to webcam.connect.prusa3d.com my camera shows up and I see a live feed. After 5-10 seconds, the screen either goes black, or it says "connecting camera" or gives an error at the top right corner of the screen. When I close and reopen the browser, camera comes up fine again for 5-10 seconds before encountering the same issue. This whole time, my iphone camera works. However, I tried using two different USB webcams, and two different computers, the issue always happens with the USB webcam. Hope there will be a fix soon. 

RE: Camera not visible on Prusa Connect, but working on Prusa Link

Thanks for letting us know! Hopefully there is a fix soon.

RE: Camera not visible on Prusa Connect, but working on Prusa Link

UPDATE:

Suddenly, camera starts working again in Connect! So it has to be related to upgrade of Prusa Connect platform.  No more issues 🙂

RE: Camera not visible on Prusa Connect, but working on Prusa Link

Yup, all should be well in camera land now. Thank you for your patience

RE: Camera not visible on Prusa Connect, but working on Prusa Link

It still isn't working for me. I'm using the docker container to push from a "other camera". Below is some test code I created. It finishes without an error but the in MK4's Connect web page it says "The snapshot is not available". It has been this way for some days. The jpg file is about 112K bytes so size should be ok. Any ideas? I have removed and re-added the camera a couple of times to no avail.

            curl -X PUT "https://webcam.connect.prusa3d.com/c/snapshot" \
                -H "accept: */*" \
                -H "content-type: image/jpg" \
                -H "fingerprint: camera0000000001" \
                -H "token: The_Token" \
                --data-binary "output_0.jpg" \
                --no-progress-meter \
                --compressed

RE: Camera not visible on Prusa Connect, but working on Prusa Link

follow up to this post, cameras all started working about 48-72 hours later. 
all three are mk3s, i am running them on individual raspie 4s, 8gb i think. each pie has 2 cams (plugged directly into them), one for first layer and one for bed overview.

RE: Camera not visible on Prusa Connect, but working on Prusa Link

My two cameras running from two separate RPi's stopped working a few days ago. They are still not working in Prusa Connect. The image file is updating on the local file system, so the image is changing. It appears to send to Prusa Connect OK because my script monitors for errors, and prints log info if curl fails for some reason to Prusa Connect, but no log messages show up. Therefore it looks like they're being sent okay, but Prusa Connect web app is not updating the image. The image placeholder appears to update every 10 seconds, as I see an update icon appear and disappear about every 10 seconds, but the image never changes. It's shown "Image is Old" for a couple days now. I've tried everything I can think of on the Pi side. It had been working well for a couple weeks, but not in the last few days.

RE: Camera not visible on Prusa Connect, but working on Prusa Link

I found this post that mentioned to send a content-length header set to the size of the image (in bytes) in the PUT request. This appears to have fixed it for me! This is the only place I found this requirement documented.

In my script (modeled after many prusaconnect_upload_cam.sh scripts found on github and forums), I added the following code to grab the image file size in bytes and send the value as the content-length header value:

 # POST the image to the HTTP URL using curl
IMAGE_SIZE=`wc -c < /tmp/output.jpg`

curl -X PUT "$HTTP_URL" \
    -H "accept: */*" \
    -H "content-type: image/jpg" \
    -H "content-length: $IMAGE_SIZE" \
    -H "fingerprint: $FINGERPRINT" \
    -H "token: $TOKEN" \
    --data-binary "@/tmp/output.jpg" \
    --no-progress-meter \
    --compressed

I also discovered that the image on Prusa Connect does not seem to update if the printer is status is OFFLINE. My XL happened to be turned off (was leaving it on, but after it blue screened the other night for no reason when sitting idle, I didn't trust leaving it on alone as much as I did prior) when I put the above change in. Still no update on Prusa Connect, so I tried turning the XL on. Once the status changed to IDLE, the image refreshed and kept refreshing every 10 seconds like it was a week or so ago.

To test the hypothesis, I powered down the XL. Again, after the status read OFFLINE, the images stopped updating. After 3 minutes, I powered the XL back on. Sure enough, once the printer status was IDLE, the images started to refresh again.

Interestingly, my script did not report any error sending the images to Prusa Connect when the printer status was OFFLINE. It appears the server accepts the image, but just doesn't update the image on Prusa Connect. This is rather puzzling why no error would be returned that I could then parse with the script again.

I'm currently running my old MK3S printer with Octoprint and have been since I built it. I wanted to add it to Prusa Connect to try it out and also have both printers on the same platform for easily monitoring remotely. However, I still want to use Octoprint to send G-code to the printer as I have other automations that I'd like to keep (auto power off the printer when done, for example) and Prusa Connect does not offer this functionality. I tried running Prusa Link from the RPi I have the webcam connected to, but then Octoprint doesn't work because Prusa Link and Octoprint can't both use the serial connection at the same time. A couple weeks ago, I go the webcam running on Prusa Connect and printing files from Octoprint. Both worked together side by side, and I was happy. Now it seems that Prusa Connect requires the printer not be in the OFFLINE state for images to update...

Maybe this info will help someone else that's confused by Prusa Connect webcam images not updating.

RE: Camera not visible on Prusa Connect, but working on Prusa Link

Hi, yup, this is how that will work from now on, sorry. We are trying to reduce the load on our camera backend after it caused problems with Connect stability, unfortunately I do not see an easy way to have both until someone reverse engineers Connect to work with Octoprint. Which I would find hilarious

RE: Camera not visible on Prusa Connect, but working on Prusa Link

Ok, got the same problem. Just installed the prusa connect camera script ( https://nvtkaszpir.github.io/prusa-connect-camera-script/test.config/) on Raspberry Pi 3 and find out it's working without doing anything on Prusa Link, but not on Connect. Actually I kind of have to kill the user using PrusaLink to test sending status, so I guess "prusalink" take the camera first, because the the script Fail on booting as a service.

Will check for any development on this forum. 

RE:

Oh man, All i had to do, is to activate the "connect button" for camera from Prusa Link !!! Then it just work. Even the token seems to be useless. I guess all the "Prusa connect camera script" installation was useless, it just work. 

RE: Camera not visible on Prusa Connect, but working on Prusa Link

🙂
so I guess I can close this issue on github? 

My script was never intended to be executed on the same machine where PrusaLink runs (especially with the same camera device that PrusaLink uses).

RE:

No.

the camera disconnect.

I have to log in again into Link and then it worked on my Mac and not my iPhone. 
I don't know exactly what is going on...

A problem, for sure, it's that you have to link into "link" (so use your local IP address) instead of just working using Connect...