measure blood oxygen level on galaxy watch objective create a health app for galaxy watches powered by wear os, utilizing the new samsung privileged health sdk to trigger and obtain blood oxygen level (spo2) measurement results. partnership request in this code lab, you will use a specially prepared mock library. it has limited functionality and uses dummy data instead of real-time data. to get real values, you will need the full version of the samsung privileged health sdk library, which is available to registered samsung partners. apply as a partner by checking out the partner app program to get exclusive access to the samsung privileged health sdk. overview samsung privileged health sdk provides means of accessing and tracking health information contained in the health data storage. its tracking service gives raw and processed sensor data such as accelerometer and body composition data sent by the samsung bioactive sensor. the latest bioactive sensor of galaxy watch runs powerful health sensors such as photoplethysmogram (ppg), electrocardiogram (ecg), bioelectrical impedance analysis (bia), sweat loss, and spo2. see samsung privileged health sdk descriptions for detailed information. set up your environment you will need the following: galaxy watch4 or newer android studio (latest version recommended) java se development kit (jdk) 11 or later sample code here is a sample code for you to start coding in this code lab. download it and start your learning experience! measuring blood oxygen level sample code (110.13 kb) turn on developer mode and adjust its settings on your watch, go to settings > about watch > software and tap on software version 5 times. upon successful activation of developer mode, a toast message will display as on the image below. afterwards, developer options will be visible under settings. tap developer options and enable the following options: adb debugging debug over wi-fi turn off automatic wi-fi connect your galaxy watch to wi-fi go to settings > connection > wi-fi and make sure that wi-fi is enabled. from the list of available wi-fi networks, choose and connect to the same one as your pc. when successfully connected, tap a wi-fi network name, swipe down, and note the ip address. you will need this to connect your watch over adb from your pc. connect your galaxy watch to android studio in android studio, go to terminal and type: adb connect <ip address as mentioned in previous step> when prompted, tap always allow from this computer to allow debugging. upon successful connection, you will see the following message in android studio’s terminal: connected to <ip address of your watch> now, you can run the app directly on your watch. start your project after downloading the sample code containing the project files, in android studio click open to open existing project. locate the downloaded android project (basic) from the directory and click ok. check capabilities for the device to track data with the samsung privileged health sdk, it must support a given tracker type – blood oxygen level. to check this, get the list of available tracker types and verify that the tracker is on the list. in the connectionmanager.java file, navigate to the isspo2available() function, use a provided healthtrackingservice object to create a healthtrackercapability instance, send it to the checkavailabletrackers function, and assign its result to the availabletrackers list. gettrackingcapability() returns a healthtrackercapability instance in the healthtrackingservice object healthtrackingservicehealthtrackingservice initiates a connection to samsung's health tracking service and provides a healthtracker instance to track a healthtrackertype. public healthtrackercapability gettrackingcapability() provide a healthtrackercapability instance to get a supporting health tracker type list. /****************************************************************************************** * [practice 1] check capabilities to confirm spo2 availability * * ---------------------------------------------------------------------------------------- * * (hint) replace todo 1 with java code * get healthtrackercapability object from healthtrackingservice * send the object to checkavailabletrackers() ******************************************************************************************/ public boolean isspo2available(healthtrackingservice healthtrackingservice) { if (healthtrackingservice == null) return false; list<healthtrackertype> availabletrackers = null; //"todo 1" if (availabletrackers == null) return false; else return availabletrackers.contains(healthtrackertype.spo2); } check connection error resolution suppose a connection to the health tracking service attempt ends with an error. in that case, you can try to resolve it using the samsung privileged health sdk api. in the connectionmanager.java file, navigate to the processtrackerexception() function, and check if the provided healthtrackerexception object has a resolution. assign the result to hasresolution variable. hasresolution() function in the healthtrackerexception object checks if the api side can fix the error healthtrackerexceptionhealthtrackerexception contains error codes and checks the error's resolution. if there is a resolution, solving the error is available by calling resolve(activity). boolean hasresolution() checks whether the given error has a resolution. /******************************************************************************************* * [practice 2] resolve healthtrackerexception error * * ----------------------------------------------------------------------------------------- * * (hint) replace todo 2 with java code * call hasresolution() on healthtrackerexception object ******************************************************************************************/ public void processtrackerexception(healthtrackerexception e) { boolean hasresolution = false; //"todo 2" if (hasresolution) e.resolve(callingactivity); if (e.geterrorcode() == healthtrackerexception.old_platform_version || e.geterrorcode() == healthtrackerexception.package_not_installed) observerupdater.getobserverupdater().notifyconnectionobservers(r.string.novalidhealthplatform); else observerupdater.getobserverupdater().notifyconnectionobservers(r.string.connectionerror); log.e(tag, "could not connect to health tracking service: " + e.getmessage()); } initialize spo2 tracker before the measurement starts, initialize the spo2 tracker by obtaining the proper health tracker object. in the spo2listener.java file, navigate to the init() function. using the provided healthtrackingservice object, create an instance of the spo2 tracker and assign it to the spo2tracker object. gethealthtracker() with healthtrackertype.spo2 as an argument will create a healthtracker instance healthtrackingservicehealthtrackingservice initiates a connection to samsung's health tracking service and provides a healthtracker instance to track a healthtrackertype. healthtracker gethealthtracker(healthtrackertype healthtrackertype) provides a healthtracker instance for the given healthtrackertype. /******************************************************************************************* * [practice 3] initialize spo2 tracker * * ---------------------------------------------------------------------------------------- * * (hint) replace todo 3 with java code * initialize spo2tracker with proper samsung privileged health sdk functionality * call gethealthtracker() on healthtrackingservice object * use healthtrackertype.spo2 as an argument ******************************************************************************************/ void init(healthtrackingservice healthtrackingservice) { //"todo 3" } perform measurement for the client app to start obtaining the data through the sdk, it has to set a listener method on the healthtracker. the application setups the listener when the user taps on the measure button. each time there is new data, the listener callback receives it. after the measurement completes, the listener has to be disconnected. since, due to battery drain, on-demand measurement should not last more than approximately 30 seconds. the measurement will cancel if the final blood oxygen level value is not delivered in time. it’s also worth noting that the sensor needs a few seconds to warm up and provide correct values, adding to the overall measurement time. the blood oxygen level values come in the ondatareceived callback of trackereventlistener. see below example of the code, in the spo2listener.java file, reading the value: private final healthtracker.trackereventlistener spo2listener = new healthtracker.trackereventlistener() { @override public void ondatareceived(@nonnull list<datapoint> list) { for (datapoint data : list) { updatespo2(data); } } }; private void updatespo2(datapoint data) { int status = data.getvalue(valuekey.spo2set.status); int spo2value = 0; if (status == measurement_completed) spo2value = data.getvalue(valuekey.spo2set.spo2); observerupdater.getobserverupdater().notifytrackerobservers(status, spo2value); } run unit tests for your convenience, you will find an additional unit tests package. this will let you verify your code changes even without using a physical watch. see instructions below on how to run the unit tests: right click on com.samsung.sdc22.health.basic (test) and execute run 'tests in 'com.samsung.sdc22.health.basic'' command. if you completed all the tasks correctly, you will see all the unit tests passed successfully. run the app after building the apk, you can run the application on a connected device to measure your blood oxygen level. right after the app is started, it will request user permission. allow the app to receive data from the body sensors. afterwards, it will show the application's main screen. to get the blood oxygen level value, tap on the measure button. to stop the measurement, tap on the stop button. you're done! congratulations! you have successfully achieved the goal of this code lab. now, you can create a health app that measures blood oxygen level by yourself! if you're having trouble, you may download this file: measuring blood oxygen level complete code (109.86 kb) to learn more about samsung health, visit: developer.samsung.com/health

measure blood oxygen level and heart rate on galaxy watch objective create a health app for galaxy watches powered by wear os, utilizing the new samsung privileged health sdk to trigger and obtain results of simultaneous blood oxygen level (spo2) and heart rate measurements. partnership request in this code lab, you will use a specially prepared mock library. it has limited functionality and uses dummy data instead of real-time data. to get real values, you will need the full version of the samsung privileged health sdk library, which is available to samsung partners. apply as a partner by checking out the partner app program to get exclusive access to the samsung privileged health sdk. overview samsung privileged health sdk provides means of accessing and tracking health information contained in the health data storage. its tracking service gives raw and processed sensor data such as accelerometer and body composition data sent by the samsung bioactive sensor. the latest bioactive sensor of galaxy watch runs powerful health sensors such as photoplethysmogram (ppg), electrocardiogram (ecg), bioelectrical impedance analysis (bia), sweat loss, and spo2. see samsung privileged health sdk descriptions for detailed information. set up your environment you will need the following: galaxy watch4 or newer android studio (latest version recommended) java se development kit (jdk) 11 or later sample code here is a sample code for you to start coding in this code lab. download it and start your learning experience! measuring blood oxygen level and heart rate sample code (128.16 kb) turn on developer mode and adjust its settings on your watch, go to settings > about watch > software and tap on software version 5 times. upon successful activation of developer mode, a toast message will display as on the image below. afterwards, developer options will be visible under settings. tap developer options and enable the following options: adb debugging debug over wi-fi turn off automatic wi-fi connect your galaxy watch to wi-fi go to settings > connection > wi-fi and make sure that wi-fi is enabled. from the list of available wi-fi networks, choose and connect to the same one as your pc. when successfully connected, tap a wi-fi network name, swipe down, and note the ip address. you will need this to connect your watch over adb from your pc. connect your galaxy watch to android studio in android studio, go to terminal and type: adb connect <ip address as mentioned in previous step> when prompted, tap always allow from this computer to allow debugging. upon successful connection, you will see the following message in android studio’s terminal: connected to <ip address of your watch> now, you can run the app directly on your watch. start your project after downloading the sample code containing the project files, in android studio click open to open existing project. locate the downloaded android project (advanced) from the directory and click ok. establish service connection and check capabilities for the device to track data with the samsung privileged health sdk, it must connect to the service by healthtrackingservice api. after establishing a connection, verify if the required tracker type is available. to check this, get the list of available tracker types and verify that the tracker is on the list. in this code lab, you will utilize blood oxygen level and heart rate trackers. the healthtrackingservice api usage is in the table below. healthtrackingservicehealthtrackingservice initiates a connection to samsung's health tracking service and provides a healthtracker instance to track a healthtrackertype. public void connectservice() establish a connection with samsung's health tracking service. public void disconnectservice() release a connection for samsung's health tracking service. public healthtrackercapability gettrackingcapability() provide a healthtrackercapability instance to get a supporting health tracker type list. initialize multiple trackers before the measurement starts, initialize the spo2 tracker by obtaining the proper health tracker object. in the connectionmanager.java file, navigate to initspo2(), create an oxygen saturation healthtracker instance, and pass it to the spo2listener instance. get the healthtracker object using the healthtrackingservice api. use the healthtrackertype.spo2 type as parameter. healthtrackingservicehealthtrackingservice initiates a connection to samsung's health tracking service and provides a healthtracker instance to track a healthtrackertype. public healthtracker gethealthtracker(healthtrackertype healthtrackertype) provide a healthtracker instance for the given healthtrackertype. pass the healthtracker object to the spo2listener instance object. spo2listener public void sethealthtracker(healthtracker tracker) set healthtracker instance for the given tracker. /******************************************************************************************* * [practice 1] create blood oxygen level health tracker object * - get health tracker object * - pass it to spo2listener ------------------------------------------------------------------------------------------- * - (hint) replace todo 1 with parts of code * (1) get healthtracker object using healthtrackingservice.gethealthtracker() * use healthtrackertype.spo2 type as parameter * (2) pass it to spo2listener using sethealthtracker function ******************************************************************************************/ public void initspo2(spo2listener spo2listener) { //"todo 1 (1)" //"todo 1 (2)" sethandlerforbaselistener(spo2listener); } next, in the connectionmanager.java file, in the initheartrate() function, create a heart rate healthtracker instance, and pass it to the heartratelistener instance. get the healthtracker object using the healthtrackingservice api. use the healthtrackertype.heart_rate type as parameter. pass the healthtracker object to the heartratelistener instance object. heartratelistener public void sethealthtracker(healthtracker tracker) set healthtracker instance for the given tracker. /******************************************************************************************* * [practice 2] create heart rate health tracker object * - get health tracker object * - pass it to heartratelistener ------------------------------------------------------------------------------------------- * - (hint) replace todo 2 with parts of code * (1) get healthtracker object using healthtrackingservice.gethealthtracker() * use healthtrackertype.heart_rate type as parameter * (2) pass it to heartratelistener using sethealthtracker function ******************************************************************************************/ public void initheartrate(heartratelistener heartratelistener) { //"todo 2 (1)" //"todo 2 (2)" sethandlerforbaselistener(heartratelistener); } start and stop trackers for the client app to start obtaining the data through the sdk, set a listener method on healthtracker. this method will be called every time there is new data. after the measurement completes, the listener has to be disconnected. to start measurement in the baselistener.java file, navigate to starttracker() function, and set trackereventlistener as listener healthtracker object. set an event listener on healthtracker object using healthtracking api. use the healthtracker.trackereventlistener object instance as parameter. healthtrackerhealthtracker enables an application to set an event listener and get tracking data for a specific healthtrackertype. public void seteventlistener(healthtracker.trackereventlistener listener) set an event listener to this healthtracker instance. /******************************************************************************************* * [practice 3] start health tracker by setting event listener * - set event listener on health tracker ------------------------------------------------------------------------------------------- * - (hint) replace todo 3 with parts of code * set event listener on healthtracker object using healthtracker.seteventlistener() * use trackereventlistener object as parameter ******************************************************************************************/ public void starttracker() { log.i(app_tag, "starttracker called "); log.d(app_tag, "healthtracker: " + healthtracker.tostring()); log.d(app_tag, "trackereventlistener: " + trackereventlistener.tostring()); if (!ishandlerrunning) { handler.post(() -> { //"todo 3" sethandlerrunning(true); }); } } to stop measurement, unset the trackereventlistener from the healthtracker object in the stoptracker() function. unset the event listener on healthtracker object using healthtracking api. healthtrackerhealthtracker enables an application to set an event listener and get tracking data for a specific healthtrackertype. public void unseteventlistener() stop the registered event listener to this healthtracker instance. /******************************************************************************************* * [practice 4] stop health tracker by removing event listener * - unset event listener on health tracker ------------------------------------------------------------------------------------------- * - (hint) replace todo 4 with parts of code * unset event listener on healthtracker object using healthtracker.unseteventlistener() ******************************************************************************************/ public void stoptracker() { log.i(app_tag, "stoptracker called "); log.d(app_tag, "healthtracker: " + healthtracker.tostring()); log.d(app_tag, "trackereventlistener: " + trackereventlistener.tostring()); if (ishandlerrunning) { //"todo 4" sethandlerrunning(false); handler.removecallbacksandmessages(null); } } process obtained and batching data the response from the platform will be asynchronous with the results you want to obtain. follow the steps below to get blood oxygen level and heart rate data. in the spo2listener.java file, navigate to updatespo2() function, and read spo2 data from datapoint: get the oxygen saturation status using the datapoint api (key: valuekey.spo2set.status). get the oxygen saturation value using the datapoint api (key: valuekey.spo2set.spo2). datapointdatapoint provides a map of valuekey and value with a timestamp. public <t>t getvalue(valuekey<t> type) get data value for the given key. /******************************************************************************************* * [practice 5] read values from datapoint object * - get blood oxygen level status * - get blood oxygen level value ------------------------------------------------------------------------------------------- * - (hint) replace todo 5 with parts of code * (1) remove spo2status.calculating and * set status from 'datapoint' object using datapoint.getvalue(valuekey.spo2set.status) * (2) set spo2value from 'datapoint' object using datapoint.getvalue(valuekey.spo2set.spo2) * if status is 'spo2status.measurement_completed' ******************************************************************************************/ public void updatespo2(datapoint datapoint) { int status = spo2status.calculating; //"todo 5 (1)" int spo2value = 0; //"todo 5 (2)" trackerdatanotifier.getinstance().notifyspo2trackerobservers(status, spo2value); log.d(app_tag, datapoint.tostring()); } in the heartratelistener.java file, navigate to readvaluesfromdatapoint() function, and read the heart rate data from datapoint: get the heart rate status using the datapoint api (key: valuekey.heartrateset. status). get the heart rate value using the datapoint api (key: valuekey.heartrateset.heart_rate). get the heart rate inter-beat interval (ibi) value using the datapoint api (key: valuekey.heartrateset. heart_rate_ibi). calculate the ibi quality using the first bit from the heart rate ibi value. calculate the ibi value using the remaining 15 bits from the heart rate ibi value. /******************************************************************************************* * [practice 6] read values from datapoint object * - get heart rate status * - get heart rate value * - get heart rate ibi value * - check retrieved heart rate’s ibi and ibi quality values ------------------------------------------------------------------------------------------- * - (hint) replace todo 6 with parts of code * (1) set hrdata.status from 'datapoint' object using datapoint.getvalue(valuekey.heartrateset.status) * (2) set hrdata.hr from 'datapoint' object using datapoint.getvalue(valuekey.heartrateset.heart_rate) * (3) set local variable 'final int hribi' using datapoint.getvalue(valuekey.heartrateset.heart_rate_ibi) * (4) set hrdata.qibi with the first of 16 bits of 'hribi' value * (use heartratedata.ibi_quality_shift 15 bits shift and heartratedata.ibi_mask 1 bit mask) * (5) set hrdata.ibi with the rest of the 15 bits of 'hribi' value * (use heartratedata.ibi_quality_mask 15 bit mask) ******************************************************************************************/ public void readvaluesfromdatapoint(datapoint datapoint) { heartratedata hrdata = new heartratedata(); //"todo 6 (1)" //"todo 6 (2)" //"todo 6 (3)" //"todo 6 (4)" //"todo 6 (5)" trackerdatanotifier.getinstance().notifyheartratetrackerobservers(hrdata); log.d(app_tag, datapoint.tostring()); } run unit tests for your convenience, you will find an additional unit tests package. this will let you verify your code changes even without using a physical watch. see instructions below on how to run the unit tests: right click on com.samsung.sdc22.health.advanced (test) and execute run 'tests in 'com.samsung.sdc22.health.advanced'' command. if you completed all the tasks correctly, you will see all the unit tests passed successfully. run the app after building the apk, you can run the application on a connected device to see blood oxygen level and heart rate values. right after the app is started, it will request user permission. allow the app to receive data from the body sensors. afterwards, it will show the application's main screen and automatically display the heart rate. to get the blood oxygen level (spo2) value, tap on the measure button. to stop the measurement, tap on the stop button. tap on the details label to see more heart rate data. you're done! congratulations! you have successfully achieved the goal of this code lab. now, you can create a health app that measures blood oxygen level and heart rate by yourself! if you're having trouble, you may download this file: measuring blood oxygen level and heart rate complete code (120.06 kb) to learn more about samsung health, visit: developer.samsung.com/health

create a daily step counter on galaxy watch objective create a native app for galaxy watch, operating on wear os powered by samsung, using health platform to read your daily steps. overview health platform provides a unified and straightforward way for accessing a wide range of health and wellness related data. with health platform api, you may easily read and write data stored in health platform on android and wear os powered by samsung. applications can have access to these secured data only with explicit user consent. additionally, users may disable access to the data at any point in time. see health platform descriptions for detailed information. set up your environment you will need the following: galaxy watch4 or newer android studio (latest version recommended) java se development kit (jdk) 11 or later sample code here is a sample code for you to start coding in this code lab. download it and start your learning experience! health step count sample code (119.87 kb) turn on developer mode and adjust its settings on your watch, go to settings > about watch > software and tap on software version 5 times. upon successful activation of developer mode, a toast message will display as on the image below. afterwards, developer options will be visible under settings. tap developer options and enable the following options: adb debugging debug over wi-fi turn off automatic wi-fi connect your galaxy watch to wi-fi go to settings > connection > wi-fi and make sure that wi-fi is enabled. from the list of available wi-fi networks, choose and connect to the same one as your pc. when successfully connected, tap a wi-fi network name, swipe down, and note the ip address. you will need this to connect your watch over adb from your pc. connect your galaxy watch to android studio in android studio, go to terminal and type: adb connect <ip address as mentioned in previous step> when prompted, tap always allow from this computer to allow debugging. upon successful connection, you will see the following message in android studio’s terminal: connected to <ip address of your watch> now, you can run the app directly on your watch. start your project after downloading the sample code containing the project files, in android studio click open to open existing project. locate the downloaded android project (stepcount) from the directory and click ok. check dependency and app manifest in the dependencies section of stepcount/app/build.gradle file, see the appropriate dependency for health platform. dependencies { implementation com.google.android.libraries.healthdata:health-data-api:1.0.0-alpha01' // ... } notelibrary might update from time to time. if necessary, choose the version suggested by android studio. request for data permissions before accessing any data through health platform, the client app must obtain necessary permissions from the user. in permissions.java, create a permission instance to trigger relevant permission screen and obtain required consent from end user. data type name: intervaldatatypes.steps read access: accesstype.read /******************************************************************************************* * [practice 1] build permission object grand permissions for read today's steps * - set interval data type of steps * - set read access type ------------------------------------------------------------------------------------------- * - (hint) uncomment lines below and fill todos with * (1) for interval data type: intervaldatatypes.steps * (2) for read access: accesstype.read ******************************************************************************************/ permission stepsreadpermission = permission.builder() //.setdatatype("todo 1 (1)") //.setaccesstype("todo 1 (2)") .build(); make a query to aggregate today’s steps create read request with all necessary information to read data through health platform api. the answer from the platform will be asynchronous with the result from which you can get all the data you are interested in. follow the steps below to get today's steps count: in stepsreader.java, create a readaggregateddatarequest with cumulativeaggregationspec instance: data type name: intervaldatatypes.steps /******************************************************************************************* * [practice 2] build read aggregated data request object for read today's steps * - set interval data type of steps ------------------------------------------------------------------------------------------- * - (hint) uncomment line below and fill todo 2 with * (1) for interval data type: intervaldatatypes.steps ******************************************************************************************/ readaggregateddatarequest readaggregateddatarequest = readaggregateddatarequest.builder() .settimespec( timespec.builder() .setstartlocaldatetime(localdatetime.now().with(localtime.midnight)) .build()) //.addcumulativeaggregationspec(cumulativeaggregationspec.builder("todo 2 (1)").build()) .build(); read cumulative steps count from cumulativedata: set variable steps value to 0l. it is the count of daily steps. get aggregatedvalue object using cumulativedata api. cumulativedataaggregateddata representing total of intervaldata over a period of time (e.g. total steps in a day). public aggregatedvalue gettotal () check the result. if it is not null, get aggregated value using aggregatedvalue api: aggregatedvaluevalue fields aggregated over a period of time. only numeric fields (longfield, doublefield) can be included in aggregation. public long getlongvalue () returns all longfields and their values that are already set. add value to the daily steps result counter. /******************************************************************************************* * [practice 3] read aggregated value from cumulative data and add them to the result * - get aggregatedvalue from cumulativedata object * - get steps count from aggregatedvalue object ------------------------------------------------------------------------------------------- * - (hint) uncomment lines below and replace todo 3 with parts of code * (1) get aggregatedvalue object 'obj' using cumulativedata.gettotal() * (2) get value using obj.getlongvalue() and add to the result ******************************************************************************************/ long steps = 0l; if(result != null) { list<cumulativedata> cumulativedatalist = result.getcumulativedatalist(); if (!cumulativedatalist.isempty()) { for(cumulativedata cumulativedata : cumulativedatalist) { //"todo 3 (1)" //"todo 3 (2)" } } } return steps; run unit tests for your convenience, you will find an additional unit tests package. this will let you verify your code changes even without using a physical watch. see instruction below on how to run unit tests: right click on com.samsung.sdc21.stepcount (test) and execute run 'tests in 'com.samsung.sdc21.stepcount'' command. if you completed all the tasks correctly, you will see all the unit tests passed successfully. run the app after building the apk, you can run the application on a connected device to see real-life aggregated steps count measured by a smartwatch. right after the app is started, it will request for the user permission. allow the app to receive data of the activity. afterwards, the application main screen will be shown. it will automatically display today’s step count. tap on refresh button to read current steps count from health platform. you're done! congratulations! you have successfully achieved the goal of this code lab. now, you can create a daily step counter app by yourself! if you're having trouble, you may download this file: health step count complete code (119.79 kb) learn more by going to health platform.

track deadlift exercise on galaxy watch objective create a native app for galaxy watch, operating on wear os powered by samsung, using health services to track deadlift exercise. this app measures repetition count, calories burned, and time spent during the exercise. overview health services provides a simple and unified way for accessing a wide range of health and wellness related data. with health services api, you will no longer need to develop your own algorithms processing sensors data in order to compute metrics like heart rate, steps counts, distance, calories burned, and other more. these are now accessible through health services embedded on wearables operating on wear os powered by samsung. see health platform descriptions for detailed information. set up your environment you will need the following: galaxy watch4 or newer android studio (latest version recommended) java se development kit (jdk) 11 or later sample code here is a sample code for you to start coding in this code lab. download it and start your learning experience! health track deadlift sample code (122.22 kb) turn on developer mode and adjust its settings on your watch, go to settings > about watch > software and tap on software version 5 times. upon successful activation of developer mode, a toast message will display as on the image below. afterwards, developer options will be visible under settings. tap developer options and enable the following options: adb debugging debug over wi-fi turn off automatic wi-fi connect your galaxy watch to wi-fi go to settings > connection > wi-fi and make sure that wi-fi is enabled. from the list of available wi-fi networks, choose and connect to the same one as your pc. when successfully connected, tap a wi-fi network name, swipe down, and note the ip address. you will need this to connect your watch over adb from your pc. connect your galaxy watch to android studio in android studio, go to terminal and type: adb connect <ip address as mentioned in previous step> when prompted, tap always allow from this computer to allow debugging. upon successful connection, you will see the following message in android studio’s terminal: connected to <ip address of your watch> now, you can run the app directly on your watch. start your project after downloading the sample code containing the project files, click open to open existing project in android studio. locate the downloaded android project (deadlift) from the directory and click ok. check dependency and app manifest in the dependencies section of deadlift/app/build.gradle file, see the appropriate dependency for health services. dependencies { implementation 'androidx.health:health-services-client:1.0.0-alpha03' // ... } notesince the library might update from time to time, it is recommended to choose the version suggested by android studio. in androidmanifest.xml file, note the following: <queries> element <queries> <package android:name="com.google.android.wearable.healthservices" /> </queries> section with requests for necessary permissions <uses-permission android:name="android.permission.body_sensors" /> <uses-permission android:name="android.permission.activity_recognition" /> check capabilities to check what can be measured during exercise, you need to check its capabilities. follow these steps to obtain them: open deadlift.java and navigate to checkcapabilities function. prepare a listenablefuture<exercisecapabilities> instance that will query for deadlift capabilities. getcapabilities() checks exercise capabilities in exerciseclient object. public void checkcapabilities() { listenablefuture<exercisecapabilities> capabilitieslistenablefuture = null; /****************************************************************************************** * [practice 1] create listenablefuture object that will get a callback with exercise * capabilities. choose correct function from exerciseclient *-------------------------------------------------------------------------------------- * uncomment line below and fill todo 1 * (1) for checking capabilities use getcapabilities() ****************************************************************************************/ //capabilitieslistenablefuture = exerciseclient.todo 1; futures.addcallback(capabilitieslistenablefuture, new futurecallback<exercisecapabilities>() { @override public void onsuccess(@nullable exercisecapabilities result) { log.i(tag,"got exercise capabilities"); try { exercisecapabilitiesset = deadliftreader.getexercisecapabilities(result); } next, go to deadliftreader.java and navigate to getexercisecapabilities function. getsupporteddatatypes() gets measurable data types in exercisetypecapabilities. public set<datatype> getexercisecapabilities(exercisecapabilities result) throws deadliftexception { if(result == null) throw new deadliftexception("exercisecapabilities is null"); exercisetypecapabilities exercisetypecapabilities = result.getexercisetypecapabilities(exercisetype); set<datatype> datatypeset = null; /**************************************************************************************** * [practice 1] read set of deadlift capabilities. choose correct function from exercise * type capabilities. * -------------------------------------------------------------------------------------- * uncomment line below and fill todo 2 * - for checking deadlift capabilities use getsupporteddatatypes() */ //datatypeset = exercisetypecapabilities.todo 2; return datatypeset; } register an event for deadlift state update in deadlift.java, navigate to startexerciseupdatelistener() function. to get exercise updates, you need to set a listener using setupdatelistener(exerciseupdatelisener). public void startexerciseupdatelistener() throws deadliftexception { if(exerciseclient == null) throw new deadliftexception("exercise client is null"); /**************************************************************************************** * [practice 2] create listenablefuture object that will get a callback with exercise * capabilities. choose correct function from exerciseclient *-------------------------------------------------------------------------------------- * uncomment line below and fill todo 3 * for setting update listener use setupdatelistener(exerciseupdatelistener) */ listenablefuture<void> updatelistenablefuture = null; //updatelistenablefuture = exerciseclient.todo 3; if(updatelistenablefuture == null) throw new deadliftexception("update is null"); futures.addcallback(updatelistenablefuture, new futurecallback<void>() { @override public void onsuccess(@nullabledecl void result) { log.i(tag, "successfully set update listener"); ismeasurementrunning = true; butstart.settext("stop"); } check the updated event to work with the data provided by an exercise, you need to get the latest reading metrics. in deadlift.java, navigate to updaterepcount() function. getlatestmetrics() gets the latest readings from an exercise update. public void updaterepcount(exerciseupdate update) throws deadliftexception { /*************************************************************************************** * [practice 3] create map object that will get readings from the update * choose correct function from exerciseupdate class * ------------------------------------------------------------------------------------- * uncomment line below and fill todo 4 * for reading latest values from update use getlatestmetrics() */ map<datatype, list<datapoint>> map = null; if (update == null) throw new deadliftexception("exercise update is null"); //map = update.todo 4; if (map.isempty()) return; run unit tests for your convenience, you will find an additional unit tests package. this will let you verify your code changes even without using a physical watch. see instruction below on how to run unit tests: right click on com.samsung.sdc21.deadlift (test) > deadliftunittest and execute run 'deadliftunittest' command. if you completed all the tasks correctly, you will see all the unit tests passed successfully. run the app after building the apk, you can run the application on a connected device to measure actual deadlift parameters. right after the app is started, it will request for the user permission. allow the app to receive data of the activity. afterwards, the application main screen will be shown. before doing deadlifts, press the start button to track your exercise. when done, tap on the stop button. you're done! congratulations! you have successfully achieved the goal of this code lab. now, you can create a deadlift exercise tracker app by yourself! if you're having trouble, you may download this file: health track deadlift complete code (122.24 kb) learn more by going to health platform.

create a watch face using tag expressions objective learn how to create a watch face that responds based on the date, time, step count, heart rate, and battery level using tag expressions in watch face studio. in this code lab, you will start by creating a basic watch face with complications such as step count, heart rate, and battery level. later on, you will improve its functionalities and make it visually dynamic by utilizing tag expressions. overview watch face studio is a graphic authoring tool that enables you to create watch faces for wear os. it offers a simple and intuitive way to add images and components, and to configure the watch movement without any coding. watch face studio supports watch faces for the galaxy watch4 or newer version, and other watch devices that run on the same platform. tag expressions are conditions in watch face studio that allows you to customize watch face through dynamic configuration of its movement and data. set up your environment you will need the following: watch face studio galaxy watch4 or newer any supported wear os watch start your project create a new project and input project name. a blank studio will show upon clicking ok. add analog hands and index watch face studio allows you to add different components like text, image, shape, analog hands, and index in a watch face. for your watch to have the look and feel of an analog watch, add the following components: time > index (index_gentle) time > analog hands > minute (watch_min_gentle) time > analog hands > hour (watch_hour_gentle) you will see that the hands are moving automatically and in sync with the device time. select all the newly added components and click group. rename the group as group_analogtime. use a progress bar for seconds a component like progress bar can be used to show how much of the process is completed and how much is left. in this step, you will use it to show how far or close the next minute is. to use a progress bar as seconds: click add component and select progress bar. rename the component to seconds. move seconds behind group_analogtime. in properties of seconds, do the following: a. adjust the dimension (width and height) to 395. b. align the component to the center. c. drag the background slider to 0%. d. make sure that the type is a circular progress bar, otherwise change it. e. in range setting, change value to 0 and click tags beside it to open the tags window. type in [sec]. it means that the value from 0 will increment as the value of second increases. f. set max value to 59 since it is the maximum value of [sec]. notein this scenario, the progress bar seems to disappear in the canvas as the preview only use the base value, which is 0. however, you can see the component still present in run. format and position a digital clock in this step, you will learn how grouping works and affects its components. you will also learn how to format the date and time using tags. to format and position a digital clock, you need to: add a digital clock > time twice. rename them as hour and minute respectively. add a digital clock > date and rename the component as date. put them in one group and rename it as group_digitaltime. go to the properties of hour and change the text appearance to 80. do the same for minute. adjust the text size of date to 15. adjust the y placements of the individual components, so that they will look like the image below. when you make changes to a certain component, it won’t affect other components in the group. format hour to only show the time in hour: a. go to its properties and click tags button in text field. b. replace text field value with [hour_0_23_z] to show current hour with leading zero. do the same for minute but replace text field value with [min_z] to show current minute in an hour with leading zero. go to group_digitaltime placement properties and align it horizontally. after that, place it to the left. you will see the components adjusted as a group. utilize health features and battery level watch face studio also allows you to utilize data like step count, heart rate, and battery level. follow the steps below to show these real-time data using tags on texts or progress bar: battery level add a circular progress bar and rename the component as battery level. drag the background slider to 0%. go to value properties. replace the value to 0 and, in tags, input or choose [batt_per] to use current battery percentage as value. add a short text complication and rename it as battery icon. complications are set of components that can be handled as one group. in the layout properties under complication settings, click + and select icon + text. then, change the default provider to watch battery and set the type to fixed. group battery level and battery icon together. rename the group as group_batterylevel. move the group_batterylevel placement to bottom right. heart rate add a circular progress bar and rename the component as heart rate. drag the background slider to 0%. go to value properties. replace the value to 0 and, in tags, input or choose [hr] to use heart rate as value. set max value to 220 since it’s the maximum heart rate a person can have. add a text component and rename it as heart rate label. in the text field, input heart rate and change the text size to 12. change the y placement to 195. add another text component and rename it as heart rate text. in the text field, input [hr] and change the text size to 30. group heart rate, heart rate label, and heart rate text together. rename the group as group_heartrate. in action properties of group_heartrate, select apply action with tap interaction and measure heartrate as action. heart rate will be measured when the components in the group_heartrate is tapped in the device. move the group_heartrate placement to center right. step count add a circular progress bar and rename the component as step count. drag the background slider to 0%. go to value properties. replace the value to 0 and, in tags, input or choose [sc_per] to use the current percentage to goal of step count. add a short text complication and rename it as step count text. in the layout properties, click + and select text + title. select step count as the default provider and set its type to fixed. it will now show "steps" as title and step count as text. place the step count text in the center horizontally. group step count and step count text together. rename the group as group_stepcount. move the group_stepcount placement to top right. select group_digitaltime, group_batterylevel, group_heartrate, and group_stepcount folders and drag them behind group_analoghands and seconds. by doing this, the analog hands would overlap the components. make use of tag expressions you already have three progress bars that show data of battery level, heart rate, and step count. this time, you will make these features more functional by changing the progress bars' color to red and add a blinking effect to a component using tag expressions. tag expressions are conditions that allow you to change the rotation, placement, behavior, and opacity of a component based on tag values. it has the power to alter your watch face appearance dynamically as the tag value changes. tag expressions support different types of operators – arithmetic, relational, logical, and ternary. for this step, you will apply tag expressions on the color opacity. but first, you will have to: make a duplicate of all the circular progress bars (seconds, battery level, heart rate, and step count). move all the duplicates in a new group called group_colorchange. make sure that group_colorchange is behind all other groups. change individual component’s color to #ffffff or white. duplicate this group and rename as group_background. move it behind group_colorchange. drag the background slider to 16% and remove tags in value properties of each component of group_background. change group_colorchange color to #ff001e or red. group_colorchange will be used as components underneath when you set the opacity of the main components to 0 using tag expressions. group_background will serve as gap filler of each progress bar. below are conditions that will trigger the opacity of main components to become 0 and reveal the duplicated red components: change the color of battery level to red if the battery level is equal or less than 20% go to group_batterylevel and select battery level. navigate to color properties. check if the color opacity value is 100. this will serve as the base value. in tags, input [batt_per]<=20?-100:0 to subtract 100 to base value of opacity if the battery level is equal or less than to 20. otherwise, the base opacity value remains the same. in the run pane, adjust the device > watch battery to 20% or less, and you will see how the color will change to red. change the color of step count to red if the goal hasn’t reached yet and the time is already 18:00 (6:00 pm) or beyond go to group_stepcount and select step count. navigate to color properties. check if the color opacity value is 100. this will serve as the base value. in tags, input ([sc]<[sc_goal])*([hour_0_23]>=18)?-100:0 to subtract 100 to base value of opacity if the step count is less than the goal, and if the value of hour in a day is 18 or beyond. otherwise, the base opacity value remains the same. play with the time control bar in the run pane and health > steps data to see how the color will change from blue to red. change the color of heart rate and seconds to red if heart rate is below or above the normal go to group_heartrate and select heart rate. navigate to color properties. check if the color opacity value is 100. this will serve as the base value. in tags, input ([hr]<60)+([hr]>100)?-100:0 to subtract 100 to base value of opacity if heart rate is below or above the normal (60-100). otherwise, it remains the same. do the same for group_analogtime > seconds. test it in the run pane by adjusting the health > heart rate to below 60 or above 100 and you will see how the color will change to red. since you added a tap action to measure heart rate, it is a good user experience to see if this function works. hr_is_measuring is a boolean tag, which returns 1 (yes) or 0 (no) if the heart rate is currently measuring or not. to add this to the project: select group_heartrate > heart rate. go to value properties and, in tags, change [hr] to [hr_is_measuring]==1? ([sec]%2==1?220:0):[hr]. this will cause the progress bar to flash on (max value) and off (min value) every second while heart rate is measuring. once it is done measuring, it will display the heart rate data. do the same for group_colorchange > heart rate copy. prolong the battery life now that you already grasp the idea of what group and tag expression are, it’s about time for you to use both for your advantage. it is observed that the darker a watch face design is, the longer the battery life can be. to help the watch stay powered even when there’s a little battery left, you will need to decrease the opacity of the watch face when the battery level is equal to or less than 10%. to do this, you have to: select and combine all created groups and components, except for group analogtime, to a new group called group_watchface. go to group_watchface color properties and change the base opacity value to 20 in tags, input [batt_per]<=10?0:80 to add 0 to the base value of opacity if the battery level is equal or less than to 10. otherwise, it adds 80 to the base value, making the whole watch face 100% visible. adjust the device > watch battery to 10% or less, and you will see how the opacity of most of the components decreased. choose components for always-on always-on display is a feature that allows your galaxy watch to show the time without checking on it by pressing a button or lifting your hand. in watch face studio, you can choose which group or component to display onto the always-on by following these steps: go to the always-on tab, and you will see the same set of components you added and grouped. click the eye icon next to the group name to hide or make it visible. hide group_watchface. at this point, your always-on display will display a basic analog watch face whenever your watch is in idle mode. test the watch face to test your watch face, you need to: connect a watch device to the same network as your computer in watch face studio, select project > run on device. select the connected watch device you want to test with. if your device is not detected automatically, click scan devices to detect your device or enter its ip address manually by clicking the + button. you're done! congratulations! you have successfully achieved the goal of this code lab. now, you can create and design a watch face using tag expressions by yourself! if you're having trouble, you may download this file: tag expression complete project (234.24 kb) to learn more about watch face studio, visit: developer.samsung.com/watch-face-studio

integrate iot devices into the smartthings ecosystem objective learn how to create your own iot device using smartthings sdk for direct connected devices. overview the smartthings sdk for direct connected devices is provided to ease the development of devices which operate with smartthings cloud and mobile application. it is small enough to work on resource limited embedded devices. in this code lab, you will learn how to create your own iot device profile at smartthings cloud and how to implement on your test device. it is explained into three parts. the first explains how you can register and deploy to test your own iot device profile in smartthings using the developer workspace. then, it demonstrates how to create your own iot device application with smartthings sdk. the last part shows how to onboard and control instances of your device with smartthings mobile application. noteyou will name the device as code lab example for this tutorial. set up your environment you will need the following: host pc this code lab is based on ubuntu linux (x64) toolchain and board support package (bsp) for micro-controller unit (mcu) board you will use an esp32-devkitc board. you may set up the environment by referring to this github repository. github repositories for the library and references or samples of smartthings sdk for direct connected devices for c $ git clone https://github.com/smartthingscommunity/st-device-sdk-c-ref.git $ cd st-cevice-sdk-c-ref $ python3 setup.py esp32 smartthings mobile application sample code here is a sample code for you to start coding in this code lab. download it and start your learning experience! smartthings sdk sample code (2.60 kb) alternatively, you may simply get it by git cloning or downloading a zip file from this github repository. register and deploy to test your device using the developer workspace, create a device profile and customize the instructions for onboarding the device on the smartthings mobile app, and deploy devices to be tested. these configurations can be edited up until the point you submit the device for publication in the production of the smartthings ecosystem. sign in to smartthings developers sign in to smartthings developer workspace using your samsung account. create new project you need to create an integration project for a direct connected device. create a new device project for device integration. select device integration, then direct-connected. afterwards, name your project respectively. add a device profile define your device’s functionalities with smartthings capability. first, navigate and select define device profile and then click create device profile. fill the required fields with respective values. afterwards, select a capability for your device. you can get more information about the capabilities available here. notethe health check capability is automatically added for all direct connected devices. it should not be removed. the required capabilities are: switch and health check add device onboarding the device onboarding guides device owners when their device is first registering and connecting to smartthings. you can customize the screens presented by adding a device onboarding profile. the ownership validation type is also defined at this stage. you may customize the screens displayed when the device onboards via the smartthings mobile app, or just use the default values. noteuse just works or button confirm for this example. add a product info the product info defines how this device is shown at smartthings mobile app catalog. you can define device’s category and its regional availability. deploy your device to test you can start testing by deploying your device to test. there are two ways to do this: via overview menu via test > test devices you will be able to see your device in the smartthings mobile app when in developer mode only after it has been deployed for testing. register test devices you can add the identity of device for authenticating it to the smartthings cloud. this requires device information like serial number and device public key (ed25519). since the maximum number of test device is limited per user, once you’ve reached it, you should remove the existing one. this example shows how to create ed25519 key pair with sdk tools. you can get device_info.json file as a result from tools/keygen/linux/output_{ serialnumber}. linux version of key generator (keygen) utility is located at st-iot-device-sdk-c-reference/iot-core/tools/keygen/ or st-device-sdk-c/tools/keygen/. serial number for testing device would be randomly generated by this tool which has stdk + 12-digit alphanumeric format: $ cd ~/workspace/st-device-sdk-c-ref/iot-core/tools/keygen/ $ python3 stdk-keygen.py –firmware switch_example_001 use following serial number and public key for the identity of your device in developer workspace. serial number: stdk**e90w***ucx public key: nfn5x***uqusq****zhobsfaaop9***kndlnjdjrew= copy stdk**e90w***ucx from keygen output and paste it into serial number field of register a test device page. copy public key string from keygen output (nfn5x***uqusq****zhobsfaaop9***kndlnjdjrew= in this example) and paste it into public key field. generate device qr code using the device qr code could be helpful while device onboarding. qr code should have format like below. refer here for more details. urlhttps://qr.samsungiots.com/?m={your mnid}&s={device onboardingid}&r={device serialnumber} {your mnid}: 4-digit alphanumeric mnid of your account {device onboardingid}: 3-digit number onboarding id, you can find it from your developer workspace project device onboarding > other info page {device serialnumber}: device serial number which is registered at your developer workspace project you can simply generate qr code with using below python script: import qrcode mnid = 'ffff' # "ffff" is an example. you should replace it with yours onboardingid = '111' # "111" is an example. you should replace it with yours serialnumber = 'stdktest0001' # "stdktest0001" is an exmaple. you should replace it with yours qrurl = 'https://qr.samsungiots.com/?m=' + mnid + '&s=' + onboardingid + '&r=' + serialnumber img = qrcode.make(qrurl) img.save(serialnumber + '.png') qrcode.qrcode(box_size=10, border=4) write device application open and edit sample device app currently, you are doing the code lab example, which is located at apps/esp32/code_lab_example directory in the github repository. download onboarding_profile.json from the overview of your device in developer workspace. copy onboarding_profile.json file into your application directory, apps/esp32/code_lab_example/main: $ cd ~/workspace/st-device-sdk-c-ref/apps/esp32/code_lab_example/main/ $ cp ~/downloads/onboarding_config.json copy device_info.json from tools/keygen/linux/output_{serialnumber} which contains your device specific information to application directory, apps/esp32/code_lab_example/main: $ cd ~/workspace/st-device-sdk-c-ref/iot-core/tools/keygen/ $ cp output_{serialnumber}/device_info.json ~/workspace/st-device-sdk-c-ref/apps/esp32/code_lab_example/main/ firmwareversion: version string privatekey: base64 encoded ed25519 private key. this value should be paired with what you registered to developer workspace. publickey: base64 encoded ed25519 public key. this value should be same with what you registered to developer workspace. serialnumber: this value should be same with what you registered to developer workspace { "deviceinfo": { "firmwareversion": "switch_example_001", "privatekey": "dh**jkmrd5x****bav+fgoxa3qzfnw3v****jhxomd0=", "publickey": "nfn5x***uqusq****zhobsfaaop9***kndlnjdjrew=", "serialnumber": "stdk**e90w***ucx" } } open sample application source code browse in apps/esp32/code_lab_example/main/ directory. open main.c file. write your device application code this example already has cloud connection functionality using smartthings sdk apis. void app_main(void) { /** easily integrate your direct connected device using the direct connected devices sdk. the sdk manages all mqtt topics and onboarding requirements, freeing you to focus on the capabilities of your device. that is, you can simply develop a basic application by just calling the apis provided by st_iot_core layer like below. // create a iot context 1. st_conn_init(); // create a handle to process capability 2. st_cap_handle_init(); (called in function 'capability_init') // register a callback function to process capability command when it comes from the smartthings server. 3. st_cap_cmd_set_cb(); (called in function 'capability_init') // process on-boarding procedure. there is nothing more to do on the app side than call the api. 4. st_conn_start(); */ unsigned char *onboarding_config = (unsigned char *) onboarding_config_start; unsigned int onboarding_config_len = onboarding_config_end - onboarding_config_start; unsigned char *device_info = (unsigned char *) device_info_start; unsigned int device_info_len = device_info_end - device_info_start; int err; iot_gpio_init(); xtaskcreate(app_main_task, "app_main_task", 4096, null, 10, null); //create a iot context iot_ctx = st_conn_init(onboarding_config, onboarding_config_len, device_info, device_info_len); if (iot_ctx != null) { err = st_conn_set_noti_cb(iot_ctx, iot_noti_cb, null); if (err) printf("fail to set notification callback function\n"); } else { printf("fail to create the iot_context\n"); } //create a handle to process capability and initialize capability info capability_init(); //connect to server err = st_conn_start(iot_ctx, (st_status_cb)&iot_status_cb, iot_status_all, null, null); if (err) { printf("fail to start connection. err:%d\n", err); } } complete your command callback function for each capability. the command callback function should contain your device control upon each command such as led on or off control. capability example for each capability would be helpful to handle attribute command for each capability. you can find it at apps/capability_example/main. static void update_switch_state(int switch_state) { const char* switch_value; if (switch_state == switch_on) { switch_value = caps_helper_switch.attr_switch.value_on; } else { switch_value = caps_helper_switch.attr_switch.value_off; } //todo: set switch attribute value and send // // example //=============================================================================== // cap_switch_data->set_switch_value(cap_switch_data, switch_value); // cap_switch_data->attr_switch_send(cap_switch_data); //=============================================================================== } static int get_switch_state(void) { const char* switch_value; int switch_state = switch_off; //todo: get switch attribute value // // example //=============================================================================== // switch_value = cap_switch_data->get_switch_value(cap_switch_data); // // if (!strcmp(switch_value, caps_helper_switch.attr_switch.value_on)) { // switch_state = switch_on; // } else if (!strcmp(switch_value, caps_helper_switch.attr_switch.value_off)) { // switch_state = switch_off; // } //=============================================================================== return switch_state; } static void cap_switch_cmd_cb(struct caps_switch_data *caps_data) { int switch_state = get_switch_state(); set_led_mode(switch_state); } static void capability_init() { //todo: initialize switch capability with using capability sample's initializae function // // example // //=============================================================================== // cap_switch_data = caps_switch_initialize(iot_ctx, "main", null, null); // if (cap_switch_data) { // const char *switch_init_value = caps_helper_switch.attr_switch.value_on; // // cap_switch_data->cmd_on_usr_cb = cap_switch_cmd_cb; // cap_switch_data->cmd_off_usr_cb = cap_switch_cmd_cb; // // cap_switch_data->set_switch_value(cap_switch_data, switch_init_value); // } //=============================================================================== } build, flash, and monitor you can build, flash, and monitor in the console with the following: $ cd ~/workspace/st-device-sdk-c-ref $ python3 build.py apps/esp32/code_lab_example $ python3 build.py apps/esp32/code_lab_example flash $ python3 build.py apps/esp32/code_lab_example monitor or $ cd ~/workspace/st-device-sdk-c-ref $ python3 build.py apps/esp32/code_lab_example flash monitor onboard and control the device via smartthings app onboarding a. enable developer mode developer mode should be enabled on smartthings mobile application. launch the smartthings app, go to dashboard > settings. long-press about smartthings for 20 seconds. enable the developer mode, then restart the smartthings app. you can find out more information here. b. add a new device go to add device and click my testing devices or scan qr code. you can now see and add your self-published devices. control by smartthings application a. device control from dashboard you can turn your device’s led on or off by clicking the button in the smartthings app. b. device control from plugin you can control various attributes and get more detailed information from the device plugin user interface. you're done! congratulations! you have successfully achieved the goal of this code lab. now, you can control your iot devices using the smartthings app all by yourself! if you're having trouble, you may download this file: smartthings device sdk complete code (2.49 kb)