I’ve created a Scene which consists of 8 RGB+CCT lights. When I activate this scene, all MQTT light commands are send after each other at high speed. Unfortunately, the MiLight Hub cannot handle this burst of commands and drops commands. As a result, several lights are not updated.
Is there a possibility to slow down the MQTT publish commands when activating a Scene without creating an Automation?
Or is it possible to wait for a light status change before sending the next light command for each Scene?
configuration.yaml
mqtt:
broker: homeassistant
port: 1883
username: user
password: password
discovery: true
discovery_prefix: ha
light:
- name: MiLight FUT089 0x1234 Zone 0
unique_id: milight_fut089_0x1234_0
command_topic: "milight/cmd/fut089/0x1234/0"
state_topic: "milight/state/fut089/0x1234/0"
<<: &MILIGHT_RGBCCT_PARAMS
platform: mqtt
schema: json
brightness: true
color_temp: true
- name: MiLight FUT089 0x1234 Zone 1
unique_id: milight_fut089_0x1234_1
command_topic: "milight/cmd/fut089/0x1234/1"
state_topic: "milight/state/fut089/0x1234/1"
<<: *MILIGHT_RGBCCT_PARAMS
- name: MiLight FUT089 0x1234 Zone 2
unique_id: milight_fut089_0x1234_2
command_topic: "milight/cmd/fut089/0x1234/2"
state_topic: "milight/state/fut089/0x1234/2"
<<: *MILIGHT_RGBCCT_PARAMS
- name: MiLight FUT089 0x1234 Zone 3
unique_id: milight_fut089_0x1234_3
command_topic: "milight/cmd/fut089/0x1234/3"
state_topic: "milight/state/fut089/0x1234/3"
<<: *MILIGHT_RGBCCT_PARAMS
- name: MiLight FUT089 0x1234 Zone 4
unique_id: milight_fut089_0x1234_4
command_topic: "milight/cmd/fut089/0x1234/4"
state_topic: "milight/state/fut089/0x1234/4"
<<: *MILIGHT_RGBCCT_PARAMS
- name: MiLight FUT089 0x1234 Zone 5
unique_id: milight_fut089_0x1234_5
command_topic: "milight/cmd/fut089/0x1234/5"
state_topic: "milight/state/fut089/0x1234/5"
<<: *MILIGHT_RGBCCT_PARAMS
- name: MiLight FUT089 0x1234 Zone 6
unique_id: milight_fut089_0x1234_6
command_topic: "milight/cmd/fut089/0x1234/6"
state_topic: "milight/state/fut089/0x1234/6"
<<: *MILIGHT_RGBCCT_PARAMS
- name: MiLight FUT089 0x1234 Zone 7
unique_id: milight_fut089_0x1234_7
command_topic: "milight/cmd/fut089/0x1234/7"
state_topic: "milight/state/fut089/0x1234/7"
<<: *MILIGHT_RGBCCT_PARAMS
- name: MiLight FUT089 0x1234 Zone 8
unique_id: milight_fut089_0x1234_8
command_topic: "milight/cmd/fut089/0x1234/8"
state_topic: "milight/state/fut089/0x1234/8"
<<: *MILIGHT_RGBCCT_PARAMS
scenes.yaml
- id: '1609961467180'
name: 'On'
entities:
light.milight_fut089_0x1234_zone_1:
min_mireds: 153
max_mireds: 500
brightness: 48
color_temp: 275
friendly_name: MiLight FUT089 0x1234 Zone 1
supported_features: 43
state: 'on'
light.milight_fut089_0x1234_zone_2:
min_mireds: 153
max_mireds: 500
brightness: 3
color_temp: 153
friendly_name: MiLight FUT089 0x1234 Zone 2
supported_features: 43
state: 'on'
light.milight_fut089_0x1234_zone_3:
min_mireds: 153
max_mireds: 500
brightness: 31
color_temp: 314
friendly_name: MiLight FUT089 0x1234 Zone 3
supported_features: 43
state: 'on'
light.milight_fut089_0x1234_zone_4:
min_mireds: 153
max_mireds: 500
brightness: 3
color_temp: 153
friendly_name: MiLight FUT089 0x1234 Zone 4
supported_features: 43
state: 'on'
light.milight_fut089_0x1234_zone_5:
min_mireds: 153
max_mireds: 500
brightness: 3
color_temp: 370
friendly_name: MiLight FUT089 0x1234 Zone 5
supported_features: 43
state: 'on'
light.milight_fut089_0x1234_zone_6:
min_mireds: 153
max_mireds: 500
friendly_name: MiLight FUT089 0x1234 Zone 6
supported_features: 43
state: 'on'
light.milight_fut089_0x1234_zone_7:
min_mireds: 153
max_mireds: 500
brightness: 112
color_temp: 329
friendly_name: MiLight FUT089 0x1234 Zone 7
supported_features: 43
state: 'on'
light.milight_fut089_0x1234_zone_8:
min_mireds: 153
max_mireds: 500
friendly_name: MiLight FUT089 0x1234 Zone 8
supported_features: 43
state: 'on'