Skip to main content
Developer DocumentationCertify and Publish Your DeviceSmartThings APIEnterprise API
Certify and Publish Your Device

Get to Know the Certification Process

Have a question or need help?

Contact us at partners@smartthings.com for assistance.

Before Certifying Your Integration​

  • Self-Testing: Complete all QA and beta testing before submitting your product for WWST certification. Ensure that your device contains all required Capabilities for your device category and does not contain any custom Capabilities. You should not consider certification as an opportunity for testing functionality of your product. If you fail certification testing with the Authorized Test Provider, there may be associated costs for re-testing your integration.

    ✅ The SmartThings Test Suite offers a comprehensive test suite for self-testing, and in some cases may eliminate the need to send your product to an Authorized Test Provider. The Test Suite enables you to thoroughly test your products’ capabilities across various scenarios, helping identify and address potential issues before deployment. Visit Test and Certify With the SmartThings Test Suite to learn more.

  • Approved Brand: Your integration must to be published under a valid brand name. You must be an authorized representative of the brand. Ensure your brand is approved prior starting a certification request.

  • Product Policies: Even if functional requirements are met, certification may be denied if it violates our Product Policies or compromises the value of SmartThings.

  • Product Delivery: If your products do not qualify for self-test certification, you must send two of each model of your product to our Authorized Test Provider before testing can proceed. If you plan to apply for certification for multiple devices with similar functionality (such as different colors or shapes), your products may qualify for Certification by Similarity (CbS). After submitting your primary device for certification in the Console, please submit each variant device for certification. When submitting through the Console, you will have the opportunity to indicate that your variant device qualifies for CbS.

  • Other Agreements: Besides the Samsung Account Privacy Policy and SmartThings Developer Terms of Service agreements you accepted to become a SmartThings Developer, there may be additional legal agreements required.

The Certification Process​

important

If using the SmartThings Test Suite to self-test your product, be sure to run all relevant Test Suite tests, and associate your test results with your product before submitting your certification request.

Submitting a Matter device to CSA ITL?

CSA tests all Matter devices for Works with SmartThings compliance on your behalf at no cost to you. Learn more about this alternative certification path at WWST Certify Matter Devices via the CSA ITL.

  1. Select an Existing Device Profile and Edge Driver
    After joining your device to your hub, we recommend starting the certification process with the Edge Device Builder. This tool will help you select an existing Device Profile and Edge Driver that best fits your device. If you need to customize an existing driver, contact us at partners@smartthings.com before starting. Be sure to thoroughly test your device before submitting for certification.

  2. Test Your Device
    The SmartThings Test Suite enables automated certification testing. In many cases, completing the required tests may qualify your products for no-cost WWST certification, eliminating the need to send your device to our Authorized Test Provider.

  3. Submit Your Certification Request in the Certification Console
    After selecting a Device Profile and Edge Driver, you are ready to create a certification request in the Certification Console. From the Console, add your product information and complete a certification request. If you are using the Edge Device Builder, some device info will be auto-populated for you. Our certification team will review the submitted application according to our Product Policies. If there is an error in your application, we will guide you on how to correct it.

    info

    If you are submitting a device that uses the Matter protocol but has not yet received Matter certification, you may still submit a WWST certification request. If your device passes WWST certification testing, your device will be published to the SmartThings catalog only after your device has received Matter certification and is registered in the CSA Distributed Compliance Ledger (DCL).

  4. (Conditional) Ship Your Device + Third-party Testing
    Depending on your SmartThings Test Suite results, your certification request may be passed to an Authorized Test Provider, who will issue you a price quote for certifying your device. After accepting your quote, ship your device to the Authorized Test Provider according to the instructions (may vary based on region). Our Authorized Test Provider will begin certification testing once they receive your device. Test results will be delivered to you within 10 working days. If a re-test is required, a quote for additional tests will be issued.

  5. Publish Your Device
    Your product will be automatically published in the SmartThings catalog once certified and will be permitted to use the WWST logo. Please contact us at partners@smartthings.com if you would like to schedule a publishing date.

Device Testing​

Z-Wave + SmartThings Hub

If you are using a SmartThings Hub to connect with your Z-Wave device, the following Z-Wave Plus V2 features are not supported by the SmartThings Hub:

  • Z-Wave Long Range star network
  • SmartStart onboarding
  • Over-the-Air (OTA) updates

With the SmartThings Test Suite​

The SmartThings Test Suite automates WWST product testing, ensuring device compatibility with the SmartThings platform. The Test Suite certification path may not require you to send your product for third-party testing, and in many cases completing the required tests qualifies your products for WWST certification at no cost to you.


The Test Suite currently supports the following integrations: Matter, Zigbee, Z-Wave, LAN, MQTT, and Cloud Connected Devices (SmartThings Schema).

To learn more about how to certify your device using the SmartThings Test Suite, visit Test and Certify with the SmartThings Test Suite.

With our Authorized Test Provider​

If you are not utilizing the SmartThings Test Suite, you must ship your device to our Authorized Test Provider for device testing.

The Authorized Test Provider will validate that your product complies with the Works with SmartThings performance requirements. After the test provider finishes testing, they will provide you with a copy of the results and will send the results to the WWST team for review. This process takes about 10 working days.

If your product does not pass the test plan, you will be provided with re-test instructions. After correcting any issues, you can request a re-test. A re-test will check only the failed items.

tip

Before submitting your device for certification, you can obtain a list of all test cases associated with a particular Capability by submitting a support ticket.

Authorized Test Provider Price Quote​

