Internet of Things (IoT) and Industrial IoT (IIoT)

 View Only
  • 1.  Strange behaviour when trying to get AP535 to forward BLE data.

    Posted May 01, 2025 05:38 AM
    Edited by rached May 01, 2025 12:17 PM

    Hi everyone, first time poster. (Second time, but I don't know what happened to my first post, so I'm posting again!)

    I have the following system:

    Name: Aruba Operating System Software
    Type: 535
    Build Time: 2025-04-01 20:20:12 UTC (build 92330) by jenkins
    Version: 8.12.0.5 SSR
    I am trying to forward all the BLE info to another server. I have tried https and websocket both, but I keep encountering very strange behaviour.  First off, if my config looks like this:
    iot radio-profile test_iot_radio
     radio-mode ble
     ble-opmode scanning
     ble-txpower 10
    
    iot transportProfile BLE-HTTPS
     endpointURL https://www.strikerit.com/ingest
     endpointType telemetry-https
     endpointToken abc123
     transportInterval 60
    
    iot transportProfile BLE-WS
     endpointURL wss://www.strikerit.com/ws
     endpointType telemetry-websocket
     endpointToken abc123
     transportInterval 60
     bleDataForwarding 
    
    iot use-radio-profile test_iot_radio

    Then obviously the profiles are both inactive and I don't expect to get any data. But what I do see is this:

    *********************************************************************************************************
     4/30/2025 15:51:18 PM    Target: 20:9c:b4:c9:40:a4 (VC)    Command: show ap debug ble-table all 
    *********************************************************************************************************
    BLE Device Table [APBs]
    -----------------------
    MAC                HW_Type   FW_Ver           Flags   Status  Radio Type  Tx_Power  Last Update  Uptime
    ---                -------   ------           -----   ------  ----------  --------  -----------  ------
    28:de:65:ac:c6:a0  BT-AP530  DFU App 1.4-185  0x0083  LIA     Internal    10dBm     1s           19h:42m:40s
    
    
    BLE Device Table [Generic]
    ---------------------------
    MAC                Address Type  RSSI  Last Update  Device Class  Generic Filter  BT-SIG Company IDs
    ---                ------------  ----  -----------  ------------  --------------  ------------------
    e4:52:1e:62:aa:00  Public        -84   I:161s       iBeacon       --              0x004C
    3c:2e:f5:77:2e:01  Public        -83   I:0s         --            --              0x038D
    ee:2a:38:4c:22:06  Static        -90   I:357s       --            --              0x004C
    d3:68:5f:99:cc:10  Static        -86   I:316s       --            --              0x004C
    ce:74:44:73:0e:10  Static        -63   I:1s         --            --              0x004C
    [...]
    d9:fe:95:37:99:f0 Static -85 I:542s -- -- 0x004C f6:96:a8:3e:bf:f3 Static -71 I:1s -- -- 0x004C Generic BLE devices:60 Total BLE devices:60 Note: Battery level for LS-BT1USB devices is indicated as USB. Note: Uptime is shown as Days hour:minute:second. Note: Last Update is time in seconds since last heard update. Note: Meas. Pow. is the averaged RSSI (in dBm) when the iBeacon is calibrated. Note: Tx_Power is shown in dBm in the APBs section for radios that support radio profile type 1. For all other APB radios, Tx_Power is a discrete level from 0-15. Status Flags:L:AP's local beacon; I:iBeacon; A:Beacon management capable :H:High power beacon; T:Asset Tag Beacon; U:Upgrade of firmware pending :u:Beacon management update received Last Update Flags:I: Device observed by internal radio :E: Device observed by external radio Generic Filter:S:serviceUUIDFilter; C:companyIdentifierFilter :M:macOuiFilter; L:localNameFilter

    As soon as I enable one of the profiles (let's say, the websocket one), the number of devices in the above list very quickly drops down to zero.  Is that normal?

    Secondly, my websocket endpoint (which is currently publicly accessible, so you can attempt to connect to it yourself), never sees a thing. The certificate is valid, and I was able to independently test that it's a working websocket endpoint.

    *********************************************************************************************************
     4/30/2025 14:48:01 PM    Target: 20:9c:b4:c9:40:a4 (VC)    Command: show ap debug ble-relay report 
    *********************************************************************************************************
    
    ---------------------------Profile[BLE-WS]---------------------------
    
    WebSocket Connect Status                : Connection Started     
    WebSocket Connection Established        : No
    Location Id                             : Not Configured
    Websocket Address                       : wss://www.strikerit.com/ws
    WebSocket Host                          : 

    www.strikerit.com

    WebSocket Path                          : ws
    Vlan Interface                          : Not Configured
    Current WebSocket Started at            : 2025-04-30 21:47:54 
    WebSocket Terminated at                 : 2025-04-30 21:47:56 
    Web Proxy                               : NA
    Proxy Username&password                 : NA, NA
    Last Send Time                          : 2025-04-30 21:47:54 
    Websocket Write Stats                   : 0 (0B)
    Websocket Write Errors                  : 0
    Websocket Write WM                      : 0B (0)
    Websocket Read Stats                    : 0 (0B)
    Websocket Read Pong Stats               : 0 (0B)

    Any ideas?

    Thanks in advance.



  • 2.  RE: Strange behaviour when trying to get AP535 to forward BLE data.
    Best Answer

    Posted May 04, 2025 05:03 AM

    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




  • 3.  RE: Strange behaviour when trying to get AP535 to forward BLE data.

    Posted May 05, 2025 10:25 AM

    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_radio iot 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!




  • 4.  RE: Strange behaviour when trying to get AP535 to forward BLE data.

    Posted May 09, 2025 10:52 AM
    Edited by Jens Fluegel May 09, 2025 10:53 AM

    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 




  • 5.  RE: Strange behaviour when trying to get AP535 to forward BLE data.

    Posted May 09, 2025 11:59 AM

    Thank you, Jens. You are a prince and a gentleman.