Commands

Create an anchor Device in the scene

Create an anchor Device in the scene with a given MacAddress. If the position is not specified then the anchor will be create at the origin of the scene, [0,0,0,0,0,0]

post/create-anchor/{mac-address}

Path parameters

mac-addressstring required

Valid UWB mac addresses must follow the above format

  • Short Mode: "XX:XX"
  • Extend Mode: "XX:XX:XX:XX:XX:XX:XX:XX" where X is an hexadecimal number.

Request body

xinteger

x coordinate in cm

yinteger

y coordinate in cm

zinteger

z coordinate in cm

yawinteger

yaw in degrees

pitchinteger

pitch in degrees

rollinteger

roll in degrees

Response

Success

Changes

Changed in 5 of the 5 revisions of this API.7215

  • 7e54e3f9ba2513See the full diff
    • deleted the query request parameter position-optional

      request-parameter-removed

    • added optional request body

      request-body-added-optional

    • added the non-success response with the status

      response-non-success-status-added

    • removed the non-success response with the status

      response-non-success-status-removed

    • for the query request parameter position-optional, the type of property pitch was generalized from integer to number

      request-parameter-property-type-generalized

    • for the query request parameter position-optional, the type of property roll was generalized from integer to number

      request-parameter-property-type-generalized

    • for the query request parameter position-optional, the type of property x was generalized from integer to number

      request-parameter-property-type-generalized

    • for the query request parameter position-optional, the type of property y was generalized from integer to number

      request-parameter-property-type-generalized

    • for the query request parameter position-optional, the type of property yaw was generalized from integer to number

      request-parameter-property-type-generalized

    • for the query request parameter position-optional, the type of property z was generalized from integer to number

      request-parameter-property-type-generalized

    • removed the request body

      request-body-removed

    • added the new optional query request parameter position-optional

      new-optional-request-parameter

    • added the non-success response with the status

      response-non-success-status-added

    • removed the non-success response with the status

      response-non-success-status-removed

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • df1e30abf42d13See the full diff
    • deleted the query request parameter position-optional

      request-parameter-removed

    • added optional request body

      request-body-added-optional

    • added the non-success response with the status

      response-non-success-status-added

    • removed the non-success response with the status

      response-non-success-status-removed

    • for the query request parameter position-optional, the type of property pitch was specialized from number to integer

      request-parameter-property-type-specialized

    • for the query request parameter position-optional, the type of property roll was specialized from number to integer

      request-parameter-property-type-specialized

    • for the query request parameter position-optional, the type of property x was specialized from number to integer

      request-parameter-property-type-specialized

    • for the query request parameter position-optional, the type of property y was specialized from number to integer

      request-parameter-property-type-specialized

    • for the query request parameter position-optional, the type of property yaw was specialized from number to integer

      request-parameter-property-type-specialized

    • for the query request parameter position-optional, the type of property z was specialized from number to integer

      request-parameter-property-type-specialized