Skip to content

Embedded Sense Sensors

Want to know if Meeting Room 101 is actually being used during its reservation? Or the average number of people occupying it per reservation? Place an Embedded Sense sensor in the room and link it to QReserve through Embedded Sense Integration to track actual resource utilization and capture other environmental metrics. Detect when a space is occupied, discover missed reservations, and record activity associated with your resources to better inform your management practices.

Creating an Embedded Sense Integration

All Embedded Sense sensors and hubs have a unique identifier that administrators will require to track a resource via the sensor network. Before you get started creating an integration through QReserve, take note of the identifiers for the sensor(s) you are using with the given resource and the corresponding hub.

Admins can create and modify integrations for their resources under the Embedded Sense Integration tab.

  1. From the site where the resource in question is located, in the left-hand column click on Administration.
  2. From the Administration page, click on Integrations in the left-hand column.
  3. On the Integrations page, ensure the Embedded Sense Sensors option is activated.
  4. In the left-hand column, under Integrations, click on Embedded Sense.
  5. At the top of the Embedded Sense Integrations page, under Add New Sensor, choose a resource from the drop-down list and enter the corresponding sensor ID. Optionally, include a Hub ID (if left blank, the closest hub will be used) and the location of the sensor (e.g. North East Corner of Meeting Room 101). Click Add Sensor and your new integration will appear below on this page.

Creating an embedded sense integration

Update data on sensor integrations

Under your list of resources with Embedded Sense Integrations, admins can verify and update essential information on their sensors.

In the example below, "Found! (3.01V)" indicates that the sensor is detected (or found) by the hub and that its battery has a charge of 3.01 volts.

Update data on sensor integrations

To make changes to one of your sensors (e.g. its location, Sensor ID or associated Hub ID), introduce the updated information under the corresponding categories of the resource in question and click Save on the right-hand side of the page.

To delete a sensor integration, locate the linked resource from the list and click Delete on the right-hand side of the page.

Enabling and viewing actual usage of resources

Enabling actual usage data to be viewed

Resources acquiring actual usage data from Embedded Sense sensors must be set to allow Unauthenticated Actual Usage.

  1. From the site where the resource in question is located, in the left-hand column, click on Administration.
  2. In the left-hand column, click on Resources.
  3. On the Resources page, select the resource for which you wish to enable actual data usage tracking.
  4. On that resource's dedicated page, select Reservations from the top menu.
  5. In the list of Reservation settings, select Actual usage.
  6. Under the option to Allow Unauthenticated Actual Usage Submissions, toggle the indicator to show "Yes".

As a reminder to administrators, a warning will appear on the Embedded Sense Integrations page for any resources that still require enabling of Unauthenticated Actual Data usage. Click on the button Access Actual Usage Options to be taken directly to the page where this option can be activated

Enabling actual usage data to be viewed

Viewing actual usage data reports

The data in Actual Usage Reports is retrieved from information sent every 2 minutes by sensors to the corresponding hub, providing administrators with precise data on the actual usage of their resources.

  1. From the site where the resource in question is located, in the left-hand column, click on Administration.
  2. From the Administration page, click on Reports in the left-hand column, then Actual Usage from the drop-down column.
  3. Click on the resource in question to view its Actual Usage report.

Actual Usage Reports allow administrators to view a series of data on the use of any resource linked to a sensor.

  • Reservation: Indicates if the resource was reserved while in use.
  • In Use: Indicates if a reserved source was actually used.
  • Records: Indicates how many times used was recorded over the given period of time.
  • Resource: This is the name of the resource in regard to which usage was detected.
  • User: This is the name of the user who was responsible for use of the resource. For example, this can be indicated by a user checking in to start his/her reservation for a meeting room.
  • Time: Indicates the date and period of time over which usage was detected.
  • Source: Indicates the source of actual usage data.
  • People: Indicates an estimation of the number of people using the resource based on motion detection.
  • irt: Indicates the infrared temperature of the object targeted by the sensor.
  • Events: Indicates the number of changes identified by the sensor in its detectable parameters (e.g. new motion, change in temperature).
  • Occupied: Indicates that the sensor detected occupation of the corresponding resource.
  • num_sensors: Indicates the number of sensors linked to the resource that detected usage.
  • ambt: Indicates the ambient temperature around the sensor

Actual usage reports

Customizing Actual Usage Reports

By clicking on Filters, on the upper right-hand side of the page, admins can customize several of the parameters explained above to narrow down their search. For example, admins can specify the date range, user and resource. Admins can also choose to retrieve data on resources depending on their use (i.e. in the example below, only see when a reserved resource was not used), view reservation overlap (i.e. only see when a resource was used without a reservation) and merge records over customizable time periods (i.e. group records if continuous use of a resource is detected at least every 5 minutes).

Customizing actual usage reports