Kaiterra Sensedge Installation guide

KAITERRA
www.kaiterra.com
Kaiterra Sensedge
Connectivity FAQs &
Troubleshooting Guide
SEPTEMBER 2020
Page !1

KAITERRA
www.kaiterra.com
Table of contents
1Overview…………………………………………………………………………………………………………………………………3
2 Kaiterra Sensedge Connectivity FAQs……………………………………………………………….……………4
3.Connectivity Troubleshooting Steps………………………………………………………………………….…..10
3.1. Is the Sensedge on the network?…………………………………………………………………………10
3.2.Is the Sensedge uploading data to Kaiterra cloud?………………………………………….11
3.3.More troubleshooting steps……………………………………………………………………………….….12
Page !2

KAITERRA
www.kaiterra.com
1.
Overview
This document is intended for use by individuals who may be responsible for
responding to IT issues and requests.
This document answers common connectivity questions for the Sensedge and
provides guidance for connectivity troubleshooting.
Page !3

KAITERRA
www.kaiterra.com
2.
Kaiterra Sensedge Connectivity FAQs
What servers does the Sensedge connect to?
For firmware versions >= 1.5:
•MQTT server:
◦sensedge.mqtt.kaiterra.com port 8884
◦sensedge.mqtt.kaiterra.cn port 8884*
•API server:
◦api.kaiterra.com port 443
◦api.kaiterra.cn port 443*
•Firmware download:
◦dl.kaiterra.com port 80"
◦dl.kaiterra.cn port 80*
*Inside China only.
Page !4

KAITERRA
www.kaiterra.com
What's the requirement for Wi-Fi on the Sensedge?
The Wi-Fi has to be 2.4GHz. 5GHz Wi-Fi is not supported.
The following Wi-Fi standards are supported: 802.11b/g/n or Wi-Fi 1/3/4 with the new
naming.
Security standards including the latest 64/128 WEP, WPA-PSK, WPA2-PSK, WPA and
WPA2 Personal are supported.
WPA2 Enterprise is NOT supported.
WPA/WPA2 are fulfilling the most part of 802.11i. The latest version of WPA3 is NOT
supported.
Internal PKI (Public Key Infrastructure) is NOT supported.
Does the Sensedge support Modbus?
There are two types of Modbus protocol, Modbus/TCP and Modbus/RTU. The
Sensedge supports Modbus/TCP via the Ethernet port. No external hardware or
dongles/adapters are needed for this.
To support Modbus/RTU, an adapter*can be used to translate from Modbus/TCP to
Modbus/RTU. On the hardware layer, this adapter converts from Ethernet to RS485.
This means that RS485 cabling will be plugged into the adapter, which in turn is
plugged into the Sensedge's Ethernet port."
When using the adapter for RS485, the Sensedge thinks it's running Modbus/TCP,
and the conversion to Modbus/RTU is happening solely on the adapter.
Page !5

KAITERRA
www.kaiterra.com
Can the Sensedge communicate via Wi-Fi to the cloud and Ethernet to BMS via
BACnet or Modbus?
The Sensedge can support connections to the cloud and BMS via BACnet or Modbus
simultaneously, but the connections have to be over the same physical layer - both
over Wi-Fi or both over Ethernet.
Can the Sensedge send data to another MQTT server?
The secondary MQTT server’s URI and port is configured in Settings -> Device
Details -> MQTT. It publishes data on this topic:
The "+" is a placeholder (or wildcard) that matches anything; in this case, the UDID of
the device.
All the data will be uploaded in one message; no sub-path is used for each pollutant.
A message looks like this:
Page !6
*Note: the external adapter requires its own 5V micro-USB power source.
device/pro/history/+

KAITERRA
www.kaiterra.com
•"ts" - Timestamp in UTC
•"rco2 (ppm)" - CO2 in ppm
•"km102.rtvoc (ppb)" - TVOC in ppb
•"km102.rhumid" - relative humidity in %
•"km102.rtemp" - temperature in celsius
•"km100.rpm25c" - PM2.5 in micrograms per cubic meter
•"km100.rpm10c" - PM10 in micrograms per cubic meter
Page !7
{
ts:!"2019-09-25T05:30:00Z",
rco2 (ppm):!441.5,
km102.rtvoc (ppb):!205.6,
km102.rhumid:!54.24,
km102.rtemp:!25.43,
km100.rgt25:!4.565,
km100.rpm25:!38.26,
km100.rpm25c:!45.65,
km100.rgt03:!4331,
km100.rpm10:!41.09,
km100.rpm10c:!49.02,
rbtrytemp:!30,
rbtryvoltage_now:!4049000,
rbtryvoltage_max:!4100000,
rbtrycurrent_now:!334000,
rbrdtemp:!37
}

