diff --git a/mintlify-docs/capability-guides/device-and-system-capabilities.mdx b/mintlify-docs/capability-guides/device-and-system-capabilities.mdx index 4f0c1d608..b682e9994 100644 --- a/mintlify-docs/capability-guides/device-and-system-capabilities.mdx +++ b/mintlify-docs/capability-guides/device-and-system-capabilities.mdx @@ -21,7 +21,7 @@ All capability flags share the following behavior: - If `true`, the device has this capability, and this capability is functional on this device instance. - If `false`, the device has this capability, but the capability is not currently functional. - See the device [errors](/core-concepts/devices) and [warnings](/core-concepts/devices) for more details about the cause of this issue. You can also examine the [properties](/core-concepts/devices) of the device and [events](/api/events/object) related to the device to learn more about the cause of this issue. + See the device [errors and warnings](/api/devices/errors) for more details about the cause of this issue. You can also examine the [properties](/api/devices/object) of the device and [events](/api/devices/events) related to the device to learn more about the cause of this issue. - If not present, the device does not have this capability. diff --git a/mintlify-docs/capability-guides/noise-sensors/configure-noise-threshold-settings.mdx b/mintlify-docs/capability-guides/noise-sensors/configure-noise-threshold-settings.mdx index c7ad6fe39..b16b9dbe7 100644 --- a/mintlify-docs/capability-guides/noise-sensors/configure-noise-threshold-settings.mdx +++ b/mintlify-docs/capability-guides/noise-sensors/configure-noise-threshold-settings.mdx @@ -165,4 +165,4 @@ Once you have configured your thresholds and webhooks, you can monitor events wi } ``` -For a detailed reference of event parameters, see [Events](/api/events/object). +For a detailed reference of event parameters, see [Events](/api/noise_sensors/noise_thresholds/events). diff --git a/mintlify-docs/capability-guides/thermostats/configure-current-climate-settings.mdx b/mintlify-docs/capability-guides/thermostats/configure-current-climate-settings.mdx index 07eafa4ab..d4d2e974b 100644 --- a/mintlify-docs/capability-guides/thermostats/configure-current-climate-settings.mdx +++ b/mintlify-docs/capability-guides/thermostats/configure-current-climate-settings.mdx @@ -24,7 +24,7 @@ Note that it's important to check the capabilities of a thermostat before attemp These imperative operations return an [action attempt](../../core-concepts/action-attempts) that enables you to track the progress of the action. Poll this action attempt, until the action completes. -Further, Seam emits a [`thermostat.temperature_reached_set_point` event](/api/events/object) when the thermostat reports a temperature within 1° Celsius of the heating or cooling temperature that you requested. +Further, Seam emits a [`thermostat.temperature_reached_set_point` event](/api/thermostats/events#thermostat-temperature_reached_set_point) when the thermostat reports a temperature within 1° Celsius of the heating or cooling temperature that you requested. --- @@ -118,7 +118,7 @@ Before you attempt to set the HVAC or fan mode settings for a thermostat, be sur Use the [`/devices/get`](/api/devices/get) endpoint for a specific device to return these capability flags. Then, use an `if` statement or similar check to confirm that the relevant flag is both present and `true` before attempting to perform the imperative thermostat action. -If the relevant capability flag is `false` or not present, you can view the [properties](/capability-guides/thermostats) of the device, [errors](/core-concepts/devices) or [warnings](/core-concepts/devices) for the device, and [events](/api/events/object) related to the device to learn more about the cause of these issues. For example, you could examine `device.properties.online`. In addition, you could look for a `device.disconnected` event. +If the relevant capability flag is `false` or not present, you can view the [properties](/api/devices/object) of the device, [errors or warnings](/api/devices/errors) for the device, and [events](/api/devices/events) related to the device to learn more about the cause of these issues. For example, you could examine `device.properties.online`. In addition, you could look for a `device.disconnected` event. **Request:** diff --git a/mintlify-docs/capability-guides/thermostats/creating-and-managing-climate-presets/activating-a-climate-preset.mdx b/mintlify-docs/capability-guides/thermostats/creating-and-managing-climate-presets/activating-a-climate-preset.mdx index fdf0e3321..58f6426fb 100644 --- a/mintlify-docs/capability-guides/thermostats/creating-and-managing-climate-presets/activating-a-climate-preset.mdx +++ b/mintlify-docs/capability-guides/thermostats/creating-and-managing-climate-presets/activating-a-climate-preset.mdx @@ -7,7 +7,7 @@ In addition to [scheduling](../creating-and-managing-thermostat-schedules) clima Activating a climate preset returns an [action attempt](../../../core-concepts/action-attempts) that enables you to track the progress of the action. Poll this action attempt, until the action completes. -Further, Seam emits a [`thermostat.temperature_reached_set_point` event](/api/events/object) when the thermostat reports a temperature within 1° Celsius of the heating or cooling [set point](../understanding-thermostat-concepts/set-points) specified in the climate preset that you've activated. You can configure a [webhook](../../../developer-tools/webhooks) to watch for this event. +Further, Seam emits a [`thermostat.temperature_reached_set_point` event](/api/thermostats/events#thermostat-temperature_reached_set_point) when the thermostat reports a temperature within 1° Celsius of the heating or cooling [set point](../understanding-thermostat-concepts/set-points) specified in the climate preset that you've activated. You can configure a [webhook](../../../developer-tools/webhooks) to watch for this event. --- diff --git a/mintlify-docs/capability-guides/thermostats/creating-and-managing-thermostat-schedules.mdx b/mintlify-docs/capability-guides/thermostats/creating-and-managing-thermostat-schedules.mdx index 32b97d312..bf8fd7a8e 100644 --- a/mintlify-docs/capability-guides/thermostats/creating-and-managing-thermostat-schedules.mdx +++ b/mintlify-docs/capability-guides/thermostats/creating-and-managing-thermostat-schedules.mdx @@ -102,7 +102,7 @@ In the Seam API, use the `starts_at` and `ends_at` parameters to define the time `starts_at` is required and must be unique within all the schedules for the thermostat. However, if you want to schedule a climate preset that starts immediately, set `start_at` to a time in the past. Alternately, you can [activate a climate preset](/capability-guides/thermostats/creating-and-managing-climate-presets/activating-a-climate-preset) immediately. -After a scheduled climate preset starts, Seam emits a [`thermostat.temperature_reached_set_point` event](/api/events/object) when the thermostat reports a temperature within 1° Celsius of the heating or cooling [set point](/capability-guides/thermostats/understanding-thermostat-concepts/set-points) specified in this climate preset. You can configure a [webhook](../../developer-tools/webhooks) to watch for this event. +After a scheduled climate preset starts, Seam emits a [`thermostat.temperature_reached_set_point` event](/api/thermostats/events#thermostat-temperature_reached_set_point) when the thermostat reports a temperature within 1° Celsius of the heating or cooling set point specified in this climate preset. You can configure a webhook to watch for this event. --- diff --git a/mintlify-docs/capability-guides/thermostats/index.mdx b/mintlify-docs/capability-guides/thermostats/index.mdx index 0a1cec085..e43cbe2af 100644 --- a/mintlify-docs/capability-guides/thermostats/index.mdx +++ b/mintlify-docs/capability-guides/thermostats/index.mdx @@ -36,7 +36,7 @@ First, connect your users' thermostats to Seam using the [Seam Console](/core-co Retrieve and monitor your users' thermostats using the [`/thermostats/list`](/api/thermostats/list) and [`/devices/get`](/api/devices/get) endpoints. The Seam API returns robust, up-to-date information about your connected thermostats. In addition, you can use these endpoints to learn the capabilities of each thermostat. -Further, you can use the [`/thermostats/set_temperature_threshold`](/api/thermostats/set_temperature_threshold) endpoint to set upper and lower acceptable temperature bounds. If the thermostat reports a temperature outside this range, Seam emits a [`thermostat.temperature_threshold_exceeded` event](/api/events/object). +Further, you can use the [`/thermostats/set_temperature_threshold`](/api/thermostats/set_temperature_threshold) endpoint to set upper and lower acceptable temperature bounds. If the thermostat reports a temperature outside this range, Seam emits a [`thermostat.temperature_threshold_exceeded` event](/api/thermostats/events#thermostat-temperature_threshold_exceeded). ### Perform Remote Management diff --git a/mintlify-docs/capability-guides/thermostats/setting-and-monitoring-temperature-thresholds.mdx b/mintlify-docs/capability-guides/thermostats/setting-and-monitoring-temperature-thresholds.mdx index ed9de8712..14f8e11c3 100644 --- a/mintlify-docs/capability-guides/thermostats/setting-and-monitoring-temperature-thresholds.mdx +++ b/mintlify-docs/capability-guides/thermostats/setting-and-monitoring-temperature-thresholds.mdx @@ -3,7 +3,7 @@ title: 'Setting and Monitoring Temperature Thresholds' description: 'Learn how to use temperature thresholds to monitor your thermostat for potential HVAC system misuse or malfunctioning.' --- -You can configure Seam to emit a [`thermostat.temperature_threshold_exceeded` event](/api/events/object) if a thermostat reports a temperature outside a specific threshold range. This capability helps you to monitor your thermostats proactively, alerting you to potential HVAC system misuse or malfunctioning. +You can configure Seam to emit a [`thermostat.temperature_threshold_exceeded` event](/api/thermostats/events#thermostat-temperature_threshold_exceeded) if a thermostat reports a temperature outside a specific threshold range. This capability helps you to monitor your thermostats proactively, alerting you to potential HVAC system misuse or malfunctioning. Use the [`/thermostats/set_temperature_threshold`](/api/thermostats/set_temperature_threshold) endpoint to set upper and lower acceptable temperature bounds. Then, you can use a [webhook](../../developer-tools/webhooks) to monitor for `thermostat.temperature_threshold_exceeded` events. diff --git a/mintlify-docs/capability-guides/thermostats/testing-your-thermostat-app-with-simulate-endpoints.mdx b/mintlify-docs/capability-guides/thermostats/testing-your-thermostat-app-with-simulate-endpoints.mdx index 89765c539..46a2f1f25 100644 --- a/mintlify-docs/capability-guides/thermostats/testing-your-thermostat-app-with-simulate-endpoints.mdx +++ b/mintlify-docs/capability-guides/thermostats/testing-your-thermostat-app-with-simulate-endpoints.mdx @@ -35,7 +35,7 @@ For more information, see [Thermostat Capabilities](/capability-guides/thermosta ## Simulate Adjusting the HVAC Mode -The `/thermostats/simulate/hvac_mode_adjusted` endpoint enables you to simulate having adjusted the [HVAC mode](./understanding-thermostat-concepts/hvac-mode) for a thermostat. This simulation is helpful for testing that your app is receiving [thermostat events](/api/events/object) correctly, such as `thermostat.manually_adjusted`. +The `/thermostats/simulate/hvac_mode_adjusted` endpoint enables you to simulate having adjusted the [HVAC mode](./understanding-thermostat-concepts/hvac-mode) for a thermostat. This simulation is helpful for testing that your app is receiving [thermostat events](/api/thermostats/events) correctly, such as `thermostat.manually_adjusted`. You can simulate having set the HVAC mode to any of the following settings: @@ -210,7 +210,7 @@ void ## Simulate Reaching a Desired Temperature -The `/thermostats/simulate/temperature_reached` endpoint enables you to simulate the thermostat reaching a specified temperature. This simulation is helpful for testing that your app is receiving [thermostat events](/api/events/object) correctly, such as `thermostat.temperature_changed` and `thermostat.temperature_reached_set_point`. +The `/thermostats/simulate/temperature_reached` endpoint enables you to simulate the thermostat reaching a specified temperature. This simulation is helpful for testing that your app is receiving [thermostat events](/api/thermostats/events) correctly, such as `thermostat.temperature_changed` and `thermostat.temperature_reached_set_point`. Specify the desired temperature that you want to simulate the thermostat reaching using either of the following parameters: diff --git a/mintlify-docs/core-concepts/connect-webviews/retrieving-devices-or-access-control-systems-connected-through-a-connect-webview.mdx b/mintlify-docs/core-concepts/connect-webviews/retrieving-devices-or-access-control-systems-connected-through-a-connect-webview.mdx index 8773873e7..5464378e2 100644 --- a/mintlify-docs/core-concepts/connect-webviews/retrieving-devices-or-access-control-systems-connected-through-a-connect-webview.mdx +++ b/mintlify-docs/core-concepts/connect-webviews/retrieving-devices-or-access-control-systems-connected-through-a-connect-webview.mdx @@ -3,7 +3,7 @@ title: 'Retrieving Devices or Access Control Systems Connected Through a Connect description: 'Learn how to retrieve the set of devices or ACS that your app user connected to Seam through a specific Connect Webview.' --- -When your app user completes a [Connect Webview](./) authorization flow successfully, the resulting [`connected_account.connected` event](/api/events/object) includes a `connected_account_id`. Also, once the connection is successful, the [`connect_webview` object](/api/connect_webviews/object) includes the `connected_account_id`. +When your app user completes a [Connect Webview](./) authorization flow successfully, the resulting [`connected_account.connected` event](/api/connected_accounts/events#connected_account-connected) includes a `connected_account_id`. Also, once the connection is successful, the [`connect_webview` object](/api/connect_webviews/object) includes the `connected_account_id`. The first step in controlling connected devices or a connected ACS is to retrieve the newly-connected set of devices or ACS. @@ -17,7 +17,7 @@ Use this `connected_account_id` in a [List Devices](/api/devices/list) command t If you set `wait_for_device_creation` to `false` when [creating the Connect Webview](/core-concepts/connect-webviews/embedding-a-connect-webview-in-your-app#step-1-open-a-connect-webview), you should wait for the [`connected_account.completed_first_sync` - event](/api/events/object) before retrieving the user's + event](/api/connected_accounts/events#connected_account-completed_first_sync) before retrieving the user's devices. This event indicates that Seam has finished the first sync of the connected account and the devices are now available. @@ -173,7 +173,7 @@ Use this `connected_account_id` in a [List ACS Systems](/api/acs/systems/list) c If you set `wait_for_device_creation` to `false` when [creating the Connect Webview](/core-concepts/connect-webviews/embedding-a-connect-webview-in-your-app#step-1-open-a-connect-webview), you should wait for the [`connected_account.completed_first_sync` - event](/api/events/object) before retrieving the user's + event](/api/connected_accounts/events#connected_account-completed_first_sync) before retrieving the user's ACS. This event indicates that Seam has finished the first sync of the connected account and the `acs_system` is now available. diff --git a/mintlify-docs/core-concepts/connect-webviews/verifying-successful-account-connection.mdx b/mintlify-docs/core-concepts/connect-webviews/verifying-successful-account-connection.mdx index 9d0ad9fc1..d104d9e10 100644 --- a/mintlify-docs/core-concepts/connect-webviews/verifying-successful-account-connection.mdx +++ b/mintlify-docs/core-concepts/connect-webviews/verifying-successful-account-connection.mdx @@ -145,7 +145,7 @@ ConnectWebview( ## **Webhook** -When Seam successfully establishes the connection to the user's device or ACS account, Seam emits a [`connected_account.connected` event](/api/events/object). This event includes a `connect_webview_id` property. +When Seam successfully establishes the connection to the user's device or ACS account, Seam emits a [`connected_account.connected` event](/api/connected_accounts/events#connected_account-connected). This event includes a `connect_webview_id` property. To avoid polling, use a Seam webhook to monitor for a `connected_account.connected` event with a `connect_webview_id` that matches the `connect_webview_id` of the appropriate Connect Webview instance. diff --git a/mintlify-docs/core-concepts/devices/displaying-device-health.mdx b/mintlify-docs/core-concepts/devices/displaying-device-health.mdx index 7e901e4c5..114478077 100644 --- a/mintlify-docs/core-concepts/devices/displaying-device-health.mdx +++ b/mintlify-docs/core-concepts/devices/displaying-device-health.mdx @@ -101,7 +101,7 @@ Online: True ## Get Device Status Using Connection-Related Events -When a device connection or disconnection occurs, Seam generates a [`device.connected`](/api/events/object) or [`device.disconnected`](/api/events/object) event, respectively. You can retrieve these events using a [List Events](/api/events/list) request or through [webhooks](../../developer-tools/webhooks) and then display the corresponding status in your app. +When a device connection or disconnection occurs, Seam generates a [`device.connected`](/api/devices/events#device-connected) or [`device.disconnected`](/api/devices/events#device-disconnected) event, respectively. You can retrieve these events using a [List Events](/api/events/list) request or through [webhooks](../../developer-tools/webhooks) and then display the corresponding status in your app. To help you test your app against events—like device disconnection or @@ -114,7 +114,7 @@ When a device connection or disconnection occurs, Seam generates a [`device.conn ### Get Connection-Related Events Using a List Events Request -When issuing a [List Events](/api/events/list) request to retrieve [`device.connected`](/api/events/object) or [`device.disconnected`](/api/events/object) events for a specific device, include the following parameters: +When issuing a [List Events](/api/events/list) request to retrieve [`device.connected`](/api/devices/events#device-connected) or [`device.disconnected`](/api/devices/events#device-disconnected) events for a specific device, include the following parameters: diff --git a/mintlify-docs/core-concepts/devices/displaying-device-power-status.mdx b/mintlify-docs/core-concepts/devices/displaying-device-power-status.mdx index 909d73f8f..5917d58e4 100644 --- a/mintlify-docs/core-concepts/devices/displaying-device-power-status.mdx +++ b/mintlify-docs/core-concepts/devices/displaying-device-power-status.mdx @@ -235,7 +235,7 @@ You can retrieve these events using a [List Events](/api/events/list) request or ### Get Battery-Related Events Using a List Events Request -When issuing a [List Events](/api/events/list) request to retrieve [`device.low_battery`](/api/events/object) or [`device.battery_status_changed`](/api/events/object) events for a specific device, include the following parameters: +When issuing a [List Events](/api/events/list) request to retrieve [`device.low_battery`](/api/devices/events#device-low_battery) or [`device.battery_status_changed`](/api/devices/events#device-battery_status_changed) events for a specific device, include the following parameters:
diff --git a/mintlify-docs/core-concepts/devices/index.mdx b/mintlify-docs/core-concepts/devices/index.mdx index 4c58541e3..4df0501ea 100644 --- a/mintlify-docs/core-concepts/devices/index.mdx +++ b/mintlify-docs/core-concepts/devices/index.mdx @@ -16,5 +16,5 @@ In addition, Seam provides the following three sets of device-related features: - **Actions:** Commands that you can issue to the device, such as unlock. For more information, see the [Capability Guides](../../capability-guides/device-and-system-capabilities). - **Properties:** The current state of the device, such as the locked, online, and managed statuses. For details, see [`device` Properties](/core-concepts/devices). -- **Events:** Notifications related to changes in the state of the device, such as an unlocking operation performed with an access code. For details, see [Events](/api/events/object).\ +- **Events:** Notifications related to changes in the state of the device, such as an unlocking operation performed with an access code. For details, see [Events](/api/devices/events).\ To help you test your app against events—like device disconnection or removal—that are difficult to orchestrate in a QA environment using real devices, Seam provides a suite of `simulate` endpoints that you can use in a [sandbox workspace](/core-concepts/workspaces/index#sandbox-workspaces). See [Testing Your App Against Device Disconnection and Removal](/core-concepts/devices/testing-your-app-against-device-disconnection-and-removal). diff --git a/mintlify-docs/device-and-system-integration-guides/33-lock-devices/get-started-with-33-lock-devices.mdx b/mintlify-docs/device-and-system-integration-guides/33-lock-devices/get-started-with-33-lock-devices.mdx index eab3a29f4..52719dc00 100644 --- a/mintlify-docs/device-and-system-integration-guides/33-lock-devices/get-started-with-33-lock-devices.mdx +++ b/mintlify-docs/device-and-system-integration-guides/33-lock-devices/get-started-with-33-lock-devices.mdx @@ -783,7 +783,7 @@ ActionAttempt( -You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/events/object). +You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/locks/events#lock-unlocked). To query the `locked` status of the device: diff --git a/mintlify-docs/device-and-system-integration-guides/4suites-locks/get-started-with-4suites-locks.mdx b/mintlify-docs/device-and-system-integration-guides/4suites-locks/get-started-with-4suites-locks.mdx index 0deb981e5..b2d774dca 100644 --- a/mintlify-docs/device-and-system-integration-guides/4suites-locks/get-started-with-4suites-locks.mdx +++ b/mintlify-docs/device-and-system-integration-guides/4suites-locks/get-started-with-4suites-locks.mdx @@ -766,7 +766,7 @@ ActionAttempt( -You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/events/object). +You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/locks/events#lock-unlocked). To query the `locked` status of the device: diff --git a/mintlify-docs/device-and-system-integration-guides/4suites-locks/index.mdx b/mintlify-docs/device-and-system-integration-guides/4suites-locks/index.mdx index 72c2921fc..091fef832 100644 --- a/mintlify-docs/device-and-system-integration-guides/4suites-locks/index.mdx +++ b/mintlify-docs/device-and-system-integration-guides/4suites-locks/index.mdx @@ -56,7 +56,7 @@ To create a [Connect Webview](/core-concepts/connect-webviews) that enables your To control 4SUITES devices using Seam, you must prompt owners of these devices to perform the following steps: 1. Obtain the credentials that you use to log in to your [4SUITES account](https://app.4suites.nl/auth/login). -2. Use these credentials to log in to the [Seam Connect Webview](/core-concepts/connect-webviews) to add your 4SUITES devices to Seam. +2. Use these credentials to log in to the Seam Connect Webview to add your 4SUITES devices to Seam. --- diff --git a/mintlify-docs/device-and-system-integration-guides/akiles-locks/get-started-with-akiles-locks.mdx b/mintlify-docs/device-and-system-integration-guides/akiles-locks/get-started-with-akiles-locks.mdx index e53f4ffb1..d0b2a3dd3 100644 --- a/mintlify-docs/device-and-system-integration-guides/akiles-locks/get-started-with-akiles-locks.mdx +++ b/mintlify-docs/device-and-system-integration-guides/akiles-locks/get-started-with-akiles-locks.mdx @@ -766,7 +766,7 @@ ActionAttempt( -You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/events/object). +You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/locks/events#lock-unlocked). To query the `locked` status of the device: diff --git a/mintlify-docs/device-and-system-integration-guides/august-locks/get-started-with-august-locks.mdx b/mintlify-docs/device-and-system-integration-guides/august-locks/get-started-with-august-locks.mdx index 8c864ce87..eda9187a0 100644 --- a/mintlify-docs/device-and-system-integration-guides/august-locks/get-started-with-august-locks.mdx +++ b/mintlify-docs/device-and-system-integration-guides/august-locks/get-started-with-august-locks.mdx @@ -798,7 +798,7 @@ ActionAttempt( -You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/events/object). +You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/locks/events#lock-unlocked). To query the `locked` status of the device: diff --git a/mintlify-docs/device-and-system-integration-guides/ecobee-thermostats/get-started-with-ecobee-thermostats.mdx b/mintlify-docs/device-and-system-integration-guides/ecobee-thermostats/get-started-with-ecobee-thermostats.mdx index f0bd3a37e..c356345e4 100644 --- a/mintlify-docs/device-and-system-integration-guides/ecobee-thermostats/get-started-with-ecobee-thermostats.mdx +++ b/mintlify-docs/device-and-system-integration-guides/ecobee-thermostats/get-started-with-ecobee-thermostats.mdx @@ -840,7 +840,7 @@ ActionAttempt( -You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/events/object). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. +You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/thermostats/events#thermostat-manually_adjusted). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. To query `properties.current_climate_setting.hvac_mode_setting` for the device: diff --git a/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/get-started-with-nest-thermostats.mdx b/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/get-started-with-nest-thermostats.mdx index 21d6cedea..d712500d8 100644 --- a/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/get-started-with-nest-thermostats.mdx +++ b/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/get-started-with-nest-thermostats.mdx @@ -833,7 +833,7 @@ ActionAttempt( -You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/events/object). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. +You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/thermostats/events#thermostat-manually_adjusted). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. To query `properties.current_climate_setting.hvac_mode_setting` for the device: diff --git a/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/index.mdx b/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/index.mdx index dc6b59f37..b2df980b6 100644 --- a/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/index.mdx +++ b/mintlify-docs/device-and-system-integration-guides/google-nest-thermostats/index.mdx @@ -68,7 +68,7 @@ Google Nest thermostats support an eco HVAC mode. To set a Google Nest thermosta ## Troubleshooting -If you have not yet [obtained Google Commercial Development](/device-and-system-integration-guides/google-nest-thermostats/obtain-google-nest-device-access-and-commercial-development), and your end user attempts to connect a Google Nest thermostat to Seam using a [Connect Webview](/core-concepts/connect-webviews), the Connect Webview displays the following error: +If you have not yet [obtained Google Commercial Development](/device-and-system-integration-guides/google-nest-thermostats/obtain-google-nest-device-access-and-commercial-development), and your end user attempts to connect a Google Nest thermostat to Seam using a Connect Webview, the Connect Webview displays the following error: > No access to partner > diff --git a/mintlify-docs/device-and-system-integration-guides/honeywell-thermostats/get-started-with-honeywell-thermostats.mdx b/mintlify-docs/device-and-system-integration-guides/honeywell-thermostats/get-started-with-honeywell-thermostats.mdx index 328b2a128..ba7f169c0 100644 --- a/mintlify-docs/device-and-system-integration-guides/honeywell-thermostats/get-started-with-honeywell-thermostats.mdx +++ b/mintlify-docs/device-and-system-integration-guides/honeywell-thermostats/get-started-with-honeywell-thermostats.mdx @@ -831,7 +831,7 @@ ActionAttempt( -You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/events/object). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. +You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/thermostats/events#thermostat-manually_adjusted). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. To query `properties.current_climate_setting.hvac_mode_setting` for the device: diff --git a/mintlify-docs/device-and-system-integration-guides/igloohome-locks/index.mdx b/mintlify-docs/device-and-system-integration-guides/igloohome-locks/index.mdx index c6fcf778a..afbfbb270 100644 --- a/mintlify-docs/device-and-system-integration-guides/igloohome-locks/index.mdx +++ b/mintlify-docs/device-and-system-integration-guides/igloohome-locks/index.mdx @@ -80,11 +80,11 @@ Seam supports the following events and event property values for igloohome devic ### igloohome Auto-Relock -igloohome devices have an auto-relock feature that automatically locks the device after a configurable period of time, for example, 30 seconds. The Seam API reports these auto-relock occurrences by emitting a [`lock.locked` event](/api/events/object) with `automatic` as the value for the `method` property. +igloohome devices have an auto-relock feature that automatically locks the device after a configurable period of time, for example, 30 seconds. The Seam API reports these auto-relock occurrences by emitting a [`lock.locked` event](/api/locks/events#lock-locked) with `automatic` as the value for the `method` property. ### igloohome Access Denied Event -Each time an igloohome device detects an invalid attempt of entry, Seam emits a [`lock.access_denied` event](/api/events/object). Invalid entry attempts include entering the wrong PIN, exceeding the PIN length, and using an invalid key card. The igloohome lock also flashes red to indicate an invalid attempt. If too many invalid attempts occur, igloohome locks produce a Keypad Security Lockout alarm, accompanied by light and sound indicators. For more information, see the igloohome support articles on [keypad security](https://support.igloohome.co/support/solutions/articles/35000169627-keypad-security-lockout-activated-and-deactivated) and [incorrect PINs](https://support.igloohome.co/support/solutions/articles/35000169625-incorrect-pin). +Each time an igloohome device detects an invalid attempt of entry, Seam emits a [`lock.access_denied` event](/api/locks/events#lock-access_denied). Invalid entry attempts include entering the wrong PIN, exceeding the PIN length, and using an invalid key card. The igloohome lock also flashes red to indicate an invalid attempt. If too many invalid attempts occur, igloohome locks produce a Keypad Security Lockout alarm, accompanied by light and sound indicators. For more information, see the igloohome support articles on [keypad security](https://support.igloohome.co/support/solutions/articles/35000169627-keypad-security-lockout-activated-and-deactivated) and [incorrect PINs](https://support.igloohome.co/support/solutions/articles/35000169625-incorrect-pin). --- diff --git a/mintlify-docs/device-and-system-integration-guides/kwikset-locks/index.mdx b/mintlify-docs/device-and-system-integration-guides/kwikset-locks/index.mdx index 5b7b4999a..356a09b71 100644 --- a/mintlify-docs/device-and-system-integration-guides/kwikset-locks/index.mdx +++ b/mintlify-docs/device-and-system-integration-guides/kwikset-locks/index.mdx @@ -89,11 +89,11 @@ Seam supports the following events and event property values for Kwikset devices ### Kwikset Auto-Lock -Kwikset devices have an auto-lock feature that automatically locks the device after a configurable period of time, for example, 30 seconds. The Seam API reports these auto-lock occurrences by emitting a [`lock.locked` event](/api/events/object) with `automatic` as the value for the `method` property. +Kwikset devices have an auto-lock feature that automatically locks the device after a configurable period of time, for example, 30 seconds. The Seam API reports these auto-lock occurrences by emitting a [`lock.locked` event](/api/locks/events#lock-locked) with `automatic` as the value for the `method` property. ### Kwikset Access Denied Event -The Seam API emits a [`lock.access_denied` event](/api/events/object) when an incorrect access code is entered three times in a row on a Kwikset device. The Kwikset device also emits warning beeps for approximately 15 seconds, and the keypad is locked during this time. The keypad remains locked for one minute after the warning beeps end. +The Seam API emits a [`lock.access_denied` event](/api/locks/events#lock-access_denied) when an incorrect access code is entered three times in a row on a Kwikset device. The Kwikset device also emits warning beeps for approximately 15 seconds, and the keypad is locked during this time. The keypad remains locked for one minute after the warning beeps end. --- diff --git a/mintlify-docs/device-and-system-integration-guides/minut-sensors/get-started-with-minut-sensors.mdx b/mintlify-docs/device-and-system-integration-guides/minut-sensors/get-started-with-minut-sensors.mdx index 5e3ee6c6d..1f027457d 100644 --- a/mintlify-docs/device-and-system-integration-guides/minut-sensors/get-started-with-minut-sensors.mdx +++ b/mintlify-docs/device-and-system-integration-guides/minut-sensors/get-started-with-minut-sensors.mdx @@ -142,7 +142,7 @@ Navigate to the URL returned by the Webview object. Since you are using a sandbo ### Get the New Webview -After you complete the login above, you'll get an event for [`connected_account.created`](/api/events/object)if you set up a [webhook handler](/developer-tools/webhooks). Otherwise you can just poll for the webview until it's status changes, as shown below: +After you complete the login above, you'll get an event for [`connected_account.created`](/api/connected_accounts/events#connected_account-created)if you set up a [webhook handler](/developer-tools/webhooks). Otherwise you can just poll for the webview until it's status changes, as shown below: @@ -558,7 +558,7 @@ echo json_encode($device[0]); Minut users can define noise thresholds at which noise alerts are sent. -You'll get an event for `noise_threshold.noise_threshold_triggered` when you set up a [webhook handler](/developer-tools/webhooks). You can also [poll for events](/api/events/list). +You'll get an event for `noise_threshold.noise_threshold_triggered` when you set up a webhook handler. You can also [poll for events](/api/events/list). Minut has a builtin threshold that can be triggered multiple times. Each Minut notice will trigger a `noise_threshold_triggered` event with the `minut_metadata.event_name` containing the Minut event name, which can be any of the following: diff --git a/mintlify-docs/device-and-system-integration-guides/minut-sensors/index.mdx b/mintlify-docs/device-and-system-integration-guides/minut-sensors/index.mdx index 2e560eaed..51d3ede7e 100644 --- a/mintlify-docs/device-and-system-integration-guides/minut-sensors/index.mdx +++ b/mintlify-docs/device-and-system-integration-guides/minut-sensors/index.mdx @@ -42,8 +42,8 @@ We support the following features: - [Configuring noise threshold settings](/capability-guides/noise-sensors/configure-noise-threshold-settings)\ You can configure a maximum of two noise thresholds per Minut sensor. The first threshold is required and represents the regular threshold for the whole day. The second threshold is optional and represents the threshold for the quiet hours timeframe. -- [Receiving noise sensor events when noise events occur](/api/events/object)\ - For more information, see the [`noise_sensor.noise_threshold_triggered` event](/api/events/object). +- [Receiving noise sensor events when noise events occur](/api/noise_sensors/noise_thresholds/events)\ + For more information, see the [`noise_sensor.noise_threshold_triggered` event](/api/noise_sensors/noise_thresholds/events#noise_sensor-noise_threshold_triggered). --- diff --git a/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/get-started-with-noiseaware-sensors.mdx b/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/get-started-with-noiseaware-sensors.mdx index 7fa20cbf3..2027f40bf 100644 --- a/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/get-started-with-noiseaware-sensors.mdx +++ b/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/get-started-with-noiseaware-sensors.mdx @@ -152,7 +152,7 @@ Navigate to the URL returned by the Webview object. Since you are using a sandbo ### Get the New Webview -After you complete the login above, you'll get an event for [`connected_account.created`](/api/events/object)if you set up a [webhook handler](/developer-tools/webhooks). Otherwise you can just poll for the webview until it's status changes, as shown below: +After you complete the login above, you'll get an event for [`connected_account.created`](/api/connected_accounts/events#connected_account-created)if you set up a [webhook handler](/developer-tools/webhooks). Otherwise you can just poll for the webview until it's status changes, as shown below: @@ -342,7 +342,7 @@ echo json_encode($device[0]); NoiseAware users can define noise thresholds at which noise alerts are sent. -You'll get an event for `noise_threshold.noise_threshold_triggered` when you set up a [webhook handler](/developer-tools/webhooks). You can also [poll for events](/api/events/list). +You'll get an event for `noise_threshold.noise_threshold_triggered` when you set up a webhook handler. You can also [poll for events](/api/events/list). NoiseAware has three distinct noise alerts: `newNoise`, `continuedNoise`, and diff --git a/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/index.mdx b/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/index.mdx index 4f96eda84..522c85014 100644 --- a/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/index.mdx +++ b/mintlify-docs/device-and-system-integration-guides/noiseaware-sensors/index.mdx @@ -42,8 +42,8 @@ We support the following features: - [Configuring noise threshold settings](/capability-guides/noise-sensors/configure-noise-threshold-settings)\ You can configure a maximum of one noise threshold per hour per Noiseaware sensor. You cannot configure thresholds with time periods that overlap. -- [Receiving noise sensor events when noise events occur](/api/events/object)\ - For more information, see the [`noise_sensor.noise_threshold_triggered` event](/api/events/object). +- [Receiving noise sensor events when noise events occur](/api/noise_sensors/noise_thresholds/events)\ + For more information, see the [`noise_sensor.noise_threshold_triggered` event](/api/noise_sensors/noise_thresholds/events#noise_sensor-noise_threshold_triggered). --- diff --git a/mintlify-docs/device-and-system-integration-guides/schlage-locks/schlage-locks-setup-instructions.mdx b/mintlify-docs/device-and-system-integration-guides/schlage-locks/schlage-locks-setup-instructions.mdx index 96a109678..caca81b85 100644 --- a/mintlify-docs/device-and-system-integration-guides/schlage-locks/schlage-locks-setup-instructions.mdx +++ b/mintlify-docs/device-and-system-integration-guides/schlage-locks/schlage-locks-setup-instructions.mdx @@ -26,5 +26,5 @@ To control Schlage Connect or Connected Keypad locks with Z-Wave technology usin 2. Connect your lock to a Z-Wave hub.\ Before connecting your Schlage locks to the internet, you must first connect them to a Z-Wave hub. Follow the hub's setup process to link your locks to it. 3. Note your login credentials for SmartThings, that is, the hub to which you have connected your lock. -4. In the [Seam Connect Webview](/core-concepts/connect-webviews), select SmartThings. +4. In the Seam Connect Webview, select SmartThings. 5. In the Connect Webview, type the appropriate SmartThings credentials to add your devices to Seam. diff --git a/mintlify-docs/device-and-system-integration-guides/sensi-thermostats/get-started-with-sensi-thermostats.mdx b/mintlify-docs/device-and-system-integration-guides/sensi-thermostats/get-started-with-sensi-thermostats.mdx index a1349e89c..4797d1115 100644 --- a/mintlify-docs/device-and-system-integration-guides/sensi-thermostats/get-started-with-sensi-thermostats.mdx +++ b/mintlify-docs/device-and-system-integration-guides/sensi-thermostats/get-started-with-sensi-thermostats.mdx @@ -823,7 +823,7 @@ ActionAttempt( -You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/events/object). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. +You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/thermostats/events#thermostat-manually_adjusted). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. To query `properties.current_climate_setting.hvac_mode_setting` for the device: diff --git a/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-smart-locks.mdx b/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-smart-locks.mdx index 4d84abec1..0f1530c96 100644 --- a/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-smart-locks.mdx +++ b/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-smart-locks.mdx @@ -788,7 +788,7 @@ ActionAttempt( -You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/events/object). +You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/locks/events#lock-unlocked). To query the `locked` status of the device: diff --git a/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-thermostats.mdx b/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-thermostats.mdx index 424295d05..17e79c8b1 100644 --- a/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-thermostats.mdx +++ b/mintlify-docs/device-and-system-integration-guides/smartthings-hubs-+-devices/get-started-with-smartthings-hubs-+-thermostats.mdx @@ -834,7 +834,7 @@ ActionAttempt( -You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/events/object). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. +You can track the status of the operation to confirm that the device was set to heat mode successfully. Query `properties.current_climate_setting.hvac_mode_setting` for the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`thermostat.manually_adjusted` event](/api/thermostats/events#thermostat-manually_adjusted). Further, if you wanted to find out whether the HVAC system was currently heating, you could inspect `properties.is_heating` for the device. To query `properties.current_climate_setting.hvac_mode_setting` for the device: diff --git a/mintlify-docs/device-and-system-integration-guides/ttlock-locks/get-started-with-ttlock-devices.mdx b/mintlify-docs/device-and-system-integration-guides/ttlock-locks/get-started-with-ttlock-devices.mdx index 38737fabe..7c4d8a916 100644 --- a/mintlify-docs/device-and-system-integration-guides/ttlock-locks/get-started-with-ttlock-devices.mdx +++ b/mintlify-docs/device-and-system-integration-guides/ttlock-locks/get-started-with-ttlock-devices.mdx @@ -790,7 +790,7 @@ ActionAttempt( -You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/events/object). +You can track the status of the unlock operation to confirm that the device unlocked successfully. Query the `locked` status of the device, [retrieve the action attempt](/api/action_attempts/get) by ID, or look for a [`lock.unlocked` event](/api/locks/events#lock-unlocked). To query the `locked` status of the device: diff --git a/mintlify-docs/device-and-system-integration-guides/ttlock-locks/index.mdx b/mintlify-docs/device-and-system-integration-guides/ttlock-locks/index.mdx index 4928de42e..b9cc4be78 100644 --- a/mintlify-docs/device-and-system-integration-guides/ttlock-locks/index.mdx +++ b/mintlify-docs/device-and-system-integration-guides/ttlock-locks/index.mdx @@ -61,7 +61,7 @@ For instructions on connecting TTLock locks to Seam, see the [TTLock Setup Guide ### Lock Not Appearing in Seam -Your users must be the top administrator for each TTLock that they want to connect to Seam. That is, they must supply the credentials for the top administrator account when completing the [Connect Webview](/core-concepts/connect-webviews) to connect their TTLocks to Seam. +Your users must be the top administrator for each TTLock that they want to connect to Seam. That is, they must supply the credentials for the top administrator account when completing the Connect Webview to connect their TTLocks to Seam. ### Lock Not Paired to Gateway Error diff --git a/mintlify-docs/low-level-apis/smart-locks/access-codes/creating-access-codes/index.mdx b/mintlify-docs/low-level-apis/smart-locks/access-codes/creating-access-codes/index.mdx index 3f75d5ec6..09bced295 100644 --- a/mintlify-docs/low-level-apis/smart-locks/access-codes/creating-access-codes/index.mdx +++ b/mintlify-docs/low-level-apis/smart-locks/access-codes/creating-access-codes/index.mdx @@ -39,7 +39,7 @@ Before you attempt to create an [online](/low-level-apis/smart-locks/access-code Use [Get Device](/api/devices/get) for a specific device to return these capability flags. Then, use an `if` statement or similar check to confirm that the relevant flag is both present and `true` before attempting to create an access code. -If either of these capability flags is `false` or not present, you can view the [properties](/core-concepts/devices) of the device, [errors](/core-concepts/devices) or [warnings](/core-concepts/devices) for the device, and [events](/api/events/object) related to the device to learn more about the cause of these issues. For example, you could examine the following device properties: +If either of these capability flags is `false` or not present, you can view the [properties](/api/devices/object) of the device, [errors or warnings](/api/devices/errors) for the device, and [events](/api/devices/events) related to the device to learn more about the cause of these issues. For example, you could examine the following device properties: - `device.properties.model.has_built_in_keypad` - `device.properties.model.can_connect_accessory_keypad` diff --git a/mintlify-docs/low-level-apis/smart-locks/access-codes/index.mdx b/mintlify-docs/low-level-apis/smart-locks/access-codes/index.mdx index 260f537ae..663520ef6 100644 --- a/mintlify-docs/low-level-apis/smart-locks/access-codes/index.mdx +++ b/mintlify-docs/low-level-apis/smart-locks/access-codes/index.mdx @@ -125,7 +125,7 @@ To help your users identify codes set by Seam, Seam provides the name exactly as ## Linking Unlock Events and Access Codes -When a user unlocks a door using an access code, Seam issues a [`lock.unlocked` event](/api/events/object). Some device manufacturers include the ID of the access code in lock-related events. This information is useful for troubleshooting and logging. Further, if you name access codes in a way that identifies the associated users, you can use these `lock.unlocked` events to identify the users who unlocked the doors. +When a user unlocks a door using an access code, Seam issues a [`lock.unlocked` event](/api/locks/events#lock-unlocked). Some device manufacturers include the ID of the access code in lock-related events. This information is useful for troubleshooting and logging. Further, if you name access codes in a way that identifies the associated users, you can use these `lock.unlocked` events to identify the users who unlocked the doors. Currently, the following device manufacturers send the `access_code_id` in the `lock.unlocked` event: diff --git a/mintlify-docs/low-level-apis/smart-locks/lock-and-unlock.mdx b/mintlify-docs/low-level-apis/smart-locks/lock-and-unlock.mdx index d0b038c80..169d55839 100644 --- a/mintlify-docs/low-level-apis/smart-locks/lock-and-unlock.mdx +++ b/mintlify-docs/low-level-apis/smart-locks/lock-and-unlock.mdx @@ -24,7 +24,7 @@ Before you attempt to lock or unlock a device, be sure to confirm that your devi Use [Get Device](/api/devices/get) for a specific device to return these capability flags. Then, use an `if` statement or similar check to confirm that the relevant flag is both present and `true` before attempting to lock or unlock the device. -If either of these capability flags is `false` or not present, you can view the [properties](/core-concepts/devices) of the device, [errors](/core-concepts/devices) or [warnings](/core-concepts/devices) for the device, and [events](/api/events/object) related to the device to learn more about the cause of these issues. For example, you could examine `device.properties.online`. In addition, you could look for a `device.disconnected` event. +If either of these capability flags is `false` or not present, you can view the [properties](/api/devices/object) of the device, [errors or warnings](/api/devices/errors) for the device, and [events](/api/devices/events) related to the device to learn more about the cause of these issues. For example, you could examine `device.properties.online`. In addition, you could look for a `device.disconnected` event. **Request:** @@ -840,4 +840,4 @@ A lock or unlock event looks like the following: } ``` -For more information about the `lock.locked` and `lock.unlocked` attributes, please see[ Events](/api/events/object). +For more information about the `lock.locked` and `lock.unlocked` attributes, please see[ Events](/api/locks/events).