Monument

I wouldn’t say I ‘run’ it, but I mess around with it

I have a base level Mac Mini I got before the price increase a few years ago, also from when models were smaller and my ambitions were less. I’ve contemplated upgrading it, but I have other things to spend my money on.

M4 processor, 16 gb ram, 256 gb storage, and a 4tb external HDD drive (an old NAS drive).

It’s fine. It’s mostly a docker machine, but I do throw AI tasks at it a few times a week. Mostly stuff that I just let it chew on for 5-10 minutes and come back to.

I run openwebui, and have several models I bounce between. I mostly run Gemma4 (Google) and Granite4.2:8B (IBM).

Editing to add: the self hosted version of all these models, via llama, just in case that was unclear.

On a review of the blueprint I’m using in HA, it does appear so!

I think I only knew that before I bought because I watched a review over them. I’m on the same page regarding IoT devices on WiFi. Needs must if I have to, but I keep a separate WiFi network for them, with different access rules.

Nah.

While they do use the Matter communication standard, these devices use the Thread protocol. The Venn diagram/conceptual model of how these interrelate is messy because Matter can run on both Thread or WiFi (depending on the hardware of the device), and Thread is a platform that supports multiple standards.

These remotes are Matter over Thread:

That’s possibly your detection settings or method (detection criteria, etc). My washer and dryer are separate devices on separate power monitoring plugs. The only time power draw for either goes above 2 watts is when they’re cycled on.

I just told the blueprint to wait 2 minutes before deciding a cycle has started before declaring it’s started, and 5 minutes after it has ended before sending a notification.

But I mean, I’m not here to yuck your yum. If it works for you, it works for you.

Sure – Ikea Bilresa scroll wheel blueprint (Matter) - The Original.
You do have to install the helper scripts and enable the disabled entities for full support, but so far, no complaints.

I use this - IKEA Bilresa scroll wheel. It also comes in a 3 pack for $28.

I’ve got it working in HomeAssistant, and they’re pretty neat. The knob has a click action, and the remote has a click action, too. Clicks on the remote allow you to select between 3 different ‘channels.’
In HA, you can set each channel so that the click and scroll does something different. (The blueprint I use has click, long press, double, triple, and quad click, as well as scroll wheel actions.)
I’m not that fancy - I’ve got each channel’s click action mapped to on/off toggle, and to brightness, color temp, and a hue scroller.

But why install an integration when the Appliance Notifications and Actions blueprint exists?

I think the only functional difference is that Washdata attempts to infer which cycle was run, but the blueprint doesn’t have to be configured via yaml.