IPCamera: Blank ImageUrl

Add-ons Bindings
, ,
21

Hi there,
I do have the same issue - probably.
The imageUrl channel

http://my-OH-IP:8080/ipcamera/my-cam-UID/ipcamera.jpg

shows no image (or kind of broken image, just a tiny grey dot is shown):

IPcam_imageUrl
IPcam_imageUrl1252×637 16.7 KB

At least approx. 99 of 100 trials. Sometime I do get the image, but when refreshing the browser there is no picture again. My intention is to send the “current” picture by mail when e.g. motion is detected. But unfortunately I do get only the grey dot as attachement and an error when trying to open the file whithin the mail.

@matt1 you mentioned…

… I also find the ‘Server port’ in several tutorials, but I do not find this to setup in my Thing’s config? Did I something miss out? Or has this been changed, I am on OH 3.3.0.M1 Milestone?

I already checked the readme - which is by the way great since it is detailed described - the second option for a snapshot

http://openHAB:8080/ipcamera/{cameraUID}/snapshot0.jpg

in combination with gifPreroll > 0 is also not properly working for me since it seems every 2nd file which is created is empty also. Sometimes snapshot0 is affected and sometime snapshot1 is the first one… That leads to Mails with correct picture attachment, and also sometime to broken image (same as when using ipcamera.jpg / imageUrl). I tried gifPreroll = 1, 15 pictures are then created.

Anyway, using imageUrl would be my favorite approach. Am I doing something wrong as mjpegUrl is working properly?

Edit: I forgot the logs (TRACE)…

2022-02-18 14:53:49.214 [DEBUG] [amera.internal.servlet.CameraServlet] - GET:/ipcamera.jpg, received from 192.168.178.21
2022-02-18 14:53:49.268 [TRACE] [era.internal.handler.IpCameraHandler] - Sending camera: GET: http://192.168.178.34:80/bha-api/image.cgi
2022-02-18 14:53:49.277 [TRACE] [era.internal.handler.IpCameraHandler] - HTTP Result back from camera is 	:<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
  <title>401 Unauthorized</title>
 </head>
 <body>
  <h1>401 Unauthorized</h1>
 </body>
</html>
:
2022-02-18 14:53:49.280 [TRACE] [era.internal.handler.IpCameraHandler] - Sending camera: GET: http://192.168.178.34:80/bha-api/image.cgi
2022-02-18 14:53:49.379 [DEBUG] [ipcamera.internal.MyNettyAuthHandler] - Camera at IP:192.168.178.34 gave a reply with a response code of :500
2022-02-18 14:53:49.380 [DEBUG] [era.internal.handler.IpCameraHandler] - Camera has no Content-Length header, we have to guess how much RAM.
2022-02-18 14:53:59.464 [TRACE] [era.internal.handler.IpCameraHandler] - HTTP Result back from camera is 	:--ioboundary
Content-Type: text/plain

doorbell:L

--ioboundary
Content-Type: text/plain

motionsensor:L

:

The cameras are: Doorbird D1101 and D101. Both show the same issue for imageURL. MJPEG URL is working properly.

22

First please create your own new thread and not post in someone elses that is 1 year+ old…
The gray dot means the camera is offline or can not get a real snapshot so it is keeping the stream alive with a gray dot until the camera fault is fixed.

Create a new thread with TRACE level logs when the camera connects for the first time. Press the PAUSE button on the thing, then un-pause it to trigger this to occur.

The only other thing worth mentioning is that if you have the camera open in another software or app, some cameras from Doorbird brand only allow a single connection at a time. It may even be this binding trying to connect multiple times for the stream and the snapshot that is tripping the camera up. There is a dedicated Doorbird binding you should check out.

23

Hi,
honestly my opinion is that post in a thread with exactly the same topic should be prefered as creating a new topic, since it makes it easier for someone in future to find the solution within one thread compared to several ones. But you are right, the guidline mentions that a new thread should be created. Sorry for that!

Let’s discuss in the new thread created by myself, see here.

1 Like