Skip to main content
This article requires you to have at least PADS4 version 2025.2.
After you set up gateways in PADS4, Workspace automatically imports them into Workspace Administration -> Occupancy Sensors. A PADS4 Gateway appears in the list of gateways in Workspace Administration. This is a generic gateway that automatically imports PADS4 devices (motion sensors and LEDs) into Workspace. Ws Sensor1
  • In the tabs next to it, you can find the sensors and LEDs that you can use in Workspace.

Sensors

  • Sensors detect motion and can be linked to one room (this includes modular spaces).
Ws Sensor2
  • To link a sensor, click the link (chain) button, select the room, and click the save button. To cancel the edit, click the dropdown button next to the save button and select Cancel.
Ws Sensor3
Linking a sensor costs an IoT license. You can find the number of licenses in the top right corner of the sensor table.
Remaining Licenses
  • License errors can occur. In that case, Workspace shows a warning indicator on the device row. You can encounter an error in two cases:
    • The sensor is linked to an invalid room. This may occur due to the room not having a license (anymore).
    • The sensor exceeds the number of available licenses.
  • Hover over the warning to see a tooltip that explains which error occurred.
Ws Sensor4
  • When you link a sensor to a room, the sensor automatically creates a booking for that room. This happens when the sensor detects motion for the number of minutes defined in the room profile. The sensor names the meeting PIR and gives it the duration defined in the room profile.
  • In the room profile, you can also define the lunch break. The lunch break is the time range during which the sensor doesn’t affect any meeting. During this time, the sensor doesn’t cut off or release a booking if people are absent. It also doesn’t create a new automatic booking.
  • Take the following example of a room profile setup:
Ws Sensor5 In this case, the sensor will:
  • Create a booking of 15 minutes once a motion sensor has detected motion for 2 minutes.
  • Cancel/remove a booking (automatic or not) if it detects no motion during the booking’s first 5 minutes.
  • Cut off/release a booking (automatic or not) if it detected motion during the meeting but hasn’t detected any new motion for 5 minutes.
  • Not cancel/release/create a booking between 12pm and 1pm.
The “Time without presence before release” timer starts counting these 5 minutes after the motion delay has passed. For example, if the motion delay of the sensor is 120 seconds (2 minutes), the sensor releases or cancels the booking 7 minutes after it last detected motion. If the sensor detects motion during these 7 minutes, it repeats the process. Automatic bookings never overwrite or overlap existing bookings. In the previous example, suppose the sensor creates an automatic booking 9 minutes before an upcoming booking. The automatic booking then lasts only 9 minutes, even though the room profile specifies a 15-minute booking.

LEDs

  • LEDs only react to events and do not act by themselves. You must link each LED to either a room or a sensor. To do this, make sure that the LED has the desired linking type: Room Link or Sensor Link.
  • To update the linking type, click the pencil icon on the right side of the sensor row to open the edit dialog.
Ws Sensor6
  • When you set the type to Room Link, click the link (chain) button to select a room for the LED. The LED then indicates the status of the linked room, including modular spaces. Red means the room is occupied or reserved by a booking. Green means the room is free with no current booking.
  • When you set the type to Sensor Link, you can select a sensor for the LED. The LED then indicates the status of the linked sensor. Red means the sensor detects motion. Green means the sensor detects no motion.
  • When the LED turns green, the motion delay has passed. The room then releases or cancels the current booking after the number of minutes configured in the room profile.