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.

What?

I had to replace the motherboard with one from a different variant (same base robot) that could be rooted. Outside of that - super easy.

Idk, the dev seems… hostile.

I’ve only ever seen a dev become “hostile” when people simply don’t read the documentation and ask the same questions over and over and over again.

If it’s a CRL-200S based robot, the manufacturer will straight up brick it within a few days.

Lidar is fucking awesome. My vacuum will damn near chase me out of wherever it’s cleaning 😂

Dumb shit like this is never the engineer’s idea.

I bought a robot vacuum, rooted it, and installed Valetudo (Wyze WVCR200S w/motherboard from a Viomi V6 - same robot).

I don’t have to worry about this shit anymore. The vacuum still does the vacuum thing whether or not it’s connected to the internet.

https://github.com/sysadminsmedia/homebox

Shareholders need more profits. So, shareholders.

Once again - blame the Dodge brothers (yes, that Dodge).

Oh noooooo hahahaha

The previous owner of mine was absolutely a pet owner. It was chock full of fur. Luckily nobody in my house has any pet allergies…

If you can manage to get video out, I’m sure it can be done. Maybe you can even stream Doom to a web browser.

Yeah, that’s a rough one. Manufacturers really don’t want us mucking about and will release different versions under the same name all to obfuscate that process.

A lot of TVs are like this as well; we have a curved Samsung 55" that lost it’s backlight last year - not only did I need the model and serial numbers, I also needed the specific T-con board revision. A similar thing happened on my former TCL Roku TV several years before. Same deal.