The installed and updated methods are commonly found in all apps. childUninstalled() - Called for the parent app when a child app is uninstalled.uninstalled() - Called when a SmartApp is uninstalled.updated() - Called when the preferences of an installed smart app are updated.installed() - Called when a SmartApp is first installed.The following methods, if present, are automatically called at various times during the lifecycle of a SmartApp: Other configuration options that affect its behavior. These screens allow the user to specify which devices the SmartApp interacts with along with The preferences section is responsible for defining the screens that appear in the mobile app when a SmartApp is The defintion section of the SmartApp specifies the name of the app along with other information that identifies and There is alsoĪ Mappings section that is required for cloud-connected SmartApps that will be described later. Sections: Definition, Preferences, Predefined Callbacks, and Event Handlers. SmartApps take the form of a single Groovy script.Ī typical SmartApp script is composed of four Manager SmartApp that is installed when pairing with a Sonos. The Service Manager SmartApp must be installed when a user utilizes aĭevice using LAN or the cloud, so for example, there is a Sonos Service To maintain the connection for those devices. Unique protocols of your external devices and a device type handler Service Manager SmartApps are used to connect to LAN or cloud devices, Team, but we will be opening them up for external development in the Solution Module SmartApps have traditionally been built by our internal The dashboard which allows you to see the comings and goings of your One example of this would be the “Home & Family” section of SmartApps is to combine SmartApps that, in the real world, intuitively These apps exist within the dashboard of the SmartThings app interface,Īnd are containers for other SmartApps. Sites, then you will be more than capable of developing SmartApps.Ī very simple example of a SmartApp would involve you walking through aĭoor and having the lights turn on automatically. We’reĬonfident that if you are familiar with back end development of web Things, most commonly invoking a command on another device. They allow you to subscribe to events from devices and call a (Note: If you set the “Time to fill tub” field for less time than it actually takes for your tub to fill with water, you may receive a notification before your laundry is ready.Event Handler SmartApps are the most common apps developed by ourĬommunity. “Time to fill tub” = the amount of time that it takes your washer to fill with water. “Minimum cycle time” = the shortest amount of time that it takes your laundry cycle to run. Since a washer may stop vibrating at certain points during a cycle (example: during the few seconds between when water stops flowing and a cycle starts, if you open up the door to check on it, etc.), the two prompts under the header “Time thresholds” are simply meant to prevent false a notification if the washer is still running but not vibrating.

The SmartApp works by sending you a notification once the washer stops vibrating. You can also select a lamp or light to turn on or flash if you’d like multiple notifications. Configure the Laundry Monitor SmartApp by selecting a Multi following the prompt: “Tell me when this washer has stopped…”. Place a SmartSense Multi on the side or top of your washing machine. You asked for it, we made it: We’ve just published a SmartApp that sends you notifications when your laundry is done.Īppropriately, it’s called “Laundry Monitor.” You can find it under the “Convenience” SmartApp category.

Smartthings smartapp example