InEnduringGrowStrong@sh.itjust.works

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

The router polling integration is probably a bit superfluous for devices that have the companion app installed.
Although, it’s still helpful for other devices like guests’ phones, or non android/ios devices.

Not sure how helpfully to your use case these will be, but a few ideas…

It’s been a while since I tinkered, but I think you can also assign multiple devices to a person and track the person’s presence instead of a specific device.
You can also create a group of persons, which is handy for some use cases.

As an example, I have a group.us which contains person.me and person.mypartner. The group’s status is home if either of us are home and only changes to away if neither of us are home.

Similarly, I have a group.guests which contains guests who sometimes spend the night.
If any guests are home, my goodnight automation ignores the bathroom and the guest bedroom lights.

group.guests:

entity_id:
  - input_text.manual_guest_tracker
  - person.guest
  - person.fren
  - person.otherfren
  - person.olefren
  - person.stepbro
  - person.nephew
  - person.cousin
  - person.niece
order: 3
icon: mdi:bag-carry-on
friendly_name: Guests

I have an input boolean that changes input_text.manual_guest_tracker to home/not_home if we wanna enable “guests mode” without having to track a device.

Single person with multiple trackers:
person.fren:

editable: true
id: fren
device_trackers:
  - device_tracker.applewafren
  - device_tracker.iphonefren
friendly_name: Fren

In the companion app, where you choose the update interval, there’s a banner of text that explains it.
Some sensors update instantly (such as connected WiFi SSID), others update on an interval (such a battery level or pressure sensor).
The maximum update interval applies to non-instantaneous sensors.

Sensors will update either instantly or on a defined interval. If the sensor supports instant updates then it will always receive instant updates. View the sensor details to learn which sensors update instantly.
If the sensor does not support instant updates then it will update based on one of the below selected options
You must restart the application when you make any changes to this setting

When you select which sensors to enable you can see whether it’s an instantly updating one or one on a timer

Haven’t had to use port forwarding for gaming in like 30 or so years, so I just looked up Nintendo’s website…

Within the port range, enter the starting port and the ending port to forward. For the Nintendo Switch console, this is port 1024 through 65535

LMAO, no thanks, that’s not happening.

For your question, you could likely route everything through a tunnel and manage the port forwarding on the other end of the tunnel.

Ultimately, do whatever you think you’ll be able to keep up with.
The best documentation system is useless if you keep putting it off because it’s too much work.

It can be in git even if you’re not doing ‘config as code’ or ‘infrastructure as code’ yet/ever.
Even just a text file with notes in markdown is better than nothing. Can usually be rendered, tracked, versionned.
You can also add some relevant files as needed too.

Like, even if your stuff isn’t fully automated CI/CD magic, a copy of that one important file you just modified can be added as necessary.

Also, the crackling might be something about the sampling rate. It’s been a while since since I poked around with audio, but I vaguely remember changing the default sampling rate and restart pulseaudio or something like that.

In my case, I think the onboard audio device is in the same group as the motherboard chipset, which would explain the host crashing when passing through.

Hmmm… I do have audio coming out of a guest VM under proxmox, but I’m passing through a whole GPU which includes audio through its HDMI.

The on-board audio might not be in an iommu group that can be passed without breaking something else, which would likely prevent booting the host correctly.

Honestly, I think I’d just go with a USB dongle for the audio. Easier to passthrough, likely better audio quality too and shouldn’t be too expensive.
You can pass either a USB device id or a port (or group of ports, depending on how it’s grouped)

are you alright?

Yea, if anything it makes good practice.
Swapping hard drives in the larger data pool isn’t as daunting anymore.
Although, I gotta be honest, swapping drives in the zpool from which proxmox boots itself is still a bit iffy to me.
I had to set a reminder, because otherwise I won’t do it often enough.

Personally I use a ZFS pool in my Linux homelab that’s been rock solid. However the pucker factor would be high if a drive fails.

I use a ZFS pool for my home stuff too.
To minimize the pucker factor, I have an extra drive of the same capacity and I rotate through them in the mirror pool.
It makes good practice replacing and resilvering drives and since it’s a mirror it’s also kind of an offline backup.
Also, I had bought the initial drives at the same time and figured rotating though them would minimize the odds of failing around the same time.
I’m much less wary of the whole thing now that I’ve resilvered the drives several times.

Are you trying to recover data here?
Seems like you didn’t use it and (maybe?) don’t have data to lose here?

Yea I’ve been using nextcloud for a while and it’s fine.
I remember when I used owncloud before nextcloud was even a thing and the upgrade experience was absolute shit.
These days it’s just fine.

Ah nice you got it working.
Once it works it’s great.
I’ve been running mine for a while now, but purposefully avoided Kernel upgrades so far.

It does seem a lot like the reset bug, but then you already tried that. :/ Kernel module aren’t as easy to install and if you’re missing the required flags it might just do nothing.

grep -E '(CONFIG_FTRACE|CONFIG_KPROBES|CONFIG_PCI_QUIRKS|CONFIG_KALLSYMS|CONFIG_KALLSYMS_ALL|CONFIG_FUNCTION_TRACER)\b' /boot/config-`uname -r`  

Should show the 6 flags =y

Or maybe some variation of manual reset…
https://forum.proxmox.com/threads/issues-with-intel-arc-a770m-gpu-passthrough-on-nuc12snki72-vfio-pci-not-ready-after-flr-or-bus-reset.130667/