makes the light dim to 100 % immediately, not honoring the 10s duration option. The specific device I'm using is a Philips Hue White and Color with the Philips Hue without the bridge app as the driver. Checking the source code for that app, the duration option should be honored, which leads me to believe there is a bug in the setCapabilityValue function.
On a side note, running the corresponding flow card using the Web API works:
How is the flow card implemented? What happens if a light does not support the "duration" capability option? Will the duration option simply not be honored, or is the flow card implementation able to detect this and not expose the duration option?
I'm currently running the runFlowCardAction function as a workaround. It is running inside an app on the Homey Pro, but the token I get from this.homey.api.getOwnerApiToken() does not have the scopes necessary to perform the runFlowCardAction call, so I have to use a token created in the Homey Web App, which is not ideal. Is there a way to get a token that has the necessary scopes directly from the app using the SDK? I noticed that if I change my app's name to "com.athom.homeyscript" I get a token with the scopes I need... Am I right in assuming that this behavior is reserved for Athom authored apps only?
Calling the setCapabilityValue function as follows:
makes the light dim to 100 % immediately, not honoring the 10s duration option. The specific device I'm using is a Philips Hue White and Color with the Philips Hue without the bridge app as the driver. Checking the source code for that app, the duration option should be honored, which leads me to believe there is a bug in the
setCapabilityValue
function.On a side note, running the corresponding flow card using the Web API works:
How is the flow card implemented? What happens if a light does not support the "duration" capability option? Will the duration option simply not be honored, or is the flow card implementation able to detect this and not expose the duration option?
I'm currently running the
runFlowCardAction
function as a workaround. It is running inside an app on the Homey Pro, but the token I get fromthis.homey.api.getOwnerApiToken()
does not have the scopes necessary to perform therunFlowCardAction
call, so I have to use a token created in the Homey Web App, which is not ideal. Is there a way to get a token that has the necessary scopes directly from the app using the SDK? I noticed that if I change my app's name to "com.athom.homeyscript" I get a token with the scopes I need... Am I right in assuming that this behavior is reserved for Athom authored apps only?