unfortunately, I cannot get the ip camera binding working with my 2 Edimax cameras after setting up OH new recently with v3. It was working well few months back on v2.5.
Platform: openhabian release 3.0.1 on RPI3
Iām using the ip camera binding and a generic ipcamera Thing type. Iām configuring the snapshot and mjpeg url with information like āhttp://192.168.178.xx:yyyyyy/snapshot.cgiā (cameraās IP and http port) which provides me the image stream in a web browser. Now, the strange thing is that as soon as I enable the Thing, I cannot access the image stream at its original adress (see above) anymore. Hence, itās clear to me that I also cannot access the stream via the bindingās image url and mjpeg url channels. These channels/items though do give me a proper target url (e.g. āhttp://192.168.178.zz:aaaa/ipcamera.mjpegā being the openhab server and server port). Just no image visible there.
Any ideas or hints? Anywhere to check further? I did already restart/reboot, also reinstalled the binding, etc. (obviously checked forumā¦)
Why guess or blindly try things when you can turn on TRACE logs and get more information. See the bindings documentation and at the top is a section called how to get help.
repeatedly. (Replace x and y with the cameraās IP and port).
Again, the very akward thing - which I was hoping to give an indication of the issue - is that I cannot access the IP cameraās image anymore even at its original IP/port as soon as I activate the openhab Thing. I can again as soon as I disable the Thing.
Some cameras only allow a single connection at a time so that may be normal for your camera?
Fair point - but no, doesnāt seem to be the case. Having the Thing/Binding deactivated, I can access the video stream from the IP cam via web browser simultaneously from different devices.
What happens in the logs when you try to open snapshots.mjpeg in any web browser?
I donāt get much info in the log when accessing any url (server url, etc.). The only I get is
2021-03-03 22:34:42.442 [TRACE] [era.internal.handler.IpCameraHandler] - Sending camera: GET: http://192.168.178.xx:yyyyy/snapshot.cgi
2021-03-03 22:34:48.849 [DEBUG] [era.internal.handler.IpCameraHandler] - File server for camera at 192.168.178.xx has started on port aaaa for all NIC's.
2021-03-03 22:34:52.857 [WARN ] [era.internal.handler.IpCameraHandler] - Binding has not been supplied with a FFmpeg Input URL, so some features will not work.
2021-03-03 22:34:52.885 [TRACE] [era.internal.handler.IpCameraHandler] - Sending camera: GET: http://192.168.178.xx:yyyyy/snapshot.cgi
You dont need ffmpeg for that feature to work and you should at least see the binding report that it knows you are asking for the stream.
I have no ideas then why it stops the camera working until you disable the binding, it may be possible to cause an internal error in the camera if something was going wrong that the camera did not like. Do you know how to use wireshark? it would be interesting to see if the camera is responding at all and with what data. If you compared what happens when the binding ask VS when you ask with a browser it may provide a clue.
If you post a 2 way data trace, make sure you change the password to something you dont care about, or just edit some of the data to make it non valid.
