Thank you, Jens. You are a prince and a gentleman.
Original Message:
Sent: May 09, 2025 10:51 AM
From: Jens Fluegel
Subject: Strange behaviour when trying to get AP535 to forward BLE data.
The playloadContent filters and the generic filters like companyIdentifierFilterare OR linked, so to limit the amount of data you receive you need remove some of them again. Just select one device class or generic filter for first testing.
The most flexible filter options are the generic input filters, all are OR related:
vendorFilter <XXXXX>,
serviceUUIDFilter <XXXX>,<YYYY>
companyIdentifierFilter <XXXX>,<YYYY>,
macOuiFilter <FFFFFF>, ....
localNameFilter <XXXX>, ....
You can disable periodic telemetry using the following command:
blePeriodicTelemetryDisable
Original Message:
Sent: May 05, 2025 10:25 AM
From: rached
Subject: Strange behaviour when trying to get AP535 to forward BLE data.
Thank you, Jens. That was incredibly helpful. Enabling a bunch of those payLoadType commands seems to have opened the floodgates. I'm having some trouble making sense of the docs. They seem somewhat ambiguous. The docs seem to say that if BLE data forwarding is enabled, then I should be getting BLE data in real time, and that if I have device type filters set up for BLE data, then this should determine which device types are included in the periodic BLE data report. Do I have that right?
I'm seeing periodic reports coming in to my websocket receiver. Here is my current config:
iot radio-profile test_iot_radio radio-mode ble ble-opmode scanning ble-txpower 10
iot transportProfile BLE-WS endpointURL ws://192.168.4.169:8765/ws endpointType telemetry-websocket payloadContent sbeacon payloadContent ibeacon payloadContent google payloadContent wifi-tags payloadContent wifi-assoc-sta payloadContent wifi-unassoc-sta payloadContent eddystone payloadContent serial-data payloadContent polestar payloadContent onity payloadContent wiliot payloadContent mysphera payloadContent zf-tags payloadContent diract payloadContent minew payloadContent unclassified endpointToken abc123 endpointID luna transportInterval 120 bleDataForwarding usbSerialDeviceTypeFilter enocean,piera,osu companyIdentifierFilter 0736
iot use-radio-profile test_iot_radioiot useTransportProfile BLE-WS
As you can see, I am using the ancient art of throwing the kitchen sink at the problem. However I only see the periodic reports. I don't see anything realtime coming in. I also see a ton of stuff, not just the stuff that corresponds to my manufacturer code. Can you help?
Thanks!
Original Message:
Sent: May 04, 2025 05:03 AM
From: Jens Fluegel
Subject: Strange behaviour when trying to get AP535 to forward BLE data.
Hi,
Your iot transportProfile configuration is incomplete. It is missing the input filter to determine the BLE traffic you would like to forward to your backend. Please not there is no forward all option. You have to explicitly define what should be forwarded. This filter also defines what shows up in the APs BLE table and that is the reason the table gets empty when you enable one of the transport profiles.
Take a look here for the Aruba Instant Documentation about the settings:
https://arubanetworking.hpe.com/techdocs/Instant_8.12.0_WebHelp/Content/instant-ug/iot/iot-config.htm?Highlight=iot%20transportProfile
Alternatively here the documentation using Central:
https://arubanetworking.hpe.com/techdocs/central/latest/content/nms/access-points/cfg/networks/iot-trnspt-strm.htm
You can check the transport profile configuration with the following commands:
show ap debug ble-relay iot-profile
show ap debug ble-relay ws-log <iot transportProfile name>
Regards,
Jens