0.19: Empowering scripts and Alexa
+ + + ++
diff --git a/atom.xml b/atom.xml index d830ce5a3e..bfc32ad784 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state
!). Passing data to script entities is available by passing the data to the script services.
automation: + trigger: + platform: mqtt + topic: some/notify/topic + action: + service: notify.notify + data_template: + message: + +automation 2: + trigger: + platform: state + entity_id: light.hue + action: + service: notify.notify + data_template: + message: is now +
Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room
into light.holiday_home_living_room
with the following config:
light: + platform: hue + entity_namespace: holiday_home +
trigger
variable to script templates (@balloob)and
and or
to combine conditions (@balloob)!envvar
(@bah2830)as_timestamp
method now available (@srcLurker)/api/discovery_info
] with basic instance info (@robbiet480)condition:
instead of platform:
. For example condition: state
.Old RFXtrx config format:
+ +devices: + 123efab1: + name: My DI.0 light device + packetid: 1b2200000890efab1213f60 +
New RFXtrx config format:
+ +devices: + 1b2200000890efab1213f60: + name: My DI.0 light device +
for
config parameter to only trigger when a state hasn’t changed for a certain period of time (@pavoni, @stefan-jonasson)
-
- Camera feeds are now directly embedded in the frontend.
-
command_line
.Scripts are now available in automations and when responding to Alexa/Amazon Echo. Both of these components will now expose data to be used in script templates (including from_state
!). Passing data to script entities is available by passing the data to the script services.
automation: - trigger: - platform: mqtt - topic: some/notify/topic - action: - service: notify.notify - data_template: - message: - -automation 2: - trigger: - platform: state - entity_id: light.hue - action: - service: notify.notify - data_template: - message: is now -
Entity Namespaces allow you to influence the entity ids for a specific platform. For example you can turn light.living_room
into light.holiday_home_living_room
with the following config:
light: - platform: hue - entity_namespace: holiday_home -
trigger
variable to script templates (@balloob)and
and or
to combine conditions (@balloob)!envvar
(@bah2830)as_timestamp
method now available (@srcLurker)/api/discovery_info
] with basic instance info (@robbiet480)condition:
instead of platform:
. For example condition: state
.Old RFXtrx config format:
- -devices: - 123efab1: - name: My DI.0 light device - packetid: 1b2200000890efab1213f60 -
New RFXtrx config format:
- -devices: - 1b2200000890efab1213f60: - name: My DI.0 light device -