The NVR doesnt have to live in the same VLAN if you give it explicit firewall rules to traverse to the tainted camera VLAN for the explicit purpose of fetching the rtsp stream from the cursed cameras. Its how I setup my network. The cameras are islanded, I setup Frigate to be allowed to go in and open that port over TCP. The cameras try to phone home and pull DNS but are ignored, only traffic they’re allowed to product is rtsp to Frigate.

Oh that’s a silly question. Why not?

The honest answer is in the US all doorbells are powered by simple 24VAC transformers that burn 6–7 watts just being powered up, forever, for decades. This annoyed me plus I wanted a fun bell so I wired up a pi to use a modern, efficient 24VDC power supy to ring the bell and it gets turned on by the pi only when its needed so now my idle wattage is more like 0.25W.

Yep, with curl because I have OliveTin setup to accept requests to ring the bell from other pis or myself if I feel the need via the web GUI.

My doorbell is a raspberry pi that uses webhooks to send me messages on my privately hosted chat server and also rings a physical bell built in 1900. Do I win for the most simple high tech doorbell?

I’m confident there are no environmental implications.

I’m in a rush but ive put Ethernet cards in both slots of my optiplex 3080 m.2 slots. The top right slot is vanilla and 4xpcie lanes,full speed. The bottom left is A+e keying and only 1x lane which is enough for 2.5gig Ethernet. This is ultimately what i used. For my prfesene box I added a second card, a 2 port Ethernet card to the top right m.2 slot and made it a four port beast.