System Alerts
The alerts Not Connected and Low Battery are system alerts; users cannot adjust them. See alerts configuration for your environment monitoring alerts. You may need to authorize [email protected] in your email system.
Not Connected
Day 1: This alert triggers after the sensor has not sent data for 2 hours. The Last Seen reports the date/time of the last data posting received. This you see in your online account or the app. A red highlight is an advisory of a delay.
It correlates with your table data and a "has not been seen in at least 2 hours" alert is sent.
Days 2-4: If the sensor cannot maintain data for 24 hours (e.g. little breaks), subsequent alerts occur once each of the next three days. These state "shows breaks in data during the last X days". If data improves, Not Connected alerts stop. If your data reverts to a 2 hour gap, the 4-day "watch" period starts over. These messages are not necessarily serious, but they can point to need to review your setup (see causes).
Note: To some extent, little breaks are normal. The gateway has one reset cycle each 24 hours or an occasional delay in data transmission can occur. Rarely will you have 100% data - enough overlap is sent to maintain need.
Note: To some extent, little breaks are normal. The gateway has one reset cycle each 24 hours or an occasional delay in data transmission can occur. Rarely will you have 100% data - enough overlap is sent to maintain need.
Common Causes:
- failure to maintain good brand-name alkaline batteries of 1.48V each
- too many sensors per gateway (limit 3-5)
- sensor too far away from gateway (max distance 200 feet, each obstacle reduces by 50%)
- RF interference (e.g. check cordless phone, microwave, engines)
- interval Min or Max too close to failure setting, causing readings to cycle in & out of bounds
- inevitable during a system change that some alerts send; we usually post a notice on this support site