mTLS is great and it's a shame Firefox mobile still doesn't support it.
Oh.. I think you also need double quotes around template brackets when used as the value in a service call..? Which conflicts with the quotes around the entity and attribute so just use single quotes there.
brightness_pct: "{{state_attr('light.kitchen_sink_ceiling', 'brightness')}}"
Just whipped up a partial example with my living room lights.
It is missing a trigger and an else butI focused on theactionyou had trouble with.
Using brightness instead of brightness_pct seemed simpler. (Or at least if both can usethe same attribute...)
alias: Example
description: ""
trigger: []
condition:
- condition: state
entity_id: light.living_room_floor_lamp_1
state: "on"
action:
- action: light.turn_on
metadata: {}
data_template:
brightness: "{{state_attr('light.living_room_floor_lamp_1', 'brightness')}}"
target:
entity_id: light.living_room_floor_lamp_2
mode: single
Hmmm if it's just complaining about expecting a float, you could maybe get away with simply multiplying by 1.0
{{state_attr("light.kitchen_sink_ceiling", "brightness") * 1.0}}
I think... {{state_attr("light.kitchen_sink_ceiling", "brightness") | float}} also works these days.
My lights return brightness=None when they're off... and None * 1.0 probably breaks something, so this might be more consistent: {{(state_attr("light.kitchen_sink_ceiling", "brightness") or 0) | float}}
PS: I can't say much about brightness_pct, I normally use brightness instead (0-255).
Oh, no, I meant it could make sense for someone to have an account on vegantheoryclub for that community... then another more generic account on another instance.
TIL
Including this article, that's now twice I've heard about this since 2017.
They can just wait for someone to approve the pull request like everyone one else.
Demon cores aren't literal.
Oui, après... c'est un peu a chacun de nous d'en faire.
Until it is done
I think OP might just have needed the quotes around the template brackets in the yaml.