Bluetooth
The Bluetooth and BTLE phys provide additional APIs for Bluetooth related data.
Bluetooth UUID names
Names Bluetooth service UUIDs from the Bluetooth ID list (btoidfile), as the web UI’s device details
show them. Each UUID is a 16-bit assigned number (feaf), the same number in 32 bits (0000feaf), or the
128-bit Bluetooth base form (0000feaf-0000-1000-8000-00805f9b34fb); other entries are ignored.
{"uuids": ["feaf", "0000180f-0000-1000-8000-00805f9b34fb"]}
readonly/phy/bluetooth/uuid_names.json/phy/bluetooth/uuid_names.ekjson/phy/bluetooth/uuid_names.prettyjsonPOSTPARAMETERS
This endpoint takes additional parameters by using a `POST` request and supplying a
JSON document or json form variable.
You can find more information about API parameters here.
uuids
list
OPTIONALUp to 64 service UUIDs
BTLE related devices
The devices in the same related group as
the BTLE device {DEVICEKEY}, the device itself included: the random addresses advertising the same payload,
as the web UI’s BTLE Related Devices timeline shows them.
The list is empty when related devices are off (btle_related), or the device isn’t in a group.
readonly/phy/btle/related-of/{DEVICEKEY}/devices.json/phy/btle/related-of/{DEVICEKEY}/devices.ekjson/phy/btle/related-of/{DEVICEKEY}/devices.prettyjsonGET
POSTPARAMETERS
This endpoint takes additional parameters by using a `POST` request and supplying a
JSON document or json form variable.
You can find more information about API parameters here.
fields
field simplification
OPTIONALKismet can reduce the amount of information being processed and returned by an API by simplifying the fields to only return the data needed by the caller.
You can read more about the field simplification API and how to use it here.