Presentation is not rendered on the detail view

Developer Programs Support
#1

@nayelyz could you please tell me what is wrong with this simple presentation

{
    "dashboard": {
        "states": [],
        "actions": []
    },
    "detailView": [
        {
            "label": "Baskets",
            "displayType": "list",
            "list": {
                "command": {
                    "name": "chooseBasket",
                    "alternatives": [
                        {
                            "key": "both",
                            "value": "Both",
                            "type": "active"
                        },
                        {
                            "key": "top",
                            "value": "Top",
                            "type": "active"
                        },
                        {
                            "key": "bottom",
                            "value": "Bottom",
                            "type": "active"
                        }
                    ],
                    "argumentType": "string"
                },
                "state": {
                    "value": "baskets.value",
                    "valueType": "string",
                    "alternatives": [
                        {
                            "key": "both",
                            "value": "Both",
                            "type": "active"
                        },
                        {
                            "key": "top",
                            "value": "Top",
                            "type": "active"
                        },
                        {
                            "key": "bottom",
                            "value": "Bottom",
                            "type": "active"
                        }
                    ]
                }
            }
        }
    ],
    "automation": {
        "conditions": [
            {
                "label": "Baskets",
                "displayType": "list",
                "list": {
                    "alternatives": [
                        {
                            "key": "both",
                            "value": "Both",
                            "type": "active"
                        },
                        {
                            "key": "top",
                            "value": "Top",
                            "type": "active"
                        },
                        {
                            "key": "bottom",
                            "value": "Bottom",
                            "type": "active"
                        }
                    ],
                    "value": "baskets.value",
                    "valueType": "string"
                }
            }
        ],
        "actions": [
            {
                "label": "Baskets",
                "displayType": "list",
                "list": {
                    "alternatives": [
                        {
                            "key": "both",
                            "value": "Both",
                            "type": "active"
                        },
                        {
                            "key": "top",
                            "value": "Top",
                            "type": "active"
                        },
                        {
                            "key": "bottom",
                            "value": "Bottom",
                            "type": "active"
                        }
                    ],
                    "command": "chooseBasket",
                    "argumentType": "string"
                }
            }
        ]
    },
    "id": "winterdictionary35590.baskets",
    "version": 1
}
#2

obsolete.

there are several issues:

  • one of them in the capability itself. it just drives the ST app crazy.
  • the second one is about translations, already reported in another thread.
#3

Hi, @veonua!

What happened after changing the command name to the correct one (“setBaskets”)?
Did you create the translations after the capability and with the correct references (attribute/command name)?

#4

of course not.
The custom capability process is undocumented, overcomplicated contains many duplications, and fails in various unexpected ways.
So I’ll wait until ST will finish chances on your side

#5

We would appreciate it if you could share specific comments about this so we can improve the documentation. The custom capability development comes from long ago and there’s a tutorial about it based on the DTH migration (custom attributes and commands).
I already reported we need more info regarding translations, in the case of new capabilities, their English translation is generated automatically.
So far, the only change considered might be regarding the label (I don’t have more info about this). The base function of the custom capability should be ok.