So, not the droid we Are looking for… :(

From my small experience with Qualcomm in the past, I’m not too hopeful. In a company I used to work for, we wanted to use one of their SoC with Linux, which they claimed they supported. It was many years ago. But was full of closed binary blobs which even when signing NDAs, we couldn’t get the source for. We’re talking user-space drivers, sensors offloaded to a separate core with closed source firmware etc. It’s Linux, but it’s not Linux in spirit, it feels so closed and proprietary and secretive. They’re coming from Android, which google architecturally enabled vendors to close their drivers by utilizing HAL. It’s the single most significant blow to Linux by any corporation so far. It enabled thousands of vendors to close their shitty driver in user-space and not maintain it for newer kernels (kernel driver is just an IO proxy for user-space drivers). I get that without it, there wouldn’t be Android phones we have today, but I expected them to slowly open up. 10+ years later, almost nothing changed, in fact - things seem worse to me.

This looks the most promising. I’ll take a closer look. Does it provide a rtsp stream?

Any PC that has virtualization features can be used. Unless it’s very old, I’d say it’s supported. But it may not be enabled in the bios by default. It’s called VT-x for Intel and AMD-v for AMD, I think. But both are supported for at least 10 years on almost any PC.

It’s a hypervisor level virtual machine host and you can use it to install multiple os’s on the same machine with little overhead. I’ve been running haos like that for a few months now and I’m super satisfied.

Compatibility is iffy on some of the newer ones. Here’s a list of what works for some of them: https://github.com/Dunedan/mbp-2016-linux

Yes, for one device, I’d do wifi too. ZigBee does add complexity, but it also adds many possibilities. Esphome is a good solution, I use it also. In fact it seemlessly integrates with HA, so it doesn’t matter

One of the bigger reasons is ZigBee is capable of mesh network forming, which is useful if you want more devices to be smart. It’s also low power. And the devices are in their private network isolated from the internet, which is also a desirable quality. In summary, ZigBee is built for smart devices, whereas wifi not so much.

This is great! I’ve only recently discovered jq and was thrilled to have it after bashing my head in bash for a couple of days. I replaced the whole operation with a single line. This tutorial is just what I need. I like that it’s interactive and has neatly grouped examples! Bookmarking it, as I’ll need it very soon again.

I have a newer ZigBee 3.0 dongle and run a few add-ons, but nothing big - z2m, nodered, mosquito is all I use. I will upgrade anyway, but I’m not in a hurry, it works fine, apart from an occasional delay in switching, which might be network related.

When you switched from pi3 to NUC , did you notice any performance improvements? I’m asking because I run my setup on a rpi3 and it mostly works ok, but the latency is sometimes high, so I’m wondering if upgrading the host will improve things.