Juniper Mist
Explaining how to use MobiusFlow Juniper Mist service to pull BLE data from the Mist network into MobiusFlow
The MobiusFlow Juniper Mist service works by interfacing with a given site on the Juniper Mist cloud. It is currently not possible to connect directly to a Mist AP due to limitations of the Mist network itself.
The service is used to subscribe to BLE data updates within the Mist cloud.
Requirements from Mist Cloud
Find the following in Mist Cloud:
Site ID: Most easily found by looking in the URL when browsed to the site on the Mist portal. The URL's take the form of https://<HOSTNAME>/admin/?org_id=<ORG_ID>#!psk/<SITE_ID>.
Region: Use the HOSTNAME in the URL and the following table to find the region.
manage.mist.com
Global 01
manage.gc1.mist.com
Global 02
manage.ac2.mist.com
Global 03
manage.gc2.mist.com
Global 04
manage.gc4.mist.com
Global 05
manage.eu.mist.com
EMEA 01
manage.gc3.mist.com
EMEA 02
manage.ac6.mist.com
EMEA 03
manage.gc6.mist.com
EMEA 04
manage.ac5.mist.com
APAC 01
manage.gc5.mist.com
APAC 02
manage.gc7.mist.com
APAC 03
Mist Authentication Key: This can be created on the Mist portal in Organization > Settings > API Token > Create Token.

For most secure setup we recommend scoping the new API key as Observer of a Specific Site (the Site you're connecting to here).

Configuration the Service
Add a Juniper Mist service to your MobiusFlow configuration:

Open the service settings of the new service:

Populate the settings you acquired from the Mist portal + Save:

Start the now configure service:

If the service connects and is operating correctly it will show:

Use with BLE Devices service
The Juniper Mist service simply forwards raw BLE data. It does not perform any decoding. As such, once the service has received the data, it is forwarded to the MobiusFlow hub (via a BCMD BLE_RX command). The hub will forward the data to any listening BLE devices services. The BLE devices service is where the raw BLE data is decoded and MobiusFlow objects are populated. See full article on the BLE devices service here.
This means, to implement full end-to-end data transfer and decoding, this service is designed to be used in conjunction with the BLE Devices service.
Last updated
Was this helpful?

