I got a couple of PM plugs with Matter support. I can’t pair them with HomeKit or Home Assistant. I spent about 5h troubleshooting this, inspecting network packets and whatnot and didn’t get any closer to having them working.
I’d rather things just had MQTT support. Happy with Zigbee though, as I can route those to MQTT as well.
I don’t think I’ve ever come across a DNS provider that blocks wildcards.
I’ve been using wildcard DNS and certificates to accompany them both at home and professional in large scale services (think hundreds to thousands of applications) for many years without an issue.
The problem described in that forum is real (and in fact is pretty much how the recent attack on Fritz!Box users works) but in practice I’ve never seen it being an issue in a service VM or container. A very easy way to avoid it completely is to just not declare your host domain the same as the one in DNS.
If they’re all resolving to the same IP and using a reverse proxy for name-based routing, there’s no need for multiple A records. A single wildcard should suffice.
Man, that brings back memories! XGH is the OG agile methodology.
I would get a CAD model of the PS5, import it into fusion and design the part around it either by extruding to it or using it as a cut tool.
They mention versions from 5.5.1 are affected.
Everywhere else I’ve read only 5.6.0 and 5.6.1 are.
Is this an abundance of caution by the Debian security team, or is Debian’s earlier version affected due to patching done by the package maintainers?
Not sure if this is helpful in any way, but it might give you some clue.
100./8 addresses are reserved for CG-NAT.
This is probably the IPv4 address your modem/router is receiving from the ISP.
The default files for each new user are stored in this directory. Each time a new user is added, these skeleton files are copied into their home directory. An average system would have: .alias, .bash_profile, .bashrc and .cshrc files. Other files are left up to the system administrator
https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/etc.html
I might pick it back up some day but at the moment I have other projects going on at the moment.
I’m still using Proxmox myself but unfortunately it’s all fairly manually configured.
I started writing a Terraform provider for Proxmox a while ago.
Unfortunately, the API is a massive mess and the documentation is not very helpful either. It was a nightmare and I eventually gave up.
K3s is k8s
lol at the downvote. K3s is k8s. The very first 2 words in its website are Lightweight Kubernetes. https://k3s-io.github.io/
On macOS I’ve been using Ollama. It’s very easy to setup, can run as a service and expose an API.
You can talk to it directly from the CLI (ollama run ) or via applications and plugins (like https://continue.dev ) that consume the API.
It can run on Linux but I haven’t personally tried it.
K8s and Proxmox operate at different levels. You can run k8s on Proxmox, and that’s what I’ve been (very slowly) building up to at home.
With Proxmox you can failover VMs between nodes as long as storage (including VM boot disk) is external to the nodes. This can be NFS on a NAS, iSCSI, Ceph or many other options.
It’s even possible to failover a USB device (e.g. a Zigbee controller or similar) by attaching one on each node and mapping them using Resource Mappings (search on the announcement post: https://www.proxmox.com/en/about/press-releases/proxmox-virtual-environment-8-0).
This can also be used if you’re deploying k8s on top of Proxmox just as well.
It’s pretty easy with Ollama. Install it, then ollama run mistral-7b (or another model, there’s a few available ootb). https://ollama.ai/
Another option is Llamafile. https://github.com/Mozilla-Ocho/llamafile
I second Shelly. A Shelly Plus 1 Mini is cheaper and probably more than enough for OP’s use case.
I run it on my router which has the CG-NAT IP address.
Whilst you’re right that it could clash, it’s very unlikely (a 1 in 4194302 chance), I imagine Tailscale would detect the clash and change IPs though I could be wrong as it never happened to me (and probably never will - though in all fairness it will eventually happen to someone).
Been using Tailscale behind CG-NAT for years. It works wonderfully and very rarely needs to route through the DERP infrastructure - it’s almost always a P2P connection.
You’re not wrong that the storage itself is undoubtedly more robust on any cloud provider than a cheap consumer NAS box.
However, there are other factors to consider.
A NAS or any storage solution is only useful if you can access it if you need and if the network speed and stability match your expectations.
A cloud solution will be inaccessible if your internet is down. It may also suffer tremendously if your connection is unstable or slow.
In that sense, even a laptop’s drive connected to your switch could prove more robust than any cloud solution.
Love Shelly and would second the recommendation except OP asked for Zigbee which they aren’t.
They’re Meross, this one specifically.
https://shop.meross.com/products/meross-matter-plug-with-energy-monitor-mss315-uk