from the integration page, it is not

[eternal forum]

You make a valid point. SmartThings is fundamentally different from most integrations because it's not just a single manufacturer's platform - it's an ecosystem with many manufacturers building on it. Samsung continuously expands it through official capabilities, samsung capabilities, and third-party developers contribute as well. This complexity justifies having a dedicated Discord server.

The reality is that this server already appears in nearly every GitHub issue discussion about SmartThings, so it's widely known within the community anyway. Adding it to the documentation would simply streamline the path for users instead of making them discover it through trial and error.

This is analogous to how Zigbee issues are better handled by directing users to the zigpy project's GitHub Issues (https://github.com/zigpy/zha-device-handlers/issues/new?template=device_support_request.yml) rather than to the main HA repository. The point is that complex integrations need dedicated issue handling and support channels - for SmartThings that's Discord, for Zigbee that's a separate GitHub organization. Pointing users to generic documentation doesn't actually solve their problems - it just adds an extra step when dedicated support channels already exist for exactly this reason.

Including a link to the SmartThings Discord in the official documentation would simply acknowledge where the proper support workflow actually happens.

[vagrant lantern]

I see your point. I think it's fine to add it.