IoT Open MQTT API Specification 2.0

Description

Servers

  • MQTT-TLS://lynx.iotopen.se:8883/MQTT-TLSMQTT

    IoT Open main server

    Security:
    • User/Password

      API-Key as password and random username

  • MQTT-Websocket://lynx.iotopen.se/mqttMQTT-WebsocketWebsocket

    Websocket interface for IoT Open main server.

    Security:
    • User/Password

      API-Key as password and random username

Operations

  • RECEIVE {client_id}/evt/{subsystem}/#

    Publish events

    Publish events to other listeners

    Operation IDpublishEvents

    Available only on servers:

    object
    client_id
    required
    string

    The client-id for installation

    subsystem
    required
    string

    The subsystems unique identifier

    Accepts the following message:

    Value Time Message

    The topic/message define what type of value has been sent

    object

    Examples

  • SEND {client_id}/evt/{subsystem}/#

    Receive events

    Receive event updates for specified subsystem on client-id.

    Operation IDreceiveEvents

    Available only on servers:

    object
    client_id
    required
    string

    The client-id for installation

    subsystem
    required
    string

    The subsystems unique identifier

    Accepts the following message:

    Value Time Message

    The topic/message define what type of value has been sent

    object

    Examples

  • RECEIVE {client_id}/obj/{subsystem}/#

    Publish values

    Publish values to other listeners

    Operation IDpublishObject

    Available only on servers:

    object
    client_id
    required
    string

    The client-id for installation

    subsystem
    required
    string

    The subsystems unique identifier

    Accepts the following message:

    Value Time Message

    The topic/message define what type of value has been sent

    object

    Examples

  • SEND {client_id}/obj/{subsystem}/#

    Receive values

    Receive object values, objects path is defined by the sub-topic in that subsystem. Objects report the value when it's confirmed by the device or subsystem. Eg. Z-wave values are published here only if the device reports the final value.

    Operation IDreceiveObject

    Available only on servers:

    object
    client_id
    required
    string

    The client-id for installation

    subsystem
    required
    string

    The subsystems unique identifier

    Accepts the following message:

    Pending message

    Pending value after a set operation

    object

    Examples

  • RECEIVE {client_id}/set/{subsystem}/#

    Set value

    Ask a system to set a object to a new value. Eg. Ask a lamp to turn on.

    Operation IDpublishSetObject

    Available only on servers:

    object
    client_id
    required
    string

    The client-id for installation

    subsystem
    required
    string

    The subsystems unique identifier

    Accepts the following message:

    Value Message

    The topic/message define what type of value has been sent

    object

    Examples

  • RECEIVE {client_id}/cmd/{subsystem}/#

    Publish command

    Publish a command to a subsystem

    Operation IDpublishCommand

    Available only on servers:

    object
    client_id
    required
    string

    The client-id for installation

    subsystem
    required
    string

    The subsystems unique identifier

    Accepts the following message:

    Undefined message

    Message where no parameters are specified

    object

    Examples

  • SEND {client_id}/cmd/{subsystem}/#

    Receive commands

    Receive commands to control operations for a specific subsystem

    Operation IDreceiveCommands

    Available only on servers:

    object
    client_id
    required
    string

    The client-id for installation

    subsystem
    required
    string

    The subsystems unique identifier

    Accepts the following message:

    Undefined message

    Message where no parameters are specified

    object

    Examples

Messages

  • #1Value MessagevalueMessage

    The topic/message define what type of value has been sent

    Message IDvalueMessage
    object
  • #2Value Time MessagevalueTimeMessage

    The topic/message define what type of value has been sent

    Message IDvalueTimeMessage
    object
  • #3Pending messagependingMessage

    Pending value after a set operation

    Message IDpendingMessage
    object
  • #4Undefined messageundefinedMessage

    Message where no parameters are specified

    Message IDundefinedMessage
    object

Schemas

  • object
  • object
  • object
  • value
    number

    The reported value

  • msg
    string

    Optional extra information that may be used in other applications

  • timestamp
    number

    The timestamp for this message, may be with decimal milliseconds

  • object