[DTH Multi-Component devices] Components not showing correctly

I know it can be difficult when you have several options in each component. My suggestion’s purpose isn’t to underestimate the impact of this situation but rather to give a workaround. I’ll let the engineering team know your comments @krlaframboise.
@orangebucket, you’ve got a good point, remember that Customer Support is open to this kind of improvement suggestions.

I had reported this issue last year and a ticket has been open ever since. While it’s awesome to see the willingness to take the feedback, it would be even better see closure in a time frame of weeks rather than months.

From the UK, the response time is weeks and they’ve historically been baffled by receiving feature requests. That’s if you know the e-mail address or can guess the one option in the app that possibly doesn’t result in your mail languishing in a Samsung mailbox indefinitely (literally - I’ve had stuff sitting there for a year).

Our only hope can be to post in here and hope what we write gets read and noticed. I like to think more of it does than we realise.

Hi, @orangebucket! Sorry for the delay, I made some digging about this situation and
you can send an email to build@smartthings.com instead to present formally your Feature Request as this is developer-related.

Ta muchly. I have done so.

When it comes to the 200 device limit, are multi-component devices considered one device?

The MCDs’ child devices appear as components under a main device. If you see there’s only one entry in the device list for this MCD, then it is considered as a single device.

The patch workaround to limit button actions shown based on the supportedButtonValues attribute no longer works for the details view.

Do you mean when you create a new device-config using the patch?
I mean, is it accepted but not applied to the presentation?

Could you share a presentation ID where you defined this property, please?

@krlaframboise, curious if your SmartThings App was recently updated?

Asking because I see something similar with the edge drivers. Displays all button actions on new version, previous version of app shows correctly. Automations/ routines display properly in both.

It turns out my presentations don’t have the patch for the details view because up until the last couple of weeks the details view only displayed the button values specified in the supportedButtonValues attribute so it wasn’t needed.

Adding the patch to the detailsView section of my presentations should solve the problem, but I haven’t tested it yet.

I’m not sure we can use the supportedButonValues patch in the detail view as it is using a state display type.
I already reported this issue as it is affecting all the integration types. As soon as I have more info, I’ll share it with you.