Alexa.Commissionable.ReportCommissioningInformation directive to your smart home add-on and you can’t handle it successfully, respond with an ReportCommissioningInformation.ErrorResponse event. For details, see Alexa.Commissionable Interface.
ErrorResponse event
In the payload for theReportCommissioningInformation.ErrorResponse, specify the type of the error and include a message with information about the error. For the list of ReportCommissioningInformation error types, see Error type values. You can send the error response in a synchronous or asynchronous response. For more details, see Alexa.ErrorResponse.
ReportCommissioningInformation.ErrorResponse payload properties
The following table shows the error response payload forAlexa.Commissionable.ReportCommissioningInformation.
| Property | Description | Type | Required |
|---|---|---|---|
type | Error type values encountered by the add-on when trying to return commissioning information. | String | Yes |
message | Error description. | String | No |
ErrorResponse event format
Error type values
The following table shows the validAlexa.Commissionable.ReportCommissioningInformation error types.
| Value | Description |
|---|---|
MAX_COMMISSIONING_LIMIT_REACHED | Endpoint was already commissioned with the maximum number of local hubs. |
FAILED_TO_BOOTSTRAP_COMMISSIONING_PROCESS | Endpoint is reachable but is unable to accept local connection. For Matter, it might mean that the endpoint failed to put the device into commissioning mode. |
ReportCommissioningInformation error types, you can use standard Alexa error types, such as ENDPOINT_BUSY, ENDPOINT_UNREACHABLE, and BRIDGE_UNREACHABLE. For details, see Alexa ErrorResponse event Error type values.
Alexa.Commissionable.ReportCommissioningInformation.ErrorResponse examples
The following examples show the payload for different error types.MAX_COMMISSIONING_LIMIT_REACHED
The following is an example error response for theMAX_COMMISSIONING_LIMIT_REACHED error type.

