I haven’t seen any ONVIF commands to do that but I will do some searching.
Have you got any logs from the app around the time it stopped?
Ideally what I need is to see the logs captured while it’s not working to see if it is showing errors that I can monitor.
Hi all,
I’ve browsed through this forumsubject but cannot find the answer i was hoping for.
My question is also a bit off-topic but maybe some of you can help.
I have a Imou Looc (IPC-C26E) camera at my front door. It is working flawless with the ONVIF app.
The plan is to get a snapshot when somebody pushes the doorbell. I have a conventional doorbell connected to a KaKu ACDB-7000B transmitter.
My flow to see who is at my frontdoor:
“When button is pushed → Take a snapshot from the LOOC → Send snapshot to…”
That all works fine.
BUT: I mentioned that it takes a while before the snapshot is taken; sometimes more the 5 to 10 seconds. When i also take a look at the LOOC under devices it takes a while before i get a image.
But only after i did not use camera for a while.
It seems to me that the camera is falling into a kind of sleep modus after a while. I have searched through all possible settings but cannot find functions like “always on” or something of that kind.
Using ‘motion’ to stay awake is not usefull in this case because my front door is on a private ‘path’ so it cannot see the public street.
Does anybody has a tip or trick to keep the LOOC awake at all times ?
Or is it just the wrong camera for the wrong purpose ?
Thank in advance,
Peter
I can’t say that I have noticed that with my Imou camera. It takes between 2 to 3 seconds every time I have tried it, but I don’t use it in the same way as you.
It’s possible that Homey or your network is just busy when you see the longer delay.
Do you a Homey Pro?
Can you share your flow so I can see if there is any way to optimise it?
There is no abnormal traffic on my Wifi/Lan network. My router reflects a usage of about 5% of total capacity. I am afraid it is just the camera waking up to slow.
My flow does not give many options to optimise speed i guess ;-). It is just simple.
BTW: I need the 1 second delay to give Homey enough time to pick up the snapshot (otherwise the picture absent)
But that cannot be the problem. The delay stays at 5 to 10 seconds before the camera responds on the snapshot request.
Thanks,
Peter
It would probably be better to split that into two flows. The one above would be the first one, but take out the send to phone action. Then create another flow that is triggered when the motion image is updated and use that to send the image.
Or use the condition card “Bewegings snapshot is klaar binnen” as this will trigger the capture and wait until it is ready before processing the actions. The time specifies the maximum time to wait and if the snapshot is ready it processes the Then section, but if it fails within the time it processes the Else section.
@Adrian_Rockall thanks for your idea.
I just looked into it, but i am a little confused now.
When i use the camera as a THEN action i have for a snapshot only the option: “Bewegingssnapshot bijwerken”.
When i use the camera in a “IF” (ALS) action i see the possibilty of 2 snapshots’:
“Snapshot beschikbaar” and “Bewegingssnapshot beschikbaar”.
Do you know the diff ?
This is what i see in the “IF” section:
But in the “THEN” section i only see the "Bewegingssnaphot:
Maybe there is a little ‘flaw’ ?
Peter
The snapshot is only updated manually (refresh button in the device display).
The motion snapshot is updated by the cameras motion detection or by a flow action.
The idea is, when you look at the device, you can view the ‘live’ image by refreshing the snapshot or the image that was captured when motion was detected by the camera or triggered by the flow.
The ‘When’ section (first section) has triggers for both snapshots.
The ‘And’ section (second section) only has a trigger and wait for the motion snapshot. So if you use that, send the motion snapshot in the ‘Then’ (third section).
The ‘Then’ section (third section) only has an option to update the motion snapshot.
I hope that is clear. It all started of simply, but as extras have been added form user requests, it has become more flexible (complicated).
Hi,
All clear 
Thanks for your response,
Peter
1 Like
Hi all,
It seems like I have the same problem as schmucke. Without any problems I was able to install my RLC 410W 5MP and got it up and running. I tried to get the motion working so I would receive a snapshot when motion would be triggered. I used all the same settings as you @Adrian_Rockall stated here above, and the same flow (Motion snapshot ready - > send notification) but it doesn’t update the motion snapshot.
Turned on the basic log mode, and noticed that the camera actually recognizes and registers motion (motion true and motion false), but for some reason, when I look at the camera overview under “motion alarm” it says that there hasn’t been any motion updates.
Uninstalled the app, installed it again and did everything from the beginning, but still it doesn’t seem to have any effect. It looks like the motion is registered but not triggered so it can’t be used in a flow.
When I hooked up a stand alone PIR sensor, created a flow “when registering motion → Update motion snapshot” and a second flow: “Snapshot is available → send a push notification” this worked flawlessly and also triggered the “motion detected” info on the camera itself.
Any idea’s on how to get the motion working from the camera and not through the stand alone PIR sensor? Thanks!
In the Advanced Settings, do you have the ‘ONVIF Motion Notification to use’ set to ‘MOTION (IsMotion)’?
Could you send me the log so i can see what motion type is being sent?
Hi Adrian,
Yes the IsMotion is active, and I just sended you the log! 
There is something strange in the log. The subscription termination time is an hour before the current time, but that should be after. Could you reboot the camera to see if that fixes it.
Also try toggling the prefer pull event option in the advanced settings.
It looks like there is a bug in the latest camera firmware. After updating my camera I am starting to see the same error in the pull request response where the termination time is earlier than the current time. I will report this to Reolink and I will see if I can find a workaround.
@Adrian_Rockall check! Did indeed the reboot and toggled the prefer pull event option, but it didn’t do much. Now with the knowledge that it is a problem with the camera itself, it all makes a bit more sense. Hopefully there will be a fix. Thanks for the help already and waiting for Reolinks reply!
It looks like the pull refresh is not working so the termination time that is returned is the last one defined during the first subscribe. I am testing a theory that if the refresh interval is negative then I will unsubscribe and subscribe again. So far this is looking good so I will hopefully push out a new test version soon.
There is a new test version ONVIF Camera | Homey.
See if that fixes the problem.
If not then can you send me another log. Let the log run for about 5 minutes before sending so it has a chance to capture the refresh information. Also, trigger the motion while logging.
It works like a charm! Motion is detected and the motion snapshot is refreshing and being send to my devices. Thanks a lot for the quick reply and the solution! 
2 Likes
Hi. I’m currently fooling around with the latest 6mp Dahua Eyeball series Wizsense camera…I only want to monitor smart intrusion motion events with Human detection object filter applied. I’m just trying to set the camera up with this App. I believe I have all the right settings such as “IsInside” mode
… Ive attached a screen cap of a log output from the camera using OnVIf manager on my PC. Would anyone be able to tell me what settings i need to enter based on this info ? Thanks Russ
I don’t think I have support for that event type yet. Could you set the log to Detailed Information (int the Homey ONVIF app - Configure App page. Then enable motion for the camera and try to trigger it a few times. Then send the log to me. Hopefully, I should see exactly what the event looks like and more information about the object id, etc. I can then add the option into the next update.
1 Like
