New Javascript SDK

New JavaScript SDK

This week, we’re excited to announce the official release of our new JavaScript SDK!

The new SDK has a smaller bundle size and fewer dependencies, and it is generated automatically on a daily basis to ensure that methods and types are always up-to-date with the latest API changes. Written entirely in TypeScript, this SDK works both on the server and in the browser, powering the Seam Console, Seam Components, Seam CLI, and more.

Our plan is to move all of our SDKs to this new auto-generated approach. We want to make sure that using any of our variety of Seam SDKs is always the best developer experience for integrating with Seam.

We encourage you to install the new Seam JavaScript SDK right away, using the following command:

ShellCopy
1npm i seam

If you’re running the original Seam JavaScript SDK (that is, the seamapi package instead of the new seam package), see our migration guide. seam is mostly a drop-in replacement for seamapi, but some method signatures and options have changed to improve overall consistency with the Seam API.

2024.09.06 Change Log

New

• Preferred access code length: We’ve added a preferred_code_length parameter to the access code create function. When creating an access code, if you do not specify a code (for example, “1234”), you can now set the preferred_code_length. Seam then generates a code of this length if the affected device supports the specified preferred code length.
• August-Yale name change events: We’ve added support for immediately detecting name changes for August-Yale devices and updating our data. Previously, it could take a while for these changes to be reflected in Seam. Note that this addition is only for August-Yale devices in North America.

Changed

• August-Yale online status: We’ve improved the detection of online/offline status for August-Yale devices. You should now see much more accurate reports.

Fixes

• SmartThings events: Previously, our backend would occasionally throw an error on incoming SmartThings events, causing some events to be dropped. We have fixed this issue. Thanks to the couple of folks who reported this issue!
• Igloohome access codes: Our Igloohome integration was incorrectly accepting PIN codes longer than six digits for online access codes on create. We’ve fixed this behavior to allow codes only between four and six digits in length. Note that offline access codes can still contain up to nine digits.
• Console: Provider logos weren’t correctly showing up in the connected account view. We’ve corrected this view.
• Seam Component edit access code function: We fixed a bug that would prevent users from editing time_bound ****access codes in our access code Seam Component.