key benefits: quick and easy works with smartthings (wwst) certification submission collaborate across your organization monitor certification progress manage consumer-facing product and brand details ready for matter device manufacturers device partners seeking wwst certification for hub connected devices have a comprehensive new tool for end-to-end lifecycle management. the smartthings console makes it easier than ever for you to submit zigbee, z-wave, and new smart home protocol matter devices which use local edge drivers. submission and management of cloud-connected devices and certification will be available soon and will be the subject of an upcoming announcement. whether your team is in a single office, maintained across verticals, or even spread around the globe—the console enables cross-functional collaboration with permission-based controls. invite your engineers, product managers, marketers, and others with the appropriate level of access to allow management of your products, brands, and submissions. use the new product submission process to register your integration and include the required details and links. create and build a library of customized onboarding experiences that walk users through in-app setup screens. if you haven’t previously created a brand for your organization, do so now by including a logo and essential details. finally, provide the necessary details for testing and certification and hit submit. you can track the status of your submission at any time in the console. for more information on our certification process, visit the certification process overview in our developer documentation. once wwst-certified, your device will be published in the smartthings catalog, where millions of consumers discover products that deliver the high level of reliability and interoperability they expect from samsung and partner products. edit and maintain the catalog content (copy, images, etc.) displayed across the various smartthings properties from your console dashboard. don’t forget to include a product purchase link to provide users who discover your device in the catalog an option to buy from your store of choice! set up your account in the console and invite others to your organization to get started (samsung account required). for detailed instructions, check out certify your device. for device development and edge driver integration, visit our edge driver documentation.

we are excited to announce hub-connected, designed to simplify device integration into the smartthings ecosystem via a smartthings-compatible hub. providing a single, powerful platform to seamlessly integrate iot products, the smartthings developer workspace provides the ability to easily integrate devices through a third-party cloud, and now through a hub! creating a hub-connected device couldn’t be easier. as with a cloud-connected integration, you simply create a new project. by choosing device integration, you will have the option to create a cloud connector or a hub connector. hub-connected includes 50 device handler templates to add your device fingerprint information. public access to device handler code samples is enabled for ease of development. a menu-driven product information page makes it easy to register the products that are supported by your device handler. test your device with the smartthings app and then publish! for step-by-step instructions on implementing a hub-connected device, a cloud connected device or creating an automation, check out our developer workspace section of our documentation page. here, we have provided the flows for you in detail with screenshots to help you navigate through the implementation process. if you have any questions, please reach out to fabiola and david from our smartthings developer support team for one-on-one support. feel free to provide us with feedback on your experience! sign up now to learn how smartthings can help you achieve your iot vision.

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!

in august, we shared the beta release of smartthings edge—a new hub architecture that allows hub connected devices to execute locally. smartthings edge creates smart home experiences that are more reliable and faster. now, developers and hobbyists can build and consume custom device drivers in a much easier way. since the beta launch, smartthings has partnered with aeotec, leviton, kwikset, somfy north america, yale, and august to transform connectivity and the smart home experience in a noticeable way. smartthings edge’s advanced technology increases the speed of automation for consumers by eliminating the need for cloud-based processing, bringing all the information directly to the hub. this not only streamlines events and commands but also allows for local device support on a home network. this local device support decreases latency and increases reliability. all zigbee, z-wave, and wi-fi devices can run locally on the hub, with the ability to connect more protocols and standards, including matter, in the future. previously, our developers were required to copy and paste code into their samsung ide accounts to distribute and leverage custom device type handlers for hub connected devices. with smartthings edge comes the introduction of the new driver sharing feature, an easy-to-use and time-efficient alternative for community distribution and consumption. smartthings users can now share custom device drivers with a simple web link—eliminating the need to copy and paste code. while device manufacturers are still encouraged to submit their drivers to smartthings for wwst certification and distribution via the smartthings catalog, the driver sharing feature can also be used to distribute custom drivers that partners may want to test before officially releasing integrations. new drivers are regularly being added. our latest release includes zigbee range extenders, z-wave buttons, water leak sensors, contact sensors, smoke detectors, and humidity sensors. smartthings edge is the latest innovation in smartthings technology, representing the company’s commitment to developing solutions for global developer networks—thereby improving the next generation of smart home experiences.

