IpCamera: New IP Camera Binding

Tags: #<Tag:0x00007f01470cefc8> #<Tag:0x00007f01470cee38> #<Tag:0x00007f01470cebe0>

(Toopy) #603

The URL I used in OH works from a web browser. It’s also the URL shown in the Starvedia manual.

I’ve tried most of the Lorex links recommended by ispy in a browser before and none of them work. I’ll try the one listed for the LNC204 in OH and see what happens.


Okay, I tried this URL generated by the ispy site and it shows an image in the control section of Paper UI and in HABPanel.


The only thing it won’t do now, is update the image. Getting there.


Maybe I’m not understanding how the snapshot feature works or how the binding works, but here’s what I discovered.

I get one image in Paper UI and HABPanel, with the Generic HTTP binding, but it won’t update. If I use a browser (Firefox) and enter this URL;

The image is updated. I originally entered this URL, generated by ispy;


but as soon as I hit enter in the browser, it strips out the information before the IP Address and updates the image. Then if I switch over to HABPanel, it updates on then next update interval but won’t update again until I refresh the page in Firefox.

The URL I have setup in the binding is this one;


but I did try the other one as well and it’s the same result.

So when I use the browser, the CGI script is executed, captures and stores the JPG image and then the binding reads the JPG file and displays it.

Is that correct? If so, how to do I combine the two steps?

(Jordi) #604


I have the same problem with a Dahua camera, although I modified the POLL_CAMERA_MS the problem persists. It works well for a few hours and then the image is frozen. As you say in the camera app, it is still working correctly.

I have made some checks.
1- I’ve tried several versions of the link, all with the same result.
2- I have noticed that the link stops working, in the log nothing appears anymore about it.
3- Once it stops working, if I remove the link from the addons folder and after a few seconds I put it back, the link will work correctly again.

(Skinah) #605

@Sepultura and @yfaway

I can not reproduce this so it will need a dedicated thread with some log output and details of your setups to look at in depth. I have for the past 5? days been running Openhab 2.4 stable with a single Dahua camera updating at 1000ms intervals and it has not stopped or been restarted in that time. Image and alarms are working fine as this is my baby monitor and used very often…

A few things to look at are…

  1. Update your java and make sure it is 32bit and Version 8 zulu if under linux. Unless things have changed this is the recommended version to use.
  2. Check this is not caused by your system running out of ram or needing a bigger java stack. Search this thread for ‘OOME’ as I run mine with an increased stack size.

EDIT:Link is
IpCamera: New IP Camera Binding

  1. Run only 1 camera for testing if you have multiple setup.

(Timmi) #606

This is really cool stuff.
I played at bit with this and my cheap Clarer D200-SW dome camera.

First I tried ONVIF but the HIKVISION API is working quite well with camera model as well.
I tried the motion and line alarm as well as the refresh button which is currently enough for my setup.

Once again thank you so much for the effort.

Best regards

(YF) #607

Thanks matt1. I did get an OOM exception last week while I was using very low poll period. I just upped it to 512MB now.

I would like to clarify if there is any correlation between the poll period in the .things file vs the motion alarm? For example, if my polling period is high, says 1.5 minutes, would that reduce the chance of getting a motion alarms if the motion alarm not falling close to the polling time? Or are these two separate channels and have no correlation?

(YF) #608

So it looks like there is a direct correlation between the polling time and the motion alarm. Since setting the polling time to 1 sec, I have been getting very reliable motion alarm. I will continue to observe for the next couple days. For some reasons I always under the impression that the binding tracks the motion alarms through a separate connection.

On a separate note, a side effect of the 1 sec polling is that the event log is spammed with the image item raw data size change every 1 sec. How do you guys suppress these?

(Skinah) #609

Each brand is different. With Hikvision the alarm stream never closes so they are not connected, however with Dahua the alarm stream stops every now and then and the stream needs to be re-opened, this is where the polling timer is connected as it will check if the stream is still running and open it again if it is closed. It seems each camera keeps the stream open for a different amount of time, when open in a browser mine for example stays open for ages.

See the readme.

(Timmi) #610

You can disable the picture refresh in the thing configuration and only update the image once the motion get triggered for example.
Best regards

(Frank) #611

