TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    [BUG] I`m adding new commands and it`s executes the command but Alexas threats as a doorbell

    General Discussion
    2
    7
    58
    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.
    • Vinicius Gimenez FiguerolaV
      Vinicius Gimenez Figuerola
      last edited by

      New Smart Home commands are discovered by Alexa correctly and execute normally, but Alexa says "Ding Dong.... Someone is in front of <device name>" for every newly created command. Older commands created weeks ago still behave correctly.

      Vinicius Gimenez FiguerolaV 1 Reply Last reply Reply Quote 0
      • Vinicius Gimenez FiguerolaV
        Vinicius Gimenez Figuerola @Vinicius Gimenez Figuerola
        last edited by Vinicius Gimenez Figuerola

        This started Happening after I ve tested that field Voice/MCP Reply in the command, I use the Alexa skill for Smart Home, even I`ve deleting that field it doesn t stop threating everything as a doorbell

        RussR 1 Reply Last reply Reply Quote 0
        • RussR
          Russ @Vinicius Gimenez Figuerola
          last edited by Russ

          @Vinicius-Gimenez-Figuerola, I noticed the same thing yesterday. When I trigger a new or changed command via the virtual Alexa Smart Home device, my Echo device says, "Ding dong, someone is at [voice word]." Old commands are not affected.

          For now, I set my Alexa device to "Do Not Disturb" so I don't hear the announcement like this article suggested:
          https://www.amazon.com/gp/help/customer/display.html?nodeId=GV7ZJNSWKL8E3D7T

          I'm looking into what changed. I think Amazon changed something recently because I didn't change anything related to the doorbell feature. You probably know this, but the doorbell feature is needed to trigger an Alexa routine when a command runs.

          It doesn't have anything to do with the Voice/MCP Reply field. The TRIGGERcmd Smart Home Alexa skill doesn't use it. Only the legacy conversational Alexa skills (called TRIGGERcmd, Trigger Command, and TC) use it.

          I opened a case with Amazon about it.

          Russell VanderMey

          Vinicius Gimenez FiguerolaV 1 Reply Last reply Reply Quote 1
          • Vinicius Gimenez FiguerolaV
            Vinicius Gimenez Figuerola @Russ
            last edited by

            @Russ Oh, yes. For now, that's exactly what I've done. I've created a routine for each command that enables the do not disturb for about 5 seconds before running the command.

            RussR 1 Reply Last reply Reply Quote 0
            • RussR
              Russ @Vinicius Gimenez Figuerola
              last edited by Russ

              @Vinicius-Gimenez-Figuerola , interesting. What triggers that routine? I would think the command couldn't trigger it because it would be too late. I'll try it.

              EDIT: I tried it - that works, but I don't want everyone to have to do that for every command, so I'm still looking for a solution. Worst case, I could make the doorbell feature (for running routines) a toggle for each command, and default it to false.

              EDIT2: I added a feature to each device to allow you to disable the "Doorbell Press Notifications".

              2abed5a5-a0cd-428d-b1db-5350fc12c5b5-image.png

              Russell VanderMey

              Vinicius Gimenez FiguerolaV 1 Reply Last reply Reply Quote 1
              • Vinicius Gimenez FiguerolaV
                Vinicius Gimenez Figuerola @Russ
                last edited by

                @Russ Yes, a permanent solution needs to be found. What I did is just a workaround because I was getting tired of Alexa saying "Someone is in front of..." every time I asked her to run a command.

                RussR 1 Reply Last reply Reply Quote 0
                • RussR
                  Russ @Vinicius Gimenez Figuerola
                  last edited by

                  @Vinicius-Gimenez-Figuerola if you rename your command, and rename it back, it will re-create the Alexa device with this new UI option to disable the doorbell press notifications. Does that solve it? I tried to default it to false, but there doesn't seem to be a way to do that.

                  e3b9debd-da26-49f4-86fd-3e71635bba16-image.png

                  Russell VanderMey

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post