Resolving sensor errors & warnings

The Mapiq Sensor network consists of a room sensor (PIR) or workplace sensor (WPS). It can occur that these sensors are not functioning properly. To capture these sensors Mapiq created a 'Mapiq Sensors' report in Power BI. Where you have an overview of all the Mapiq sensors that report errors.

This guide is to help you identify the sensors in an error and how to reactivate them where possible.


TABLE OF CONTENTS


Glossary

  • WPS: Work Place Sensor, provided with a sensor strip and a power adapter.
  • PIR: Passive Infra-Red sensor, also known as ar oom sensor, works on battery power.
  • WPS-old: Old Work Place Sensor work similar as PIR sensor.
Old Work Place Sensors (WPS-old) have no LED light embedded in its housing. It works as a room sensor, thus it has no detection strip, and it's battery powered. Ignore the resolution written for the WPS-old sensor when not applicable for you. 


Hard reset procedure

Room sensor (PIR)

  • If the status does not update, first check to see if other sensors are updating their status when triggered as it might indicate a network outage.
  • If other sensors are responsive, perform a hard reset of the sensor. This will force it to reconnect to the network.

Steps for the hard reset:

  1. Confirm that 2 charged batteries are in Mapiq room sensor and that their orientation is correct. 
  2. Confirm you are in range of the Mapiq sensor network and that your gateway is in commissioning mode (LED on the gateway should be orange) 
  3. Remove 1 battery from the Mapiq room sensor  
  4. Wait for at least 10 seconds  
  5. Replace the removed battery into the battery compartment. 
  6. Observe the LED behind the lens of the sensor blinking red intermittently. 
  7. During the period the LED stops blinking and stays red, remove 1 battery again. 
  8. Wait for at least 10 seconds 
  9. Replace the removed battery into the battery compartment. 
  10. The following sequence LED sequence on the Mapiq room sensor indicates a successful connection:
    1. Red intermittent blinking  
    2. Red continuous 
    3. Green intermittent blinking 
    4. Off 


Workplace sensor (WPS)

  • Confirm that the Mapiq Workplace sensor is powered by verifying that the LED is on

Steps for the hard reset:

  1. Unplug the power cable
  2. Press – and hold – the button on the front of the Mapiq Workplace sensor
  3. Plug in the power cable while holding the button
  4. Release the button after the LED has blinked purple
  5. Wait for at least 60 seconds
  6. Press the button and verify that the LED does not turn purple
  7. If the LED turns purple this indicates that:
    1.  You are not close enough to the gateway or an online router within the correct VLAN
    2. If you are, please contact Mapiq Support


An unexpected duration of one occupancy state (WPS)

The sensor occupancy state remains in the same status (free, occupied, cooldown) for too long and seemingly isn’t responding to any occupancy change anymore.
  1. Check the current status of the LED.
  2. If green:
    1. Check if the detection-strip placed under the desk is reacting to movement, when waving your hand underneath.
    2. The LED should on the sensor should change color. If nothing happens, check if the cable of the detection-strip is properly inserted in the sensor.
    3. If uncertain or if loose, please remove the cable from the sensor and insert it once more. When plugging in an audible click can be heard.
    4. Ensure that the strip is detecting movement by waving underneath the strip.
  3. If red:
    1. Check if the cable of the detection-strip is properly inserted in the sensor.
    2. If uncertain or if loose, please remove the cable from the sensor and insert it once more. When plugging in an audible click can be heard.
    3. Ensure that the strip is detecting movement by waving underneath the strip.
  4. If the LED shows no color: then the sensor has no power.
    1. Check the power cable of the sensor on both ends (sensor-end, outlet-end).
    2. After plugging in the power notice that the LED is turning on again.
    3. It should turn green after startup.
    4. Ensure that the strip is detecting movement by waving underneath the strip.
  5. If all above doesn't result in a working sensor, please try a hard reset (see procedure at the end).
  6. Check if there is no tempering with the sensor (e.g. tape) or physical damage.
  7. If even the hard reset doesn't work notify Mapiq Support.


An unexpected duration of one occupancy state (WPS-old)

The sensor occupancy state remains in the same status (free, occupied, cooldown) for too long and seemingly isn’t responding to any occupancy change anymore.
  1. Check the current status of the sensor in the Mapiq 3D map.
  2. If green:
    1. Check if movement detection is active. Wave under the infrared sensor.
    2. On the 3D map, the sensor should change symbol from green to red.
    3. If nothing happens, check if nothing is blocking the infrared sensor from measuring movement.
  3. If red:
    1. Wave in front of the sensor to trigger a response.
    2. Check if nothing is moving that might trigger the infrared sensor.
    3. Check if the sensor is not damaged.
  4. If all above doesn't result in a working sensor, please try a hard reset (see procedure at the end).
  5. If even the hard reset doesn't work notify Mapiq Support.


Doesn't have an IOIID in API endpoint /nodeIOIpairs

The sensor is reporting back to the gateway, but we didn’t link the sensor to any work spot and/or meeting room.
  1. These sensors are usually older or spare sensors still active. However, it can also indicate recently swapped sensors which Mapiq is not updated about. The newly installed sensor availability will then not be shown to users, making it useless.
  2. Check if the sensors in stock are corresponding with the IDs.
  3. Check if recently sensors have been swapped or installed without informing Mapiq. If so, please indicate which sensor IDs are placed at which work spot/room.


Doesn't show up in API endpoint /nodes

Mapiq linked the sensors in the editor, but the sensor isn’t registering itself on the gateway. For allowing the sensor to register on the gateway, Mapiq needs to turn on the registration mode.
  1. Check if sensor is working properly physically (e.g. not damaged, LED switching).
  2. Note if the sensor was working before or if it was newly installed.
    1. Newly installed:
      • Make sure that the sensors have had a hard reset prior to installation (see hard reset below). If not, the sensor won’t register itself on the network.
      • Double check if sensor ID is correct.
    2. Working before (WPS):
      • Check if the sensor is powered (indicated by a LED). If not, check if the power cable is properly plugged in on both sensor- and outlet side.
    3. Working before (WPS-old): 
      • Double check if the battery isn’t depleted 
      • Check if the sensor ID is correct.
  3. Do a hard reset of the sensor.


For more than 2 hours nor response from sensor

The sensor isn’t reporting back to the gateway for more than 2 hours, whereas it normally does so every 15 minutes if no status is changed.
  1. Check if the sensor is powered (indicated by a LED). If not, check if the power cable is properly plugged in on both sensor- and outlet side.
    1. Note that this can also be the case if desks have been moved and sensors are still installed under the desk! If no power is given to the sensors this error can pop-up!
  2. Try a hard reset of the sensor (procedure shown at the end).
  3. If above doesn't work, please notify Mapiq Support.


 In case of an old WPS sensor, it could be that registration on the network was done on a different router then where sensor was actually placed. Thus, not communicating with the router where it’s installed.

 

Only has an IOI ID in API endpoint /nodeIOIpairs and visible for client

Work spot/room is created in our editor with the intention to have a sensor ID linked, but the sensor ID was never communicated to Mapiq.
  1. Check if the workspot/room actually has a sensor placed.
  2. If so, communicate sensor ID.


There is another sensor that contains the same nodeID

Two or more sensors have the same nodeID annotated. This occurred by either an error on Mapiq side or the swapping of sensors, were only the new locations where shared and the old sensor IDs were not communicated to be removed.
  1. Locate all sensors with the same nodeID/sensorID
  2. Note down the sensorID to the corresponding meeting room/work spot
  3. Communicate the correct sensorID with corresponding meeting room/work spot with Mapiq
T
Thijs is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.