Devices

Conduit brings connected devices into the same workspace as your properties, reservations, contacts, and operations. Your team can manage devices in the app, let Conduit agents act on them, trigger workflows from device events, or use the device tools through Conduit’s MCP server. Supported device types include:

• Smart locks and connected access systems
• Thermostats
• Noise and environmental sensors
• Motion and occupancy sensors
• Cameras and video doorbells

​

Supported Smart Locks

Conduit supports connected locks from the following brands: Available actions vary by model and setup. For example, some locks require a compatible bridge or keypad before they can be controlled remotely or accept access codes. If you use RemoteLock today, Conduit generally replaces it. Tell our team which physical lock models you have; in most cases, you can disconnect those locks from RemoteLock and reconnect them directly in Conduit, eliminating the separate RemoteLock subscription. Contact our team to plan the move. Have another device or access system in mind? Contact our team to explore it. We have additional device integrations available beyond this public list and can confirm the right setup for your model.

​

Commercial Access Control Systems

Conduit also supports commercial access control systems. Compatibility and available credentials depend on the exact controllers, readers, lock hardware, firmware, and licenses installed at your property. Contact our team with your exact hardware specifications so we can confirm the setup.

​

Access Grants

Access Grants provide time-bound access across one or more doors. They are not limited to access codes. Depending on your hardware, an Access Grant can also issue:

• Cloud keys for authenticated web or API-based unlocking
• Plastic key cards for hotel, office, and other card-based systems
• Mobile keys for Bluetooth-based access
• Instant Keys, shareable unlock links that work without requiring an app download

You can combine multiple credential types in the same Access Grant. For example, a guest can receive both an access code and a mobile key for the same stay. Instant Keys require compatible Bluetooth-capable hardware and the appropriate mobile-key licenses. Many commercial access systems are effectively offline at the door and require a Bluetooth credential to unlock. Instead of asking a guest to download and set up a full mobile app, you can send an Instant Key link. Opening the link launches an iOS App Clip or Android Instant App with the Bluetooth key, so the guest can unlock the door immediately.

​

What You Can Do

​

Manage The Device Fleet

• Sync devices from one or more connected accounts
• Search and filter by device type, property, and status
• Map a device to one or several properties, including shared building entrances
• Monitor online status, battery level, lock state, and current readings
• Review activity across the workspace or open a single device’s history
• See a fleet-wide health summary of offline and low-battery devices

​

Control Access

• Lock or remotely unlock a compatible door
• Create ongoing, time-bound, or one-time access codes
• Read a newly created code after the lock confirms it
• Find the active and past codes on a lock
• Revoke a code when a stay ends, a code is exposed, or a vendor’s access window closes
• Automatically generate a door code for each reservation and publish it to the guest portal

​

Manage Climate And Sensors

• Read temperature, humidity, noise, motion, and occupancy data reported by a device
• Read a thermostat’s current temperature, target temperature, and HVAC mode
• Set a thermostat to heat, cool, heat_cool (auto), or off, with a target between 10°C and 32°C
• Configure daily quiet hours and a decibel or Noise Risk Score threshold
• React to noise, temperature, humidity, smoke, motion, and other sensor events

​

Automate Operations

Device events can start workflows. Common examples include creating a security task after a noise threshold breach, notifying the team when a lock goes offline or reports a low battery, and checking device conditions before a guest arrives. Agents can also open a high-priority service-recovery task from a device incident and link the relevant device and property automatically.

​

Use Devices With Agents

Device tools are available to Conduit chat agents, voice agents, workflows, and Operator. Once Devices is enabled, Operator can use device tools. Enable them explicitly for each customer-facing agent that should have access. When an agent is helping a contact, Conduit limits device access to the contact’s active stay. Access-code reads are also restricted to that guest’s own codes, including when a building entrance is shared by several properties. Common agent jobs include:

• Checking whether a lock is online before troubleshooting a lockout
• Giving a guest their confirmed door code
• Creating temporary access for a guest, housekeeper, or inspector
• Locking a door after checkout
• Pre-heating or pre-cooling a property before arrival
• Checking a noise complaint against live sensor readings
• Summarizing offline devices and low batteries for the operations team

​

Device Tool Reference

The following device tools are available to agents and through the full Conduit MCP server. Write tools require a read/write token when called over MCP. Conduit agents also have the get-device-health-summary tool, which returns total devices, counts by type, offline and low-battery lists, and average indoor temperature in one call.

​

Connect Devices

1. Open Operations > Devices.
2. Select Add Devices if the add-on is not enabled yet.
3. Select Connect a device account and complete the authorization flow.
4. Wait for the authorized devices to sync into the list.
5. Map each device to the property or properties it serves.
6. Enable the required tools on each agent, then review device policies before allowing write actions.

To confirm a specific model, discuss a device category not shown here, or plan a larger rollout, contact support.