Home Assistant Connect AUX-2 and your Vome home
Home Assistant's new €59 box puts Bluetooth, old serial gear, a Z-Wave stick and an amplifier on the network instead of in the back of the server. What it is, what it says about where home automation is going, and what it means for a home we host.
Posted 12 November 2026 hardwareesphomez-wavebluetooththreadhome-assistant
Home Assistant launched Connect AUX-2 on 11 November. It is a small PoE box, $69 / €59, that "can stream audio, control RS-232 serial devices, and connect a Z-Wave adapter, all while acting as a Bluetooth hub." We have not had one in our hands yet. This is a read of what was announced: what it does to a home we run, and what it says about home automation. Where we are guessing, we say so.
What it is
An ESP32-S3 running ESPHome, with the ports an ESP32 does not have on its own:
- audio out: a TI PCM5122 DAC behind one jack that is either analogue or optical, 16-bit/48 kHz, played from Music Assistant over Sendspin;
- two RS-232 ports on 3.5 mm jacks, with switches to swap TX and RX;
- USB-A for a Connect ZWA-2 Z-Wave stick, a ZBT-2, or a $15 RS-485 adapter for Modbus;
- Bluetooth LE, working as a Bluetooth proxy as soon as it is added;
- a Grove port for sensors;
- Ethernet with PoE (802.3af), or USB-C power and 2.4 GHz Wi-Fi.
It needs Home Assistant 2026.9 or later. The bootloader is unlocked, and the board and case files are due to be published.
Is it an expensive ESP32 with some connectors on it? It is an ESP32 with connectors on it, and that is the point. Home Assistant says PoE "accounted for most of the hardware cost", so the serial ports and the DAC came cheap. The news is not really the box. It is that the software now lives in ESPHome and Home Assistant: a serial proxy (still marked experimental), last year's Z-Wave proxy, and Zigbee over the network for ZHA from 2026.11. Any ESP32 can run it.
We have written up how to build your own for anyone who wants to see how it works or needs a different mix of ports. Done properly, it saves surprisingly little, so the box itself is the better buy for most people. Accept Wi-Fi, a phone charger and no case, and a bare dev board does most of it for about a third of the price.
What it says about home automation
This part is our opinion.
The hub stops being a place: edge radios
For ten years "the hub" meant a box with radios plugged into it, so Home Assistant had to sit next to the radios, in the middle of the house. With the radios on the network, that stops being true. The radios become edge radios: small, cheap boxes that each do one job, placed where the devices are.
Edge radios are cheap to add and cheap to move, and one failing takes out one room's devices, not the house. The first to gain are people who have fought to pass a USB stick through to Proxmox or Docker.
A hub that is only software is the bet Vome is built on, so we are biased, but this confirms it. It matters most for a home we host, where there is no box in the house to plug a stick into.
Old gear gets a second life
For decades, AV receivers, projectors, pool controllers and alarm panels were controlled over RS-232, and most amplifiers of the last thirty years have an optical input. The Open Home Foundation's phrase is "no device left behind". A €59 box that keeps a good amplifier out of the skip is a better environmental argument than most.
Open audio, while the big names close theirs
Sendspin is royalty-free, and Music Assistant is dropping its Cast bridging after Google cut back its firmware. If amplifier makers adopt Sendspin, multi-room audio stops belonging to one brand of speaker.
The limits come from physics
Home Assistant says it could not get Thread working through AUX-2: it is too sensitive to delay to run reliably over a network connection. That is easy to misread as "Thread cannot cross a network". It is narrower than that.
A Thread stick is only a radio. The software that runs the Thread network lives on the computer the stick is plugged into, and the two talk constantly, on tight timing. Put a network between them and the timing breaks. A border router keeps the radio and that software together in the house. What leaves it is ordinary IPv6, and IPv6 crosses any network. Thread was designed to work that way.
Zigbee is in between. ZHA over the network works, and Home Assistant is not advertising it yet. Zigbee2MQTT on a box in the house does the same trick as a border router: radio and software together, and only messages travel. Be wary of anyone who says every radio can now live anywhere, and of anyone who says Thread needs Home Assistant in the house.
More doors on your LAN
Each proxy opens a network path to a radio, or to an old device that has no login of its own. ESPHome encrypts its connection, but when Z-Wave over the network arrived last year, Z-Wave JS did not use that encryption. Put these boxes on a network you trust. With Vome, the stretch between your house and us runs inside the tunnel.
Competition will come quickly
Home Assistant's own hardware now covers Zigbee, Thread, Z-Wave, voice, Bluetooth, serial and audio. Because the software is in ESPHome, other makers get it for free. Expect boxes with more ports or a lower price within months, which is how open software is meant to work.
In a Vome home
If your Home Assistant runs in your house, nothing changes on Vome's side: AUX-2 is an ESPHome device like any other, and our ESPHome tools see it. If we host your Home Assistant, open Vome hosted home. Two more, for homes with a standby and for what may come next:
If you want to tinker
The firmware is unlocked. If Claude is connected to your home through Vome, it can write the config for a Grove sensor, validate it and flash it over your Vome link. Adopt the box into ESPHome Device Builder first, and remember that once you take over its config, building its updates is your job. Or start from parts: build your own.