akenza.io
WebsiteAPI DocumentationWhat's newLogin
  • Overview
  • Getting Started
    • Connect a Device
  • Changelog
  • General
    • Applications
    • Organization context
    • Workspace Context
    • Users
      • User Roles
  • Device Management
    • Managing an organization
      • API keys
      • Users (Organization)
        • Add & removing users from your organization
    • Managing a workspace
      • General Settings
        • Device Lifecycle Reports
        • Workspace properties
        • Occupancy settings
        • Device Setup Assistant
      • Custom fields
      • Tags
      • Users (Workspace)
    • Devices
      • Device
      • Device Simulator
      • Bulk actions
      • Bulk import CSV templates
    • Rules
      • Input
      • Logic blocks
        • Comparison
        • Custom Logic
          • Logic Block Scripting
      • Timed Rules
      • Rule Actions
        • Downlink
    • Data Flows
      • Device Connectors
        • Device Security
          • Using Device Credentials
            • Creating Public/Private Key Pairs
            • Using JSON Web Tokens (JWTs)
              • Python
              • Java
        • HTTP
        • MQTT
        • CoAP
        • LoRaWAN
          • Connectivity Management
          • Swisscom LoRaWAN
          • The Things Network
          • Loriot
          • Actility’s ThingPark Wireless
          • EWZ
          • Cibicom
          • Helium
          • ChirpStack
        • NB-IoT
        • mioty
        • Disruptive Technologies
        • VergeSense
        • Spaceti
        • Haltian
      • Device Types
        • Custom Device Types
          • Uplink
          • Downlink
          • Scripting
        • Library
      • Output Connectors
        • Databases
          • akenza DB
          • InfluxDB
          • SQL Databases
        • Streaming
          • Webhook
          • Azure IoT Hub
          • AWS Kinesis
          • Google Cloud Pub/Sub
          • Apache Kafka
        • Notifications
          • E-Mail
          • SMS
          • Microsoft Teams
          • Slack
    • Custom Components
    • Integrations
    • Reference
      • REST API
        • Filtering
        • Querying Device Data
      • WebSocket API
      • Scripting
        • Stateful Operations
        • Utility Functions
      • Payload Templating
  • Reference
  • Dashboard Builder
    • Managing Dashboards
      • Embedding dashboards
    • Components
      • Map
      • Floorplan
  • Device Setup Assistant
    • Device Setup Assistant - Overview
  • Tutorials
    • BI Tools
      • Grafana Data Source Plugin
      • How to build a dashboard with Retool
      • How to analyze data with AWS QuickSight
    • Devices
      • How to integrate the XDK device from Legic via MQTT on akenza
      • How to connect the Disruptive Technologies-cloud on akenza
      • How to send Downlinks to the Kuando Busylight device
      • How to integrate an Arduino device via MQTT on akenza
      • Integrate a MClimate Vicki LoRaWAN Radiator Thermostat on akenza
      • How to integrate an ERS Elsys device with Loriot on akenza
      • How to integrate the IAM Decentlab device with TTN on akenza
      • How to integrate the Seeed SenseCAP T1000 tracker on akenza
      • How to integrate a Swisscom Multisense device on akenza
    • Notifications
      • How to send SMS notifications
      • How to send notifications to Slack
      • How to send notifications to Microsoft Teams
    • Enterprise solutions
      • How to send data to Azure IoT Hub
      • How to send data to the Google Cloud Pub/Sub
      • How to send data to InfluxDB
      • How to send data to AWS Kinesis
      • How to send data to Azure Event Hubs with Apache Kafka
    • IoT Starter Kits
      • How to integrate the IAQ Kit with Actility on akenza
      • How to integrate the CoWork Kit with Actility on akenza
      • How to integrate the Smart Building Kit with Actility on akenza
      • How to integrate the Pepperl+Fuchs Kit with Actility on akenza
  • Support Center
    • FAQ
    • Status Page
    • Service Desk
    • Request a feature
  • Deprecated
    • SIM-Cards
    • Everynet
    • Sigfox
    • How to connect the Yanzi Lifecycle cloud on akenza
Powered by GitBook
On this page
  • 1. Adding tags during device creation
  • 2. Adding tags on the device detail page
  • 3. Managing tags on the workspace settings page
  • 4. Use of tags as rule input

Was this helpful?

  1. Device Management
  2. Managing a workspace

Tags

PreviousCustom fieldsNextUsers (Workspace)

Last updated 7 months ago

Was this helpful?

Devices can be structured by annotating them with tags. This allows managing large amounts of Assets within a Workspace at once and brings more convenience by setting up that apply to multiple . The following steps are explained in more detail:

Asset Tags can also be used to filter or search for assets within the Asset Inventory.

1. Adding tags during device creation

A tag can be added optionally to a device during device creation. Already existing tags will be displayed on the tag field and can be selected if wanted. Otherwise, a new tag can be created by giving an individual name. Tag names are limited to 64 characters and could stand for a group of sensors such as Temperature, Humidity, or CO2 or for certain rooms or areas like 1st-floor building A.

2. Adding tags on the device detail page

When adding tags to a device on the device detail page you can choose from the existing workspace tags or create a new tag. A device can have one or multiple tags. When tags are removed from a device, they are not deleted from the workspace.

3. Managing tags on the workspace settings page

A tag can be added or edited on the Tag management page in the workspace settings. Already existing tags can be viewed and modified. A new tag can be created or a set of new tags can be imported using bulk import (see the template below).

Tag names are limited to 64 characters and have to be unique within a workspace. A tag can stand for a group of sensors such as Temperature, Humidity, or CO2 or for certain rooms or areas like floor1.

A bulk import template for tags can be downloaded here:

4. Use of tags as rule input

Tags can be used as rule input on the Rule Engine. This simplifies the selection of a multiple devices that shall have the same rule logic applied. All existing tags in the Workspace are displayed on the Rule Input as Available tags and can be selected as a Rule Input.

To apply tags as a Rule Input, devices must have the same data schema (topic and data key)

Rules
Assets
127B
Tag bulk import template.csv
Asset tags during device creation
Asset tags on device detail page
Tag as rule input