imagine being able to control your water heater from the smartthings app! rinnai corporation recently announced they have successfully completed integration and are now part of our ecosystem. the rinnai tankless water heater is the first water heater to be included in the smartthings ecosystem. “smartthings allows homeowners to connect their devices and manage them as one. this gives homeowners more convenience and control over their tankless water heater than ever before,” said mark buss, vice president of marketing for rinnai. it is easy to make your device compatible with smartthings. as a result of rinnai's successful integration, rinnai's tankless water heater will be accessible in the smartthings app which is used by millions of users. the smartthings app is also available on smart phones, tablets, samsung smart tvs and the samsung family hub. you can connect many different kinds of devices to smartthings including a cloud-connected device, direct connected device and coming soon: hub connected devices. the integration as well as the publication process is simplified even more through the use of the developer workspace. where you create a device profile which allows you to easily define the components and capabilities used by your device. depending on whether you are building a cloud-connected, directly-connected, or hub-connected, simply follow the steps as provided to you in the developer workspace. what devices would you like to see connected to smartthings? stay tuned for upcoming announcements regarding new device integrations with smartthings! if you have any developer related questions, contact fabiola and david from our smartthings developer support team or check out our smartthings community page under the "developer" category. sign up now to learn how smartthings can help you achieve your iot vision.

by patrick barrett, robert masen, and zach varberg how we got here last month, we announced the launch of smartthings edge! looking back, smartthings provided a few different ways to integrate devices onto the platform. for hub connected devices we have always used device type handlers (dths). these were written in groovy and would run in a sandboxed environment on the smartthings cloud. while groovy dths helped us launch smartthings, they presented special challenges for local execution on the hub. with the ongoing work to modernize the platform and move away from legacy systems, we wanted to provide a better way to handle devices. similar to dths, we looked to provide a way for developers (both internal staff and partners) to define the behavior of a hub connected device through some combination of data and code. given that one of our primary goals is to support the execution of these on hubs—which we see as the edge of the smartthings platform—we decided to call these “edge drivers.” we set out to engineer a solution that would be able to deliver the developer and user experience that we were looking for. as you may have guessed from the title, edge drivers are built around lua © as the programming language... so why lua? simple the hub is a resource-limited environment. with the need for users to potentially run many edge drivers at a time, we were looking for something lightweight. lua has a small set of core structures and functionality. this leads to a small footprint, which works well for executing on hubs. with the core language being pretty small, it is pretty easy for developers to learn. additionally, as an interpreted language, developers building edge drivers do not need to worry about compiling their code. embeddable it should not come as a surprise that the smartthings hub platform software is a complex system. it is responsible for managing many aspects of how devices connect and execute within the smartthings platform. most of this software is written in rust and c (stay tuned for more on this in the future!) and we needed something that would work well in this environment. when looking for solutions, we began by investigating “prior art” to answer the question: are there other complex systems out there that needed to solve a similar problem, and if so, what did they do? we have a set of core functionality that needs to execute in a performant manner (hubcore), but want to allow extensions that give developers the tools to build unique use cases (device drivers). we found that lua had been extensively used in the video game industry (along with other non-video game software) as a way to allow developers to extend existing functionality—which is exactly what we were looking for! this means that lua could work well with c and rust, allowing your hub to run extensions with a minimal impact to the existing hub software. safe historically, all locally executing dths were either written or reviewed by our engineering teams. allowing users to run code locally on their hub that we did not write, review, and test brings up complex questions about boundaries and guardrails. as a result, it was important to identify a solution that we could sandbox—that is, lock the untrusted code in a room where it cannot hurt anyone else. lua itself provides some opportunities to tweak and limit the runtime. in addition to this, we wrap all device drivers in a second, more secure sandbox layer, with a coherent api to further protect hubs in instances where we did not believe the built-in options were enough. learn more you can visit the smartthings community to learn more about integrating your zigbee, z-wave, and lan devices with smartthings edge. lua is free software distributed under the terms of the mit license. if you want to learn more about developing with lua, we recommend getting involved with the lua community.

open theater platform innovation, developer program, iot works with smartthings 2.0 the new era of smart homes, driven by open standards like matter, is creating new challenges and opportunities for device makers, and the works with smartthings program is evolving to better address device partners’ development and business needs. in this session, we show you how works with smartthings helps your products stand out in a competitive market, leveraging the scale and confidence of the samsung brand, and new opportunities to drive preference and purchase by smartthings users. and when users bring your devices home, our new and upgraded tools help your products look and perform their best. to bring you all these benefits sooner, we’ve streamlined our certification process for hub-connected devices, to get your entire product family certified and promoted to users through a single process, with greater speed and predictability. learn why to partner with us in the new era of works with smartthings, and follow it up with the developer center session to learn how! speakers daniel moneta smartthings back to list

