Question about standardTile UI update in SmartThings app

First to answer your overall question - the current dev docs are here:
https://smartthings.developer.samsung.com/docs

anything older - ignore…

OK - now I follow - this has nothing to do with HUE - it has to do with a poorly maintained DTH.

OK - so the best link in that thread that comes CLOSE to working is THIS DTH:
Ubuntu Pastebin

But there are some significant problems with that DTH - The BIGGEST one is Smartthings no longer supports the ‘THERMOSTAT’ capability and instead broke it into:

So you need to start by taking that DTH linked above and modifying it to:
add all of the necessary capabilities above and then replacing instances that reference the THERMOSTAT capability with their counterparts in the capabilities you added. (In most cases just adding the capabilities in and remarking out the old thermostat capability should work - I believe the actual attributes, properties, methods, etc. of all of the new capabilities match their counterparts in the old monolithic THERMOSTAT capability.)

Just by making that change if you do it correctly - the system should take over and say - oh wait this is a standard capability - I have a way of showing that. And it SHOULD give you some basic controls. (If you don’t use the app a lot like me, this might be enough to get you going)

NOW - once you get the basics in to make it WORK, how to customize the DTH completely changed after last December. They now use ‘custom presentations’ to modify the default display of a capability. ALL Of that is currently in beta - learn more about that here:

Beyond that you’ll need someone with a lot more DTH authoring experience than I have to troubleshoot if it goes sideways…

1 Like

OK, let me try.

Thank you for your support. :+1:

Hi Nathan,

FYI. I did my custom capability based on your given resources.

Thank you for your support.

1 Like

Hello Nathan,

I discovered that the Samsung developer site has a new link for those “Hub Connected Devices” (see below link)

Is that mean I need to develop a “driver” for my ZXT-600 to operate with my Hub V3 ?

Thank you for your support.

Hi Nathan,

Sorry, I found another link “Changes to the Legacy SmartThings Platform”

May I know the time frame for phase 3?

That is suggested, yes. If you have a Samsung Connect Home or a SmartThings WiFi Hub, please consider what I mentioned in this post:

You can base on:

There’s no ETA yet for that. Please, stay tuned to the Announcements and Newsletter (subscribe at the bottom of this page).

Thanks Nayelyz

Hi Nayelyz,

I followed the instruction of the link (listed below) and try to install the SmartThings CLI but was not successful.

After I downloaded the binary for MacOS, I unzipped the file and I got a filename “smartthings”. How can I install it?

According to the instruction in step2, I need to install it and rename it.

  1. Download the appropriate binary from the
    releases
    tab of the github page.
  2. Install it on your path and rename it to “smartthings”. It does not need
    administrator privileges but of course will need to be executable.
  3. Run smartthings --help to make sure it’s working.
  4. Run a specific command with smartthings <command>

Would you help to provide more information about how to install the binary?

Thank you for your support.

You don’t need to install it, only call it for execution. Once you’re inside the directory where the file is in the console/terminal, you need to add ./ (dot slash) before the binary name.

Here are more details about how it works in the case of Unix-based OS.

Hi Nayelyz,

I’m following this tutorial and installing POP OS on my Raspberry pi in success.

However, I failed to complete this command.

smartthings edge:drivers:assign

And I got this message (Please see attached screenshot)

May I know what’s going on?

Apologies, the command in the post was incorrect, the assign command belongs to the channels endpoint:

smartthings edge:channels:assign

I already updated the original post, thanks for pointing this out.

Hi Nayelyz,

OK, it works now. I can walk through all steps.

Then, I have several questions about the new implementation.

  1. For normal users, When a new Z-Wave device is included in the network, what criteria to determine the newly developed UI (lua) or UI (groovy) is loaded for the device?
  2. During the development stage, a Z-Wave device is included in the network and newly developed UI (Lua) is loaded. If there is any UI or feature is updated (or modified), how can the developer refresh the UI?

Do you mean how it’s determined which to use the DTH or Edge driver for the device?
This is the order that is followed when the discovery process is running (this means when the user taps on “scan nearby” or accesses the brand and device through the catalog in the ST app):

  1. Self-published DTH (these are the DTHs that the user saved and published in his IDE)
  2. Edge driver installed
  3. Stock DTH (DTHs officially published by the manufacturer or SmartThings)

Wherever the matching fingerprint is found first, it will become the device’s handler/driver.

It depends:

  • If you make changes to the device profile (add/remove capabilities), you might have to clear the ST app cache (Android devices).
  • If you’re using custom capabilities and you update their presentation, if you’re using a custom VID, you need to create the device-config again. (see more details here)

Note: For all options, you need to package, publish and install the driver again.

Let me know if you have any issues with the update of the device UI and we can discuss it further.

Thanks nayelyz,

Finally I did the following steps

  1. linked up with Github account for the device handler source code
  2. Created a “Product Info”
  3. Have an approved brand

Before I publish my device for public users, how can I test (walkthrough) all steps at first internally?

I would like to download the “self-assessment checklist” but the link is not worked.

Thanks

Your Publish Request is using a DTH, correct?
I’m checking with the engineering team for more details about the “self-assessment checklist”. As soon as I get their feedback, I’ll let you know. :smiley:

Hi Nayelyz,

Yes, I attached DTH for Publish request. Is that I can test it internally before open to the public?

I also search the keyword in the supporting site and I can see some link that is related to the Z-Wave device. However, this link is not working. Would you help to review this link?

https://developer-preview.smartthings.com/edge-device-drivers/search.html?q=device+Profile&check_keywords=yes&area=default#

This issue is already reported. For now, when you use the search bar and click on one of the results, you need to correct the URL. Eg.
If we click on “Z-Wave Class”, instead of:
https://developer-preview.smartthings.com/edge-device-drivers/zwave/deviceundefined?highlight=device%20profile
We need to use:
https://developer-preview.smartthings.com/edge-device-drivers/zwave/device.html

Hi Nayelyz

self-assessment checklist

Would you help to forward the checklist for our reference?

Hi, @westwoodhk. I sent you a DM with more information, please check it and let me know if you have any doubts.