Reolink cameras in v6.1 (with ONVIF Profile M)
AnsweredI understand that Reolink isn't an officially supported brand, but with the release of v6.1 and support for ONVIF Profile M, I was hoping we might see better support with the Reolink cameras. So far it doesn't seem to be the case. I'm wondering where the breakdown might be happening.
If I open a Reolink E1 Outdoor camera in ODM, the events page will initialize with the following different RuleEngine responses.

I turned on the ONVIF analytics plugin and when I try to setup a rule with an Analytics Event, there is just one Rule Engine type for Cell Motion Detector - Motion. Should it be detecting some of the other event types like RuleEngine/MyRuleDetector/FaceDetect?
How is ODM picking up on these events and the new ONVIF Analytics plugin doesn't?
A similar issue happens with Reolink's Video Doorbell camera. ODM sees the same events listed above, but also. tns1:RuleEngine/MyRuleDetector/Visitor (used when the doorbell button gets pressed).
-
Hi Jeff Jones,
I checked the Onvif Profile M specification, and I don't see the endpoint
tns1:RuleEngine/MyRuleDetector/in the document.With kind regards.
0 -
Ok. I wonder what specification ODM is using to see the events.
Since ODM is detecting these, they must be some kind of valid event, just maybe proprietary wording. Can the server software be updated to see all valid ONVIF XML events and then we could set a custom rule to look for custom keywords?
0
Please sign in to leave a comment.
Comments
2 comments