Hello everyone,
I’m facing a strange and persistent issue with the core conversation integration. My goal is to set up custom sentences for my voice assistant, but I’m unable to access the configuration UI.
My Home Assistant version is: 2025.10.1
The Problem:
The “Configure” button for the Conversation integration is missing from the Settings > Devices & Services page.
When I try to access the configuration page directly using the URL (/config/config_flow_start?domain=conversation), I get a completely blank white page. This is not a 404 error; the page is served but fails to render any content.
This happens on multiple devices (Android phone, PC) and different browsers, so it’s not a client-side cache issue.
What I’ve already tried (troubleshooting steps):
Verified the integration is loaded: The entity conversation.home_assistant exists and is visible in the Developer Tools > States page. This confirms the backend component is running correctly.
Checked configuration.yaml: My setup uses default_config:, which should automatically load the conversation integration. I also tried to explicitly add conversation: to the configuration file, but this did not solve the issue.
Restarted in Safe Mode: The blank page issue persists even in Safe Mode. This rules out any conflict with custom integrations (HACS) or custom themes.
Reinstalled Home Assistant Core: I ran the ha core reinstall command via the terminal. The process completed successfully, but the problem remains exactly the same after a full restart.
Checked Logs: I have checked the logs at Settings > System > Logs after a restart and while trying to access the blank page, but there are no critical errors or obvious entries related to conversation or a failing frontend component.
My Conclusion:
It seems the backend of the conversation integration is working, but the frontend part responsible for its configuration UI is broken in a fundamental way that even a core reinstall doesn’t fix.
Has anyone ever encountered such an issue? Is there any other place to look for the root cause, or a way to safely and manually reset the configuration entry for the conversation integration from the backend?
Thanks for any help you can provide.