From 1f9ce581fc3076acf2df488207fe4f9b920a7da0 Mon Sep 17 00:00:00 2001 From: Kaloyan Danchev Date: Fri, 16 Oct 2026 15:20:55 +0300 Subject: [PATCH] HA: corridor Bluetooth proxy added Co-Authored-By: Claude Opus 5.5 --- docs/CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 6043ad7..735c111 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -4,6 +4,7 @@ --- ## 2026-10-16 +- Home Assistant: `corridor-bt-proxy` (Olimex ESP32-POE-ISO) added to the ESPHome integration and running as an active Bluetooth proxy. Temporarily on hAP ax3 ether3, VLAN 10 (192.168.10.100); it moves to CAP XL ether2 (VLAN 30) when mounted. ### Network: cAP ether2 ports for Olimex Bluetooth proxies - **[NETWORK]** CAP XL ac (192.168.10.2): ether2 `pvid=30`, untagged on VLAN 30 (was pvid 1, so no VLAN was allowed). CAP AC (192.168.10.4) ether2 was already VLAN 30 (since 2026-09-27). Both feed Olimex ESP32-POE-ISO BT proxies (corridor, living room). ether2 PoE-out is passive 24 V (bundled adapter), too low for the 802.3af Olimex, so the Olimex boards take USB 5 V power.