Correct, I fear…
I presume, for example, that Chamberlain wants SmartThings to solidly prevent linking Amazon Alexa to the open/close Commands, for both security and safety. As we know, currently Alexa doesn’t have native garage door or lock controls, but we can easily sync a Virtual Switch (“Alexa, turn garage on.” = close the garage door). I believe that Chamberlain will not allow any such workaround or hack to be permitted, and thus, a MyQ instance will have to be restricted to use only with officially vetted & published SmartApps.
This is a significant fundamental change to the SmartThings Device:Capability paradigm which should make any manufacturer / model of device that conforms to a standard Capability swappable with any other, in all SmartApps that do not use any custom Commands, Attributes or Events for that device.
I believe that SmartThings is facing the same challenge to accommodate Nest’s restrictions.
I suppose this sets the stage – and precedent – for the platform to handle all sorts of special cases, but every special case moves SmartThings further and further away from being an “open” system with an abstracted device type layer; on the other hand, SmartThings could avoid precedent here by playing hardball and pushing back – hard – on Chamberlain.