Synaccess PDUs
Overview

The Synaccess integration allows QReserve to automatically control power outlets based on reservations. This is useful for laboratory equipment, shared workstations, or any scenario where power should be managed based on booking schedules.
Each outlet can be linked to one or more resources, and each link can have its own set of automation rules.
Compatible Devices
QReserve integrates with the Synaccess netBooter DX series of switched PDUs. These devices provide remote power control capabilities and are available in various configurations (number of outlets, voltage ratings, etc.).
The integration uses Synaccess Cloud, which simplifies networking and management by allowing devices to communicate through Synaccess's cloud infrastructure rather than requiring direct network access to each PDU.
Requirements:
- A netBooter DX series device with Cloud functionality enabled
- The device must be connected to the internet to communicate with QReserve
- A Synaccess Cloud API token (obtained through Synaccess cloud and configured in QReserve's site settings)
Availability: The Synaccess integration is available on Standard plans and above. Contact QReserve support to have this feature enabled for your site.
For detailed device specifications and purchasing information, visit the Synaccess website.
Configuration Options
When linking an outlet to a resource, the following options are available from the Synaccess management page in Administration:
Automatic Power Control
These settings control when the system automatically turns outlets on or off:
Setting | Description |
|---|---|
Auto turn on before start | Automatically turn ON the outlet a specified duration before the reservation starts |
Auto turn off after end | Automatically turn OFF the outlet a specified duration after the reservation ends |
Turn on at check-in | Automatically turn ON when the user checks in |
Turn off at check-out | Automatically turn OFF when the user checks out |
Manual Power Control
These settings control when users can manually turn outlets on or off:
Setting | Description |
|---|---|
Allow manual on before start | Allow manual ON a specified duration before the reservation starts |
Allow manual off after end | Allow manual OFF a specified duration after the reservation ends |
Allow manual on during reservation | Allow manual ON during the reservation |
Allow manual off during reservation | Allow manual OFF during the reservation |
Status Requirements
Setting | Description |
|---|---|
Require approved reservation status | If enabled, automation only applies to approved reservations. If disabled, both approved and pending reservations are considered |
Outlet Settings
These settings apply to the outlet itself, independent of any resource links:
Setting | Description |
|---|---|
Lock outlet off | When enabled, the outlet cannot be turned on via QReserve (except by admins) |
IP Restrictions | Comma-separated list of IP addresses or CIDR ranges. When set, users without Synaccess admin permissions must make requests from an allowed IP |
IP Restrictions
IP restrictions provide an additional layer of security for outlet control. When configured on an outlet:
- Synaccess administrators: Not affected by IP restrictions
- Users with qualifying reservations: Must make requests from an allowed IP address
This is useful for scenarios where outlets should only be controlled from specific locations (e.g., within a lab network) even if the user has a valid reservation.
Format examples:
- Single IP:
192.168.1.100 - Multiple IPs:
192.168.1.100,192.168.1.101 - CIDR range:
192.168.1.0/24 - Mixed:
10.0.0.5,192.168.1.0/24,172.16.0.0/16
Precedence Rules
The most important principle in the Synaccess integration is: ON takes precedence over OFF.
This means that if any rule indicates the outlet should be ON, it will not be turned OFF automatically. This prevents situations where one user's equipment is powered down while another user needs it.
Automatic Turn-Off Precedence
When the system attempts to automatically turn off an outlet, it first checks if any of the following conditions are true:
- Another reservation is in its turn-on window: If another reservation's auto turn-on window has started, the outlet stays ON
- Another reservation is currently active: If another reservation is in progress and has auto turn-on configured, the outlet stays ON
- Someone is checked in: If "Turn on at check-in" is enabled and someone is currently checked in, the outlet stays ON
Manual Control Precedence
When a user tries to manually turn OFF an outlet, the system checks if another user has ON access. The rules are:
- Active reservations take priority: If another user's reservation has started and they have manual ON access (via "Allow manual on during reservation" or "Allow manual on before start"), the first user loses their OFF ability
- Back-to-back reservations: If User A's reservation has ended but they're in their manual off window, and User B's manual on window has started, User A loses their OFF ability
- Check-in based precedence (when "Turn on at check-in" is enabled): Precedence is based on actual check-in status, not just reservation times. User A keeps their OFF ability until User B actually checks in.
Examples
Example 1: Basic Automatic Control
Configuration:
- Auto turn on before start: 10 minutes
- Auto turn off after end: Immediately
Reservation: 2:00 PM - 3:00 PM
Behavior:
- 1:50 PM: Outlet automatically turns ON
- 2:00 PM - 3:00 PM: Outlet stays ON
- 3:00 PM: Outlet automatically turns OFF
Example 2: Back-to-Back Reservations
Configuration:
- Auto turn on before start: 10 minutes
- Auto turn off after end: Immediately
Reservations:
- User A: 1:00 PM - 2:00 PM
- User B: 2:00 PM - 3:00 PM
Behavior:
- 12:50 PM: Outlet turns ON for User A
- 1:50 PM: User B's turn-on window begins (outlet already ON)
- 2:00 PM: User A's reservation ends, but User B's is active - outlet stays ON
- 3:00 PM: User B's reservation ends, outlet turns OFF
Example 3: Overlapping Turn-On Windows
Configuration:
- Auto turn on before start: 30 minutes
- Auto turn off after end: 5 minutes
Reservations:
- User A: 1:00 PM - 2:00 PM
- User B: 2:00 PM - 3:00 PM
Behavior:
- 12:30 PM: Outlet turns ON for User A
- 1:30 PM: User B's turn-on window begins
- 2:00 PM: User A's reservation ends, User A's turn-off window starts
- 2:05 PM: User A's turn-off window ends, but outlet stays ON because User B's reservation is active
- 3:00 PM: User B's reservation ends
- 3:05 PM: Outlet turns OFF (no more active reservations)
Example 4: Manual Control with Precedence
Configuration:
- Allow manual on before start: 10 minutes
- Allow manual off after end: 30 minutes
- Allow manual on during reservation: Yes
- Allow manual off during reservation: Yes
Reservations:
- User A: 1:00 PM - 2:00 PM
- User B: 2:00 PM - 3:00 PM
Manual Control Access:
Time | User A Can Turn ON | User A Can Turn OFF | User B Can Turn ON | User B Can Turn OFF |
|---|---|---|---|---|
12:50 PM | Yes | No | No | No |
1:00 PM | Yes | Yes | No | No |
1:50 PM | Yes | No (User B's ON window started) | Yes | No |
2:00 PM | No | No (User B's reservation active) | Yes | Yes |
2:30 PM | No | No (window expired) | Yes | Yes |
3:00 PM | No | No | No | Yes |
3:30 PM | No | No | No | No (window expired) |
Key insight: At 1:50 PM, even though User A's reservation is still active, they lose their OFF ability because User B's ON window has started. This prevents User A from turning off equipment right before User B needs it.
Example 5: Check-in Based Precedence
Configuration:
- Turn on at check-in: Yes
- Allow manual on during reservation: Yes
- Allow manual off after end: 30 minutes
Reservations:
- User A: 1:00 PM - 2:00 PM
- User B: 2:00 PM - 3:00 PM
Scenario: User A finishes at 2:00 PM, User B arrives late at 2:15 PM
Manual Control Access:
Time | Event | User A OFF Access |
|---|---|---|
2:00 PM | User A's reservation ends | Yes (User B hasn't checked in) |
2:05 PM | User A still cleaning up | Yes (User B still hasn't checked in) |
2:15 PM | User B checks in | No (User B is now checked in) |
Key insight: When "Turn on at check-in" is enabled, User A keeps their OFF ability until User B actually checks in. This is useful when users may not arrive exactly at their reservation time.
Example 6: Require Approved Status
Configuration:
- Auto turn on before start: 10 minutes
- Require approved reservation status: Yes
Reservations:
- User A: Approved reservation 1:00 PM - 2:00 PM
- User B: Pending reservation 2:00 PM - 3:00 PM
Behavior:
- 12:50 PM: Outlet turns ON for User A
- 2:00 PM: User A's reservation ends, outlet turns OFF (User B's pending reservation is ignored)
- Once User B's reservation is approved: Automation will apply normally
Example 7: Locked Outlet
If an outlet is marked as "locked off", manual and automatic turn-on attempts are blocked:
- Automatic turn-on rules will not turn on the outlet
- Manual ON attempts by users will fail
- Synaccess administrators can still control the outlet
This is useful for maintenance periods or safety lockouts.
Example 8: IP Restrictions
Configuration:
- IP Restrictions: 192.168.1.0/24 (lab network)
- Allow manual on during reservation: Yes
- Allow manual off during reservation: Yes
Scenario:
- User A has a reservation from 1:00 PM - 2:00 PM
- User A tries to turn on the outlet from their office (IP: 10.0.0.50)
- Request is denied because 10.0.0.50 is not in the allowed range
Later:
- User A goes to the lab (IP: 192.168.1.25)
- User A tries to turn on the outlet
- Request succeeds because 192.168.1.25 is within 192.168.1.0/24
Note: A Synaccess administrator could control this outlet from any IP address.
Edge Cases
Same User with Multiple Reservations
If the same user has back-to-back reservations, they retain full manual control throughout. The precedence rules only apply between different users.
Example:
- User A: 1:00 PM - 2:00 PM
- User A: 2:00 PM - 3:00 PM (same user)
User A has continuous ON and OFF access from 12:50 PM through 3:30 PM (assuming 10-minute before and 30-minute after windows).
Overlapping Reservations (Different Resources, Same Outlet)
If an outlet is linked to multiple resources and has reservations on different resources at overlapping times, all reservations are considered for precedence.
Cancelled Reservations
Cancelled reservations are ignored for all automation and precedence calculations.
Late Arrivals with Turn on at Check-in
If "Turn on at check-in" is the only turn-on mechanism (no auto turn-on before start configured), the outlet will only turn on when the user actually checks in, regardless of the reservation start time.
Equipment Left Running
If a user forgets to turn off equipment and the turn_off_after_reservation window passes without another reservation, the outlet will be turned off automatically. However, if there's a subsequent reservation in the queue, the outlet may stay on to serve that reservation.
Permissions
Users can control outlets if they have:
- Synaccess administrator permission: Full control over all Synaccess outlets on the site (exempt from IP restrictions)
- Resource-specific Synaccess permission: Full control over outlets linked to specific resources (exempt from IP restrictions)
- A qualifying reservation: Manual control based on the configured windows (as described above), subject to IP restrictions if configured on the outlet
Automation Task
The system runs an automated task every minute that:
- Finds reservations entering their auto turn-on window and turns on the associated outlets
- Finds reservations that have ended and are within their auto turn-off window, checks precedence rules, and turns off outlets if safe
Troubleshooting
Outlet won't turn off automatically
Check if:
- Another reservation is in its turn-on window
- Someone is checked in with "Turn on at check-in" enabled
- The outlet is linked to multiple resources with overlapping reservations
User can't manually turn off outlet
Check if:
- Another user's reservation has started
- Another user's turn-on window has begun
- Another user is checked in (when "Turn on at check-in" is enabled)
Outlet won't turn on
Check if:
- The outlet is marked as "locked off"
- The Synaccess token is configured correctly
- The reservation status is approved (if "Require approved reservation status" is enabled)
- IP restrictions are configured and the user is not on an allowed network
User gets "permission denied" despite having a valid reservation
Check if:
- IP restrictions are configured on the outlet
- The user's IP address is within the allowed range
- Synaccess administrators bypass IP restrictions