I do have the same issue - probably.
The imageUrl channel
shows no image (or kind of broken image, just a tiny grey dot is shown):
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
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"
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
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
The cameras are: Doorbird D1101 and D101. Both show the same issue for imageURL. MJPEG URL is working properly.