Custom Capability and CLI Developer Preview

[nayelyz (SmartThings Developer Support)]

Hello @SZaf,

For the DTH update, you could try the workaround of changing its name instead of creating a new device. We mentioned above that the device configuration presentation is cached, so you can also try the workaround mentioned there.

As for the available displayTypes, currently, the list is fixed, if you want to see the presentation of a predefined capability, you can use the command below to visualize the configuration in JSON format.

smartthings capabilities:presentation capabilityName -j

[SZaf]

Thank you @nayelyz

One more question: I couldn’t find any documentation regarding icons.
Below is a section from the switch capability’s JSON under dashboard. Is the ___PO_CODE_SMARTTHINGS_DREAM_SAC_SBODY_ON_T_SAMSUNG_CONNECT an icon?

If so, is there a list of all the icons for the new app, similar to http://scripts.3dgo.net/smartthings/icons/ (that is used in tiles)?

“alternatives”: [
“key”: “on”,
“value”: “___PO_CODE_SMARTTHINGS_DREAM_SAC_SBODY_ON_T_SAMSUNG_CONNECT”,
“type”: “active”

[nayelyz (SmartThings Developer Support)]

Hi @SZaf,
No, that value in the switch capability is not an icon, is part of the conventions of the predefined capabilities.

Here’s a list that was shared previously in this thread. You can use these values in the device profile metadata, for example:

{
  "name": "deviceIconTest",
  "components": [
      {
          "label": "main",
          "id": "main",
          "capabilities": [
              {
                  "id": "capabilityID",
                  "version": 1
              }
          ],
          "categories": []
      }
  ],
  "metadata": {
      "deviceType": "Fan",
      "ocfDeviceType": "oic.d.fan",
      "vid": "xxx-xxx-xxx",
      "mnmn": "SmartThingsCommunity"
  }
}

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Is there an ETA to fix these issues? It’s been 23 days since I reported bugs with the toggleSwitch, list and custom child components, while I appreciate the reproduction and submission of the bug reports, however without a fix I don’t see how to move forward.

[erickv (Erick)]

Hello, @RBoy

Following-up on this issue about setter commands from custom capabilities supporting the list display type, here are some IDE logs where the key has been sent as argument instead of the value specified at the capability’s presentation.

As mentioned before, this would be impacting the flow-control of command handlers. For example, where I could be handling commands as following:

def setTodo(String arg) {
    	sendEvent(name: 'todo', value: arg)
}

I’m forced to do this:

def setTodo(String arg) {
    if (arg == 'Do copy'){
    	sendEvent(name: 'todo', value: 'copy')
	}
    if (arg == 'Do paste'){
    	sendEvent(name: 'todo', value: 'paste')
    }
    if (arg == 'Do cut'){
    	sendEvent(name: 'todo', value: 'cut')
    }
}

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

@erickv

Following-up on this issue about setter commands from custom capabilities supporting the list display type, here are some IDE logs where the key has been sent as argument instead of the value specified at the capability’s presentation.

@erickv a couple of things:

1. I’m not seeing this happen on iOS. The command is never called in the IDE when the command is invoked on the UI.
2. As of this week, the UI isn’t updating at all on the mobile phones. The same control is showing different UI components on Android and iOS. My iOS is stuck showing a state in the detailView where as the Anrdoid is showing a stepper. The presentation file is set to a list

"detailView": [
        {
            "label": "Arm Mode",
            "displayType": "list",
			"list": {
                                     ...

The VID is 7c7c3ec0-db88-3fc2-b498-d4135a2a22dd

iOS (v1.6.49-413)

Android (v1.7.50-21)

I’ve logged out and logged back into the mobile app it’s still completely disconnected from reality. I’ve deleted the capability completely and started over and everything is still disconnected from each other.

In short, the whole thing is a mess and nothing is working as directed/documented or even in sync with each other. I don’t know the iOS, Android and VID are showing controls which are completely different from each other?

[SZaf]

@nayelyz

thank you again. Regarding the icon, can you change the DTH presentation icon with the iconURL parameter rather changing the device profile? In the api I noticed “preload” suffix before the URL which I didn’t find any explanation for.

I tried “iconUrl”: “http://cdn.device-icons.smartthings.com/Appliances/appliances11-icn@2x.png” yet it didn’t change anything (I deleted the app’s cache as you suggested).

Am I doing something wrong?

On a different note, when I tried to update the device on the app by changing the device’s name there was an error. The device is a Child device and it seems like a bug in the app because it happened with other child devices that I tried. I had to delete the device and recreate it from the Classic App.

[cscheiene]

@RBoy

As of this week, the UI isn’t updating at all on the mobile phones. The same control is showing different UI components on Android and iOS

I’m seeing this to. I have done a minor text change to my custom capability presentation. It’s been 4-5 days now. The change has not been made yet, even though the cli reports the change if I check the presentation.

I’m also seeing mismatch between ios and Android, even between devices using the same DH on Android.

Makes it very hard to test changes, you don’t know if the changes didn’t work or just hasn’t been updated yet

[nayelyz (SmartThings Developer Support)]

Hi @SZaf,
You can also set those properties in the DTH definition, for example:

metadata {
    definition (name: "DTH Icon", deviceType:"fan",ocfDeviceType:"oic.d.fan", ...) {
        ...
    }
}

You would see the icon of the sample below:

The workaround I mentioned to update the device presentation refers to changing the DTH’s name so the device can detect the last published version. Apologies for the confusion.

[cscheiene]

@RBoy

As of this week, the UI isn’t updating at all on the mobile phones

@rboy Now all my custom capabilities does not display anything in the detail view anymore. Even on Smartthings own SmartWeather Station tile the capabilities have disappeared, only standard capabilities are displayed. They still show up in the history in new app. Both ios and Android. Have you seen anything similar?

[hongtat (HONGTAT TAN)]

Yea. The custom capabilities have disappeared! Only standard capabilities are displayed!

[cscheiene]

Nice to know that it’s not only me.

Tagging @jody.albritton @erickv @nayelyz any info on this issue?

[Benjamin_Ginders]

I wonder if this is the same thing that is affecting the various 3rd party buttons/remotes as discussed here:

Ikea Tradfri Button (square)

All of my buttons now report NO info in the ST apps, just a completly blank page, other than the name. There is not even the overflow menu so cannot edit or delete. They still operate as previously, but I cannot change anything. I reconnected one, after a battery replacement, and still no controls, battery reporting, history, etc.

[SZaf]

Same here. Custom cap disappeared after changing device type (I’m not sure it’s related).

[erickv (Erick)]

Hi, @cscheiene

I’ve noticed this behavior as well, using either dth or device profiles. Also, I’ve found that running the presentation:device-config:create command will return a 400 Bad Request status code for both device configuration types (dth and profile). This has blocked recreating any integration with custom capabilities.

Both issues have been documented and reported accordingly. Thank you all for sharing.

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

At this point there is so much broken that it’s better to wait until the baseline is working again. Even the samples no longer work so it’s difficult to work on this as one doesn’t know if there’s an issue with the configuration or the platform is having trouble. I’ve lost count of the number of issues reported with the new app (across the board), hopefully we’ll start seeing issues being fixed faster than being reported. I know that there is focus to make some progress on this over the next few weeks so I’m going to wait till we get a green light to proceed again.

[jody.albritton (Jody)]

We are aware of issues with custom capabilities and are actively working to resolve them. We will make updates that might be breaking changes during this developer preview, but once things return to baseline the instructions should be valid once again. I will keep posting updates to this thread.

[milandjurovic71 (Milan)]

@jody.albritton this changes are happening in prod not dev, unless entire SmartThings is dev preview.

[jody.albritton (Jody)]

@milandjurovic71 custom capabilities are released as a developer preview in our production environment. The only way we can do beta testing with our external developers today, is in the production environment.

[Alwas]

@jody.albritton

. The only way we can do beta testing with our external developers today, is in the production environment.

Before telling users to migrate to the new app, wouldn’t it be better to make sure it works first? to have your own beta testers to make sure the new app is functional before you release it to the masses? I think you’re going about things the wrong way around.