Core: Scenes do not properly set brightness_pct

Created on 31 Oct 2019 · 4Comments · Source: home-assistant/core

Home Assistant release with the issue:
0.101.0

Last working Home Assistant release (if known):
0.100.3

Operating environment (Hass.io/Docker/Windows/etc.):
Docker container on Linux

Integration:
Scenes being used with MQTT Lights

Description of problem:
I have the scene in the code block below, and it used to turn the MQTT lights on to 25% brightness when I ran the scene on version 100.3. Now in version 101, it turns the lights on to 100% brightness instead. If I set the light brightness manually using the slider in the UI or by having the UI run the light.turn_on service with a brightness_pct of 25, those both work as expected in version 101.

- name: Mood Lighting
  entities:
    light.living_room_hanging_light:
      state: on
      brightness_pct: 25
    light.bedroom_hanging_light:
      state: on
      brightness_pct: 25
    light.kitchen_cabinet_lights_left:
      state: on
      brightness_pct: 25
    light.kitchen_cabinet_lights_right:
      state: on
      brightness_pct: 25

MQTT Light Config:

- platform: mqtt
  name: 'Kitchen Cabinet Lights Left'
  state_topic: 'homeseer/master/Kitchen Cabinet Lights Left/state'
  state_value_template: >-
        {% if value|int > 0 %}
          99
        {% else %}
          0
        {% endif %}
  command_topic: 'homeseer/master/Kitchen Cabinet Lights Left/set'
  brightness_state_topic: 'homeseer/master/Kitchen Cabinet Lights Left/state'
  brightness_command_topic: 'homeseer/master/Kitchen Cabinet Lights Left/set'
  brightness_scale: 99
  payload_off: 0
  payload_on: 99
  on_command_type: brightness

Source

sqldiablo

Most helpful comment

should we add a breaking change for this in the blog post? seems like its going to impact a lot of users

dshokouhi on 31 Oct 2019

👍3

All 4 comments

With reproduce state it is no longer possible to use attributes in scenes that are no device state attributes. Use brightness (0-255) instead.

Take a look at dev -> states to see which attributes are possible.

Santobert on 31 Oct 2019

Does this affect my current scenes using covers, too? They worked with 0.100.3 but are now reported invalid.

From my unchanged "scenes.yaml":

- name: Sichtschutz
  entities:
    cover.neq1368021:                                                                                                         
      position: 0
    cover.neq1368092:                                                                                                           
      position: 30
    cover.neq1368281:                                                                                                         
      position: 30

Log-Message:

2019-10-31 10:25:12 ERROR (MainThread) [homeassistant.config] Invalid config for [scene]: State for cover.neq1368021 should be a string for dictionary value @ data['states'][0]['entities']. Got None. (See /config/scenes.yaml, line 0). Please check the docs at https://home-assistant.io/integrations/scene/
2019-10-31 10:25:12 ERROR (MainThread) [homeassistant.config] Invalid config for [scene]: State for cover.neq1367183 should be a string for dictionary value @ data['states'][0]['entities']. Got None. (See /config/scenes.yaml, line 11). Please check the docs at https://home-assistant.io/integrations/scene/

Tried to replace "position" with "current_position", didn't work either.