Datacake Docs
  • Welcome
  • Get Started
  • Changelog
  • Best practices
    • Best practices: Getting started
    • Best practices: Resolution (Timeframe)
    • Best practices: Dashboards
    • Best practices: Reports
    • Best practices: Grouping Devices
  • Datacake LNS
    • Getting Started
    • Gateways
      • Milesight LoRaWAN Gateway - UG6x
      • RAKwireless WisGate Edge Light 2
    • Devices
    • Add Devices without Gateway
  • Device
    • Product
    • Configuration
    • Claiming
    • Historical Data
    • Database
      • Configuration Fields
      • Fields
        • Manual input
        • Field Roles
        • Formulas
        • Mapping Fields
      • Data retention & Datapoints
      • Examples
        • Mapping 4-20mA Signals
        • Converting Units
  • Dashboards
    • Global Dashboards
      • Setting Homepage
    • Device Dashboards
    • Multi-Device Dashboards
    • Widgets
      • Value Widget
      • Chart Widget
      • Image Map
      • Map Widget
      • Text Widget
      • SOS Widget
      • Boolean Widget
      • iFrame Widget
      • Downlink Widget
      • Set Value Widget
      • Measurement List Widget
      • Heatmap Widget
      • Table Widget
      • Image Widget
  • Portal
    • Multi-Tenancy (Workspaces)
    • Reports
      • Energy Report
    • Administrators
    • Members
      • API Users
    • Security & Privacy
    • Billing
      • Support Packages
      • VAT Exemption / Tax ID
      • SMS Credits
      • Access Invoices
      • Unused time and Remaining time in Invoices (Prorations)
      • Codes
    • White Label
    • Rules
      • Legacy Rule Engine
        • Sending notifications via Telegram
      • New Rule Engine
        • Rule Engine Table Overview
        • Copy/Paste and Template Functionality
        • Advanced Rule Engine E-Mail and Webhook Templates
        • Time Restrictions
    • Zones
  • Cake Red
    • Get Started
    • Overview
  • LoRaWAN
    • Get Started
      • CSV Import
      • Custom LoRaWAN Device
    • Configuring LNS
      • The Things Stack (TTN / TTI) Automated Setup
      • The Things Stack (TTN / TTI) Manual Setup
      • Loriot
      • Kerlink Wanesy
      • Helium
      • ChirpStack
      • Tektelic
      • Actility ThingPark
      • Senet
      • Milesight Gateway
      • KPN
    • Downlinks (LoRaWAN)
      • Set Time Frame
    • Securing Webhooks
    • Payload Decoders
      • Location and GPS
      • Access Gateway Metadata
      • Access Measurements
      • Global Variables
    • Using Cayenne LPP
    • Converting Payload
  • Generic API Devices
    • HTTP Downlinks
  • Integrations
    • MQTT
    • Particle
      • Get Started
      • Adding Integrations
      • Decoding Payloads
      • Calling Functions
      • Templates
        • Particle Tracker One
    • Incoming Webhooks
    • Outgoing Webhooks
      • Securing Outgoing Webhooks in Datacake
    • Golioth
    • Blues Wireless Notecard
    • Sigfox
    • Swarm Asset Tracker
    • Grandcentrix Modbus Cloud Connect
    • YuDash LYNX IoT Gateway
    • Dragino NB-IoT
      • Changing NB-IoT Bands
    • Hardwario CHESTER
    • 1NCE OS
  • API
    • Exporting Data
    • Record Measurements via API
    • Node RED to Datacake
    • Generate Access Token
    • Internal MQTT
      • Get Started
      • MQTT Documentation
      • MQTT over WebSocket
      • Example Code
    • GraphQL API
      • Using GraphQL
      • Device Creation
      • Tutorials
        • Read Group via Tags
  • Guides
    • Python
    • Send Slack Notifications
    • Forward Data to Cake Red
    • Multiple Data Feeds
    • Automated Dynamic Downlinks
    • Ingesting JSON Data into Datacake API Devices
    • Working with Default HTTP Decoder on API Devices and Code Examples
    • Accessing Measurements in Decoders
    • Connecting Datacake to Notion Using Zapier
    • How to set up and use location on non-GPS devices
    • How to integrate with AWS IoT Core
    • How to Schedule Mass-Downlinks (Multicast) using Datacake Rule Engine
    • How to Map Sensor Values to Ranges or Booleans, Strings using Mapping Fields
    • Understanding Internal vs. External MQTT Brokers on Datacake
    • Sending UDP Messages between 1NCE OS and Datacake
    • Concepts of LoRaWAN Payload Decoders on Datacake
    • How to check if a value stays above or below limits for given time
Powered by GitBook
On this page
  • What is a Field?
  • Creating a new Field
  • Type
  • Integer
  • Float
  • String
  • Boolean
  • Geolocation
  • Name
  • Identifier
  • Unit
  • Conversion
  • Role
  • Formula

Was this helpful?

  1. Device
  2. Database

Fields

Last updated 11 months ago

Was this helpful?

What is a Field?

In the Datacake Cloud the measured values of your devices are stored in "Fields". These are entries in our time-series database. Depending on your subscription plan, a certain number of fields can be created per device. This are also the so-called "datapoints".

Creating a new Field

To create your own field, open any device and navigate to its configuration area using the tab bar.

There you scroll down a little until you see the "Fields" panel:

Just click on the blue button "Add Field" to create a new field. The following dialog should appear:

Type

We support following field types:

Integer

Stores natural numbers, called in computer science integers, for example, 1234567.

Float

Stores numbers with decimal places, even floating point, such as 1234.56. This type is suitable for storing values with fractions, such as

  • Temperature

  • Pressure

  • Air quality

String

Save complete character strings. like Sensor OK, Your own payload information, A83B8CFH38420. These are being stored unprocessed in the database including a timestamp.

Use this data type to store e.g.:

  • status messages

  • events

  • Your own payload data

In addition, strings can be used in conjunction with mapping fields to convert numeric sensor values into a status via look-up table.

Boolean

Via Boolean fields you can store measured values of digital signals that are either only 0 or 1, or True or False. Use these for:

  • Status-Signals of digital Inputs

  • True / False conditions

  • Events

Geolocation

This field type stores geolocation coordinates, which are provided by GPS modules, for example, and can be used to display positions on maps.

If you choose to store coordinates using a location field, the field expects you to deliver the data as a string and formatted as follows:

"(latitude,longitude)" // Structure
"(52.0123,4.124521)" // Example

Name

This is the displayed, readable name as it can be used in the portal, e.g. to give widgets on dashboards a title or in other places.

You can change this name at any time later.

Identifier

The identifier is a unique designation that is used for storing data in the database.

Once the field is created, the identifier cannot be changed. If you still want to change it, you must delete the field.

Unit

Use the input field to define the unit of the measured values that are being recorded into that field. Thanks to a free text field, you can define any units here, whether °C, PPM, Bar, Fahrenheit or cake, biscuits, whatever.

Conversion

You want to convert units into another one? No problem! Use mapping fields for the conversion of your measurement values via scaling, look-up table or linear scaling of a value range. Use Formula Option of a field to do simple mathematical operations.

Role

The roles assigned allow you to visualise the most important fields of your devices on the list, grid and map views. Learn more about them:

Formula

Each field has the function of a formula. Here, simple mathematical operations can be used to combine measured values from other fields or to perform special calculations. More on this topic is given in the following section:

Mapping Fields
Formulas
Field Roles
Formulas