#oof. Well, guess people will still be

1 messages · Page 1 of 1 (latest)

lusty tapir
#

Short answer, no - changing the brightness will turn them on.

What you could do would be write an #automations-archived that's triggered by the lights turning on at zero brightness and resetting the brightness.

lucid skiff
#

Interesting idea, and oops that I was in the wrong channel, but i don't know that would work directly since at least currently my google home is affecting the hue bridge directly, so HACS wouldn't get the request. I'll try to poke around in the scripting and see if I can find something that could be run during daylight hours so it's less noticable

lusty tapir
#

HACS? What has HACS got to do with that?

#

If you meant HA then it can detect changes to devices it's connected to

lucid skiff
# 
mode: single
trigger:
  - platform: device
    type: turned_on
    device_id: 164de00862673003f753caac657cec97
    entity_id: ba8e892297c1216d9e41264e8e44cd2c
    domain: light
condition:
  - condition: numeric_state
    entity_id: light.sera_bedroom_1
    attribute: brightness
    below: 1
action: []
```All the device and entity id's are pointing to sera_bedroom_1, even if the names don't match. Is this looking right for a start?
lusty tapir
#

Device triggers are weird, but yes

lucid skiff
#

Weird is something I can work with. I just wanted to make sure I got the basics first

lusty tapir
#

People will recommend you move to traditional triggers, as they have many advantages

# 
description: ""
mode: single
trigger:
  - platform: state
    entity_id: light.sera_bedroom_1
    to: 'on'
    from: 'off'
condition:
  - condition: numeric_state
    entity_id: light.sera_bedroom_1
    attribute: brightness
    below: 1
action: []
lucid skiff
#

Where would I find those?

#

oh, I just picked the wrong starting point? ok

lusty tapir
#

Entity is what you're after

#

Basically, ignore Device - they're the training wheels version, limited in features

#

Plus, if you replace a device you have to re-work every device trigger/condition/action

#

You can just change the entity_id of the new device to have all the traditional triggers/conditions/actions carry on happily

lucid skiff
#

luckily i'm still early on on making automations. mostly 'turn these lights off or down' at bedtime

#

I'll have to poke more at this later, since I'm being silly and having trouble finding how to call entities as the action, but it's also late and I don't have the headspace to read through the docs. I feel like there's more that I can do with this once I know what I'm doing

lusty tapir
#

Service calls

#

light.turn_on

manic falconBOT
lucid skiff
#

so, I don't normally like to necro threads, but wanted to let you know what ended up happening. I couldn't get the script you gave me to work because afaik from the error it didn't have 'below' as a valid option for the comparison

#

That said, I did poking around and I finally got this to work alias: Sera AM ```lighting fix
description: Resolves issue of lights turning on at brightness zero
trigger:

  • platform: state
    entity_id:
    • light.bedroom
      from: "off"
      to: "on"
      condition:
  • condition: state
    entity_id: light.sera_bedroom_1
    attribute: brightness
    state: 0
    action:
  • service: scene.turn_on
    metadata: {}
    target:
    entity_id: scene.bedroom_100
    mode: single
lusty tapir
#

Sounds like you weren't looking at numeric_state

lucid skiff
#

I couldn't figure out how to access that

lusty tapir
lucid skiff
#

ahhh, and i went state I guess. oops