# \[APP\]\[Pro\] Support for ONVIF compatible cameras (Release 2.0.70, Test 2.0.70) **URL:** \ **Category:** Apps\ **Created:** [April 14, 2020, 4:57pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377 "2020-04-14T16:57:37Z")\ **Posts on this page:** 20\ **Page:** 64
**Author:** ![Stefan\_1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stefan_1/32/128096_2.png) [@Stefan\_1](https://community.homey.app/u/Stefan_1)\ **Post date:** [November 3, 2023, 9:46am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1274 "2023-11-03T09:46:21Z")
One small gamechanger idea: In the settings after integration this field is not editable. Can you make this field editable? (for changing url to https or portchange or whatever.). ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dc21949afefd84ab9c8e347b8814243b3ff4ad06.png) ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [November 3, 2023, 11:08am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1275 "2023-11-03T11:08:50Z")
You can override it in the User URL field below it. If that field is empty it uses the data received from the camera, else it will use the user input. ---
**Author:** ![Aybee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aybee/32/80977_2.png) [@Aybee](https://community.homey.app/u/Aybee)\ **Post date:** [November 4, 2023, 11:33am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1276 "2023-11-04T11:33:37Z")
It doesn’t work properly with my Anke Cams (HikVision Label), if I want to send a snapshot, it takes forever or the app always crashes. c0112a76-d8cc-4dba-b6b9-e9dddefdd02b ![Screenshot_3](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/a/8a207021e697a263f396b513e16f8963c01b9671.png) ---
**Author:** ![Geert\_Jacobs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geert_jacobs/32/81062_2.png) [@Geert\_Jacobs](https://community.homey.app/u/Geert_Jacobs)\ **Post date:** [November 6, 2023, 10:27pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1278 "2023-11-06T22:27:09Z")
Hi Adrian, The onvif experimental versions work for my mobotix camera’s. Unfortunately the official version of the app doesn’t. For some reason when refreshing the snapshot or movement, the snapshot or movement image which is send via a flow to my telegram account after refresh is still tje old image when the onvif app was first activated but not the latest. I send you a log. Any idea what is going wrong? ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [November 6, 2023, 11:17pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1279 "2023-11-06T23:17:25Z")
The log shows everything is working as expected. Does the image in the Homey device update OK? Could you show the flow you are using? ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [November 6, 2023, 11:31pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1280 "2023-11-06T23:31:27Z")
The log has lots of errors: 2023-11-04T07:12:27.643Z [log] [MyApp] SnapShot error (Cam Garten): request to [http://192.168.178.89/onvif-http/snapshot?Profile\_1](http://192.168.178.89/onvif-http/snapshot?Profile_1) failed, reason: socket hang up socket hang up means the camera is not responding to the request. could you try putting that URL into a web browser to see if you see an image? ---
**Author:** ![Geert\_Jacobs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geert_jacobs/32/81062_2.png) [@Geert\_Jacobs](https://community.homey.app/u/Geert_Jacobs)\ **Post date:** [November 6, 2023, 11:39pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1281 "2023-11-06T23:39:01Z")
Please see the flow in Dutch language. The snapshot updates fine when looking im the onvif app. It’s when i try to send the snapshot via telegram, then it is sending the first old snapshot. Is there a way to check what snapshot image homey is seeing/storing. ![IMG_8733](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/7/27ce02cab7040ab57082eca575d086387f84e109.jpeg) ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [November 6, 2023, 11:50pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1282 "2023-11-06T23:50:30Z")
I can’t see what triggers the Flow, but I see you then update the snapshot. That takes a bit of time so the following commands probably run before it has fetched it There are two solutions: 1. Put the commands to send the snapshot in another Flow that is triggered by the snapshot is ready card. 2. Use the condition card “Motion snapshot is ready within” card as that will block the Flow until either the snapshot is ready or times out. ---
**Author:** ![Aybee](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/aybee/32/80977_2.png) [@Aybee](https://community.homey.app/u/Aybee)\ **Post date:** [November 7, 2023, 7:50am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1283 "2023-11-07T07:50:39Z")
With the URL directly from the camera, I can see the screenshot without any problems ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [November 7, 2023, 10:08am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1284 "2023-11-07T10:08:46Z")
That is strange. Have you tried rebooting Homey to see if that helps? The other issue I see in the log is a lot of storage failed events coming from the camera,. However, the camera hasn’t reported that it supports those events, so the alarm capabilities wasn’t created. That appears to be the cause of the crash as it makes the app uses too much CPU time. I have made a fix that I will publish that partially overcomes that by adding the capability on the fly so it no longer reports an error but if the events keep hitting the app at the current rate it might still crash it. ---
**Author:** ![Jerome\_Revillard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jerome_revillard/32/33414_2.png) [@Jerome\_Revillard](https://community.homey.app/u/Jerome_Revillard)\ **Post date:** [November 8, 2023, 6:22am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1285 "2023-11-08T06:22:42Z")
Hello @Adrian_Rockall, Any news ? Best, Jérôme ---
**Author:** ![Jerome\_Revillard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jerome_revillard/32/33414_2.png) [@Jerome\_Revillard](https://community.homey.app/u/Jerome_Revillard)\ **Post date:** [November 8, 2023, 6:36am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1286 "2023-11-08T06:36:43Z")
Well, in fact I just test again and…it works! I dont know if it’s related to your last update or not… Best, Jérôme ---
**Author:** ![Mareike\_B](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mareike_b/32/80103_2.png) [@Mareike\_B](https://community.homey.app/u/Mareike_B)\ **Post date:** [November 19, 2023, 9:46am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1287 "2023-11-19T09:46:30Z")
Hi everyone, I am trying to get the sabotage event triggered. What can I do? I have a reolink poe doorbell and when I open it and/or remove the lan cable it does not fire any event. Motion and Visitor events are send. Does anybody have an idea how to fix this? ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [November 19, 2023, 10:06am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1288 "2023-11-19T10:06:28Z")
> [@Mareike\_B](#): > > I have a reolink poe doorbell and when I open it and/or remove the lan cable it does not fire any event AFAIK the doorbell doesn’t have any tamper detection. Also, how would the camera be able to fire an event when you remote the LAN cable, _which also provides it with power_? ---
**Author:** ![Mareike\_B](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mareike_b/32/80103_2.png) [@Mareike\_B](https://community.homey.app/u/Mareike_B)\ **Post date:** [November 19, 2023, 1:09pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1289 "2023-11-19T13:09:42Z")
Thanks for the reply. I was hoping that it somehow detects the opening of the case. ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [November 19, 2023, 2:10pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1290 "2023-11-19T14:10:42Z")
> [@Mareike\_B](#): > > I was hoping that it somehow detects the opening of the case. Doesn’t look like it, my WiFi Doorbell doesn’t emit anything when I pop it from the holder. ---
**Author:** ![Jote](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jote/32/71412_2.png) [@Jote](https://community.homey.app/u/Jote)\ **Post date:** [November 26, 2023, 6:44pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1291 "2023-11-26T18:44:21Z")
![Skjermbilde 2023-11-26 185420](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/9/e98462a5720da90e2bc3c76740e4bb6dc62fb93d.png) Hi, want to start out with a thanks for the app. Have recently added a reolink NVR and two CX410 which works well with the app. Question; sometimes the ‘person’ card disappears for one of the cameras, is there some logic to this? Also, would it be possible to have a smart detection card like the ubiquiti system I have? This would make for a ‘cleaner’ flow in my case. ![personcard missing 2](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/1/b1dfcc8f352c289c1bf450389072b2b4619d8c4d.png) ![personcard missing](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/9/d97c00f7adc4afea716bc87af436537ebdd67c4d.png) ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [November 26, 2023, 7:02pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1292 "2023-11-26T19:02:21Z")
Some of the capabilities are added on the fly base on the information that is received. I will take a look to see why it disappears. What do you mean by a smart detection card? ---
**Author:** ![Jote](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jote/32/71412_2.png) [@Jote](https://community.homey.app/u/Jote)\ **Post date:** [November 26, 2023, 7:11pm UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1293 "2023-11-26T19:11:17Z")
Thanks, tried restarting the apps and homey but that does not cure it. It has disappeared before but after a while it came back in the list. just strange that it happens for the one camera, and there is 2 identical ones running on a nvr (channel 1 and 2). The ubiquiti app has a card for smart detection, if it is a vehicle or person identified by either of the cameras (not including motion alarms which I don’t want, and ubiquiti does not support pet detection sadly.) it will activate. If the onvif app had a similiar card one could add events like vehicle/pet/person/visitor with one card for several cameras? ---
**Author:** ![Adrian\_Rockall](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/adrian_rockall/32/13209_2.png) [@Adrian\_Rockall](https://community.homey.app/u/Adrian_Rockall)\ **Post date:** [November 29, 2023, 8:11am UTC](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377/1294 "2023-11-29T08:11:41Z")
So the person alarm is removed if the camera does not report it supports that option: ```auto if (notificationTypes.indexOf('PERSON') >= 0) { if (!this.hasCapability('alarm_person')) { this.addCapability('alarm_person') .then(() => { this.setCapabilityValue('alarm_person', false).catch(this.error); }) .catch(this.error); } } else { if (this.hasCapability('alarm_person')) { this.removeCapability('alarm_person').catch(this.error); } } ``` I will look into adding an app based trigger for motion that has a tag for the type of motion that was detected. [Previous page](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377.md?page=63) [Next page](https://community.homey.app/t/app-pro-support-for-onvif-compatible-cameras-release-2-0-70-test-2-0-70/28377.md?page=65)