Hey, I’ve seen your deleted post about trying to seed your instance.
You seem to be the admin of a new instance.
By default, your instance won’t see any remote communities content until someone subscribes.
Which is kind of a catch 22, because you kinda have to know about it to subscribe.
To browse for communities:
https://lemmyverse.net/communities
You can then use your instance’s search bar to fetch it initially in order to subscribe to it yourself.
Which you’ve likely already done for this one.

There’s also a tool that can do this for you:
https://lemmy-federate.com/ (which was formerly known as communityboost)
Then again it may subscribe to things you aren’t interested in, so that may or may not be for you.

Cheers, welcome and good luck.

Fighting global warming with… nuclear winter.
🤔

Anywhere that’s free of light pollution.
I just wanna look at the stars dammit

40 minutes, once, in 2015, Canada.

Usually, 2-5 minutes.

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.

Way back in the day, developing photo film in the shop’s backstore lab.
The coroner pictures were always… something.
At least the hawking boss would GTFO though, silver linings.
Then again that’s not as bad as being actually there and scooping various stuff.

Presumably, a live baby would move way too much for photogrammetry to be useful.

an ancient card with a colorful box from 3dfx.
I think it was a voodoo 2, but not one that came bundled with creative soundblaster.
Yes, we needed another physical card for sound.

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.

Sunken cost fallacy maybe.

Good ole firehose

Évelyne is faily common around here still.

Gilgamesh is one I haven’t heard in a hot minute, not sure about the comeback though.

That one standoff got loose 12 years ago, so none.
Otherwise, it’s all HDMI and DP.