• Learn
    • Code Lab
    • Foldables and Large Screens
    • One UI Beta
  • Develop
    • Mobile/Wearable
    • Galaxy GameDev
    • Galaxy Themes
    • Galaxy Watch
    • Health
    • Samsung Blockchain
    • Samsung DeX
    • Samsung IAP
    • Samsung Internet
    • Samsung Pay
    • Samsung Wallet
    • View All
      • Galaxy AR Emoji
      • Galaxy Accessory
      • Galaxy Edge
      • Galaxy Z
      • Galaxy Performance
      • Galaxy FM Radio
      • Galaxy S Pen Remote
      • Galaxy Sensor Extension
      • PENUP
      • Samsung Automation
      • Samsung Neural
      • Samsung TEEGRIS
      • Samsung eSE SDK
      • Galaxy Watch for Tizen
      • Watch Face Studio
      • One UI Watch for Tizen
      • Galaxy Watch Studio Converter
      • Samsung IAP for Galaxy Watch (Tizen)
    • Visual Display
    • Smart TV
    • Smart Hospitality Display
    • Smart Signage
    • Digital Appliance
    • Family Hub
    • Platform
    • Bixby
    • Knox
    • SmartThings
    • Tizen.NET
  • Design
    • Design System
    • One UI
    • One UI Watch
    • Smart TV
  • Distribute
    • Galaxy Store
    • TV Seller Office
    • Galaxy Store Games
    • Instant Plays
  • Support
    • Developer Support
    • Remote Test Lab
    • Samsung Android USB Driver
    • Galaxy Emulator Skin
  • Connect
    • Blog
    • News
    • Forums
    • Events
    • Samsung Developer Conference
    • SDC23
    • SDC22
    • SDC21
    • SDC19 and Previous Events
  • Sign In
Top Global Search Form
Recommendation
  • Blog
  • Code Lab
  • Foldable and Large Screen Optimization
  • Forums
  • Galaxy Emulator Skin
  • Galaxy GameDev
  • Health
  • Remote Test Lab
  • SDC22
  • Watch Face Studio
