-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
itsreverence edited this page Jun 3, 2026
·
2 revisions
Try this first:
- Restart Home Assistant after installing or updating.
- Confirm Codex Assist appears under Settings → Devices & services.
- Reload the config entry if the integration exists but the conversation entity is missing.
- Check Home Assistant logs for
codex_assistsetup errors.
Confirm your Assist pipeline uses Codex Assist as the conversation agent. Installing the integration is not always enough; the pipeline must be configured to use it.
Usually this is an Assist exposure issue.
Check:
- the target entity is exposed to Assist
- the entity is available in Home Assistant
- the device can be controlled manually from Home Assistant
- the request uses a clear name or alias
Start with one exposed light before testing more complicated devices.
Codex Assist refreshes tokens before model calls, but upstream auth can still be invalidated.
Try:
- Open Home Assistant Repairs or the Codex Assist integration page.
- Complete the reauth flow if offered.
- Restart Home Assistant if the entity remains stuck after reauth.
- Check logs for
codex_assisterrors.
HACS may cache available releases. Refresh HACS, confirm the release version, install the update, and restart Home Assistant.
Open a GitHub issue for normal bugs. Do not post tokens, cookies, private logs, or Home Assistant secrets publicly. For sensitive reports, follow the repository Security Policy.