Hello … I am relatively new to Openhab and very new to this camera binding … so please, bear with me.
I have my Amcrest camera connected to Openhab and I am in the process of configuring the system.
Motion Detection works in principle, I just need to finetune it to my specific setup.
I like to be able to send a snapshot via Telegram, when motion is detected. First step towards this, I guess, is to fetch the snapshot. Am I correct in my assumption that the IMAGEURL channel is the way to start? I have the following item set up for this:

    String itemname       "itemdisplayname"
        { channel="ipcamera:AMCREST:Cam_001:imageurl"}

When is this item supposed to get populated? I do not get any URL info displayed in PaperUI at all right now.

Your help is appreciated.

(Skinah) #612


Does this post by a user help at all? If your ONVIF port is wrong the url will not update, but I would forget about the url as the camera has authentication that will stop you, hence it is better to use the image channel as below. Another approach is to use the cameras built in features to send the email and to enable and disable the email sending using the API. Some of the camera brands can turn the emails off whilst leaving the alarm enabled.

(YF) #613


With the polling set at 1 sec, the motion alarm has been working very reliable for close to 24 hours now. Thank you for all the work you put it the binding! Could you add a one or two sentences regarding the correlation between the polling period and the motion alarm to the first message of this thread and the read me file? It could help to avoid confusion similar to what I had.

With pointer from you and Timmi, I see the various values for IMAGE_UPDATE_EVENTS. If I set the value to 4 (refresh image during motion alarm), there is strange behavior, after couple of minutes of updates, the image no longer update when I click on the UpdateImageNow switch. Here’s the log immediately after clicking on the switch (note that motion alarm continues to work, but image is no longer refreshed):

2018-12-27 22:02:44.225 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Sending camera at IP:,    URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.230 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - CommonCameraHandler created.... 2 channels tracked (some of these may be closed).
2018-12-27 22:02:44.237 [TRACE] [ipcamera.internal.MyNettyAuthHandler] - MyNettyAuthHandler is now setup for    GET:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.240 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Have  opened  a  brand NEW channel:2   GET:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.268 [TRACE] [ipcamera.internal.MyNettyAuthHandler] - 401: Normal for DIGEST authorization.  URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.271 [DEBUG] [ipcamera.internal.MyNettyAuthHandler] - 401: Mark as closing, the  channel:2   GET:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.277 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Resending using a fresh DIGEST         URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.280 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Sending camera at IP:,    URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.287 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - CommonCameraHandler created.... 3 channels tracked (some of these may be closed).
2018-12-27 22:02:44.293 [TRACE] [ipcamera.internal.MyNettyAuthHandler] - MyNettyAuthHandler is now setup for    GET:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.298 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Have  opened  a  brand NEW channel:3   GET:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.304 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Digest realm="Login to AMC01857529401DFB3",qop="auth",nonce="2109503158",opaque="c030d02c0c128144ebfd5edcf11b54ffad75c010"
Connection: close
2018-12-27 22:02:44.308 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Channel marked as closing, channel:2   URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.311 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - EmptyLastHttpContent
2018-12-27 22:02:44.314 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Camera has sent some kind of message.Bytes=0
2018-12-27 22:02:44.317 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Camera has sent last part of the message.Bytes=0
2018-12-27 22:02:44.320 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - commonCameraHandler closed channel:2   URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.324 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - commonCameraHandler closed channel:3   URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.326 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Closing CommonCameraHandler.           URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:44.327 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Closing CommonCameraHandler.           URL:/cgi-bin/snapshot.cgi?channel=0

