-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device.getCapabilityOptions(capabilityId: string) fails with Invalid capability #296
Comments
Can you share the result of |
This on a Homey Pro 2023 (10.0.0-rc.62)
|
And the same app on a Homey Pro 2019
|
Interesting finding regarding |
Some more information on this. Strangely this happens only on a new device, if the capabilityOptions for max value is not predefined in driver.compose.json. Exact error is:
After adding:
to the current_limit capability the error goes away and the device works fine. And finally, with the device already configured and removing the code from device.compose.json, the device continues to work fine. |
With a custom capability "current_limit.json":
fails with
Invalid capability "current_limit"
on Homey Pro 2023 even thou there is options in the definition json. This works fine on previous Homey Pros.Now if I add to the driver.compose.json:
The code starts working on Homey Pro 2023 also. Is this a bug?
The text was updated successfully, but these errors were encountered: