1
0
mirror of https://github.com/home-assistant/core.git synced 2025-12-24 12:59:34 +00:00
Files
core/tests/components
Phil Frost 920f9f132b Report scripts and groups as scenes to Alexa (#11900)
* Send Alexa Smart Home responses to debug log

* Report scripts and groups as scenes to Alexa

The Alexa API docs have a couple display categories that sound relevant
to scenes or scripts:

    ACTIVITY_TRIGGER: Describes a combination of devices set to a
    specific state, when the state change must occur in a specific
    order.  For example, a “watch Neflix” scene might require the: 1. TV
    to be powered on & 2. Input set to HDMI1.

    SCENE_TRIGGER: Describes a combination of devices set to a specific
    state, when the order of the state change is not important. For
    example a bedtime scene might include turning off lights and
    lowering the thermostat, but the order is unimportant.

Additionally, Alexa has a notion of scenes that support deactivation.
This is a natural fit for groups, and scripts with delays which can be
cancelled.

https://developer.amazon.com/docs/device-apis/alexa-discovery.html#display-categories

The mechanism to map entities to the Alexa Discovery response is
refactored since extending the data structures in MAPPING_COMPONENT to
implement supportsDeactivation would have added complication to what I
already found to be a confusing construct.
2018-01-25 21:06:57 -08:00
..
2017-11-05 13:51:52 +01:00
2018-01-22 22:54:41 -08:00
2017-11-05 18:42:31 -08:00
2018-01-20 22:35:38 -08:00
2018-01-19 16:27:40 +02:00
2017-11-20 20:26:36 -08:00
2017-07-21 21:38:53 -07:00
2017-05-12 20:14:17 -07:00
2017-09-24 15:48:45 -07:00
2018-01-23 11:39:55 +01:00
2017-09-23 17:15:46 +02:00
2017-10-24 19:36:27 -07:00
2017-10-27 10:15:47 +02:00
2017-12-27 13:06:04 -08:00
2017-11-03 10:28:31 +01:00
2017-03-30 00:50:53 -07:00
2018-01-05 16:34:03 -08:00