| Excerpt |
|---|
This guide covers how to configure Philips Hue Motion Sensors for use with the ResourceXpress workspace management system. |
...
The RX Sensor Service is a Windows Service which that connects ResourceXpress to Philip Hue Motion Sensors via Hue Bridges.
It is used to detect user movement at desks, huddle spaces or meeting room workspaces and to automatically create a booking for a default period. When movement is no longer detected it then initiates a check-out process to terminate the booking. If the booking is coming to an end and movement is detected it will extend the booking for another period.
Check out our release notes here → Release Notes [RX Sensor Service ]
Requirements
ResourceXpress server (V5 or above)
ResourceXpress Workspace licences (1 per workspace sensor)
Philips Hue Bridge (v2.0) - 1 per local group of sensors
(see Philips Hue Sensor & Bridge Limitations for range and capacity guidelines)Philips Hue Motion Sensor (1 per workspace)
...
| Expand | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
For this stage, ResourceXpress server workspace profiles are assumed to be created. This next step locates any new sensors that have not previously been connected. In the URL textbox add a “/” then paste your API User Token, ensure you keep the original “/api” value.
 For each sensor that will be connected to this Hue Bridge remove the small plastic tap found on the front of the device. The LED on the front of the sensor should start flashing red/orange which indicates the sensor is in pairing mode. In the URL textbox after the API user token add “/sensors”
Remove the text from the Message Body textbox. The message shown in the Command Response textbox will indicate that the Hue Bridge is now looking for all new devices. List All New SensorsAllow a few moments for Hue Bridge to discover all the sensors, then add “/new” to the URL textbox.
Click the GET button.  In the Command Response textbox, a list of all the newly added sensors will be displayed. You will need to take note of the ID number for each “motion” sensor only. If configuring sensors on a new system it is likely the ID values will be 2, 5, 8, 11, 14, 17… etc List All SensorsIf you already have sensors connected use the URL as above but remove the “/new” section from the URL, then click the GET button. Assign an RX ProfileWe advise taking the time now to work out which sensor and RX Profile are to be linked. 
Checking for Motion
To ensure the sensor is accurately detecting motion, enable usertest.
In the Message Body use the below value:
Click the PUT button.  In the Command Response textbox, you will see confirmation of the updated change.  When the sensor detects motion, a green LED on the front of the device will turn on. You can use the green LED to visually find the Motion Sensor device with this sensor ID. Naming the SensorTo allow the Sensor Service to know which RX Profile a sensor is paired with, the RX Profile ID needs to be added to the sensor name. To update a sensors name, remove “/config” from the URL textbox.
In the Message Body textbox enter the below value (modify the name to your requirement):
Click the PUT button.  In the Command Response textbox, you will see a message confirming the new name of the sensor. 
Disable usertestTo disable usertest, add “/config” after sensor ID in the URL textbox:
In the Message Body use the below value:
Click the PUT button. In the Command Response textbox, you will see confirmation of the updated change. Repeat this step for each sensor being used with this Bridge. |
...