search

athombv / homey-apps-sdk-issues

This issue tracker is for Homey Developers using the Apps SDK.
21 stars 4 forks source link

Capability set to non-settable still gets action card, which always errors out #363

Closed robertklep closed 1 month ago

robertklep commented 2 months ago

I have configured thermostat_mode as follows:

"capabilitiesOptions": {
  "thermostat_mode" : {
    "getable" : true,
    "setable" : false
  }
}

However, making the capability non-settable doesn't prevent an action card for it being generated that allows setting. The card always fails though, because "Capability Not Setable" 🤦🏼‍♂️

image

Is there a way to prevent this card from being offered to the user?

As an aside: the correct spelling of the word is "settable".

robertklep commented 1 month ago

Bump.

jeroenwienk commented 1 month ago

I have configured thermostat_mode as follows:

"capabilitiesOptions": {
  "thermostat_mode" : {
    "getable" : true,
    "setable" : false
  }
}

However, making the capability non-settable doesn't prevent an action card for it being generated that allows setting. The card always fails though, because "Capability Not Setable" 🤦🏼‍♂️

image

Is there a way to prevent this card from being offered to the user?

As an aside: the correct spelling of the word is "settable".

No that's not possible. Wondering the use case here why use thermostat capability if it's not setable?

robertklep commented 1 month ago

As a read-only (status) indicator.