new december zigbee and z-wave device releases for smartthings-managed edge drivers what is smartthings edge? 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. our smartthings-managed collection of edge drivers provides functionality for common devices. as part of our works with smartthings program, device oems can add their devices to our existing drivers or build custom drivers with unique functionality. below are the latest devices migrating to smartthings edge. in the future, this will expand to include more protocols and features, like the new matter standard. interested in learning more? contact build@smartthings.com for more information. 2021 december drivers new drivers supported devices zigbee lock multiple models from yalemultiple models from kwiksetschlage be468multiple models from assa abloy irevo assa abloy irevo izbmodule01samsung sds zigbee window treatment rexense window treatment kg0001rexense window treatment dy0010feibit co ftb56-zt218ak1.6feibit co ftb56-zt218ak1.8somfy glydea ultra curtainsomfy window treatment rollerezex window treatment e2b0-kr000z0-hayookee d10110yooksmart d10110rooms beautiful c001 z-wave thermostat multiple models from honeywelgocontrol z-wave plus battery powered smart thermostatlinear thermostateverspring thermostataeotec radiator thermostatpopp thermostat2gig ct100 programmable thermostatfibaro thermostatstelpro ki thermostatqubino thermostattrane thermostatdanfoss lc13 thermostatwe’ve also included generic drivers for non-supported models. z-wave window treatment rexense/kg0001rexense/dy0010feibit co ftb56-zt218ak1.6feibit co ftb56-zt218ak1.8somfy glydea ultra curtainsomfy rollerezex e2b0-kr000z0-hayookee d10110yooksmart d10110rooms beautiful c001 z-wave fan ge enbrighten z-wave plus in-wall smart fan control, 14287leviton decora dzr15-1rzhoneywell z-wave plus in-wall smart fan control, 39358 z-wave switch multiple models from aeotecmultiple models from gemultiple models from fibaromultiple models from levitonmultiple models from inovellimultiple models from honeywellmultiple models from enerwavemultiple models from eva logikmultiple models from satcomultiple models from eatonmultiple models from gocontrolmultiple models from zoozmultiple models from everspringmultiple models from neo coolcammultiple models from poppmultiple models from qubinomultiple models from minostonmultiple models from itecmultiple models from remotecmultiple models from dawon power manager dome power outletwyfy touch z-wave switchwe’ve also included generic drivers for non-supported models. z-wave bulb multiple models from aeotecillumin rgbw bulbfibaro light

by vlad shtibin how long does it take for a light switch to turn on a light bulb? how about for the garage opener to start raising the door? how often does the switch not work? does it still work when the internet is down? the average “not smart” home is fast and reliable. this is the challenge we took on when thinking through building our next generation of automations. in order to create a smart home that is able to meet these goals, we need to take advantage of both cloud services and hubs on the edge. this blog post describes the architecture behind the smartthings rules engine that is used by the cloud and hub to power automations on the smartthings platform. device communications the following diagram conveys a high-level summary of what the smartthings platform “does” with devices. events—in the form of protocol specific messages (zigbee, z-wave, and more)—are converted into a common format (which we refer to as the capabilities) and used by smartthings services. commands from smartthings to a device follow the same pattern, just in reverse. cloud vs. local devices device communications can happen on the cloud or hub. this is mainly driven by the integration type: wi-fi integrations execute on the cloud with cloud and direct connected devices, while zigbee, z-wave, and lan integrations execute on the hub with edge drivers. we also need to provide the flexibility for unique situations, like smartapp connected cloud devices or hub connected devices that do not follow published specifications. in these cases, we use the cloud for parsing. thought experiment with philips hue our partnership with philips hue is a great example of an integration seamlessly executing across cloud and hub. for a bit of background: there are multiple ways to connect philips hue products to the smartthings platform, creating a broad topology: to summarize the topology, all input and output (i/o) is dependent on where the integration is deployed and all rule evaluation logic is independent of the deployment location. with the above use cases in mind, we needed to cover the two main integration points: event delivery: ability to consume events and get device states. command dispatch: ability to send commands to devices, set location modes, and more. looking at the architecture, we had additional requirements for high reliability, memory efficiency, and low overhead for delivery. we decided to use a rust based solution because it is memory efficient, reduced code duplication across surfaces, and easily integrated with our existing experience and release engineering infrastructure. the following table summarizes the requirements in a bit more detail: requirement description benefits of rust high reliability ensures all events are picked up and evaluated and automations execute, regardless of origin on the hub or cloud the type system and ownership model mitigates a large class of potential bugs, ensuring memory and thread safety memory efficiency this is extremely important for embedded devices (aka hubs) that run the rules engine small footprint and processor demand make it easy to run on hubs delivery overhead we needed to balance the quick delivery of features and availability of the cloud platform versus the long firmware cycles for embedded devices reduce feature implementation time, flexible with multiple deployment targets smartthings engineering compatible release engineering at smartthings is standardized, new features must work with existing tooling our rust smes were able to leverage the rich ecosystem for integration with our ci/cd processes for deployment application architecture with the above requirements, topology, and architecture in mind, we created rule engine. the resulting application architecture is essentially as follows: hive the brains of the rule engine that contains and is responsible for the majority of the rule execution code, hive has two main functions: expose an api to execute rules and provide an interface for parent services to interact with the platform. to reduce overhead, hive is dedicated to executing rules, trusting the parent service to provide contextual data needed for rule execution, such as device states or location modes. for example, when a parent service receives a device state change event, it invokes hive to evaluate (for example, is equals condition true), and executes the rule. swarm the cloud container for hive and management of i/o functionality for cloud execution, this service is deployed to the cloud and listens to events from the smartthings event pipeline. when events are consumed, swarm invokes hive to execute rules. the implementation of hive’s interface by swarm is a set of http clients that interact with the smartthings api. for example, when hive requires a device state to evaluate is equals condition true, swarm dispatches a get request to the device api and forwards the state to hive. similarly, when hive needs to send a device command, swarm dispatches a post request to the device api. drone the container for hive embedded on edge devices (aka hubs), drone invokes hive to execute rules when events are consumed locally on the hub. to implement hive’s interface, drone uses a rust api provided by services on the hub (for example, hubcore). today, this application is bundled with smartthings hub firmware and listens to events from a dispatcher on the hub. for example, when hive requires a device state to evaluate is equals condition true, drone calls into hubcore to retrieve the device state. similarly, when hive needs to send a device command, drone calls a senddevicecommand() function on hubcore’s rust api. rule engine end-to-end, the process looks something like this: rule: if switch a is on, set switch b to on user turns switch a on swarm (cloud) or drone (hub) receives the on event swarm/drone tells hive to execute rules with if switch a is on hive evaluates the rule conditions and determines to be true hive then evaluates actions, set switch b to on hive says, “send device command to switch b” swarm/drone receives “send device command to switch b” and executes the request conclusion our team has been very impressed with the capabilities of the rust programming language and supporting libraries. in the cloud, a small cluster of swarm applications is able to execute hundreds of millions of rules per day, resulting in drastically reduced cost of smartthings hosted automations. we are then able to deploy virtually the same codebase on an embedded device—with a negligible footprint—and execute consistent, low latency and reliable automations in users’ homes. since the initial launch, we have released new locally executing features with each new firmware update. looking ahead, we are regularly adding new features to rule engine that can bring you more complex automations. to learn more, check out our rules api documentation and sign up for sdc21 to participate in smartthings sessions.

