BLE usage on Aruba AP's

Prodigyplace · February 11, 2022, 10:41am

Unless you somehow reverse engineer I suspect most all of the information needed is confidential restricted to HPE and select Zigbee partners constrained by nondisclosure agreements.

thatkide · June 23, 2022, 2:32pm

I would be interested in something like this.

ericleb · November 10, 2022, 9:02pm

Coming in late. I am able to track BLE beacons and also extract temperature/humidity data from Govee BLE sensors. Basically, I use an IoT transport profile with websocket enabled, A simple websocket server in Python receives the data and pass it to home assistant through mqtt. I happen to be an Aruba engineer, but I didn’t need any non-public documentation. I am not a programmer, not enough time and qualifications to write a proper integration.

jarvih · November 14, 2022, 5:43pm

Here is aruba’s own example how to control HUE lights.
Somebody just have to write integration to aruba’s api.

github.com

aruba/aos8-iot-server-example-websocket/blob/e3924babb6f298d39895bde46b72572c2278825a/README_zigbee.md

# Using the ZigBee Southbound API

## Setup your Aruba AP/Controller

There are a few settings you need to change on the Aruba Access Point. You can change all of them the easiest via the Webinterface (-just open the IP of your AP in a browser-) or if you prefer via ssh.

<strong>Note</strong>: In the Instant WebUI, the IoT configuration can be found under `"Services"`. Scroll down to the `"IoT"` section.

<strong>Note</strong>: In ArubaOS MCR WebUI, the IoT configuration can be found under `"Configuration"`->`"IoT"`.

1. First you need to set a `IoT-Radio-Profile`. This radio needs to use `ZigBee` as Radio mode and needs to act as "Coordinator". The channel can be set manually (e.g. 11) or in auto mode. If you want to use another channel, that works as well but it has to be set on all instances and supported by the devices. Philips Hue bulbs are said to support channels 11,15,20 and 25.

2. You also have to set up a `ZigBee Service profile`. Please enable "Security", set "PAN ID" on automatic and always allow new devices to join. Users don't have to always allow new devices to join but this helps avoid connection problems when trying out the SouthBound API.

3. The `ZigBee-Socket-Device-Profile` configures which Endpoints, Clusters and Profiles are allowed. It can be configured as follows:

```
Source Endpoint  Destination Endpoint  Cluster ID  Profile ID  Direction
---------------  --------------------  ----------  ----------  ---------
232              11                    0006        0104        outbound

This file has been truncated. show original

Lexodexo · October 30, 2023, 8:15am

I just wrote a little example to parse the Xiaomi Mija BLE sensor, seems to be working just fine with 5 APs and 6 Xiaomi Mija sensors. Sadly I had not enough time to write a full integration, but maybe this still helps some people.

TestInProd · February 11, 2024, 6:44pm

I’m curious if anyone has ran with this and has been playing with integrating Aruba Zigbee into ZHA or Zigbee2MQTT.

Saoshen · August 18, 2025, 12:26am

have some aruba iap-505’s and would love to see these supported for BT/ZB in home assistant

robertoamd90 · May 28, 2026, 9:56pm

Hi everyone,

I’ve been working on a Home Assistant custom integration for Aruba AP BLE support:

GitHub - robertoamd90/aruba-ble-proxy: Passive Aruba BLE proxy for Home Assistant · GitHub

The goal is different from the previous MQTT-based experiments: the integration receives Aruba IoT BLE Data over WebSocket and forwards the decoded advertisements directly into Home Assistant’s Bluetooth
stack.

Current status:

passive BLE scanning MVP is working
Aruba APs connect to Home Assistant over the Aruba Telemetry WebSocket transport
Aruba BLE Data protobuf messages are decoded
BLE advertisements are forwarded into HA as Bluetooth advertisements
BTHome devices work in my test setup
SwitchBot thermometer advertisements work in my test setup
no MQTT broker or separate local bridge is required

Important limitations:

this is passive scanning only for now
active BLE/GATT is not supported, so devices requiring connections or commands, such as SwitchBot Lock, will not work through this yet
Zigbee/ZHA support is not implemented
this has only been tested on my own Aruba/HA setup so far
installation is still manual as a custom integration

The integration also generates the Aruba CLI configuration needed for the IoT radio profile and BLE Data transport profiles. Aruba has a limit of 10 service UUID filters per transport profile, so the
generator splits them into multiple profiles automatically.

I would be interested in feedback from anyone with Aruba APs that support IoT/BLE Data forwarding, especially AP-5xx users. Useful test data would be:

AP model
Aruba Instant / ArubaOS version
whether the AP can connect to the WebSocket endpoint
which BLE integrations start working in Home Assistant
any devices that are seen by normal HA Bluetooth/ESPHome proxies but not through Aruba

This is still early, but the passive BLE path is already usable enough for real testing.

robertoamd90 · May 31, 2026, 6:17am

Small update on the Aruba BLE Proxy custom integration:

GitHub - robertoamd90/aruba-ble-proxy: Home Assistant Aruba BLE proxy integration · GitHub

The project has moved quite a bit since my previous post.

Current status:

Passive BLE scanning is working and usable in Home Assistant.
Aruba APs connect directly to Home Assistant using the Aruba IoT / BLE Data telemetry WebSocket.
BLE advertisements are decoded from Aruba protobuf messages and forwarded into Home Assistant’s Bluetooth stack.
Aruba APs show up as Bluetooth sources/adapters in Home Assistant.
The HA Bluetooth advertisements view and Bluetooth graph now show devices seen through the Aruba APs.
BTHome devices work in my test setup.
SwitchBot thermometers work in my test setup.
Experimental active BLE/GATT support is now available.
SwitchBot Lock / Lock Pro commands are working in my test setup, including tests with multiple locks.
No MQTT broker or separate bridge process is required.

A few important notes:

This is still a custom integration and should be considered experimental.
Active BLE/GATT support is new and still needs broader testing across AP models and ArubaOS versions.
Zigbee/ZHA support is not implemented.
I have mainly tested this on my own Home Assistant + Aruba setup so far.
Installation is currently through HACS as a custom repository or manual copy.

The integration also includes a CLI/config generator for the Aruba IoT radio profile and BLE Data transport profiles. It handles Aruba’s service UUID filter limits by splitting UUIDs across
multiple transport profiles automatically.

I would be very interested in feedback from anyone with Aruba APs that support IoT/BLE Data forwarding, especially AP-5xx users.

Useful test feedback would be:

AP model
Aruba Instant / ArubaOS version
whether the AP connects to the Home Assistant WebSocket endpoint
whether passive Bluetooth advertisements appear in HA
which BLE integrations start working
whether active BLE/GATT works for devices such as SwitchBot locks
any errors or devices that work through ESPHome Bluetooth Proxy but not through Aruba

If you find the project useful, starring the GitHub repo would also help make it easier for other Aruba/Home Assistant users to discover it.

Still early, but it is now beyond passive-only testing and is becoming usable for real-world BLE proxy experiments.

kedas · July 28, 2026, 6:33pm

Didn’t realize that there was already work done on this, but I recently wrote a similar tool that parses ATC1441 and PVVX broadcasts, then duplicates and publishes them to MQTT. This supports home assistant discovery and requires minimal configuration to run alongside home assistant in Docker.

In the future I’m looking at implementing more sensors, but I’m largely implementing this based on my own needs.

dax333 · October 4, 2026, 6:11am

Amazing work.