Following as I have the same issue with one of my dimmers, and it still works.
Just got an email from SmartThings:
Some devices will see names of capabilities shown as _PO_CODE…
This doesn’t impact the functionality.
We are investigating the issue
WOW, that was fast! My devices all show normally.
Yeah, fixed for me now.
All of my routines are for lighting, sensors, buttons, etc so they all look fine. I’d contact ST support about your issue…
Yes, gone this morning.
I noticed this error for the first time today, all of my Aeotec Multisensors, both Gen 5 and Gen 6s. No other devices affected that I can see
Has there been some updates to these drivers that has broken another of my device types?
Last Updated 2023-06-14 6:52 AM BST
Hi, @Tino_Race
The team is following up on this since others have reported it as well and it seemed to be solved in the past. Once we have more info, we’ll let you know.
I’m also seeing it now for the first time.
I am trying to control the temperature level of the device using the statelessTemperatureButton. However, when I used the device profile registered with the presentation created in the device config, it is displaying with the following label. How can I change this label?
__PO_CODE_STATELESSSTEMPERATUREBUTTON_TEMPERATURE…
this is my device-config
{
"mnmn": "SmartThingsCommunity",
"vid": "ba5675a6-0c21-31c2-9627-29f5b38429aa",
"version": "0.0.1",
"type": "profile",
"dashboard": {
"states": [
{
"component": "main",
"capability": "switch",
"version": 1,
"idx": 0,
"group": "main",
"values": [],
"composite": false
}
],
"actions": [
{
"component": "main",
"capability": "switch",
"version": 1,
"idx": 0,
"group": "main",
"inline": null
}
],
"basicPlus": []
},
"detailView": [
{
"component": "main",
"capability": "switch",
"version": 1,
"values": [],
"patch": []
},
{
"component": "main",
"capability": "healthCheck",
"version": 1,
"values": [],
"patch": []
},
{
"component": "Single",
"capability": "statelessTemperatureButton",
"version": 1,
"values": [
{
"key": "availableTemperatureButtons.value",
"enabledValues": [],
"label": "LevelControl",
"range": [
0,
8
],
"step": 1
}
],
"patch": []
}
],
"automation": {
"conditions": [
{
"component": "main",
"capability": "switch",
"version": 1,
"values": [],
"patch": [],
"exclusion": []
},
{
"component": "main",
"capability": "healthCheck",
"version": 1,
"values": [],
"patch": [],
"exclusion": []
},
{
"component": "Single",
"capability": "statelessTemperatureButton",
"version": 1,
"values": [],
"patch": [],
"exclusion": []
}
],
"actions": [
{
"component": "main",
"capability": "switch",
"version": 1,
"values": [],
"patch": [],
"exclusion": []
},
{
"component": "main",
"capability": "healthCheck",
"version": 1,
"values": [],
"patch": [],
"exclusion": []
},
{
"component": "Single",
"capability": "statelessTemperatureButton",
"version": 1,
"values": [],
"patch": [],
"exclusion": []
}
]
},
"presentationId": "ba5675a6-0c21-31c2-9627-29f5b38429aa",
"manufacturerName": "SmartThingsCommunity"
}
Hello everyone.
The engineering team mentioned they found the issue and that it should be solved now, can you help us confirm, please?
Note: You should close the app completely and open it again. In the case of Android, you can also delete the app cache to force a refresh.
ok, thank you for the feedback, @Paul_Oliver
I’ll let the engineering team know.
Can you provide support access to your account, please? The engineering team needs the device ID for further investigation.
Hi, @Paul_Oliver. Following up, the team mentioned this should be fixed now, can you verify again, please?
Yes, it is fixed. Thanks for following up.
Awesome!
Thank you for taking the time to provide the requested info and help us check.
Have a great weekend!