2018-12-27 22:02:53.781 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - !!!! Channel was found idle for more than 15 seconds so closing it down
2018-12-27 22:02:53.784 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - EmptyLastHttpContent
2018-12-27 22:02:53.786 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Camera has sent some kind of message.Bytes=0
2018-12-27 22:02:53.787 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Camera has sent last part of the message.Bytes=0
2018-12-27 22:02:53.789 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - commonCameraHandler closed channel:1   URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:53.791 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Closing CommonCameraHandler.           URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.683 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - The alarm checking stream was not running, going to clean channels and re-start it now.
2018-12-27 22:02:54.686 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - ******** Cleaning channels for camera at *********
2018-12-27 22:02:54.687 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Clean channels is now locked
2018-12-27 22:02:54.689 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Channel status is -1 for URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.691 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Channel status is -1 for URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.692 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Channel status is -1 for URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:54.694 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Channel status is -1 for URL:/cgi-bin/snapshot.cgi?channel=0
2018-12-27 22:02:54.696 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Clean channels is now unlocking
2018-12-27 22:02:54.697 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Sending camera at IP:,    URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.700 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - CommonCameraHandler created.... 0 channels tracked (some of these may be closed).
2018-12-27 22:02:54.705 [TRACE] [ipcamera.internal.MyNettyAuthHandler] - MyNettyAuthHandler is now setup for    GET:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.707 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Have  opened  a  brand NEW channel:0   GET:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.732 [TRACE] [ipcamera.internal.MyNettyAuthHandler] - 401: Normal for DIGEST authorization.  URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.735 [DEBUG] [ipcamera.internal.MyNettyAuthHandler] - 401: Mark as closing, the  channel:0   GET:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.737 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Resending using a fresh DIGEST         URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.739 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Sending camera at IP:,    URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.742 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - CommonCameraHandler created.... 1 channels tracked (some of these may be closed).
2018-12-27 22:02:54.746 [TRACE] [ipcamera.internal.MyNettyAuthHandler] - MyNettyAuthHandler is now setup for    GET:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.747 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Have  opened  a  brand NEW channel:1   GET:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.750 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Digest realm="Login to AMC01857529401DFB3",qop="auth",nonce="368394585",opaque="c030d02c0c128144ebfd5edcf11b54ffad75c010"
Connection: close
2018-12-27 22:02:54.753 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Channel marked as closing, channel:0   URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.755 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - EmptyLastHttpContent
2018-12-27 22:02:54.757 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Camera has sent some kind of message.Bytes=0
2018-12-27 22:02:54.758 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Camera has sent last part of the message.Bytes=0
2018-12-27 22:02:54.760 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - commonCameraHandler closed channel:0   URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.762 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Closing CommonCameraHandler.           URL:/cgi-bin/eventManager.cgi?action=attach&codes=[All]
2018-12-27 22:02:54.763 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - DefaultHttpResponse(decodeResult: success, version: HTTP/1.1)
HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Expires: Thu, 01 Dec 2099 16:00:00 GMT
Connection: Keep-Alive
Content-Type: multipart/x-mixed-replace; boundary=myboundary
2018-12-27 22:02:54.766 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Packet back from camera is multipart
2018-12-27 22:02:54.767 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Packet back from camera is HttpMessage
2018-12-27 22:02:54.770 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - DefaultHttpContent(data: PooledSlicedByteBuf(ridx: 0, widx: 188, cap: 188/188, unwrapped: PooledUnsafeDirectByteBuf(ridx: 188, widx: 188, cap: 1024)), decoderResult: success)
2018-12-27 22:02:54.771 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - Camera has sent some kind of message.Bytes=0
2018-12-27 22:02:54.774 [DEBUG] [ing.ipcamera.handler.IpCameraHandler] - HTTP Result back from camera is        :HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Expires: Thu, 01 Dec 2099 16:00:00 GMT
Connection: Keep-Alive
Content-Type: multipart/x-mixed-replace; boundary=myboundary

(YF) #614

Here’s the updated code that matt1 posted:


When motion alarmed is triggered, the scripts retrieve x number of snapshots and send it to email.

(Skinah) #615

I see this as a bug as I would prefer things work without needing to read a manual and do work arounds. I will have to find some time to consider how best to handle it, perhaps when the channel closes I can detect that and auto restart it giving full freedom to setting the poll time as you wish.

I’ll take a look at your log later in more depth but I do not see anything at a quick glance. I have not tested that part of the code in a while so may pay for me to test it.

(Skinah) #616

New build “29-12-2018 Take 3” is now available and needs testing under multiple brands for the following changes. I have tested it for a few hours with Dahua cameras only and all seems ok. Older builds are also at the download link should u need to roll back.

  • Fixes for @yfaway who reported a bug where Dahua and Hikvision cameras would not update the snapshot if the bindings setting was set to only update on start or during alarm events. Please report any bugs that occur when these options are selected as there are many alarm types and testing each one starts and stops updating the picture will take time to look for bugs.

  • Binding only closes a channel to the camera if it idles for more than 30 seconds instead of previous 15 seconds. May help Dahua alarm streams to stay open for longer, or it may cause issues.

  • Changes to Dahua alarm detection.

(Keiron Cheesbrough) #617

Will try with my Hik cameras this evening, thank you.

