New: SmartThings Edge for Devices and Automations
last year, we told you that we are transitioning to an api-first smartthings platform. as a part of this, we started investing deeply in improving stability and security. we are excited to announce the beta release of smartthings edge, a new architecture for hubs that uses device drivers and rules to execute hub connected devices locally. what is smartthings edge? we are taking smart home events that would have happened on the smartthings cloud and moving them to your smartthings hub. smartthings edge uses lua©-based device drivers and our rules api to control and automate devices connected directly to a smartthings hub. this includes zigbee, z-wave, and lan devices as well as automations triggered by timers and other hub-connected devices using drivers. in the future, this will expand to include more protocols and features, like the new matter standard. for users, edge processing means reduced latency. for partners and developers, smartthings edge also brings new benefits, including reduced cloud costs, an improved device permissioning model, and the ability to deploy updates to their drivers. local device support is open to everyone—not just wwst partners—enabling easier device support and integration with standard capabilities. hub-connected devices are defined by a driver package that includes the fingerprints, components, preferences, and lua source code. with this beta release, you can start testing features and providing us feedback before we start the platform migration. as a wwst partner, you can create your own driver package or add your device’s fingerprint to our predefined supported drivers. building hub-connected devices to get started, all you need is a smartthings hub with firmware version 000.038.000xx or greater and a zigbee, z-wave, or lan device. visit the smartthings community to learn how to get started with the smartthings cli and building drivers. rules and automations as part of our june smartthings app release, you may have noticed that some of your automations show a little 🏠. this means the automation is using locally-executing conditions and actions, such as time of day. as your devices begin using drivers and compatible rules, they will begin running on your hub, meaning higher reliability and faster response times. we have started expanding the rules api to include new operations, including: risesabove / dropsbelow, risestoorabove / dropstoorbelow, and securitystate. to learn more, visit these sample rules. sharing and distribution previously, sharing device type handlers (dth) required end-users to copy and paste the code for each individual dth into their accounts. this could be confusing and time-consuming for users to ensure they had the latest updates installed. with smartthings edge, we are also introducing driver sharing for device testing and community distribution. oems can submit their drivers to smartthings for wwst certification and distribution in the smartthings catalog. however, hobbyists can now share custom devices with a simple link—no need to copy and paste code! learn more about driver sharing and how you can start testing edge drivers. getting started along with this launch, we’ve also released a new developer documentation portal. to learn more about building smartthings edge devices and automations, check out our new developer documentation portal. this includes a new capabilities reference guide that clearly delineates between live, proposed, and (soon-to-be) deprecated capabilities. visit the new documentation portal and the smartthings community for tutorials, code samples and more. have feedback? reach out to us on the smartthings community and share your projects with @smartthings on twitter!