Change thunder icons for lights

Hi All,

Happy 2021!

IS there a way to change the thunder icons for lights:

Schermafbeelding 2021-01-07 om 13.21.53

The light bulb is changeable in customize part. But the thunder part I can’t change.
Cheers,

Is that a light entity? What card is this? Is it the modal pop-up on the entity? You need to give more details. Show your relevant config(s) and explain what you’ve done and tried.

entities:
  - entity: binary_sensor.zwave2mqtt_nodeid_108_contact
    name: Motion Diningroom
  - entity: light.dressoir_all
    toggle: true
    type: 'custom:slider-entity-row'
  - entity: light.dressoir_1
    toggle: true
    type: 'custom:slider-entity-row'
  - entity: light.dressoir_2
    toggle: true
    type: 'custom:slider-entity-row'
  - entity: light.dressoir_3
    toggle: true
    type: 'custom:slider-entity-row'
show_header_toggle: false
type: entities

Just basic from HA itself

usually this is displayed on switches. not lights. you can get the toggle to appear using

homeassistant:
  customize_glob:
    light.dressoir*: # <---- replace this with you lights, but only if this is needed on all dressoir lights
      assumed_state: false

still, seems odd this would be necessary for lights, havent seen that before. Are they special kind of lights?

1 Like

Where did the lights come from? What integration? Post your configuration for the integration. Also, go to developer tools -> states page and take a screenshot of the light.

You’re assuming he uses customui…

@petro

The Light is not in customize or global

- name: "Dressoir 1"
  command_topic: "Milight_Hub/0xAAAF/rgb_cct/1"
  state_topic: "Milight_Hub/states/0xAAAF/rgb_cct/1"
  <<: &MILIGHT_PARAMS
    platform: mqtt
    schema: json
    color_temp: true
    rgb: true
    brightness: true
    effect: true
    qos: 1
    optimistic: true
    retain: false
    availability_topic: "Milight_Hub/client_status"
    payload_available: "connected"
    payload_not_available: "disconnected"
    effect_list:
      - "night_mode"
      - "white_mode"
      - "0"
      - "1"
      - "2"
      - "3"
      - "4"
      - "5"
      - "6"
      - "7"
      - "8"

- name: "Dressoir 2"
  command_topic: "Milight_Hub/0xAAAF/rgb_cct/2"
  state_topic: "Milight_Hub/states/0xAAAF/rgb_cct/2"
  <<: *MILIGHT_PARAMS

- name: "Dressoir 3"
  command_topic: "Milight_Hub/0xAAAF/rgb_cct/3"
  state_topic: "Milight_Hub/states/0xAAAF/rgb_cct/3"
  <<: *MILIGHT_PARAMS

- name: "Dressoir All"
  command_topic: "Milight_Hub/0xAAAF/rgb_cct/0"
  state_topic: "Milight_Hub/states/0xAAAF/rgb_cct/0"
  <<: *MILIGHT_PARAMS

You don’t have a state_value_template for any of those lights so the system doesn’t know if the light is on or off. Add a state_value_template and it will switch from the lightning bolts to a toggle.

HA is know when light is going on.
When I turn it on in the milight_hub interface I see the light goes on in HA as well.
So that is working.

You mean this line then?

state_value_template: "{{ value_json.state }}"

assumed_state: false is documented in the core docs, don’t need custom_ui for that:

must admit Im not sure customize_glob is too, but it certainly is for recorder integration, so it might be for customize…
if not, one can customize per entity in core, without custom_ui.

Yes, state_value_template. But the template needs to extract the correct info out of your state_topic to properly handle the state.

Also, you’d probably want an effect_value_template, which does something similar.

Yes, I know that. But you posted code for custom_ui and globbing, which is not in core. To clarify to you: Globbing comes from customui.

as I already supposed myself. Even worse, it is only documented for switches, so OP might not be able to use any of my suggestions…

but, given the fact these are mqtt lights, and your suggestion for a value_template, he should be good to go.

This is the MQTT output:

{
  "state": "OFF",
  "status": "OFF",
  "brightness": 255,
  "level": 100,
  "kelvin": 51,
  "color_temp": 264,
  "bulb_mode": "white",
  "color": {
    "r": 255,
    "g": 255,
    "b": 255
  },
  "effect": "white_mode"
}

That I guess this must be correct to add if I want add all the options:

command_off_template: '{"state": "OFF"}'
command_on_template: '{"state": "ON"}'
state_template: '{{ value_json.state }}'
effect_template: '{{ value_json.effect }}'
color_temp_template: '{{ value_json. color_temp }}'
brightness_template: '{{ value_json. brightness }}'
red_template : '{{ value_json.color[0] }}'
green_template : '{{ value_json.color[1] }}'
blue_template: '{{ value_json.color[2] }}'

I would guess so. you can easily add it to your anchor, so give it a whirl.

Tried already. Checker gives a error and VSC say on all lines its not allowed… haha

in a JSON Schema there are no:

command_off_template: ‘{“state”: “OFF”}’
command_on_template: ‘{“state”: “ON”}’
state_template: ‘{{ value_json.state }}’
effect_template: ‘{{ value_json.effect }}’
color_temp_template: ‘{{ value_json. color_temp }}’
brightness_template: ‘{{ value_json. brightness }}’
red_template : ‘{{ value_json.color[0] }}’
green_template : ‘{{ value_json.color[1] }}’
blue_template: ‘{{ value_json.color[2] }}’

So this won’t work.

Change this card like this. Tap on the bulb turn on/off, long press give me color_picker.
Behind the brightness line I see the percentage of brightness.

entities:
  - entity: binary_sensor.zwave2mqtt_nodeid_108_contact
    name: Motion Diningroom
  - entity: light.dressoir_all
    toggle: false
    tap_action:
      action: toggle
    hold_action:
      action: more-info
    type: 'custom:slider-entity-row'
  - entity: light.dressoir_1
    toggle: false
    tap_action:
      action: toggle
    hold_action:
      action: more-info
    type: 'custom:slider-entity-row'
  - entity: light.dressoir_2
    toggle: false
    tap_action:
      action: toggle
    hold_action:
      action: more-info
    type: 'custom:slider-entity-row'
  - entity: light.dressoir_3
    toggle: false
    tap_action:
      action: toggle
    hold_action:
      action: more-info
    type: 'custom:slider-entity-row'
show_header_toggle: false
type: entities

Rubbish

1 Like

TIL, wasn’t always there though :wink: