Https://graph.api.smarthings.com Failed to load devices

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@geko

Everyone has its own agenda, and there’s no guarantee that a seemingly useful SmartApp that’s not been officially reviewed and approved by SmartThings won’t abuse access to security system or other critical components inside my home. Most customers don’t have sufficient knowledge or ability to assess the risks, particularly if the source code is closed. That’s why the official review process is absolutely critical in this case.

The “official” SmartThings review / publication process does not address the security of external services.

Please see details and direct the relevant discussion over to this existing Topic, thanks!

@tgauchat

“Officially” published Third-Party services (via the method above, OAuth Web Services SmartApps) do have their SmartApps Only go through a review process (by SmartThings) before being published, which does not significantly increase trustworthiness of the service, though, because SmartThings still has no control of the actual Third-Party service. SmartThings could certify, for example, that the particular Web Services SmartApp does, in fact, only access Devices for “read-only” purposes, but that would be appropriate for a limited set of third-party services, obviously. The ones I list, IFTTT, Alexa, etc., need “control” permission, but even in the cases of published integrations, SmartThings is not able to audit the service itself to confirm their functionality, security, and data retention policies.