Seam Integration of New Schlage API Version

Seam Integration of New Schlage API Version

This week, we’re excited to announce a significant update to our Schlage integration. Schlage has released version 2 of their API, so we’re changing the inner workings of our Schlage integration to use their new API version.

Schlage’s API update includes changes to event and device schemas, as well as updates to the access code schema and creation flow. These changes increase reliability in access code creation and improve event accuracy over time.

But you won’t need to do anything to take advantage of these improvements!

We do the integration maintenance with our manufacturer partners so that you don’t have to. You can look forward to a seamless transition to these Schlage enhancements.

Further, we’ve given our feedback about these changes directly to Schlage, and we’ve requested that they make updates for improved access code reliability. We work to maintain collaborative and productive manufacturer relationships so that we can bring you the best possible API experience.

We’re rolling out our migration to the new Schlage API version now, and we expect this migration to be complete by the end of next week.

Feedback Request: Locations!

We want to hear from you! We’re exploring the idea of introducing a new location resource that groups Seam devices together. Right now, you can do this kind of grouping using custom metadata, but we’d like to find a more dedicated, intuitive, and efficient way to group resources.

Help us make the Seam API even more useful for you! Let us know what would help you group devices most effectively.

2025.03.21 Changelog

New

• Lockly remote lock and unlock: We have added support for performing remote lock and unlock actions on Lockly devices, including updating the capability flags accordingly for Lockly devices. For instructions, see Locking and Unlocking Smart Locks.

• Lockly custom access codes: We have added support for creating custom access codes for Lockly devices. These codes must be six to eight digits long.

• Search by location: We have added the ability to search for devices by location in Seam Console. Previously, you could only search by device name.

• New thermostat simulations: We have added two new simulations for thermostats.

  • /thermostats/simulate/temperature_reached enables you to simulate having adjusted the HVAC mode for a thermostat. This simulation is helpful for testing that your app is receiving thermostat events correctly, such as thermostat.manually_adjusted.
  • /thermostats/simulate/hvac_mode_adjusted enables you to simulate the thermostat reaching a specified temperature. This simulation is helpful for testing that your app is receiving thermostat events correctly, such as thermostat.temperature_changed and thermostat.temperature_reached_set_point.

  For more information, see Testing Your Thermostat App with Simulate Endpoints.

• Salto KS access code schedule updates: We have added support for updating the starts_at and ends_at times on access codes for Salto KS devices. For instructions, see our docs.

• Device name change event: We have introduced a new device.name_changed event to help you keep your app up to date. This event is relevant if a user changes a device’s name in a manufacturer’s app, such as in the Yale Access app. The device.name_changed event is applicable to both smart locks and thermostats, and its payload includes the new device_name.

Changed

• Online access code capability reporting: We improved our data for the device.can_program_online_access_codes capability flag for Yale and August devices.
• Improved Igloohome error messaging: We improved the error message that we return when an Igloohome bridge is offline.
• Kwikset access code setting: We improved our handling of cases in which access codes fail to set on Kwikset devices.
• August/Yale capability reporting: We improved our detecting and reporting of capabilities for a Yale Approach lock. Seam now correctly reports that this lock supports an accessory keypad.

Fixes

• Accounts with only unmanaged devices in Seam Console: We corrected an issue in which Seam Console was not displaying the Devices page for connected accounts with only unmanaged devices.
• Thermostat temperature_reached_set_point events: We corrected an issue in which thermostat.temperature_reached_set_point events were not being sent after the heating or cooling set points were changed.
• Excessive API requests for Igloohome: We corrected an issue that was causing too many API requests to be sent for Igloohome devices.
• Extraneous thermostat event sending: We corrected an issue in which two extraneous events were being sent upon thermostat connection. These events were thermostat.temperature_reached_set_point and thermostat.temperature_changed. Note that we do continue to send these two events when appropriate.
• Incorrect sort button in Seam Console: We removed an extraneous sort button from Seam Console.
• Tedee locks missing from Seam Component: We corrected an issue that was preventing the device table Seam Component from displaying Tedee locks. Note that this Seam Component displays Tedee locks that report their locked status at least once.
• Salto lock capability detection: We corrected an issue in which Seam did not correctly detect that a specific Salto lock model did not support access code creation.
• Unmanaged thermostat updating: We corrected the extent of updating that Seam performs for unmanaged thermostat devices.
• Climate setting error checking in Seam Console: We corrected an issue that made it possible for users to omit the mandatory HVAC mode setting when modifying a climate setting in Seam Console.
• Expired access code updating: We corrected an issue in which an expired access code was incorrectly pushed to an August lock multiple times.