IpCamera: New IP Camera Binding

Have you tried to connect the cameras with lan cable?
I have problems with reolink WLAN camera but with cable it works great.

Hi Sebastian

both are connected via LAN.

I thought maybe its due to the powerline, but for test purposes I connected both cameras directly to the switch. At the time of the failure, both were directly connected to the switch


Hey guys.

Does anybody know if the Xiaomi Mi 360° Home Security Camera 2K would work as a Generic camera?


See here as you would need a working rtsp or http stream as a minimum for it to work as generic.

That’s what I thought, thanks. Apparently some CfW for the Xiaomi cam offer both RTSP and ONVIF, but as of yet not my model.

Recently i upgraded a Reolink RLC-811A IP camera to the latest FW version v3.1.0.956_22042008. Before, i.e. with FW v3.1.0.764 everything worked like a charme. But with latest FW, camera seems to reboot every ~4 minutes. I don’t even receive any motion indication although there’s mortion.
Critical here, Reolink upgraded ONVIF protocol to version 21.06. Usually standardized protocols are backwards compatible, however with ONVIF device manage 2.2.250 i don’t face any issues and i even receive motion indication messages.
Now i’m wondering, makes ip camera binding use of more and different messages compared to ONVIF DM manager or is there probably a somehow “mailformed” packet send by the binding?

Rational on why i want to stay with recent Reoliunk FW: They introduced and still improve AI to further detail the motion, i.e. person, pet, car.
I’m having discussion with Reolink support team in parallel.
Currently I’m struggling with “log:set TRACE org.openhab.binding.ipcamera” answering “Error executing command: Unable to set level for logger”, hence i don’t have more details yet :-(.

Meanwhile i managed to set the ipcamera binding log level to TRACE. Having had a look into three retries, i noticed “Sending ONVIF request:PullMessages” to be the last output of the binding before camera connection got lost (camera most probably restarts).
Any idea on whether there has been changes in the ONVIF protocol in version 21.06?
Will share the same with Reolink support team.

If switching off the ipcamara binding, does the Reolink camera work as intended (i.e. no reboots at all)?

Yes, in this case camera is stable. Similar to disabling the ONVIF interface/port on camera side.

Just checked: ONVIF DM makes use of “PullMessages” as well.But in contrast to ipcamera binding, the IE “MessageLimit” within the body isn’t <1> but <1000>. Don’t think the other IE “Timeout” with “PT8S” vs “PT1M” makes any difference. Despite that body seems to be identicall for both.

The “PullMessages” answer takes 3 IP fragments with std ethernet (i.e. MTU = 1500). Hope above messages are not treated as IP fragments.
Will next take a tcpdump during misbehaving situation.

I’m not an expert on interpreting ONVIF messages, but what i see in misbehaving situation: from 3 “PullMessages” requests within the short tcpdump, seems just one received an answer.
Kindly let me know what further tests could be done / what to focus on in detail. Thanks a lot!

From memory the binding asks that only 1 event is reported in each reply to the “PullMessages” request. This means the camera has to only reply with 1 event instead of the binding having to parse multiple events out of the one reply which may contain 1000 events to parse. The binding will keep asking for “PullMessages” and the camera is meant to send 1 at a time until there are no more. Perhaps there is an issue in the way that is working in the cameras firmware. Since the messages were modelled around the ODM software they should be almost identical so very few areas that can cause 1 to work and the other to not.

I managed to modify, build and apply the ipcamera binding. Root cause of the Reolink camera reboot seems to be MessageLimit set to 1. I started with 1000, similar to what the ONVIF DM set the setting to. After proofing this, i went down to 10, and this works as well.
Question to the IpCamera maintainer: Is there any reason to stay with 1? Setting the parameter to e.g. 10 shouldn’t harm i assume.
I will communicate the same to Reolink support team. Not sure how fast / whether they will incorporate a fix.
Hence, to be on the safe side, changing the binding might be the best and fastest approach.

Haven’t seen your chat before i send my latest updates :frowning: How about the complexity to parse multiple messages?

Its not hard it just needs someone to implement it. If you don’t implement it then the camera could send multiple events even just a CPU load message and you would miss the 2nd event in the same message which may be a motion event that you care about. The value of 1 is a valid request and the camera should be able to handle it, it just takes multiple replys instead of 1 holding many events.

ok, got it. Thanks! Lets see whether Reolink shares any update on this in the near future.
I fear issue will show up on more Reolink cameras than just RLC-811A with latest firmware :frowning:


did you manage to connect HikVision DS-KV6113 to openhab?


Unfortunately not with the IPCamera Binding. As I use a Synology, this DS-KV6113 is handled by Video Surveillance Station. There is a OpenHAB binding for this but I did not yet experiment it.


could you please point me out to the binding you’ve mentioned?


More info concerning this binding is available here: GitHub - nibi79/synologysurveillancestation: Synology Surveillancestation Binding
You can install this binding directly your openhab instance (third party binding). it requires to have a
Synology NAS, video surveillance station software and the KV6113 installed as a camera.

I was also able to connect OpenHAB to the KV6113 to have the status of the call button. I thus receive notification when someone push the call button. But this requires some tricky operations. But if you are interested, I can share this information as well.