public enum HomeAvailability

Matter commissioning works and nothing else does. The graph is empty; no trait can be read or written.

This is what Android reports by default, and it is the most important distinction in this enum. Google Play services can commission a Matter accessory into the user’s Google Home with no setup at all, but reading or controlling that accessory afterwards needs the Google Home APIs, which need a Google Cloud project and a Home Developer Console registration that only the app’s developer can create.

Reporting AVAILABLE here would make the constant mean something entirely different on Android than on iOS, and an app written against the iOS meaning would show an empty home with no explanation. See SmartHome.getConfigurationProblems() for what to enable.

Everything is authorized and there are no homes to show.

Its own state rather than an empty AVAILABLE, because it is both common and actionable: HomeKit exists on every iOS device, so “supported” is not a useful answer to a user who has never opened the Home app. Send them to SmartHome.openEcosystemApp().

A local, app-private simulated home. Reads and writes work and are durable, but nothing outside this app can see the accessories and no physical device is involved.

Reported by the simulator, the desktop ports and the JavaScript port. The simulator can be scripted to report any other constant in this enum, so an app’s recovery branches are reachable without a device.

The user was asked and said no.

Its own state rather than PERMISSION_REQUIRED, because the recovery is different and the wrong one gets nowhere: iOS asks for HomeKit once and never again, so an app that answers a refusal by calling SmartHome.requestAuthorization() gets the same refusal back with no prompt shown and no way for the user to see what is being asked. Send them to SmartHome.openHomeSettings() instead.

New constants go after this one: the ports carry these across as ordinals.

Nothing has connected to the backend yet, so there is nothing to report. Call SmartHome.refresh(), which connects.

Its own state rather than PERMISSION_REQUIRED, which iOS reported on every cold launch: creating HomeKit’s manager is what prompts, so until something does, this process cannot tell a user who has already authorized from one who has been asked and refused from one with no home set up. Answering “not asked” for all three sent an app that follows the documented branch into requestAuthorization() when the user had already answered, and iOS asks once – so nothing appeared on screen and the app returned having done nothing.

Last in this enum, and new constants go after it.