While Disruptive Technology sensors are robust and accurate, external factors can cause them to go offline or have unexpected readings. This guide will help you troubleshoot and resolve common sensor issues for the Tactile Touch Sensor (101594, 101643).
The guide assumes that you have access to Studio.
Troubleshooting
To fix the issue, please read each section thoroughly to figure out the problem with the sensor and apply the suggested corrective action.
No connection
Sensors are determined to be offline (no signal icon) if the Cloud hasn't received a periodic heartbeat within the expected period. Typically, a sensor is offline because it cannot reach an online Cloud Connector so that its measurement can get to the cloud.
| Possible cause | Corrective action |
|---|---|
|
No online Cloud Connector nearby The sensor can only send data to the cloud if a nearby online Cloud Connector exists. |
|
|
Service disruption Cloud service disruptions can impact sensor connectivity. |
|
|
Temperature outside the operating range Sensors may stop reporting data if the temperature is outside the range of -40°C to 85°C (40°F to 185°F) or if condensation is present. The sensor is not designed to operate in condensing environments, and condensation at any RH level is outside the supported operating range. |
|
|
Exposure to magnetism Magnetic fields can drain the battery and cause unresponsiveness for the sensor. |
|
|
Mechanical damage The sensor is sealed and robust, but impacts can damage it. |
|
|
Water penetration The sensor is waterproof (IP68), but prolonged exposure to water/condensation may shorten its lifespan, especially in high temperatures. |
|
|
The sensor is placed on metal The sensor has a small antenna that will be affected if the sensor is placed on a metal surface. |
|
|
Depleted battery The sensor needs a working battery to measure temperature and send radio messages. |
|
|
Regional product incompatibility DT devices have two versions: EU and US that use different radio frequencies. |
|
Unstable connection
If the sensor experiences spotty connectivity, the issue may be caused by range limitation or environmental factors affecting the signal. The table below outlines possible causes and corrective actions to help restore consistent connectivity.
| Possible cause | Corrective action |
|---|---|
|
Cloud Connector is out of range The sensor can only send data robustly to the cloud if a nearby online Cloud Connector exists. Otherwise, it will enter Boost mode (boost icon) or sporadically go offline. |
|
|
Environmental challenges The sensor's placement affects signal strength. Metal or glass doors, as well as enclosed spaces with thick walls can weaken connectivity. |
|
|
Electromagnetic interference Strong electromagnetic interference may inhibit radio reception in the sensor or the Cloud Connector, causing intermittent communication loss even with a strong connectivity indication. |
|
|
Near end-of-life A low sensor battery may cause it to go offline and online intermittently. |
|
Unexpected measurements
If the sensor is not installed correctly or without considering environmental factors, it may give unexpected readings. To avoid this, it is recommended that you follow the instructions provided in the Installation Manual for Tactile Touch Sensors.
| Possible cause | Corrective action |
|---|---|
|
The sensor is exposed to water or condensation Small water droplets reaching the inside of the sensor housing may trigger the touch sensor and cause false touch events or prevent touch events from being detected. |
|
|
Mechanical damage or obstruction If the button surface is stuck or damaged, it may prevent touch events from being correctly detected. |
|
|
Impact of electrical equipment If the sensor reports false or inconsistent detections, it may be affected by electromagnetic interference (EMI). This can happen when the sensor is installed too close to devices like fluorescent lights, motors, or large electrical machinery, which can disrupt its capacitive sensing. |
|
Troubleshooting did not fix the problem?
Please get in touch with us if the above-mentioned fixes did not resolve the issue. Please include the ID of the device(s) and a description of the issue when contacting support.