DRIVR Datapoint/Setpoint MQTT API for Connectors 1.1.0

This page provides an overview of all MQTT topics which can be utilized for data submission (e.g. measurements taken by sensors which should be stored within DRIVR) or listening for commands triggered within the cloud and which your device should perform (e.g. adjust heating temperature of your HVAC system to 20*C). This allows you to retrieve System and Component information, Create Datapoint/Setpoint and Read/Acknowledge Setpoint within DRIVR. This can be used for debugging and error handling purposes as DRIVR will return error messages which might occur.

PLEASE NOTE: For comprehensive explanations of terms such as Domain, System, Component, Event, Service, Characteristic, and others used in this document, please refer to Terms.

Servers

  • mqtt://mqtt.drivr.cloud:{port}/secure-mqtt 3.1.1drivr-mqtt-broker

    DRIVR MQTT Broker

    object
    port
    required
    string
    Default value:"8883"
      Allowed values:
    • "8883"

Operations

  • SUB drivr/v1/{slug}/systems/{systemUuid}

    Subscribe for updates on the System using its systemUuid within a given domain. A System serves as a logical group of one or more IoT components which are usually positioned at the same geographic location and serve a common system function in DRIVR. A systemUuid is a unique identifier for a system.

    Operation IDgetSystemInformation

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    object

    Accepts the following message:

    SystemInformation<anonymous-message-1>
    Message ID<anonymous-message-1>

    Information about a System within a DRIVR Domain. Information is retained until the System is deleted.

    object [SystemInformation]

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}

    Subscribe for updates on the Component using the componentCode within the System and the systemUuid within a given domain. A Component is an entity belonging to a System that represents an actual device that sends and receives data. Examples of components are devices, gateways, modules, parts or virtual devices. A componentCode is a unique identifier for a component within a system.

    Operation IDgetComponentInformation

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    object

    Accepts the following message:

    ComponentInformation<anonymous-message-2>
    Message ID<anonymous-message-2>

    General information about a Component within a DRIVR System.

    object [ComponentInformation]

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/dp

    Subscribe for updates on the current value of the referenced characteristic(characteristicUuid) of the service(serviceCode) of the component(componentCode) in the system(systemUuid) within the given domain. A Service groups multiple characteristics and defines a specific function of a device. The dp i.e Datapoint is the measurement data sent from the device to DRIVR. For example, a Component like smart socket has a Service like State Monitoring may include multiple characteristics like State , Current timestamp and the values for those characteristics like “ON” at 12:00 PM yesterday will be datapoints. The data payload is expected to be in the JSON format.

    Operation IDgetCharacteristicDatapointJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    object

    Accepts the following message:

    CharacteristicDatapoint<anonymous-message-3>
    Message ID<anonymous-message-3>

    A Datapoint which is published for a specific Characteristic within a Component.

    object [CharacteristicDatapoint]

    The message structure which DRIVR sends if a Datapoint has been sent from a System.

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/dp/msgpack

    Subscribe for updates on the current value of the referenced characteristic(characteristicUuid) of the service(serviceCode) of the component(componentCode) in the system(systemUuid) within the given domain. The dp i.e Datapoint is the measurement data sent from the device to DRIVR. For example, a Component like smart socket has a Service like State Monitoring may include multiple characteristics like State , Current timestamp and the values for those characteristics like “ON” at 12:00 PM yesterday will be datapoints. A msgpack is a binary format which is smaller and faster than JSON. The data payload is expected to be in the msgpack format.

    Operation IDgetCharacteristicDatapointMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    object

    Accepts the following message:

    CharacteristicDatapoint<anonymous-message-3>
    Message ID<anonymous-message-3>

    A Datapoint which is published for a specific Characteristic within a Component.

    object [CharacteristicDatapoint]

    The message structure which DRIVR sends if a Datapoint has been sent from a System.

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/sp/{receiptId}

    Subscribe for updates on the current request to change a setting of the referenced characteristic(characteristicCode) of the service(serviceCode) of the component(componentCode) within a system(systemUuid) in a given domain. A sp (i.e Setpoint) is a value set by a user or an application to change the state of a device. A receiptId is a unique identifier for a setpoint. For example, a Component like Temperature Sensor has a Service like Temperature Monitoring may include multiple characteristics like Temperature, Current timestamp and the value set are Set "20 Degrees" at 12:00 PM Today will be Setpoint. The data payload is expected to be in the JSON format.

    Operation IDgetCharacteristicSetpointJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    receiptId
    required
    string

    The receipt ID of a Setpoint within DRIVR used by a System to report back once the Setting change request on a TimeStream has been done.

      Examples values:
    • "asd28dfa"
    object

    Accepts the following message:

    CharacteristicSetpoint<anonymous-message-4>
    Message ID<anonymous-message-4>

    A Setpoint for a specific Characteristic within a Service and Component.

    restricted any allOf

    The message structure which DRIVR sends if a Setpoint has been sent from a System.

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/sp/{receiptId}/msgpack

    Subscribe for updates on the current request to change a setting of the referenced characteristic(characteristicCode) of the service(serviceCode) of the component(componentCode) within a system(systemUuid) in a given domain. A sp (i.e Setpoint) is a value set by a user or an application to change the state of a device. For example, a Component like Temperature Sensor has a Service like Temperature Monitoring may include multiple characteristics like Temperature, Timestamp and the value set are Set "20 Degrees" at 12:00 PM Today will be Setpoint. The data payload is expected to be in the msgpack format. Emits payloads encoded as msgpack.

    Operation IDgetCharacteristicSetpointMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    receiptId
    required
    string

    The receipt ID of a Setpoint within DRIVR used by a System to report back once the Setting change request on a TimeStream has been done.

      Examples values:
    • "asd28dfa"
    object

    Accepts the following message:

    CharacteristicSetpoint<anonymous-message-4>
    Message ID<anonymous-message-4>

    A Setpoint for a specific Characteristic within a Service and Component.

    restricted any allOf

    The message structure which DRIVR sends if a Setpoint has been sent from a System.

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/sp/{receiptId}/state

    Subscribe for updates on the current state of a Setpoint change, for a characteristic(characteristicCode) within a service(serviceCode) for a component(componentCode) within a system(systemUuid) in a given domain. A receiptId is a unique identifier for a setpoint. A state of the setpoint can be CREATED, REJECTED, ACCEPTED.

    Operation IDgetCharacteristicSetpointStateJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    receiptId
    required
    string

    The receipt ID of a Setpoint within DRIVR used by a System to report back once the Setting change request on a TimeStream has been done.

      Examples values:
    • "asd28dfa"
    object

    Accepts the following message:

    CharacteristicSetpointState<anonymous-message-5>
    Message ID<anonymous-message-5>

    A state change of a Setpoint for a specific Characteristic within a Service and Component.

    restricted any allOf

    The payload of a Setpoint state change.

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/sp/{receiptId}/state/msgpack

    Subscribe for updates on the current state of a Setpoint change for a characteristic(characteristicCode) within a service(serviceCode) for a component(componentCode) within a system(systemUuid) within a given domain. A receiptId is a unique identifier for a setpoint. A state of the setpoint can be CREATED, REJECTED, ACCEPTED. Emits the payload encoded as msgpack.

    Operation IDgetCharacteristicSetpointStateMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    receiptId
    required
    string

    The receipt ID of a Setpoint within DRIVR used by a System to report back once the Setting change request on a TimeStream has been done.

      Examples values:
    • "asd28dfa"
    object

    Accepts the following message:

    CharacteristicSetpointState<anonymous-message-5>
    Message ID<anonymous-message-5>

    A state change of a Setpoint for a specific Characteristic within a Service and Component.

    restricted any allOf

    The payload of a Setpoint state change.

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/sp/{receiptId}/message

    Subscribe for updates on when a message has been published during a Setpoint(receiptId) change for a characteristic(characteristicCode) within a service(serviceCode) for a component(componentCode) within a system(systemUuid) within a given domain. A message is a statement or information which is sent to indicate a change in state or a specific occurrence. The data payload is expected to be in the JSON format.

    Operation IDgetCharacteristicSetpointMessageJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    receiptId
    required
    string

    The receipt ID of a Setpoint within DRIVR used by a System to report back once the Setting change request on a TimeStream has been done.

      Examples values:
    • "asd28dfa"
    object

    Accepts the following message:

    CharacteristicSetpointMessage<anonymous-message-6>
    Message ID<anonymous-message-6>

    A message for a Setpoint for a specific Characteristic within a Service and Component.

    restricted any allOf

    An optional message to add to the receipt of a Setpoint.

    Examples

  • SUB drivr/v1/{slug}/systems/{systemUuid}/components/{componentCode}/services/{serviceCode}/index/{serviceIndex}/characteristics/{characteristicCode}/sp/{receiptId}/message/msgpack

    Subscribe for updates on when a message has been published during a Setpoint(receiptId) change for a characteristic(characteristicCode) within a service(serviceCode) for a component(componentCode) within a system(systemUuid) within a given domain. A message is a statement or information which is sent to indicate a change in state or a specific occurrence. Publishes the payload encoded as msgpack.

    Operation IDgetCharacteristicSetpointMessageMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    componentCode
    required
    string

    A uniquely identifiable code of an ACTIVATED Component within a DRIVR System.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-component"
    • "flood-creation-entity"
    serviceCode
    required
    string

    A uniquely identifiable code of a Service within a DRIVR Domain.

      Examples values:
    • "death-star-laser"
    • "ocean-evaporation-service"
    • "flood-creation-service"
    serviceIndex
    required
    integer

    The index of a Service referenced when adding a Service to a ComponentModel in DRIVR.

      Examples values:
    • 0
    • 1
    • 2
    characteristicCode
    required
    string

    A uniquely identifiable code of a Characteristic within a Service.

      Examples values:
    • "laser-power"
    • "evaporation-rate"
    • "water-level"
    receiptId
    required
    string

    The receipt ID of a Setpoint within DRIVR used by a System to report back once the Setting change request on a TimeStream has been done.

      Examples values:
    • "asd28dfa"
    object

    Accepts the following message:

    CharacteristicSetpointMessage<anonymous-message-6>
    Message ID<anonymous-message-6>

    A message for a Setpoint for a specific Characteristic within a Service and Component.

    restricted any allOf

    An optional message to add to the receipt of a Setpoint.

    Examples

  • PUB drivr/v1/{slug}/input/dp/json

    Publish Datapoints(i.e dp) by Connectors. Only entities which are allowed to manipulate a complete Domain can use this topic. This topic is intended for other Applications which are sending data from multiple Systems. Compared to adding the issuerUuid in the topic it can be added in the payload. If not set, issuerUuid will not be recorded or set. The data payload is expected to be JSON.

    Operation IDpublishGlobalDatapointJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    GlobalDatapointInputWithIssuer<anonymous-message-7>
    Message ID<anonymous-message-7>

    The payload to be processed by DRIVR to import Datapoints on the global MQTT endpoints. Allows to additionally record an issuerUuid in the payload and is intended for Connectors and mass data processing. Following table outlines all possible combinations of required and optional parameters for creating a datapoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/dp/json/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the JSON format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/dp/msgpack

    Publish Datapoints(i.e dp) by Connectors. Only entities which are allowed to manipulate a complete Domain can use this topic. This topic is intended for other Applications which are sending data from multiple Systems. Compared to adding the issuerUuid in the topic it can be added in the payload. If not set, issuerUuid will not be recorded or set. The data payload is expected to be in the msgpack format.

    Operation IDpublishGlobalDatapointMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    GlobalDatapointInputWithIssuer<anonymous-message-7>
    Message ID<anonymous-message-7>

    The payload to be processed by DRIVR to import Datapoints on the global MQTT endpoints. Allows to additionally record an issuerUuid in the payload and is intended for Connectors and mass data processing. Following table outlines all possible combinations of required and optional parameters for creating a datapoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/dp/msgpack/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the msgpack format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/dp/json/{issuerUuid}

    Publish Datapoints(i.e dp) by Connectors. Only entities which are allowed to manipulate a complete Domain can use this topic. This topic is intended for other Applications which are sending data from multiple Systems. Compared to adding the issuerUuid in the topic it can be added in the payload. If not set, issuerUuid will not be recorded or set. The data payload is expected to be JSON.

    Operation IDpublishGlobalDatapointJsonWithIssuer

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    GlobalDatapointInput<anonymous-message-9>
    Message ID<anonymous-message-9>

    The payload to be processed by DRIVR to import Datapoints on the global MQTT endpoints. Following table outlines all possible combinations of required and optional parameters for creating a datapoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/dp/json/{issuerUuid}/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the JSON format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/dp/msgpack/{issuerUuid}

    Publish Datapoints(i.e dp) for Connectors. Only entities which are allowed to manipulate a complete Domain can use this topic. This topic is intended for other Applications which are sending data from multiple Systems. The data payload is expected to be in the msgpack format.

    Operation IDpublishGlobalDatapointMsgpackWithIssuer

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    GlobalDatapointInput<anonymous-message-9>
    Message ID<anonymous-message-9>

    The payload to be processed by DRIVR to import Datapoints on the global MQTT endpoints. Following table outlines all possible combinations of required and optional parameters for creating a datapoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/dp/msgpack/{issuerUuid}/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the msgpack format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/sp/json

    Publish Setpoints(i.e sp) for Connectors. Only Connectors can use this topic as they are allowed to impersonate (via passed issuerUuid) the person who send the request. This topic is intended for other Applications which send data commissioned by one ore multiple Systems. Compared to adding the issuerUuid in the topic it can be added in the payload. If not set, the issuerUuid will not be recorded or set. The data payload is expected to be JSON.

    Operation IDpublishGlobalSetpointJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    GlobalSetpointInputWithIssuer<anonymous-message-10>
    Message ID<anonymous-message-10>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. It allows to set who this intent has been initiated by with a passed issuerUuid. Following table outlines all possible combinations of required and optional parameters for creating a setpoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/sp/json/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the JSON format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/sp/msgpack

    Publish Setpoints(i.e sp) for Connectors. Only Connectors can use this topic as they are allowed to impersonate (via passed issuerUuid) the person who send the request. This topic is intended for other Applications which send data commissioned by one ore multiple Systems. Compared to adding the issuerUuid in the topic it can be added in the payload. If not set, the issuerUuid will not be recorded or set. The data payload is expected to be in the msgpack format.

    Operation IDpublishGlobalSetpointMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    GlobalSetpointInputWithIssuer<anonymous-message-10>
    Message ID<anonymous-message-10>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. It allows to set who this intent has been initiated by with a passed issuerUuid. Following table outlines all possible combinations of required and optional parameters for creating a setpoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/sp/msgpack/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the msgpack format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/sp/ack/json

    Publish acknowledgement of Setpoints(i.e sp) for Connectors. Only Connectors can use this topic as they are allowed to impersonate (via passed issuerUuid) the person who send the request. The topic is intended for other Applications which send data commissioned by one ore multiple Systems. The data payload is expected to be JSON.

    Operation IDpublishGlobalSetpointAckJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    SetpointAck<anonymous-message-11>
    Message ID<anonymous-message-11>

    One or multiple messages sent acknowledging that a Setpoint representing a change request of a User on a System has been processed. Each acknowledgment can only be send once.

    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/sp/ack/json/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the JSON format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/sp/ack/msgpack

    Publish acknowledgement of Setpoints(i.e sp) for Connectors. Only Connectors can use this topic as they are allowed to impersonate (via passed issuerUuid) the person who send the request. The topic is intended for other Applications which send data commissioned by one ore multiple Systems. The data payload is expected to be in the msgpack format.

    Operation IDpublishGlobalSetpointAckMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    SetpointAck<anonymous-message-11>
    Message ID<anonymous-message-11>

    One or multiple messages sent acknowledging that a Setpoint representing a change request of a User on a System has been processed. Each acknowledgment can only be send once.

    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/sp/ack/msgpack/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the msgpack format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/sp/json/{issuerUuid}

    Publish Setpoints(i.e sp) for issuers with global access using issuerUuid. Only entities which are allowed to manipulate a complete Domain can use this topic like DomainOwners, Connectors, and DomainAdmins. The data payload is expected to be JSON.

    Operation IDpublishGlobalSetpointJsonWithIssuer

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    GlobalSetpointInput<anonymous-message-12>
    Message ID<anonymous-message-12>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. Following table outlines all possible combinations of required and optional parameters for creating a setpoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/sp/json/{issuerUuid}/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the JSON format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • PUB drivr/v1/{slug}/input/sp/msgpack/{issuerUuid}

    Publish Setpoints(i.e sp) for issuers with global access using issuerUuid. Only entities which are allowed to manipulate a complete Domain can use this topic like DomainOwners, Connectors, and DomainAdmins. The data payload is expected to be in the msgpack format.

    Operation IDpublishGlobalSetpointMsgpackWithIssuer

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    GlobalSetpointInput<anonymous-message-12>
    Message ID<anonymous-message-12>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. Following table outlines all possible combinations of required and optional parameters for creating a setpoint, ensuring that all necessary attributes are included for successful data submission

    Field Combo 1 Combo 2 Combo 3 Combo 4 Combo 5 Combo 6 Combo 7 Combo 8 Combo 9
    timeStreamUuid
    system(Uuid|Code)
    characteristicUuid
    characteristicCode
    componentUuid
    componentCode
    serviceUuid
    serviceCode
    value
    time
    uuid
    serviceIndex
    ✓: Required, ○: Optional
    oneOf

    Examples

  • SUB drivr/v1/{slug}/input/sp/msgpack/{issuerUuid}/error

    This topic is used by DRIVR to publish errors which occur during processing on the parent topic. The data payload is expected to be in the msgpack format.

    Operation IDsubscribe

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    issuerUuid
    required
    string
    format: uuid

    The unique UUID of the User or System of the entity in DRIVR which issues the change.

      Examples values:
    • "f5b7c457-b6f8-4eb2-9bbe-9c7a81f22bea"

    Accepts the following message:

    ValidationError<anonymous-message-8>
    Message ID<anonymous-message-8>

    An error message from the server.

    object [ValidationError]

    Examples

  • SUB drivr/v1/{slug}/output/sp/s/{systemUuid}/c/json

    Subscribe to Setpoints(i.e sp) for Systems(i.e s) using systemUuid. This topic sends additionally to the payload which should be changed the referenced codes of the Characteristic, Service and Component. The data payload is expected to be in the JSON format.

    Operation IDsubscribeSystemSetpointJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    object

    Accepts the following message:

    SystemSetpointOutputByCode<anonymous-message-13>
    Message ID<anonymous-message-13>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. Includes additionally to the basic Setpoint parameters the codes of the Characteristic, Service, and Component.

    object allOf

    The message structure to send a new to be recorded Setpoint for a SETTING Characteristic on a System's Component. It includes the code of the Characteristic, Service, and Component to be recorded.

    Examples

  • SUB drivr/v1/{slug}/output/sp/s/{systemUuid}/c/msgpack

    Subscribe to Setpoints(i.e sp) for Systems(i.e s) using systemUuid. This topic sends additionally to the payload which should be changed the referenced codes of the Characteristic, Service and Component. The data payload is expected to be in the msgpack format.

    Operation IDsubscribeSystemSetpointMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    object

    Accepts the following message:

    SystemSetpointOutputByCode<anonymous-message-13>
    Message ID<anonymous-message-13>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. Includes additionally to the basic Setpoint parameters the codes of the Characteristic, Service, and Component.

    object allOf

    The message structure to send a new to be recorded Setpoint for a SETTING Characteristic on a System's Component. It includes the code of the Characteristic, Service, and Component to be recorded.

    Examples

  • SUB drivr/v1/{slug}/output/sp/s/{systemUuid}/u/json

    Subscribe to Setpoints(i.e sp) for Systems(i.e s) using systemUuid. This topic provides additionally to the payload which should be changed the referenced UUIDs of the Characteristic, Service and Component. The data payload is expected to be in the JSON format.

    Operation IDsubscribeSystemSetpointOutputByUUIDJson

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    object

    Accepts the following message:

    SystemSetpointOutputByUUID<anonymous-message-14>
    Message ID<anonymous-message-14>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. Includes additionally to the basic Setpoint parameters the UUIDs of the Characteristic, Service, and Component.

    object allOf

    The message structure to send a new to be recorded Setpoint for a SETTING Characteristic on a System's Component. It includes the UUID of the Characteristic, Service, and Component to be recorded.

    Examples

  • SUB drivr/v1/{slug}/output/sp/s/{systemUuid}/u/msgpack

    Subscribe to Setpoints(i.e sp) for Systems(i.e s) using systemUuid. This topic also sends the referenced UUIDs of the Characteristic, Service, and Component along with the payload that should be changed. The data payload is expected to be in the msgpack format.

    Operation IDsubscribeSystemSetpointOutputByUUIDMsgpack

    Available only on servers:

    object
    slug
    required
    string

    The slug of your individual Domain.

      Examples values:
    • "adam"
    • "eve"
    systemUuid
    required
    string
    format: uuid

    The unique UUID of the System within DRIVR.

      Examples values:
    • "24ee14a3-f1c8-49aa-95fc-ad0432e23b99"
    object

    Accepts the following message:

    SystemSetpointOutputByUUID<anonymous-message-14>
    Message ID<anonymous-message-14>

    The payload to be processed by DRIVR recording an intent by a User to change a SETTING Characteristic in DRIVR. Includes additionally to the basic Setpoint parameters the UUIDs of the Characteristic, Service, and Component.

    object allOf

    The message structure to send a new to be recorded Setpoint for a SETTING Characteristic on a System's Component. It includes the UUID of the Characteristic, Service, and Component to be recorded.

    Examples