GetBuildingByBLEBeacon

Class Description

Returns a Building-ID for the given Attributes. If Beacon exisits in multiple Buildings, the closest one will be returned.

RPC Configuration

Rpc Name:

Plain: GetBuildingByBLEBeacon
Sha1: c2e926ff6673be1cf41df4dd9b7591da0d0ce524

Rpc Call

RPCs can be called by their plain name or their SHA1 representation.

Rpc Parameters:

"lat" : float,
"lon" : float,
"uuid" : string,
"major" : int,
"minor" : int 

Requires Login:

true

Requires Context:

Context

The context providing parameter can either be a contagt-id (8-Bytes, Alphaumeric) or an integer as a building id. The context parameter name should make the choice obviouse, the type has not to be defined manually.

false

Requires WriteAccess:

WriteAccess

Only accounts that have an explicit write access to the defined context can execute this RPC, no matter if the authentication level matches or not.

false

Requires AuthenticationLevel:

Context

Authentication levels allow the SuperUser to define a by-RPC granular access configuration. If RPCs are chained in a single unified call and lenient is enabled, all allowed RPCs will be executed, while execution will fail entirely with lenient set to false.

STANDARD_USER

Requires Subbuilding Merge Strategy:

REPLACE

Cache Configuration

Response Cache

All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache and readonly.

Cache enabled:

true

Cache Time to Live:

60

Sample Request

->

{
    "lat": 49.49883791753421,
    "lon": 8.468609601259232,
    "uuid": "c0117467-c011-7467-c011-7467c0117467",
    "major": 10001,
    "minor": 10001
}

<-

{
    "building_id": 1,
    "roottag": "Wt8jFR4A",
    "distance": 0
}