Sign into Dashboard

Documentation

⌘K
  2. Home
  4. Docs
  6. Documentation
  8. Data Sources
  10. Device Tags
  12. Add Tag

Add Tag

On the Data Source tab, first click on the device (See Devices) on the Devices table that you’d like to add the tag information to. Click the Add Tag button.

Type the Tag Name and Tag Description. Then, select the Tag Scope. Note: A tag can only have 1 topic associated with it. If this topic is being used on multiple different devices, Developers will have to create the tag separately for each device.

  • Tag Name: Tag identifier. This value appears in the Project Editor when selecting tags for widgets.
  • Tag Description: Brief explanation of tag purpose.
  • Tag Scope: Where the value of a tag applies and is visible. It can be MQTT or Client. Note: the options change depending on the selection.
    • MQTT: See next section.
    • Client. If Client, click Add Tag. Tag will be listed in the Tag Table.

MQTT Scope

The MQTT scope is for defining tags that have values shared by all devices and clients, like web browsers accessing a Nimbus808 project. Changing the value of an MQTT tag on one client will publish an update to the Nimbus808 broker. Any client subscribing to that same tag is updated with the new value.

  • Topic: An MQTT topic path is specified to define what messages to publish/subscribe to in the Nimbus808 broker. A topic should follow typical MQTT structure and be as descriptive as needed for the current project development.
  • Payload Format: Based on the device sending data to the broker. The format of the payload in messages that Nimbus808 publishes/subscribes to.
    • JSON
      • Data Path: Enter Path
      • Timestamp Path: Enter Path
    • RAW
      • Data Format: Select Format from dropdown
      • Data Offset: Number of words (16-bits) from the start of the data payload.
  • Use default JSON format: Check to open the default settings.
  • Access: Level of permissions granted to a Tag.
    • Read/Write:
    • Read Only:
  • Log Data: Enables data logging for a Tag.

Client Scope

The Client scope is for tags with values specific to each client accessing the tag. In Nimbus808, each web browser accessing an Nimbus808 project has its own instance of a client tag.

Changing the value of a client tag will not affect the value of the same client tag on a different browser.