Hi, I have two questions related to the official IKEA scroll integration and compatibility with custom drivers. As you may know I made a custom driver for it, way before knowing there would be official support.
The official integration has tailor made icons and there’s a mention of a custom plugin apparently tied to a device-specific presentation provided by SmartThings.
Right now stock drivers are using an embedded device configuration in the profile that references icon://button_wheel and icon://button_multi. I could certainly add that to my custom driver to have the new icons.
The question: Are they documented somewhere? Are they like capabilities that can be deprecated / removed? What would happen if they are removed?
2. The custom presentation
Apparently for the scroll they are replacing the embedded configuration with a custom presentation used by a custom plugin.
Here comes my problem: while I could add the icons URLs to my profile I cannot add the custom presentation because I use a custom capability to run scenes depending on the amount scrolled and the SmartThings presentation doesn’t know about my custom capabilities of course. Meaning users would not be able to use the added features from the app and would need to use the Rules API which is not user friendly.
The question: Is the custom plugin of the app tied to that specific custom presentation? I was expecting something more generic that would work just by detecting the knob capability. Or can I somehow “extend” the custom presentation so the app includes my automation conditions and still enjoy whatever features that custom plugin brings?
There’s no documentation regarding the icons.
What do you mean by capabilities being removed? Are you referring to the usual capabilities or the properties of the device config, or the icon URL changing?
I checked the presentation, and didn’t see anything out of the usual except for the icon URL.
I would need to check with the internal team if there’s a special plugin for these devices.
It would help if you had a screenshot of how the device looks using that specific driver, if possible (I don’t know exactly when this change will be released to production but I can investigate to compare the difference if you have this device at hand).
I meant the icons, if there’s a URL change for instance and I’m not aware of that. Capabilities are documented and even the CLI warns you if a capability is deprecated to stop using it. I guess the app will just use the category icon if the specified URL no longer exists so it’s probably nothing to worry about.
Edit: I tested specifying a non existing icon URL, it uses a generic icon but nothing breaks. No problem then.
Yeah, we will have to wait since my SmartThings app is the production version and can’t see any custom plugin yet. Just wanted to anticipate a potential issue. From github comments it looks like the custom plugin adds instructions to use the device, if it’s just that and the knob can still be configured with the user interface it’s not a problem either.
I asked the engineering team about this, and they mentioned that we cannot guarantee they won’t change. So, they suggest using only documented features or relying on changes in the official Edge Drivers to see if the URL is affected.
I also asked about this, and they mentioned that this change is only for the likea scroll wheel and is configured according to the likea hardware configuration, so, it cannot be used in another context.
Also, when you open the device details, for certain special features like this to appear, the device config must meet specific conditions. So, we cannot guarantee it will using your config.
For example, for the Video plugin, a special property called dpInfo must be included in the device config: Struggling with getting devices live - #11 by nayelyz
