This week, we’re excited to announce that we’ve released real-time events for Yale and August devices within the North American region. That is, if you control your devices using the Yale Access app, you should now notice a massive improvement in how quickly you receive events relating to your device unlocking or changing online status. For devices outside of North America, we are working with Yale’s APAC and EMEIA teams to bring this enhancement later on.
From polling to real-time
The August-Yale integration is one of our oldest and has relied from the start on plain old polling to update device status and events. That meant that when a lock operation (such as an unlock) took place, it would take a few minutes for the event to be emitted from the Seam API to your server. Furthermore, as the number of Yale devices connected via Seam grew larger, we further decreased polling frequency to avoid flooding Yale’s server (fun fact: Seam’s Yale largest connected partner!).
Last spring, our friends at Yale informed us that real-time events would become available for Seam to consume and relay. We were thrilled and jumped at the opportunity to implement this enhancement for our customers. Not only does it improve the overall Yale-Seam integration experience, but it also ensures that our Yale friends can sleep soundly at night.
Rollout and available events
we began rolling out real-time events in late June. Given the importance of reliable events, we only slow rolled this out to more customers in July. As of August, we’re making this enhancement broadly available to all our customers, at no extra charge.
The following events are currently available:
lock.lockedlock.unlockeddevice.connecteddevice.disconnected
We are also working on adding additional events for access code creation operations and device metadata updates, such as a user changing a device name.
What about Yale devices out of North America
As some Yale owners may recall, in May of 2023, Assa Abloy sold its Yale North American assets to Fortune Brands. As a result of this transaction, all Yale users outside of North America were migrated to a new backend accessible via the Yale Home app. For all intents and purposes, this is effectively a completely different integration. We are currently working with the Yale Home team to add support for real-time events and will release this at a later time.
Change Log
New
- August-Yale real-time events: All August and Yale devices in North America now support real-time events for unlocking operations.
- Connect Webview events: We’ve added two new events—
connect_webview.login_succeededandconnect_webview.login_failed—to notify you whenever a Connect Webview completes. This will also create a more consistent developer experience with the events you receive from the iFrame-embedded Connect Webview. - Connect Webview styling: When you set a primary color, we now automatically adjust the text color to maximize contrast-ratio. Thanks to our friends at Lodgify for spotting this for us!
- Lockly offline codes: You can now program offline access codes on all Lockly devices, and we also added the
can_program_offline_access_codescapability flag. If you are not familiar with offline access codes, check out our Managing Offline Access Codes documentation. - Event descriptions: We’ve added an
event_descriptionto the payload for all events. It’s a human-readable string that tells you what the event is about and saves you a trip to our docs. - Access denied event: We’ve added a new
lock.access_deniedevent to indicate when an incorrect access code is entered multiple times in a row on a smartlock device. This is only available on Kwikset devices at the moment. - Automatic relock event: We’ve added a new
automaticvalue forlock_methodevents, which means that we now make it clearer when a lock automatically relocks after an unlocking operation. - Unmanaged device location: We now expose the
locationfield forunmanageddevices. This enhancement can make it easier to identify where a device is located and whether it should be converted tomanaged.
Changed
- Deprecate Get Locks: We’ve deprecated the
/locks/getendpoint. If your code uses it, you will begin to see a warning. - Kwikset duplicate code name error: We’ve improved the error message to indicate clearly that Kwikset requires the first 14 characters of a Kwikset device access code name to be unique across the device.
Fixed
- Schlage silent failing code: We’ve received a handful of reports that access codes on Schlage devices would occasionally report as
set, despite not actually being set on the device. After weeks of investigation, we’ve identified the issue as a false positive status reported by the Schlage API. The good news is that we know how to identify this and have since implemented a fix that automatically recreates the code. We’ve seen a vast reduction in Schlage related access codes errors. - Kwikset Seam API unlock: Previously,
lock.unlockedevents on Kwikset devices didn’t reliably add theseamapiunlocking method to the event payload. We’ve improved the logic to make this detection more reliable. - Igloohome: We’ve fixed an issue related to the handling of invalid auth tokens whereas the renewal process wasn’t always correctly initiated.
- Lockly: We now surface a clearer error message whenever a Lockly account’s API key does not have sufficient permissions.
- Honeywell Resideo: We added a unique account id constraints on a given workspace because creating the same account twice lead to errors later on.
- Nuki: We’ve improved the Nuki offline status detection because it was previously reporting devices as online when they were not.