IpCamera: New IP Camera Binding

I’m not able to read what function this binding will have? Rtsp mjpeg convert? Ptz control?

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.

Terrible start.
You should always discuss how features will work before they exist.


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.

Why not combining forces?:



I have already sent an email to Thomas and also posted in that thread to see if it is possible to join forces.

1 Like

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.

1 Like

Foscam FI9826W + FI9826P v1/v2 + FI9821 v2
CGI User Guide contains all commands

typical address for getting MJPEG stream:

1 Like

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 :slight_smile: but does blueiris also support webbrowser support including speaker/mic audio (without activex etc)?

ps: currently I’m using nexus cameras (in my case model 235fw). they support onvif. as streaming protocol only rtsp.

cant beat free :slight_smile:

You can if it’s a lame implementation…

1 Like

you get the point

@DubZ yes you could potentially use the binding with the right camera if I am successful for a doorbell with two way audio. You may be interested in this upcoming product on page 18 as it will support the same api that I will be using.

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 .

1 Like

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” 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.

I open my cams trough a http-link in habpanel, works perfect

1 Like