Can't get my Edge custom capability switch to work - missing something?

Hi, @edleno.

There’s an open report about this issue, it is caused by the usage of separate commands, so, you need to use a setter like shown in the sample.
Remember to specify in the capability definition that the command roomSet it’s the setter of the attribute. For example:

"attributes": {
    "powerSwitch": {
        "schema": {
            "type": "object",
            "properties": {
                "value": {
                    "type": "string",
                    "enum": [
                        "On",
                        "Off"
                    ]
                }
            },
            "additionalProperties": false,
            "required": [
                "value"
            ]
        },
        "setter": "setPower"
    }
},

As a side note, this line is no longer needed, the issue about failing to recognize custom capabilities is solved.

For future reference, in Edge, if you see that the command is received in the driver’s logs but it is not handled correctly, it is due to your “capability_handlers” configuration.
If the “network error” is received but there are no logs about the event, the issue is in the capability presentation. If you have the correct configuration, then it is caused by something internal and that’s what we report.
But don’t worry, even if you had an error, we are here to help you out. Getting another pair of eyes to look at your configuration is very useful.

Please, let me know if this solves the issue in the dashboard view as well

1 Like