If OP somehow needs to translate between beignes and brightness_pct.
Probably something like this:

brightness: "{{state_attr('light.kitchen_sink_ceiling', 'brightness') | float(0) /255*100}}"

I think OP might just have needed the quotes around the template brackets in the yaml.

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).

They can just wait for someone to approve the pull request like everyone one else.

The CVV should really be 2FA from your card issuer.

But even my current Xiaomi router with stock firmware creates hash mismatches using apt

That’s a huge fucking red flag and I would yeet any network equipment responsible for fudging such a thing.

Clothes dryer and a bucket of sand would probably work.
Plus you can sell the self-dismantled dryer for parts after.

Sorry, I didn’t mean to joke about your situation.
I’ve had my share of sketchy roomies.

That person sounds like a terrible match.

cut him out after this lease is up.

Are you roommates or is this some new rent-a-friend gig economy dystopia I don’t know about?

Same kinda genius who programs it with “KEEP YOUR EYES ON THE ROAD”, but more dangerous.

Indeed

Edit the sudoers file.

## user is allowed to execute halt and reboot 
whateverusername ALL=NOPASSWD: /sbin/halt, sbin/reboot, /sbin/poweroff

I can assure you that some people climb without being anywhere close to what I’d call “very careful”.

To me, part of being careful includes not trusting any random unknown person or their gear.
It includes double-checking the people I trust and requiring them to double-check me.

Don’t get me wrong, I’ve met plenty of great people who were careful, safe climbers.
I’ve also met a few climbers of a… weird kind, like it’s almost a caricature, but these people exist.

Climbers who could barely tie a knot, climbers that were stoned af, climbers that kept using carabiners or rope that I wouldn’t even trust to tie their dog.

Also: Even careful people make mistakes.

Aye. Whether or not it happened is completely irrelevant to the meme.

I’ve done this in the past and it works, briefly.

From the lemmy.world sidebar.

Please note, you will NOT be able to comment or post while on a VPN or Tor connection

https://lemmy.world/post/11967676

Xitter (pronounced shitter)

This looks like a charity embezzlement scheme more than anything.