• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Amcrest AD410 Video Doorbell & Echo Show

    Support
    4
    26
    1852
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Monocle
      Monocle @tammymfreeman last edited by

      @tammymfreeman

      Go ahead and post a log of what the Monocle Gateway is doing when your request the camera stream. I can take a look and see how far in the process it is getting and see if there is a clear reason why its not streaming.

      Monocle: https://monoclecam.com
      Getting Started | Troubleshooting Guide | FAQ | Contact Support

      1 Reply Last reply Reply Quote 0
      • B
        bill @Monocle last edited by

        @Monocle Agree fully. However mine (thus far) will only work with the string I posted above. But thanks for your input! :+1:

        1 Reply Last reply Reply Quote 0
        • T
          tammymfreeman last edited by

          Thanks for all the help. Here is the full output below (btw, it is still running, keeps trying something). I had to post a photo bc the actual code gets flagged as spam.

          5033d055-66b9-43a2-8220-995672841028-image.png

          Monocle 1 Reply Last reply Reply Quote 0
          • Monocle
            Monocle @tammymfreeman last edited by

            @tammymfreeman

            So it looks like its failing to authenticate with the camera.

            1.). The first DESCRIBE request fails and the camera’s response indicates (via 401 response) that its wants DIGEST authentication. This is all normal.
            2.). The Monocle Gateway then attempts DIGEST authentication but the camera rejects the auth request with a 401 response.
            3.). The Monocle Gateway then attempts BASIC authentication but the camera rejects the auth request with a 401 response.
            4.). Monocle Gateway then gives up because both methods of authentication have failed.

            This would typically indicate an invalid username/password. Some cameras may be picky about special characters in the password. I also recall a bug in the the Hikvision doorbell camera firmware truncating the password to 6 characters and thus the user would have to only specify the first 6 characters if the password were longer. I would try verifying the username and password and then maybe try some simpler/shorter password combinations just to see if you can get it working.

            Thanks, Robert

            Monocle: https://monoclecam.com
            Getting Started | Troubleshooting Guide | FAQ | Contact Support

            1 Reply Last reply Reply Quote 0
            • T
              tammymfreeman last edited by

              I really appreciate all the help and feedback. Unfortunately none of it worked. On a brighter note the new doorbell camera arrived and it works flawlessly with the built in Alexa skill :). I’ll be returning the Amcrest Camera.

              B 1 Reply Last reply Reply Quote 0
              • B
                bill @tammymfreeman last edited by

                @tammymfreeman And what doorbell did you decided on, please ?

                T 1 Reply Last reply Reply Quote 0
                • T
                  tammymfreeman @bill last edited by

                  @bill I went with the Foscam listed below. So far so good. It added to my NVR with no problem using Onvif and it announces to all my devices and shows the live video on the echo all using the native skill.

                  https://www.amazon.com/dp/B093WBF4MD?psc=1&ref=ppx_yo2_dt_b_product_details

                  B 1 Reply Last reply Reply Quote 0
                  • J
                    justdo71 last edited by

                    Was able to get a solution to work so that when the doorbell is rang it will show on the Echo Show. The quick and dirty explanation was to create an alexa routine connected to the binary sensor front_door_call_no_answered from Home Assistant and follow these videos to connect it to alexa:



                    For the tutorial to connect home assistant to alexa by everything smart home, I needed to make some small changes. In the Alexa development console, under permissions, turn on “Send Alexa Events”. In Home Assistant, edit the configuration.yaml file with the following values under smart_home

                    endpoint: https://api.amazonalexa.com/v3/events
                    client_id: YOUR_SKILL_CLIENT_ID
                    client_secret: YOUR_SKILL_CLIENT_SECRET

                    Reason why is because there needs to be a way for Home Assistant to push the state of the binary sensor to Alexa instead of Alexa pulling that data from Home Assistant.

                    B 1 Reply Last reply Reply Quote 0
                    • B
                      bill @tammymfreeman last edited by

                      @tammymfreeman Sorry for my delay. Thank you for the info. It looks like a nice choice for sure, and I’m happy that it is working well for you. I had no idea that Foscam even had a doorbell. Continued success!! :relaxed:

                      1 Reply Last reply Reply Quote 0
                      • B
                        bill @justdo71 last edited by

                        @justdo71 This looks great, but (maybe unfortunately) I do not use Home Assistant. I have my AD210 doorbell displaying fine (with audio also) through Monocle whenever I ask Alexa to show me the 'Doorbell". However when the doorbell is pressed Alexa only announces that someone is at the doorbell, but the camera doesn’t display anymore.

                        Of course the camera should display with the native Amcrest App itself without the need for Monocle, but that stopped working a while back. No idea why. :upside_down_face:

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Privacy Policy  |  Terms & Conditions

                        © 2018 shadeBlue, LLC.