Hmmm - interesting. I hadn’t bothered to check before now, but I’m seeing something similar on one of the two PBS CTs I run.

Comparing the output of netstat -lantop on both CTs, I can see that the one with more outbound traffic has more waiting connections from localhost on port 82, the port Proxmox Backup Servers provides its API over:

tcp        0      0 127.0.0.1:51562         127.0.0.1:82            TIME_WAIT   -                    timewait (40.38/0/0)
tcp        0      0 127.0.0.1:56342         127.0.0.1:82            TIME_WAIT   -                    timewait (29.92/0/0)
tcp        0      0 127.0.0.1:44864         127.0.0.1:82            TIME_WAIT   -                    timewait (58.94/0/0)
tcp        0      0 127.0.0.1:45028         127.0.0.1:82            TIME_WAIT   -                    timewait (11.88/0/0)
tcp        0      0 127.0.0.1:44026         127.0.0.1:82            TIME_WAIT   -                    timewait (48.66/0/0)
tcp        0      0 127.0.0.1:44852         127.0.0.1:82            TIME_WAIT   -                    timewait (58.80/0/0)
tcp        0      0 127.0.0.1:59620         127.0.0.1:82            TIME_WAIT   -                    timewait (0.00/0/0)
tcp        0      0 127.0.0.1:56374         127.0.0.1:82            TIME_WAIT   -                    timewait (30.98/0/0)
tcp        0      0 127.0.0.1:51544         127.0.0.1:82            TIME_WAIT   -                    timewait (39.98/0/0)
tcp        0      0 127.0.0.1:59642         127.0.0.1:82            TIME_WAIT   -                    timewait (0.00/0/0)
tcp        0      0 127.0.0.1:45008         127.0.0.1:82            TIME_WAIT   -                    timewait (10.92/0/0)
tcp        0      0 127.0.0.1:45016         127.0.0.1:82            TIME_WAIT   -                    timewait (11.76/0/0)

I’m wondering if the graph is pulling aggregated network data, including the loopback interface. If so, and it’s all just port 82 stuff on 127.0.0.1, then it’s probably nothing to worry about.

Edit: found this forum post that seems to indicate it’s aggregating all the byte values from /proc/dev/net, so this is probably nothing to worry about if your netstat output, like mine, only shows API conections to/from 127.0.0.1 on port 82.

Ah, no worries mate. Almost got excited for a minute there.

Are you sure? I went looking after I upgraded and I still only have Assist; Scripts; Actions; and Open Page.

I use Shortcuts with NFC tags to automate some stuff with HA, and could probably achieve something on an entity by entity basis.

My point is that we used to have the ability to put a widget on the screen with about 6 or 8 entities on it, for simple, single-click access. And now we don’t. Seems silly to have taken it away from us.

The casting bit is the missing piece for me.

I’ve built a RasPi with Kodi for our caravan, to use Plex and stream our free-to-air TV here in Australia (using Musk’s space innernets). I just miss being able to cast from my phone, for the occasional thing I can’t do with a Kodi add-on.

It possibly would, but I don’t have any Homekit devices, and I just feel hat this is a simple thing a home automation app should offer, it’s almost conspicuous by it’s removal/absence.

Yep, that’s it. One of my most frequent uses of this widget was to turn the kitchen light off - the teenagers are forever walking in to the kitchen while we’re watching TV in the loungeroom nearby, then forgetting to turn the light off when they leave again.

Having a quick access widget for it just made it such a non-issue for me to turn it off. No fumbling and swiping for the app, and no interrupting what we’re watching to issue a voice command.

Disappointing that, if this was a thing, they removed it. Seems like the very definition of regression to me.

At least I know I’m not imagining it. Or that I’m not the only one. ;) Cheers!

Nah - not a widget per light. Per my OP, I had a widget that had a number of lights on it. The number varies based on widget size. I think mine had about 12 entities on it.

So you can’t possibly conceive that a single finger tap on a home screen widget to control a light is far simpler, and takes less effort, than having to open the app each time, potentially scroll to the location of the entity you want to control, then tap?

Yep, but I’m talking about widgets that you place on your phone’s home screen - not in the app directly.

Thanks for this. Yale was also on my list to look into.

Fantastic. Thank you. Yale was second on my list to research.

Yeah, I’m aiming at quality lock over quality smart. As long as I can get remote lock/unlock going, the smarts will be built into my HA/Node-RED automations.

Good point re keyed lock. I won’t be changing my back door locks, so can always jump a fence if I get desperate.

Awesome feedback. Thanks for that.

Do you happen to know if all Schlage smart locks support the same features, or only a specific model range?

Maybe, but I’ve read some posts that state some Schlage locks can be entirely controlled through Z-Wave without needing cloud access.

But, that may mean I don’t get battery monitoring that way.

+1 to everything you just said - I’ve been using Immich for a little less (370 days, thanks to the same button). It’s feature rich and rock solid.

Only thing I hope they add to the mobile app is the Years/Months/Days option, to make it easy to quickly group, then find, your photos. It’s the one thing that keeps me using my phone’s own Photos app (locally - no cloud sync).

Withy some compression straps around it to make it look smaller in places

Do yuo have IDP/IPS turned on on pfSense? My OPNsense on my 1Gbps fibre will easily drop from an average of 900Mbps down to around 300Mbps-500Mbps, if I turn on IDS.

I’m still using it via mbasic. It looks like shit, but I can get to my messages and reply, etc.