I’m not sure that a $100 espresso machine even exists.

My humble opinion is you’ll be hard pressed to find something that’s less work than an aeropress, let alone anything that takes even less space than that.
If you’re just looking to froth milk, maybe just get an electric milk frother.

advising firewall customers to take steps to secure their firewall management interfaces amid unverified rumors of a possible new vulnerability.

This should already be done regardless of this vulnerability though.

The only way to protect yourself from something like this is to own your own domain name.
You can still use something like Google as a provider but you can switch providers and recreate the same email addresses.

Exit polls are flawed in the sense that the people who don’t vote aren’t there to begin with.

Like say… stand in the middle of Fifth Avenue and shoot somebody.

Not even sure that would do it tbh.

Time and experience over things.

The actual swamp.

Removing this one as a duplicate. Keeping the other one, which has comments.

It’s as if… the time to get this done was a long time ago.

All blame and no plan It’s like corporate middle manglement

8k hours is a lot.
That’s like PhD level, into a game I’ve never heard of before now.
Sure, It’s trust their input.

Last?
(x) doubt

I honestly can’t tell these apart between a $200k one and a $10 one. They’re all just different outputs from the same prompt

Regardless of this bug… this part is completely insane:

As I write this, its most expensive champion is listed at $256,570,000.

I predict someone will win this election.

40 minutes, once, in 2015, Canada.

Usually, 2-5 minutes.

Jlai.lu

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.