Presenting Erroneous Accessory State to the User

This page is still in DRAFT state

TLDR: Your accessory should always be reachable and fully operational.

// general motivation to fail as gracefully as possible and to guarantee best uptime possible.

Using dedicated, Accessory-specific characteristic values

Some services expose characteristics that can be used to encode a "not-ready" state (e.g. AirQuality characteristic has a unknown value; or e.g. of a sensor use the not-detected state).

Using the Active Characteristic

Use the active characteristic available on most services.

Fatal Errors

In severe error cases that require user attention use HapStatusError with values of HAPStatus (e.g. service communication failure, most of the others have special meaning).