
Readings View
Select the Readings Tab within the tab bar to view the devices
data history as time stamped data.
- On the far right of the Sensor History Data is a cloud
icon( ). Selecting this icon will export a .csv file
containing sensor data.
Exported Data
The exported .csv file will have the following columns of data:
MessageID: Unique identifier of the message in our database.
Sensor ID: If multiple sensors are exported, you can distinguish between them using this number, even if the names are
the same.
Sensor Name: The name you gave the sensor.
Date: The date the message was transmitted from the sensor.
Value: Primary data value presented with transformations applied, but without labels.
Formatted Value: Data transformed and presented as shown in iMonnit.
Battery: Estimated life remaining of the battery, reported as a percentage.
Raw Data: Raw data as it is stored from the sensor.
Sensor State: Binary field represented as an integer containing information about the state of the sensor when the
message was transmitted. (See Sensor State explained below.)
Gateway ID: ID of the gateway that connects the sensor to the Internet
Alert Sent: Boolean indicating if this reading triggered a notification to be sent from iMonnit.
Signal Strength: Strength of communication signal between the sensor and the gateway, shown as percentage value.
Voltage: Actual voltage measured at the sensor battery used to calculate battery percentage, similar to Received Signal
you can use one or the other or both if they help you.
PAGE 7
Note: Make sure you have the date range for
the data you need input in the From and To
text boxes. This will be the previous day by
default. Only the first 2,500 entries in the
selected date range can be exported.
Sensor State
The value presented here is generated from a single byte of stored data.
A byte consists of eight bits of data that we read as Boolean (True (1) / False (0)) fields.
When broken into individual bits, the State byte contains the following information: aaaabcde
STS: This value is specific to the sensor profile and is often used to indicate error states and other sensor conditions.
UNUSED: This sensor does not use these bits.
AWARE: Sensors become aware when critical sensor specific conditions are met. Going aware can cause the sensor to
trigger and report before the Heartbeat, causing the gateway to forward the data to the server immediately or nearly
immediately.
TEST: This bit is active when the sensor is first powered on or reset and remains active for the first nine messages when
using default configurations.
STS Specific Codes:
0 = No problems sensor is functioning normally, 5 = Calibration failed due to unstable readings, 6 = Duplicate calibration
command was sent multiple times by the system and was rejected, 7 = Calibration failed, 8 = Calibration passed,
12 = Reading exceeded 50 ppm limit, 13 = Temperature range exceeded, 14 = Hardware error, 15 = Sensor initializing
because it was just powered on or reset.