The Authorized Test Provider will issue a price quote for certifying your device. See the pricing guide for estimated test costs. Once you accept the quote, the Test Provider will provide guidance on shipping your product. If you deny the quote or do not respond to the quote within 90 days from when you originally submitted your certification request, your certification request will be canceled at the discretion of SmartThings.

The test plan and test scope are determined by the following:

  • The type of device and the functionality that you use to connect with SmartThings
  • The Capabilities that your product supports
  • The technical specifications of your product
  • The compatibility of countries in which you want the product published
  • Any additional work according to the characteristics of your products
note

Multiple devices sharing features may save time and cost with the Certification by Similarity (CbS) program.

Ship Your Device​

After accepting your certification quote, the Authorized Test Provider will provide guidance on shipping your product. Depending on the size or type of product, you may need to ship either the entire product or a working, representative component. At least two identical devices must be shipped to confirm the normal operation of the product. Functional tests are provided in the United States and South Korea. You can choose either region. If possible, we recommend a location close to the market where the product will be released.

info

Direct Connected Devices that require supplemental testing may be sent to partner laboratories in Germany or China for security review.

Testing Guidelines​

All integrations will be thoroughly tested as part of the WWST certification process. Specific testing will be determined based on the type of product you submit for certification. For example, testing for motion sensors will be different from light bulbs.

Devices

Hub Connected
  • Pairing and Onboarding
  • Control via Capabilities
  • Verification
  • Device Reset
  • UI/UX Content
    • Cloud Connected
  • Onboarding
  • Control via Capabilities
  • Cloud Connectivity
  • Rate Limit Compliance
    • Direct Connected
  • Pairing
  • Control via Capabilities
  • Security Review
    • Mobile Connected
  • Pairing Connectivity (including reconnection by proximity BLE)
  • Control via Capabilities
  • UI/UX Content

    • Connected Services

    		OAuth
  • Authorization Content
  • Privacy Policies
  • Rate Limit Compliance

    • Publish Your Device​

    Hub Connected and Cloud Connected Devices will automatically be published to the SmartThings catalog once certified.

    When certification is complete, the Works with SmartThings logo can be used for your product and package. The logo and guidelines can be downloaded as part of our press kit. SmartThings compatible (legacy program) and non-certified products are restricted from using the logo. If you want to use the logo, please follow the Works with SmartThings certification procedure above.

    Certified products can be displayed in the SmartThings app and website, helping customers find the products they need. In order to expedite the process, we have created this form to collect the following product information:

    • Lifestyle Images
    • Product Descriptions
    • Product Images
    • Brand Images
    • Buy Now Links

    Additionally, customers must be able to contact you with support questions. Ensure your integration, support URLs, and contact information are included.

    Additional information​

    Tracking Your Certification​

    After you submit your product for certification, you can view your certification request from the Certification page. You can track the status of your certification request in the status column. See below for an explanation of status codes:

    • PENDING: The certification request has been received. The test provider will issue a quote.
    • APPROVED: The product has passed certification and the WWST logo may be used on products.
    • REJECTED: The product did not pass certification. You can resubmit once you’re ready to try again.
    • CANCELED: Either you, someone in your organization, or the SmartThings team canceled the request.

    Stale Certification Requests​

    Certification requests awaiting a response from you may be closed after 90 days from the original submission date at the discretion of SmartThings.

    Rejection​

    If we reject your submission, review the Testing Guidelines. Once you have verified your changes, you can re-submit your device for WWST certification. Note: fees may be incurred by the Certification vendor for multiple rounds of testing. For getting additional troubleshooting support is needed to complete certification, visit the SmartThings Developer Documentation or Community forums. If you believe we have erred in our rejection, you may file an appeal using this form. Filing an appeal is not a guarantee of success, but we will give your appeal fair consideration.

    Release Management​

    You cannot change your integration after certification is complete. In order to upgrade your integration or change the content, you will need to version your WWST certification submission using the Developer Workspace. For more information, visit the Publish section of the Developer Workspace.

    [For Custom Edge Drivers Only] Submit a Pull Request​

    important

    This step applies only to Hub Connected Devices that are seeking to create a new Device Profile or add a sub-driver.

    All other device integrations, including Hub Connected Devices built with the Edge Device Builder, visit Submit a Certification Request - no pull request is required.

    Submit a pull request containing your Edge Driver changes against the SmartThingsEdgeDrivers public repository. You will be entering your pull request URL into the Certification Console in a later step. Your pull request will automatically be merged once your device is certified.

    ➡ Each device seeking certification must have its own pull request.

    ➡ Ensure your pull request code adheres to the Code Formatting and Submission Criteria outlined below.

    ➡ Thoroughly test your device behavior.

    ➡ Submit your pull request containing your changes against the SmartThingsEdgeDrivers public repository. By submitting a pull request, you represent that you have the right to license your contribution to SmartThings and agree that your contributions are licensed under the Apache 2.0 license.

    ➡ After submitting your pull request, you will be asked to agree to the SmartThings Individual Contributor License Agreement before your contributions can be merged. By submitting a pull request, you represent that you have the right to license your contribution to SmartThings and agree that your contributions are licensed under the Apache 2.0 license

    ➡ Once your device is certified, your pull request will automatically be merged and your Certified Device will be available publicly in the SmartThings app.

    You will also be asked to associate your product with a driver and fingerprint in the Console. The driver package is uploaded and associated with your organization ID during the development process using the SmartThings CLI.

    If your driver and fingerprint do not appear in the Console dropdown menu when creating your product in the Console, you can use the following command in the SmartThings CLI to upload your driver and associate it with your organization ID:

    smartthings edge:drivers:package [path_to_dir] -O [organization_id]