Show HN: Proxmox -> Share your host's Bluetooth with a VM over the network

Summary

Bluetooth in your Proxmox Linux VMs. Finally. TL;DR: Bluetooth passthrough to a Proxmox VM fails for Intel onboard chips (BE200, AX210, AX211 - by hardware design, no setting fixes it) and is unreliable on gaming distros like ChimeraOS and Bazzite. This tool shares the host's Bluetooth with the VM over the network instead - two commands, works with any chip Linux supports, survives reboots. Controllers, headphones, and Home Assistant sensors all work. Pair your Xbox / PlayStation controller, headphones, or sensors inside your gaming VM (ChimeraOS, Bazzite, Home Assistant, plain Linux) - even with Bluetooth chips that "can't be passed through". You built a gaming VM on Proxmox. Everything works... except Bluetooth. Your controller just blinks, blinks, blinks, and gives up. You bought an Intel BE200 / AX210 card because a forum said so. Still nothing. You tried qm set ... -usb, saw the device in the VM, and it still refused to work. Every thread ends with someone saying "just use a USB cable". It's not your fault, and your hardware is not broken. Intel built their Bluetooth chips so that only the machine that boots them can drive them. The moment Proxmox hands the chip to a VM, it wipes itself blank. No setting fixes this. It is physically how the chip works. First: try the simple thing Plain USB passthrough works for plenty of setups - a normal dongle into a normal Linux distro (Debian, Ubuntu) often just works: qm set <vmid> -usb0 host=<vendor:product> If that gives you working Bluetooth in your VM, stop reading - you don't need this project. This exists for when it doesn't work: Intel onboard chips (BE200/AX2xx - never work, by design), gaming distros (ChimeraOS/Bazzite kernels + quirky chip firmware), trimmed cloud kernels, and dongles that wedge after a few VM restarts. The fix: don't hand over the chip. Share it. The chip stays on your Proxmox host, where it works. A tiny bridge streams it into the VM over the local network. Your VM sees a completely normal Blue...