So, before, it showed both in the same format? I don’t have info about that, if this happens for all the devices, I think you should report it to the ST Customer Support team, they handle the issues with the SmartThings app (non-developer related).
Can you share the ID of that custom capability? I’ll check that behavior and also the one of the multi tiles.
it was created in feb 18
{
"dashboard": {
"states": [
{
"label": "{{switchAllOnOff.value}}"
}
],
"actions": [
{
"displayType": "standbyPowerSwitch",
"standbyPowerSwitch": {
"command": {
"on": "All On",
"off": "All Off"
},
"state": {
"value": "switchAllOnOff.value",
"on": "All On",
"off": "All Off",
"valueType": "string"
}
}
}
],
"basicPlus": []
},
"detailView": [
{
"label": "All Switch On-Off",
"displayType": "toggleSwitch",
"toggleSwitch": {
"command": {
"name": "setSwitchAllOnOff",
"on": "All On",
"off": "All Off",
"argumentType": "string"
},
"state": {
"value": "switchAllOnOff.value",
"valueType": "string",
"on": "All On",
"off": "All Off"
}
},
"state": null
}
],
"automation": {
"conditions": [
{
"label": "All Switch On-Off",
"displayType": "list",
"list": {
"alternatives": [
{
"key": "All On",
"value": "All On",
"type": "active"
},
{
"key": "All Off",
"value": "All Off",
"type": "active"
}
],
"value": "switchAllOnOff.value",
"valueType": "string"
}
}
],
"actions": [
{
"label": "All Switch On-Off",
"displayType": "list",
"list": {
"alternatives": [
{
"key": "All On",
"value": "All On",
"type": "active"
},
{
"key": "All Off",
"value": "All Off",
"type": "active"
}
],
"command": "setSwitchAllOnOff",
"argumentType": "string"
}
}
]
},
"id": "legendabsolute60149.switchAllOnOff1",
"version": 1
}
ok, I made a test with a capability I created long ago as well. In my case, the button changes from blue to gray. The design changed, though (I would need to confirm that).
Have you checked if clearing the app’s cache helps with the status?
Clearing the cache doesn’t fix anything.
The only thing I have seen is that the switch stock capability has a different type of display in the detail view:
"detailView": [
{
"label": "{{i18n.label}}",
"displayType": "standbyPowerSwitch",
"standbyPowerSwitch": {
"command": {
"on": "on",
"off": "off"
},
The custom capability:
"detailView": [
{
"label": "All Switch On-Off",
"displayType": "toggleSwitch",
"toggleSwitch": {
"command": {
"name": "setSwitchAllOnOff",
"on": "All On",
"off": "All Off",
"argumentType": "string"
},
And indeed I have now seen that all the custom capabilities that have the “displayType”: “toggleSwitch”, are now displayed the same 
Will I have to change them all???
Would you want to change them only because of the design? Let me confirm with the team if this is permanent.
About the icon remaining blue, I think it’s because of the alternatives, my capability has them configured:
"detailView": [
{
"label": "Power",
"displayType": "toggleSwitch",
"toggleSwitch": {
"command": {
"on": "powerOn",
"off": "powerOff"
},
"state": {
"value": "powerSwitch.value",
"valueType": "string",
"on": "On",
"off": "Off",
"label": "{{powerSwitch.value}}",
"alternatives": [
{
"key": "On",
"value": "Power On",
"type": "active"
},
{
"key": "Off",
"value": "Power Off",
"type": "inactive"
}
]
}
}
}
]
I will create another one to confirm, but before, it changed based on the on/off, without alternatives, right?
Before, It changed color perfectly and also the type of button was identical to the switch
Refresh now causes all capabilities to spin, and will flag them with the broken cloud if they don’t emit an event quickly enough. Once the cloud is there, an event won’t clear it - you have to return to the dashboard and then go back to detail view. Maybe this works with a simple, fast responding device like a switch, but it’s pretty awful with a slower or sleepy device.
On a positive note, the detail view is now respecting component labels. Pool in that screenshot is the re-labeled Main component. Maybe that happened a while ago, but this is the first that I’ve noticed it.
Thanks for sharing this issue. I’m already checking it with the engineering team. Just to confirm, this is a Z-Wave device working with Edge, right?
Correct, but as @K_White points out I’m seeing it on zigbee and LAN too. I don’t have much left using a DTH, so can’t comment on Edge vs DTH.
My vote is that the prior behavior was perfect. Previously Refresh gave a brief animation in the app and that was all.
I have verified that the displayType: “toggleSwitch” still works fine on another phone that has the previous android app version
New app version
Previos app versión
The problem with refresh reported by @philh30, in phone with previous app version refresh works fine too
Hi @nayelyz,
Do you know something new about if these changes in app for the displayType will be permanent?
It is to know if I have to modify the presentations of all the custom capabilities by adding alternatives or change to another displayType.
As they are now displayed in the app, it leads to errors in the interpretation of the state.
Thank you
Sorry for the delay, there are still things pending to confirm but, so far, I know the design change is permanent, the one that would look like the “Switch” capability is the “Switch” display type.
About the button being colored all the time, adding the alternatives solved the problem, but I’m still confirming with the team if that’s expected or not.
I made a copy of your capability (adding the alternatives) and the status changes correctly:
commonsmall09402.switchAllOnOff1
Well, then I have quite a bit of extra work ahead of me!!
A post was split to a new topic: [Custom capabilities] NumberField displayType doesn’t show the unit
I have found this oddity in a zigbee bulb display, the colour temperature is showing as if the device is on, clearly it is not, should it not be greyed out like the rest of the display
If this is not urgent, please let me confirm with the team if this is expected and if we need to set that configuration or not.
I’m not sure if this is a behavior change due to the last app update, do you remember what happened in previous versions?
I never noticed this behaviour before Nayelyz, i am sure if i had seen it previously i would have reported it as it appears incorrect to the state of the device
The device is using a standard Smartthings driver not a Community created driver
I notice that supportedButtonValues is suddenly being ignored for the quick controls in the Details View again. That’s a real frequent flyer.
It just feels like there has been a significant update to the plugin recently and it sucks big time.
