Lockly Integration Enhancements

Lockly Integration Enhancements

This week, we’re excited to share a series of enhancements that we’ve made to our Lockly integration. When you use Seam, you don’t have to spend your developer resources on keeping your app up to date with a bunch of device providers’ API changes. Our commitment to updating our integrations takes care of that for you!

Check out our recent Lockly updates!

Custom Access Code Support

When Lockly added support for specifying custom online access codes to their API, we jumped right in to add this feature to our Lockly integration too. These codes must be six to eight digits long. For instructions, see Creating Access Codes.

Remote Lock/Unlock Support

In March, we added support for performing remote lock and unlock actions on Lockly devices, including updating the capability flags accordingly. For instructions, see Locking and Unlocking Smart Locks.

Time-Bound Access Code Fixes

In April, we resolved a time zone issue that had affected access code start and end times. Time-bound access codes on Lockly devices behave as expected—and, as you should expect, we continue to improve and refine our device provider integrations.

Getting Started

To get started, go to Seam Console, click Add Devices, and select Lockly. For more details, check out our Lockly integration guide and Lockly Supported Devices page.

2025.05.09 Changelog

New

• Salto KS access code schedule updates: We now support updating the starts_at and ends_at times for Salto KS access codes.

Changed

• Access code length reporting: Because users can now report access code length constraints for SmartThings devices, we’ve added this information and the original code length to SmartThings metadata. To view this metadata, use the /devices/get endpoint for a SmartThings device. For details about reporting access code length constraints for SmartThings devices, see our docs.

Fixes

• Incorrect min_heating_cooling_delta_fahrenheit value: We fixed a conversion issue that was causing Seam to display the min_heating_cooling_delta_fahrenheit value incorrectly.