The day I hit a tree with my sports car or what have you, my family would certainly be less sad if they could keep the lights on, control the heating and so on.
It’s made so you could remove node red and still have basic functionality, but I really need to document a bit, share passwords, so a trusted friend could help them just in case
250! Wow, I thought I was already nuts with my 42 ZigBee devices + 10 reflashed sonoff over WiFi and my 8 cameras, doorbell etc… Let’s round up to 60; you are way ahead (oO)
I run everything on a single N100 mini NAS/PC with a remote slave backup NAS and the odd raspberry pi.
I’m more concerned about having to document in case I die than being able to keep all in mind, so far
I run docker within LXC too, but I have just a pair of docker instances with a collection of compose stacks on each. I really need stickers.
I should have a look at podman one day
Debian and docker. When you’ll have your local server, just go with Proxmox, which is based on Debian. On that you’ll be free to run any Linux flavour as an LXC container. As you are already familiar with it, that’s a no-brainer. The day you decide to play with a raspberry pi, Raspberry-Pi OS is also Debian with very little customisation.
I use owntracks with a free cloudaqmp plan for the mqtt broker. It felt safer than trying to manage my own mqtt open inf the internet. The data is decrypted and parsed by a dedicated node on my main node red instance.
We’re on the first Sunday of the month, mdadm raid array be scrubbing… With Debian 13 came a crazy complex systemd scheduling for that, I liked the awkward cron job better. It’s now using some kind of random delay before start, and cut in chunks of 6 hours or so over multiple days Edit: typos