-
Notifications
You must be signed in to change notification settings - Fork 89
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
AD410 Doorbell Alarm/Siren entity not exposed #131
Comments
I'll look into this today and get back with you |
I'm not able to find the API to control the siren yet. Still digging. |
Having a hard time finding the APIs to trigger the siren. Anyone else able to find it? |
Nope. I actually opened an Amcrest Support ticket asking specifically about the Siren API, and after several back and forths, got this absurd answer...
What concerns me is this may be what to expect in a forthcoming firmware update - a complete neutering of the http server and API. This appears to have already occurred with the equivalent Lorex doorbell and the latest firmware update to the Dahua DB6I. Reports I've seen say they do NOT accept API commands. Oh - there is a way to simulate a siren on the AD110/AD410. Send a compatible G117 audio file that is long and loud of whatever siren sound you want. The API for this is documented under 4.3.3 Post Audio Stream. I've tested it sending an appropriately converted sound file with Home Assistant using curl system command and it works just fine. It could be built in to the integration. |
this integration does not seem to expose the alarm entity as suggested in the documentation for the AD410 doorbell, everything else seems to work fine, including the strobe light functionality
The text was updated successfully, but these errors were encountered: