This binding is now merged into openHAB 2.5.9 and newer.
See below for more details on what each brand of camera has working as often choosing the right camera will save you from needing to purchase an extra video server (both the cost to purchase the server, plus the ongoing electricity costs) to process the video feeds.
Features for Generic cameras with only RTSP (no snapshot url):
Snapshots (jpg) can be created from RTSP with low CPU overhead but requires non stop network traffic to keep a running RTSP stream. Much lower network traffic for cameras that have a snapshot url.
Ability to create mjpeg streams from RTSP on demand. High CPU overheads for this ability that stop when you close the stream. More than a few of these cameras open at the same time and you should look at a dedicated server, or better cameras with an API.
Can use FFmpeg to create motion and audio alarms. High CPU load, consider external zwave or zigbee PIR sensors or ONVIF/API cameras if this is an issue. You may also need to create a rule to change the motion settings when night vision is used, or simply put up with more false positives, some API cameras automatically change settings for you at night greatly simplifying setup.
A group of cameras can scroll through in a set order on your TV and if motion occurs the camera with motion can skip the cameras with no motion.
Binding allows the use of an external PIR sensor (zwave PIR for example) to unlock the features that require a motion alarm like the feature mentioned above.
Ability to create an animated GIF that can be emailed or sent via pushover or other services to your mobile phone.
HLS video streams can be produced with FFmpeg for any camera that uses a h264 format. This stream can be used in compatible browsers or cast directly to Chromecasts for high res and FPS video.
Features for Generic cameras with snapshot and RTSP ability:
All the above feaures, PLUS the ones below.
Can create 1 FPS mjpeg feeds from cameras with a snapshot ability without using much CPU power and low network traffic.
Features for ONVIF cameras with no API:
All the above features, PLUS the ones below.
Some cameras will gain ONVIF Alarms/Events.
PTZ movements with all three Onvif movement methods now working.
Easier setup due to auto discovery of the camera and also the snapshot and rtsp urls.
PTZ preset recalling if the presets are created in another app like Onvif Device manager.
Features for cameras with API and ONVIF ability:
All the above feaures, PLUS the ones below.
MJPEG video streams with high FPS and next to no CPU load.
Motion Alarm features (very low CPU usage as it does not need ffmpeg) for Amcrest, Dahua, Doorbird, Foscam HD, Hikvision and Instar cameras.
Enable/Disable the motion alarm with Amcrest, Dahua, Foscam HD, Hikvision, and Instar.
Advanced SMART alarms with HIKVISION and Amcrest/Dahua only. Line crossing, Face detection and many more should now be working. Most of these are now added to ONVIF thing type if the camera sends the correct data.
Audio Alarm features with (very low CPU usage as it does not need ffmpeg) Amcrest, Dahua, Foscam HD, Hikvision and Instar cameras.
Audio Alarm THRESHOLD control feature with Dahua and Instar (100 levels of control), Foscam HD (3 levels only).
Control over the Infrared LED is now possible with Amcrest/Dahua, FOSCAM HD and INSTAR HD. Amcrest/Dahua have control over the brightness, where Foscam and Instar are just on/auto and off.
External Alarm inputs with Amcrest, HIK and Dahua. Could be used for a doorbell button.
External Alarm output switching with Amcrest, HIK, Dahua and Doorbird. Could be used to trigger a doorbell buzzer.
Text overlay on top of the video stream for Amcrest/Dahua, Instar HD and Hikvision.
API cameras reported as working
If missing, it just means no one has reported back (it probably works just fine if not in this list).
Just create an ONVIF binding. Creating separate code for different cameras will be extremely hard to maintain as there are no standards, except ONVIF. I use BlueIris and it integrates beautifully with OH.
If you are indeed decided on making API BASED binding for cameras, you will need to implement something as massive as this
First off the binding does not exist yet, only a concept and a few lines of code currently. I have spent a while looking into what is possible to ensure what I create will get what I need running.
It is my understanding in regards to mjpeg and other stream formats openHAB’s infrastructure does not support it in at least some of the user interfaces. Mjpeg is the only format currently to work in all the different user interfaces that openhab has to offer. My ideas are to offer two streams, one which is high res for internal network use and a second for off site storage and viewing. Snapshots also.
But please let’s not discuss how features willl work when they don’t exist. Instead I would love to hear from people what they currently have working and what they wished would work.
I agree @luckymallari that onvif would be an excellent binding to have in openhab. I would like to see it added as well.
The bottom line is I don’t believe I woULD be able to get my
Cameras working with all features by using onvif without resorting to using a combination of both methods which is more work.
I will be happy if I can get four or more camera brands working, since I don’t get paid and won’t go buying loads of cameras to test with it will be limited to what other kind users contrIbute towards helping others out for free.
First off the binding does not exist yet, only a concept and a few lines of code currently
Yes I got this. That’s why I used the word “will”
but please let’s not discuss how features willl work when they don’t exist
I was not just asking how it works, I was asking about what features you are talking. I don’t know what problem your probably future binding is going to solve? Maybe it’s just me who didn’t read that out of your text. But would be nice to explain it a bit more at least for me
Since I am writing this to get my setup working The features will be the ones I need to implement a baby monitor and general alarm and security uses. My camera has the ability to do audio alarms and adjust the alarm threshold by its API so I will be able to get a message on my tv from openhab warning me the baby is crying and I can then view with night vision into the room with ptz controls and have two way audio.
Does that answer your questions? I could take your question as meaning a few things.
If you have a camera that is onvif. Find out what profile it is and look up what may or may not be supported in this document here.
What I am needing to do is not covered by the onvif standard yet my camera does support it by an api.
For those interested, as I mentioned above, BlueIris does wonders. You can set triggers based on motion, time, audio, etc, and has already implemented APIs from TONS of manufacturers, of course, including ONVIF. BlueIris also integrates with OH well. You can run a command, call REST, trigger a GPIO, etc based on the triggers. Has an iOS, Android, and Windows apps also.
@matt sounds interesting. so did I understand it correct that I could also use it as door phone?! what I’m searching at the moment is the possibility to transfer not only video, also audio via webbrowser and I wanted to read more about webrtc which seems the only possible way (for tablet browser without flash, silverlight etc.)
@lucky blueiris costs sth. so if there is someone who wants to create a binding for free… perfect but does blueiris also support webbrowser support including speaker/mic audio (without activex etc)?
But I would hold off until I get to play with my amcrest to see what is possible and what compatibility issues I may hit. Currently it sounds like you have more experience with ip cameras than I do so things like what you posted about getting 2 way audio in browsers is something I will need to look at it more depth before making a feature promise on what can be done with a binding that does not exist. I’ll look at the two way audio first then because if an issues arises then it may change how I tackle this.
matt1, I have a Lorex LNR 1182, the Cameras are a mix of LNB4163-C and LNB4173-C … I’m not sure of the HTTP information you need. I have to use a program called FLIRCloudClient to be able to remotely view the cameras from a computer or android smart phone.
I had a quick look and it appears the Lorex do not have an API (at least easily found) so you would be limited to what your camera has implemented in ONVIF or RTSP or other features it may or may not have. As my post above went into there are a number of ONVIF profiles and depending on which profile is implemented into your camera you may have only very limited controls available. Not all cameras are equal and just because it has ONVIF written on it does not mean it has everything available that the standard has defined.
The brands that I looked at that do have API’s are
HIKvision (beware of chinese fakes/clones that will brick if you try to update firmware)
With the amcrest api it allows for a lot more in depth control over the camera .
I did notice that I can log in locally with my web browser, if I type in the private IP address of the NVR and download and instal a plug-in “LOREX_webplugin version 220.127.116.11” I’m sure in order to see them outside of the network it would take some port forwarding rules in my DSL router. The sad thing about mt DSL router is that it gets its public IP dynamically, so if it reboots … it gets a new public IP.