Bryan B

My feedback

  1. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Alexa Smart Home » Whole Home API  ·  Flag idea as inappropriate…  ·  Admin →
    Bryan B supported this idea  · 
  2. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  0 comments  ·  Alexa Smart Home » Whole Home Metadata  ·  Flag idea as inappropriate…  ·  Admin →
    Bryan B supported this idea  · 
  3. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Bryan B supported this idea  · 
  4. 38 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Received  ·  6 comments  ·  Alexa Smart Home » Whole Home API  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Bryan B commented  · 

    I agree this is needed. The problem is somewhat solved by the groups feature for lighting, but not for other devices generally. Every room with an air purifier, for example, would still require "Alexa, turn on the air purifier in the bedroom" rather than "Alexa, turn on the air purifier" with the backend then figuring out which room and sending the right commands. In general the more Alexa tries to do on its own the less flexibility developers will have.

    Related to that is the Alexa.Speaker interface. I thought for sure this would enable a device to be usable as the "default speaker" in a group but for some reason Alexa won't allow that. Apparently only Amazon devices and a few third party devices can be default speakers. Why can't any streaming music player be the default speaker for "Alexa, play music?" Without that flexibility, again, I would need the smart home API to send information about which Echo device received the request so I can do the mapping of generic commands to specific devices in the same room.

    Also, related to this is the lack of speaker (user) identification in Smart Home Skills. In the custom skill I can get information about who is making the request and that way, for example, I can prevent children from opening the garage door or turning on the coffee maker. I know speaker identification is not "secure" but it has proven to be a good filter generally.

    To summarize, the request is to do one of the following:

    1) Send the device ID of the Echo receiving the smart home API interaction to the Lambda function.

    2) Extend the existing "Alexa, turn on the lights" group feature generally to any user-created type of device (not just lights and speakers). And for smart speakers, allow any Alexa.Speaker interface device to be the room default.

    And for both options: Please start including the personID information for recognized user voices.

    Bryan B supported this idea  · 

Feedback and Knowledge Base