(beta3) Remote camera "404"
-
Latest builder is unable to connect to remote camera on RPi4, also with latest available image. Looks like when I click on one of available remote cameras the "server responded with status code 404" warning count is incremented.
-
Thanks for the report! We were able to reproduce the issue. It is a regression related to a fix in encoding camera IDs for the web page. We'll include a fix in the next release.
Meanwhile, to work around it in the Builder, you may manually enter a non-encoded camera ID to Image Source. For example,
remote:http://192.168.0.1 webcam:video0. That is, decode%3Ato:. If the camera URL contains other encoded characters, undo percent decoding for them as well. -
@Topi Thanks!
-
@Topi said in (beta3) Remote camera "404":
remote:http://192.168.0.1 webcam:video0
I tried a couple different cameraId combinations, but none of them worked.
-
Sorry, I forgot the port in my answer. I'm however a bit puzzled by the log. The camera ID
remote:http://192.168.2.59:2015/ webcam:video0seems correct to me, but the log indicates an connection attempt was made to an URL without the slash after ":2015".
To make sure that the hardware gave the name "video0" to your camera, enter the URLhttp://192.168.2.59:2015/cameras/webcam%3Avideo0/to a browser. If that works (you should get a directory listing), try re-entering the value shown in the picture. It should work. -
@Topi said in (beta3) Remote camera "404":
I typed the cameraId, instead of selecting one and modifying cameraId. It works.
