Sensors play a pivotal role in gathering occupancy data, and once sensors are commissioned in Mapiq, you can access occupancy data in your environment. However, like all technology, sensors can sometimes face issues, ultimately disrupting the data stream. Addressing these issues promptly ensures accurate data collection and optimal system performance. This article will guide you through common sensor-related problems and their solutions.

Sensors can face challenges both at the software and hardware levels. Recognizing these issues is the first step in troubleshooting.

Here's a breakdown of common problems and their solutions:

Cause: The sensor might not be linked to a location, or unpublished changes to the building are present, preventing sensor linking. As well as deleting locations, desks, or meeting rooms will decommission the sensor.

Solution: Ensure the sensor is commissioned to a location. Re-commission sensors if necessary, especially after making changes to the building. If decommissioned, you can easily re-commission sensors by visiting the sensor overview and assigning a 'new' location. Remember to publish the building first to avoid issues with unavailable locations.

Cause: Some sensors are battery-powered and might stop working when the battery is depleted.

Solution: Monitor battery levels and replace them as needed.

Cause: Sensors powered by cables might get disconnected, and if a sensor is disconnected from power, it will appear broken.

Solution: Check both ends of the power cable connected to the sensor and the wall outlet, as wires can become loose over time. Ensure that the sensor is reconnected if it is unplugged for any reason.

Cause: Mistakes or typos during commissioning can cause mismatch between the added sensor and the actual sensor ID.

Solution: Always double-check sensor IDs and avoid using white spaces before or after the ID.

Cause: Sensors provide periodic updates to indicate their activity. If a sensor is physically blocked in some way, it may remain occupied even when it's not in use.

Solution: Remove any objects blocking the sensor and monitor its status over time. If the sensor doesn't work after removing the object, it may be broken.

Cause: A broken sensor can either have a damaged occupancy detection mechanism or fail to send data. In the first scenario, check if the sensor is truly broken or another issue is causing the problem.

Solution: Check the power cable if the sensor doesn't provide data or respond. If the cable is connected but the sensor isn't working, replace the broken sensor and remove it from the sensor overview page.

Cause: Sensors generally communicate through an internet connection, but network issues or firewall restrictions might affect data transmission.

Solution: Ensure stable internet connectivity and check for any network restrictions. Mapiq can help identify the problem but often requires local internal IT work to fix it.

Cause: Sensor networks rely on hardware and have a single entry and exit point for all information: the gateway. Issues with the gateway can halt data transfer.

Solution: Try a power cycle, check firewall/internet settings, or replace the gateway to address these issues.

Cause: Mapiq uses various services to support sensor networks, which can be impacted by degradation or outages.

Solution: In such cases, Mapiq will address the issue(s).