KAITERRA
www.kaiterra.com
Does the Sensedge allow login for secondary MQTT?
No. It only supports anonymous MQTT. Anonymous MQTT does not require or allow
login info.
What happens to data recorded while the Sensedge is o!line?
If the Sensedge is turned on but not connected to the Internet, it still records and
saves readings to local storage for later upload.
When connectivity is restored, it will continue sending current readings once per
minute. At the same time, it will send data pending upload to the server, prioritizing
with the most recently recorded data.
How much data does the device transfer? What are the bandwidth requirements?
A single reading for a minute is typically around 300-350 bytes per message. With all
of the other data included, a rough average of data transmission speed is around 1kB
per minute, which equals approximately 1.4MB per day.
How fast does the Sensedge upload o!line historical data to the cloud?
The Sensedge uploads 10 records to the cloud per minute.
The time needed to upload historical data to the cloud can be derived by dividing the
o#line time period (in days) by 10.
Page !8

KAITERRA
www.kaiterra.com
As an example, if the Sensedge were o#line for 10 days, it would take 1 day to upload
the historical data.
Page !9
Note: Backlogged data is sent via primary MQTT to our cloud. Secondary MQTT
data upload via local server is currently not supported.

KAITERRA
www.kaiterra.com
3.
Connectivity Troubleshooting Steps
In this section, we are going to walk you through some troubleshooting steps to
fix the connectivity problems you may be facing with your Sensedge.
Usually, most connectivity issues can be identified and solved in two steps:
1. Check if the Sensedge is on the network.
2. Check if the Sensedge is uploading data to Kaiterra cloud.
3.1 Is the Sensedge on the network?
Let’s begin by checking if the Sensedge is on the network. First, make sure that
the Wi-Fi/Ethernet icons in the top-right status bar are white. If not:
1. Ensure that the device has an IP address (Settings->Wi-Fi/Ethernet). A
network administrator will know if the network provides automatic IP
address configuration, or you need to set a static IP on the device.
2. Ensure that IT is not using a whitelist to allow devices on the network/
firewall. If devices are whitelisted, you will have to provide IT with the MAC
address of the device (which can be found on the Wi-Fi/Ethernet pages in
Settings).
Page !10

KAITERRA
www.kaiterra.com
3. Make sure that the firmware on the Sensedge is updated to v1.7.7 or later
versions. After updating, please forget the current Wi-Fi network and try to
connect again.
4. Some routers build a profile of the tra#ic sent by devices, and disconnect
them from the network if they don't look like a PC or Mac. Please make sure
there are no policies like this in place.
5. In rare cases, using a static IP might work better than using automatic
(DHCP) configuration, even if the network supports DHCP. This should be
avoided if possible.
If you have confirmed that the Sensedge is indeed on the network, and are still
having connection issues, let’s move on to the second step and check if the
Sensedge is uploading data to Kaiterra cloud.
3.2 Is the Sensedge uploading data to Kaiterra cloud?
Sometimes in corporate settings the Sensedge will be able to connect to Wi-Fi (or
Ethernet) but will be unable to communicate with our servers. In the top-right status
bar, check the two arrows pointing up and down. If they're grayed out, this means
that the Sensedge is on the network, but it can't upload data to the cloud.
If so, here are some quick points that the IT department can check for :
1. Please ensure communication to MQTT, API, and firmware download servers.
(See "What servers does the Sensedge connect to?" above).
Page !11

KAITERRA
www.kaiterra.com
2. Please ensure there isn’t a CaptivePortal requiring a username and password.
The Sensedge will be able to handle some CaptivePortal logins, but there may
be issues with timeouts, and not all networks are supported.
3. To determine its location, the device uses Google APIs (outside China) and
Gaode APIs (inside China). Make sure these aren't blocked.
3.3 More troubleshooting steps
While these steps will solve most network issues, if they don’t fix the problem, try
some of the steps listed below.
1. Check the device's date and time. If it's not set to automatic and is set too
far into the future, data won't show up on the dashboard.
2. On the device, try going to the MQTT page (Settings -> Device Details ->
Connectivity -> MQTT) and press Restart Service.
Page !12
Tried all the steps but still having issues? Contact us at [e-mail].