smartthings and zigbee alliance are joining forces at the zigbee alliance member meeting in seoul from october 14th -17th , 2019. zigbee’s open global certification standard provides device manufacturers with an accelerated path for works with smartthings (wwst) certification. our certification places devices into a vast ecosystem of products from samsung and other industry leaders. below are a couple examples of manufacturers that have recently benefited from the enhanced zigbee and works with smartthings certification process. if you would like to learn more about building with smartthings and cannot join us in seoul, join us in san jose october 29th and 30th, 2019 at samsung developers conference. register with promo code sdc19-ser-st for 50% off. global iot lighting developer sengled is using zigbee protocols to quickly move its smart lighting innovations toward works with smartthings certification, making them quickly and conveniently available to the largest possible number of customers, including smart homes, commercial buildings, and the future of connected cities. zigbee certification allows sengled devices to be seamlessly integrated with the smartthings hub, touted as the “most versatile hub available” by smart home starter (https://smarthomestarter.com/do-you-need-a-hub-for-sengled-smart-bulbs). smartthings’ partnership with zigbee alliance provides sengled and all zigbee device developers with fast, streamlined access to wwst certification, allowing their products to quickly reach consumers using the smartthings hub to connect their smart homes and buildings. somfy is another global smart product leader using its zigbee alliance membership to quickly reach more customers through smartthings certification. somfy offers a line of motorization controls for blinds, shades, curtains and other window coverings that allows for control and status knowledge of all equipped components. users are able to pre-design scenes and directly control items remotely. individually and combined with smart lighting technology, these products can provide power cost savings and energy conservation. through zigbee certification, somfy’s tahoma hub and app will soon hold works with smartthings certification, instantly providing an exponential boost to their ability to deliver these products to a worldwide customer base. for information on zigbee alliance: https://zigbee.org more about smartthings and zigbee alliance: smartthings is the most versatile iot platform available, and includes a comprehensive range of devices from samsung and other iot leaders. smartthings is partnering with zigbee alliance to provide device developers with the fastest pathway to works with smartthings certification, making their devices compatible with smartthings hub, and including in the most comprehensive iot ecosystem. the zigbee alliance is an organization of hundreds of companies creating, maintaining, and delivering open, global standards for the iot. zigbee’s board of directors includes leaders of key members of the iot community including smartthings, samsung, amazon, leedarson, comcast, and many more. in august 2019 the alliance announced its total number of certifications surpassing 3,000. developers who already partner with smartthings are able to quickly leverage their products to the maximum number of potential customers using zigbee certifications.