Onvif Doorbell Event Name: tns1:Device/Trigger/DigitalInput - InputToken: onvif_port_10 - LogicalState: true #1064
christiandion
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Mr. @koush !
For the Onvif Doorbell Event Name, if I use Device/Trigger/DigitalInput, it will trigger the doorbell if any digital input changes, from 1 to 10.
The context is the 2N IP Solo Doorstation doesnt have a specific onvif event for the doorbell keypress. I used the Onvif Device Manager to discover the onvif events and firure it out. There is an automation tab in the web UI of this 2N device, which allows to program a trigger for an onvif event on keypress and release. As I cannot create a custom onvif event, I'm only able to change the state of one of the available Virtual Digital inputs.
But as I said, even if I only trigger to change the onvif_port_10, it will trigger the doorbell if any DigitalInput changes. Is it possible to add a filter somewhere so the Onvif Doorbell Event Name: Device/Trigger/DigitalInput will only track the LogicalState's change from the Source - InputToken: onvif_port_10? instead of the changes of any sources of this topic?
PS: Synology Surveillance Station is able to get the doorbell trigger from the 2N IP Solo if I choose the 2N profile. They use the onvif for streaming and digital IO, combined with the TCP http API for the rest of the integration.
Thank you,
Chris.
Beta Was this translation helpful? Give feedback.
All reactions