AutoconnectTemplates

Class Description

Method requires user to be of Type AuthorizationLevel::SUPERUSER Will connect all existing templates of rooms to the best matching tag. Only templates that have a single tag, beeing the closest by a delta of 1m to the next tag will be connected, elsewise ignored.
@param float threshold The minimum difference of the closest to the second closest possible tag. if the distance is smaller, it will be ignored.

@param float maximumDistance The maximum distance a tag can be away from the templates geometry.

RPC Configuration

Rpc Name:

Plain: AutoconnectTemplates
Sha1: 725c507177b87aa934f47696c10193b037afb23e

Rpc Call

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

Rpc Parameters:

"building_id" : int,
"floor" : int,
"threshold" : float = 1,
"maximumDistance" : float = 1 

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.

true

Requires contextParamName:

building_id

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.

true

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.

SUPERUSER

Requires Subbuilding Merge Strategy:

SUBBUILDING_ONLY

Cache Configuration

Response Cache

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

Cache enabled:

false

Sample Request

->

{
    "building_id": 131
}