New SecondaryData (v0.0.1)

Event is triggered after TODO

Event

Overview

The NewSecondaryData event is triggered when Iot-Processing processes a message that has no location information but does contain information about the state of a tag or tool.

At the moment this secondary data is only created for heartbeat messages.

Message transport details

  • Servicebus: ht-tst-service-bus
  • Topic: secondary_data
  • Subject: New SecondaryData

Schema

schema.json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Position",
  "type": "object",
  "properties": {
    "tagId": {"type": ["string", "null"]},
    "tagIdentifier": {"type": ["string", "null"]},
    "toolId": {"type": ["string", "null"]},
    "date": {"type": "string", "format": "date-time"},
    "dataSource": {
      "type": ["string"],
      "enum": [
        "IET10RC1-HeartBeat33",
        "IET10RC1-HeartBeat39",
        "IET10RC1-Magnet"
      ]
    },
    "magnetClosed": {"type": ["boolean", "null"]},
    "batteryLevel": {"type": ["number", "null"]},
    "fillingStatus": {"type": ["number", "null"]},
    "tofCounter": {"type": ["number", "null"]},
    "correlationId": {"type": "string"}
  },
  "required": [
    "tagIdentifier",
    "toolId",
    "date",
    "dataSource",
    "magnetClosed",
    "batteryLevel",
    "fillingStatus",
    "tofCounter",
    "correlationId"
  ],
  "additionalProperties": false
}

Schema viewer

Generated code