All Search Form
Recommendation
    Suggestion
      All Search Form
      Filter
      Filter
      Filter
      • ALL (15)
      • DOCS
      • SDK
      • API REFERENCE
      • CODE LAB
      • BLOG
      • NEWS/EVENTS
      • OTHERS
        api reference code lab blog news/events
      1. announcement | iot

      blog

      The New Era of Edge and Matter

      since launching 10 years ago, smartthings has been at the forefront of the smart home space, providing delightful experiences that have allowed users to connect their homes and control a multitude of devices from a huge number of hardware manufacturers, growing to include unique features with samsung tvs and appliances. one of the most popular methods to integrate devices into the smartthings platform has been to connect directly to hubs in the home, using radio protocols such as zigbee and z-wave. to date, smartthings has used the groovy programming language to facilitate these device communications. while the groovy framework has allowed developers a great amount of flexibility, the connected home is fast outgrowing this technology and therefore smartthings has had to evolve. beginning september 30, 2022, groovy device dths, smartapps built on groovy, and the developer ide will be removed from the smartthings platform and will no longer be supported. edge drivers using lua have replaced the legacy groovy dths for controlling devices. as has been the topic of many communications throughout this transition, edge reduces the need to send device commands or automations to the smartthings cloud for processing and they are now processed right on the hub, reducing latency and increasing reliability across the connected home. a list of available edge drivers can be found here. as the door closes on groovy-based smartapps, a new door opens for developers with the rules api. developers can build simple or complex automations based on any number of triggers to customize experiences using common action, command, and operand semantics. additional processes and features, such as integrating a manual command, can be developed using the scenes api. smartthings is leading the development and launch of the matter industry standard along with ecosystem partners and members of the connectivity standards alliance. this common protocol will revolutionize the connected home for end users and developers alike. the journey so far has been an exciting one, and the launch of edge drivers and rules apis are the first steps toward taking smartthings and our developer community to more places than we could have imagined months ago when we first announced these updates. stay tuned for more matter announcements as we approach its launch this fall!

      SmartThings Developers

      https://developer.samsung.com/smartthings/blog/en-us/2022/08/17/the-new-era-of-edge-and-matter
      1. announcement | iot

      blog

      Why We Chose Lua for SmartThings Edge Drivers

      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.

      SmartThings Developers

      https://developer.samsung.com/smartthings/blog/en-us/2021/09/15/why-we-chose-lua-for-smartthings-edge-drivers
      1. announcement | iot

      blog

      December Release - Beta Drivers for SmartThings Edge

      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

      SmartThings Developers

      https://developer.samsung.com/smartthings/blog/en-us/2022/01/06/december-release---beta-drivers-for-smartthings-edge
      1. announcement | iot

      blog

      New SmartThings Console for Device Certification

      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.

      SmartThings Developers

      https://developer.samsung.com/smartthings/blog/en-us/2022/11/14/new-smartthings-console-for-device-certification
      1. Connect
      2. Samsung Developer Conference

      web

      SDC22 | SmartThings Edge: The next level experience

      session iot, security & privacy smartthings edge: the next level experience discover how samsung is transitioning the smartthings-published groovy dths to edge drivers while maintaining a seamless experience for our users. we’ll walk through the process of onboarding edge-based devices and how to set up an automation with an edge device that runs locally. speakers evan artis smartthings inc. alissa dornbos smartthings inc.

      https://developer.samsung.com/conference/sdc22/sessions/smartthings-edge-the-next-level-experience
      1. announcement | iot

      blog

      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!

      SmartThings

      https://developer.samsung.com/smartthings/blog/en-us/2021/08/19/new-smartthings-edge-for-devices-and-automations
      1. Connect
      2. Samsung Developer Conference

      web

      SDC23 | Developer Center Announcement

      tech session platform innovation, iot, developer program developer center announcement join aaron swift, the director of product management at smartthings, as he introduces the company's brand new developer center, aimed at fostering seamless product testing, certification, and support. with smartthings serving as the heart of millions of samsung users' smart homes, new developer tools are designed to not just enhance compatibility but to emphasize differentiation. aaron will explore the significance of the "works with smartthings" certification and its potential to elevate products in an ever-evolving ecosystem. delve into new tools, such as the no-code edge driver builder and the certification console, built to ensure products shine in the smartthings environment, and drive sales. in addition, discover how this suite of offerings can propel your product's visibility and user engagement, setting it apart in the market. understand the strategic alignment of smartthings with the larger samsung ecosystem and the role it plays in end user decision-making. the session concludes with an engaging q&a, diving deeper into smartthings' vision and its collaborative partnership with developers. speakers aaron swift smartthings back to list

      https://developer.samsung.com/conference/sdc23/sessions/developer-center-announcement
      1. Develop
      2. SmartThings

      web

      SmartThings | Samsung Developers

      smartthings integrate your devices, automate interactions, and extend capabilities with connected services. get started get started do more with smartthings smartthings is one of the largest open ecosystems of connected devices, including over a billion galaxy devices and samsung appliances, millions of customers, and an ever increasing number of partners. smartthings provides a cohesive platform for iot devices to interoperate and communicate, enabling smarter living solutions that enrich our world. developers can access a comprehensive set of features, an instant mobile ui, and leverage voice control with bixby and others. documentation learn how to build new and innovative user experiences. community forum share ideas, ask questions, get support, and connect with customers and developers. developer console seamlessly integrate your iot products into the smartthings ecosystem. partner with us connect with hundreds of brands and thousands of devices. inviting you to an ecosystem of smarter living solutions the smartthings platform connects with the largest coverage of samsung and partner devices available. check out the current list of compatible brands and explore possible integrations. discover brands & devices get your devices ready for matter we truly believe that matter is the foundation and future of iot. we are thrilled that samsung smartthings will be accelerating smart home adoption and bringing users more convenient connected home experiences wherever they are. - michelle mindala-freeman, head of marketing , connectivity standards alliance. learn more explore the ecosystem local control with smartthings edge smartthings edge allows wifi, zigbee, and z-wave device manufacturers to automate and control smart homes devices faster than ever. mobile connected devices integrate your bluetooth devices with over 100m smartthings find nodes and help your customers locate their devices offline. cloud connected devices managing your own cloud? smartthings schema is the easiest method of integrating your cloud connected devices. smartthings cloud integrations use the smartthings cloud as the backend for your mqtt projects. connected services link your apps and services with millions of smartthings users. we have multiple options, depending on what platform you are looking to use. get your device certified works with smartthings certification offers professional, comprehensive testing for your product. smartthings community get help, learn, and share experiences using smartthings. join our community to connect with customers and developers. finding resources on writing for the new platform writing smartapps finding the official tutorials on edge topics writing edge drivers faq: getting started with the new rules api rules api custom capability and cli developer preview tutorials latest blog posts go to blog find in-depth technical content written by smartthings developers.

      https://developer.samsung.com/smartthings/
      1. success story | iot

      blog

      SmartThings Edge Provides Reliable, Faster Smart Home Experiences

      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.

      SmartThings Developers

      https://developer.samsung.com/smartthings/blog/en-us/2021/10/29/smartthings-edge-provides-reliable-faster-smart-home-experiences
      1. success story | iot

      blog

      Accelerating Home Automation at SmartThings with Rule Engine

      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 Developers

      https://developer.samsung.com/smartthings/blog/en-us/2021/10/21/accelerating-home-automation-at-smartthings-with-rule-engine
      No Search Results
      No Search results. Try using another keyword.
      • <<
      • <
      • 1
      • 2
      • >
      • >>
      Samsung Developers
      Samsung Developers
      Quick Link
      • Android USB Driver
      • Code Lab
      • Galaxy Emulator Skin
      • Foldables and Large Screens
      • One UI Beta
      • Remote Test Lab
      • Developer Support
      Family Site
      • Bixby
      • Knox
      • Samsung Pay
      • SmartThings
      • Tizen
      • Samsung Research
      • SamsungOpen Source
      • Samsung Dev Spain
      • Samsung Dev Brazil
      Legal
      • Terms
      • Privacy
      • Open Source License
      • Cookie Policy
      Social Communications
      • Facebook
      • Instagram
      • Twitter
      • YouTube
      • Buzzsprout
      • Rss
      • Linkedin
      • System Status
      • Site Map
      • System Status
      • Site Map
      • facebook
      • instagram
      • twitter
      • youtube
      • buzzsprout
      • rss
      • linkedin

      Copyright © 2023 SAMSUNG. All rights reserved.