The use of other attributes than device state attributes is deprecated and will be removed in a future release. Invalid attributes are ['transition']. Read the logs for further details: https://www.home-assistant.io/integrations/scene/
This error show up in the logs because the transition, currently within the entity_id of a scene, will be removed soon in favor of the following syntax:
action:
service: scene.turn_on
data:
entity_id: scene.romantic
transition: 2.5
The issue is, being this a scene, it would be much more useful if a scene that has lots of lights that should act in different ways, can be pre-written.
Please have a look at the example below.
Suppose you wake up in the night and want that a group of lights will turn on slowly, the following scene would apply:
- name: Living area slow
entities:
light.light_3:
state: on
brightness: 254
color_temp: 443
transition: 3
light.light_2:
state: on
brightness: 254
color_temp: 443
transition: 5
light.light_1:
state: on
brightness: 254
color_temp: 443
transition: 8
which will be called from the following automation:
- id: 'living area on slow'
initial_state: true
trigger:
- platform: state
entity_id: binary_sensor.bedroom_door_occupancy
from: 'off'
to: 'on'
condition:
- condition: state
entity_id: input_boolean.it_is_night_and_we_sleep
state: 'on'
action:
- service: scene.turn_on
data:
entity_id: living_area_slow
Using the new kind of scenes, that ‘action’ must be converted to (and suppose that light_x_slow exist) :
...
action:
- service: scene.turn_on
data:
entity_id: light_3_slow
transition: 3
- service: scene.turn_on
data:
entity_id: light_2_slow
transition: 5
- service: scene.turn_on
data:
entity_id: light_1_slow
transition: 8
And that makes really little to less sense.
My request then is if the scenes may please have the transition back.
Thanks