Authorize a local AI application

Authorize the application

1. Open the compatible AI application on your computer and connect it through the local adapter supplied for that application.
2. When the application asks for the home hub’s encrypted local credential, provide it only if you trust the application and want to grant owner-level access to installed devices.
3. Start by allowing the application to read devices and capabilities. This lets it enumerate installed devices, known capabilities, and recorded room identities.
4. Only after device reads work, authorize supported actions for the device you intend to control.

What you can expect after authorization

• The application can read locally observed device information while ALYT Cloud is unavailable.
• The application can request supported actions for installed devices, but an accepted request does not prove the device physically completed it.
• The adapter does not replace ordinary ALYT controls or local routines, and other existing local clients can remain connected.
• If you restart the hub, previous action identities are no longer valid, and you must reconnect and rediscover after a changed home binding.

Use readings and actions carefully

Readings can be known, stale, or unknown. A refresh request is not proof that an older reading is current. Observation pages show the latest readings, not a complete historical event log. If you request an action, check the current observations and existing results after a timeout or disconnection before sending another one. Separate requests can succeed or fail independently.

Matter devices expose their standard features to ALYT. The controls you can use depend on the features reported by the actual device. Vendor-specific extensions may need separate support.

Troubleshooting

1. If the service is absent, keep using ordinary ALYT controls and ask your installer or developer to check the hub and adapter.
2. If the credential is rejected, confirm that you are using the home hub’s encrypted local credential for the current bound home and that you are giving it only to the adapter, not to a model conversation, support log, public file, or shared configuration.
3. If the application reports an unknown outcome, wait for current observations, then check whether the device changed state before trying again.
4. If you need to withdraw access, disconnect the application and remove its access to that credential. If the credential has been exposed, ask your authorized installer for credential recovery.