SolidGrue

They’re like the Lincoln & Ford (or Acura & Honda, if you prefer a less ambiguous simile) of the electrical components world

What your situation for data backup? You mentioned a homelab and a NAS, are you running regular backups to an off-box store? You could mate it with a few TB of inexpensive USB disk, maybe some software RAID, and use it for off-box backups. Doesn’t have to be fast, just reliable.

Specs like that, you have some options. Virtual assistant, IPCam NVR like MotionEye or Frigate, media server for your car (takes DC voltage, right?), weather base station, ADS-B feeder, smart mirrors.

Or (if you’re in the US) you could repair it and then, if you donate it to a suitable charity, you could take the the cost of the repair as a deduction on your taxes. Probably doesn’t help you that much, but it could maybe really help someone else who needs it.

Or, just wipe it and send it to e-waste.

deleted by creator

News to me! Good to know, though.

I think realtime media routed through the node back when I was running one, but that was quite a while ago now. It wasn’t bad for my crew, but load scales exponentially in those sort of applications as you take on endpoints.

I ran an ejabberd node on an old x86 for years for family and some close friends. Works great.

Then I got tired of maintaining devices after long days at work doing IT things. We talked. Signal is easier. We moved over to that, in the end.

A Pi3 1GB will easily scale to 4 people.and beyond. XMPP is really lightweight for text and images. Consider a Pi4 for voice or video though.

I think the i5 is Ivy Bridge, but I couldn’t tell you what gen that is. My main use of HA aside from the automation is Frigate, which apparently needs the hardware AVX flags. This chip supports AVX512, where my older AMD did not, so that’s why I went with it. Its an i5-3470T, if that helps.

For an older SFF unit, it’s a beast for HA.

I’ve got HA with Frigate + USB Coral w/4 cams, FlightRadar24 receiver/feeder, ESPHome, NodeRed, InfluxDB, Mosquitto, and Zwave-JS on a refurbished Lenovo ThinkCenter M92p Tiny, rigged with an i5 3.6GHz, 8GB RAM and 500GB spindle drive. It’s almost overkill.

Frigate monitors 2 RTSP and 2 MJPEG cams (sometimes up to 3 RTSP and 5 MJPEG, depending of if I’m away for the weekend) with hardware video conversion. FR24 monitors a USB SDR dongle tracking several hundred aircraft per hour. I live under one.of the main approaches to a major US hub.

Processor sits at 10% or less most of the time, and really only spikes when I compile new binaries for the ESP32 widgets I have around the house. It uses virtually none of the available disk. It’s an awesome platform for HA for the price.

I am also bailing on Gandi, and am in the process of divesting them of my assets.

I was already using Let’s Encrypt for my self-hosted applications, and never used Gandi’s certificate service.

In July of this year I moved all of my Gandi mailboxes over to MXroute after subscribing to their $99 lifetime subscription plan. It’s more than I’ll ever really need.

I plan to move my domains over to Porkbun as they come up for renewal at Gandi, starting with two domains next month. I hold several domains in the standard TLDs and am US-based, so porkbun is a good fit for my needs. I’ll need to sort out DDNS services for a couple of my hosts, but if Porkbun isn’t sufficient then DuckDNS seems popular and well supported among the applications and self hosted services I use. If they have a paid tier, I will probably consider using that.

I intend to avoid Cloudflare except as a very last resort for more or less the same reasons I might avoid Google or Amazon: privacy, intellectual property and good netizenship.

Sure, you could set up any syslog receiver stack like Splunk (as the other OP suggested) or an ELK Stack or even just syslog-ng or rsyslog to disk. Anything that can ingest syslog format will handle Unifi logs.

Decide how you want to receive, store and parse your logstream data. Once you have a syslog receiver set up, set Unifi (System > Site > Enable Remote Logging) for the Syslog server remote address:port and start shipping logs.

Whatever you do with those logs is out of scope for this discussion, but your logger should at least ingest them and spool them.