@[email protected] There is absolutely no way any starter will see that page and not be intimidated. I am a well seasoned selfhoster and even I saw that and went "Wow that's a lotta words and images on a single page."

Even arch wiki has sensible ToC with pages divided into what the current topic is.

@[email protected] Hygrometers are only as good as their components. Buying a DHT11/22 or SHT31 from AliExpress ($1-2) alongside an ESP8266/32 and you'd have much better results than buying these "are my cigars dry" pucks.

@[email protected] I have about $150 worth of Ali parts and components coming just this month for whole house monitoring for this kinda thing - temp, humidity, CO2, VOCs, pressure, light sensors etc. Would be glad to ping y'all once that writeup is done :)

@[email protected] You Could in theory just use wireguard with nginx.

DNS pointing to Public VPS -> Nginx running on public vps -> Nginx resolving to internal wg IPS -> Any of your other devices.

@[email protected] Fwiw, LinuxServer still maintains a resilio-sync docker image for 3.0.0. They are fairly trustworthy.
https://hub.docker.com/r/linuxserver/resilio-sync

@[email protected]

@[email protected] In theory you could use Matrix and use bridges to access these. On the other hand it kills encryption because now Your endpoint is where it decrypts and re-encrypts the new messages.

Spantaleev's Matrix Docker Ansible remains the most popular project for this (lots of documentation, good community): github.com/spantaleev/matrix-docker-ansible-deploy

@[email protected] SHT31/41 are better than DHT22 tbf. DHT would have a variance of about 2-5%. It also takes a while for it to stabilize.

@[email protected] True - but it really depends what you're measuring with BME280/680s though (680>280). As a combination temp/humidity/pressure they're excellent, but for humidity alone I think SHT gives better "expected" readings than BME.

Someone nerded it out on arduino forums about five years ago: https://forum.arduino.cc/t/compare-different-i2c-temperature-and-humidity-sensors-sht2x-sht3x-sht85/599609/10

@[email protected] I'd start with ABS anyway. It is the most mature selfhosted Audiobooks platform out there right now. My only paint points have been that their API docs are lackluster.

@[email protected] You could use Frigate for the 'feature' set, no? frigate+HA should work very well for the use case. Rest you should be okay with something that does RTSP and feeding that to frigate/HA, no? I remember researching something about this last year, and found that Reolink IIRC offers that.

@[email protected] Spantaleev's setup is probably the easiest way to get matrix setup honestly. Otherwise bridges etc tend to be a pain. You don't necessarily need to be a coder -- just follow documentation instructions step by step, and ask in their matrix channel if you get stuck.

You could also set it up on a device that's already encrypted on boot (via luks), so you'd have some protections if turned off.

I've been running it close to 5-7 years (don't remember lol).

@[email protected] You don't need a "NAS" per se -- just running a baremetal distro and using containers in it will suffice.
Further, while Nextcloud can work fine, I'd suggest not using it and going for individual solutions instead of something AIO -- NC is fairly clunky, and fairly slow comparatively. It's also PHP.
I personally use Proxmox + LXC/VMs in one Micro PC (i5-7xxx/24G), and Just Ubuntu with Docker compose in another(i5-6xxx/16G) alongside a couple of Oracle VMs. It works out fairly well.
For Digitizing paperwork and mail, paperless-ngx is a good solution. For your pirate ship, look into *arr solutions. jellyseerr -> sonarr/radarr -> bazarr -> jellyfin works fine.

@[email protected] Why not do something like wireguard/tailscale in your public facing instance, having nginx there, and reroute photos.domain.com to your private server?

so, something like subdomain.domain-> dns pointed to public -> hits your public -> nginx there routes to wireguard ip of 10.1.1.5 of your private box -> <OVER WIREGUARD> -> hits your private 10.1.1.5:8080 or something?