(Frank) #618


thank you for the hints.
It turned out that the notification via Telegram was much easier than I thought. The Image item can be included directly in the Telegram “Send” command.
Here a copy from the documentation of the “Telegram Action”

rule "Send telegram with Image Item image and caption"
    Item Webcam_Image changed
    sendTelegramPhoto("bot1", Webcam_Image.state.toFullString, "sent from openHAB")

I use this approach for sending an image when motion alarm was triggered.

(Toopy) #619

I had a chance to spend some more time with my Lorex cameras and the IP camera binding and I still can’t get the snapshot image to update in the PaperUI control or HABPanel, unless I run the CGI URL first.

The other thing I can’t seem to get to work is using the built-in camera motion detector and PIR detectors to cause the image to update. Both those sensors will however, send me an email using the built-in Lorex email service.

I was able to write this rule to use a motion sensor on my DSC alarm system to take 5 consecutive snapshots and email them to me.

import java.util.List

rule "Cam Pic"


        Item Zone3_ZoneStatus changed from CLOSED to OPEN

	var i = 0
	while ((i=i+1) < 6) 
        executeCommandLine("wget http://admin:xxxxx@ -O /tmp/snapshot" + i + ".jpg")

        val List<String> attachmentUrlList = newArrayList(

        sendMail("xxxxx@gmail.com", "Motion", "Motion Has Been Detected", attachmentUrlList)


(Keiron Cheesbrough) #620

Unfortunately I can’t seem to add my Hik cameras, when I try to add one as a thing I just get ERROR: 500 - Request failed. I’m running OH Mac 2.4.0 and ipcamera29-12-2018-Take3 here’s my log:

Caused by: java.lang.ClassNotFoundException: javax.xml.soap.SOAPException cannot be found by org.openhab.binding.ipcamera_2.4.0.201812291002
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484) ~[?:?]
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395) ~[?:?]
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387) ~[?:?]
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?]
at org.openhab.binding.ipcamera.internal.IpCameraHandlerFactory.supportsThingType(IpCameraHandlerFactory.java:34) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.createThingOfType(ThingRegistryImpl.java:247) ~[?:?]
at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.create(ThingResource.java:207) ~[?:?]
at jdk.internal.reflect.GeneratedMethodAccessor157.invoke(Unknown Source) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) ~[?:?]
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144) ~[?:?]
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161) ~[?:?]
at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160) ~[?:?]
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99) ~[?:?]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) ~[?:?]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) ~[?:?]
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) ~[?:?]
at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) ~[?:?]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) ~[?:?]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) ~[?:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:315) ~[?:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:297) ~[?:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:267) ~[?:?]
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) ~[?:?]
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) ~[?:?]
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) ~[?:?]
at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) ~[?:?]
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) ~[?:?]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) ~[?:?]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) ~[?:?]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) ~[?:?]
at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) ~[?:?]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) ~[?:?]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535) ~[?:?]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[?:?]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) ~[?:?]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) ~[?:?]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) ~[?:?]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) ~[?:?]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) ~[?:?]
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) ~[?:?]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) ~[?:?]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) ~[?:?]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) ~[?:?]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) ~[?:?]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) ~[?:?]
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) ~[?:?]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) ~[?:?]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) ~[?:?]
at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) ~[?:?]
... 10 more

(Skinah) #621

New build 31-12-2018 has following changes:

  • Bug fixed for Hikvision reported by @JSamijn where the intrusion and PIR alarms would turn on but not back off.
  • HIK Fixes for updating snapshot when events are occuring.
  • Improvement for when the polling time is longer then the time the alarm it triggered for, this ensures a snapshot is not missed when the setting is to only take snapshots during alarms.
  • Dahua + Amcrest fixes for when NVR setting was > 0 alarm controls would not refresh correctly.
  • Amcrest multiple fixes for audio alarm controls now refresh.

I have tested it with Hikvision cameras today and found no issues that would stop it from working. If you are new to openhab I would suggest you check for typos if you did textual config. Also try giving the binding the wrong ONVIF port deliberately as SOAP is related to ONVIF and that is mentioned in your log… Perhaps you did not enable ONVIF? this is mentioned in the first post of this thread and has a video on how to enable it.

(_) #622

Hi @matt1,

Could you find time to implement - Dahua Output control -https://github.com/Skinah/IpCamera/issues/15