Why do you want to ditch KeePass? I use it with Syncthing between at least six different devices without an issue.

The other maintainer, nel0x (who does the Play Store releases), has started distributing a degoogled version of their own. nel0x is arguably more trustworthy.

Could you tell me more about the non standard implementation? Coz I just use composerize to convert docker run commands to compose (or if I find compose files then hooray!) and pop those into portainer. Seems to work fine.

Portainer is generally fine, but if you decide to migrate away from it, you will basically need to rebuild your whole compose stack setup.

I don’t like that a lot of features seem to be hidden behind a costly subscription, but thems the brakes.

Yeah, that was a big reason I moved away from it myself. They used to be way more flexible, but started really clamping down on free users a few years ago.

As for proxmox… is it lighter weight than Debian?

Proxmox uses Debian as its base OS, and since Proxmox is built to run full VMs, it isn’t really comparable to running Docker containers on bare metal. You can run multiple Docker stacks inside a VM (including Portainer) - I do this with several VMs. But running a full VM inside a hypervisor on top of already-stressed hardware is probably a tall ask. So in your case, I would stick to Debian with Docker on bare metal.

The other thing I’m curious about - are you running a desktop environment on this machine? Or is it running headless? A DE will take up a lot of resources that the N5095 is already short on, and that CPU isn’t exactly a great contender for streaming, either… It tends to fall on it’s face if running much more than a single stream - including other services.

Portainer is just a docker container that manages other Docker containers. IMO, it’s going down the enshittification hole. They chose to use a non-standard implementation of compose files, so you’re stuck using Portainer unless you reconfigure your whole setup.

Proxmox, by contrast, is a hypervisor meant to run VMs and LXCs. The Proxmox devs have explicitly stated that nothing else should be running outside of it.

Home Assistant.

If you want smart devices but not the data collection that goes with it, then Home Assistant is your friend. Just be forewarned that it is a seriously deep rabbit hole.

My only gripe is that there isn’t a good Android app to go with it. I’d like to receive notifications on my phone, too.

Home Assistant can do notifications for Frigate that are very similar to Ring’s notifications.

I use Home Assistant’s own Connect ZBT-1 and ZHA. It works well with my ~40 zigbee devices.

I used to run Wyze bulbs over wifi, but they were too unreliable and didn’t always respond to commands. Switched to ZigBee with Thirdreality bulbs, they respond much quicker and are far more reliable than the Wyze bulbs ever were.

Muffler bearing

Oh no!

Anyway…

This is the kind of attitude that drives people away from open source.

Yes, people should read the manual, but at some point they will have questions, and there are a lot of projects that aren’t clear on certain things. Such as YAML changes.

Could it be a competitor for that particular product? Hired some foreign entity to hit anything related to their own product?

Syncthing itself is fine. Syncthing-Fork, a completely separate project that wraps Syncthing into a neat app for Android, is what’s going through the repo drama.

Besides - it looks like the new repo owner is pretty transparent about the whole thing and appears to be making good-faith efforts to keep the original Syncthing-Fork devs involved.

I mean, 35W maximum is still incredibly low. At that point, you’re looking at a cost difference in the single-digits over the course of an entire year.

My little lab has 5 machines, 3 of which are tiny/mini/micro PCs. Total draw from my entire setup, including the t/m/m machines, is right around 100W. And since I started measuring it back in February, it’s used a total of 635 kWh. And most of that is from the spinning rust hard drives. For reference, my whole household’s monthly usage averages around 1200 kWh.

I haven’t figured out the whole high availability thing yet; I just move VMs/containers to different nodes if I need to bring a node down, or shift resources around, or whatever.

A 7th-gen i7-powered tiny/mini/micro is perfect for HA. Plenty of grunt for lots of HA addons and integrations, lots of USB ports for dongles (zigbee, z-wave, etc), often with 2x M.2 slots (usually one B/M key and one A/E key) and SATA interface, very low power draw, and cheap due to businesses offloading them all the time.

I have a Proxmox cluster and still went with a separate machine for HA. I figure the thing controlling my house should be on it’s own, since the cluster is more a playground for me than anything else.

I stopped using CF tunnels specifically because of shit like today’s outage.

It was posted Sunday afternoon.

Today is Tuesday.

Ahh. To my knowledge, iRobot units aren’t rootable, and are therefore unsupported by Valetudo.

https://valetudo.cloud/pages/general/supported-robots.html

My Wyze is based on an ODM unit, the 3irobotix CRL-200S. Companies like Wyze, Xiaomi, Viomi, iLife, Conga, and other brands customize and sell it as their own models since that’s cheaper than manufacturing their own units. Parts are swappable between them as they are all the same robot underneath… Kinda like how car companies rebrand models based on region. As far as I’m aware though, iRobot builds their own robots.