-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing AVTech AVM2453 #20
Comments
Hi, @jpiscaer currently the event names are hardcoded. I will take a look at making these configurable. Until then feel free to submit a PR against this file: https://github.com/dmitrif/onvif2mqtt/blob/master/src/onvif/SubscriberGroup.js#L13 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! I have a couple of AVTech AVM2453 cameras with ONVIF support which don't show up on mqtt.
They do connect successfully:
{"level":30,"time":1607202992810,"name":"ONVIF/camera-driveway","hostname":"10.10.10.10","msg":"Successfully connected.","v":1}
But I think the ONVIF messages these cameras send are non-compliant. The camera's config page shows
tnsav:MotionDetection
as the topic for motion events, and this is configurable.But when I check out the actual messages being sent, they're sending out
![Screen Shot 2020-12-05 at 22 31 49](https://user-images.githubusercontent.com/7115118/101265801-b55f6400-3749-11eb-9cda-ae0b6a490385.png)
tns1:VideoAnalytics/tnsav:MotionDetection
as the topic.I tried setting the topic to the more standard
![Screen Shot 2020-12-05 at 22 31 03](https://user-images.githubusercontent.com/7115118/101265853-446c7c00-374a-11eb-951e-d7748d0c67f1.png)
tns1:VideoSource/MotionAlarm
but then the cameras send outtns1:VideoAnalytics/tns1:VideoSource/MotionAlarm
, which isn't picked up by onvif2mqtt either.The question here is: how can I edit onvif2mqtt to pick up the
tns1:VideoAnalytics
prefix?The text was updated successfully, but these errors were encountered: