Fix "Invalid handler specified" error on initial config flow setup

[Copilot]

When loading the integration, HA's Python 3.14 environment raises cannot import name 'wrap' from 'aiofiles.base' because the installed version of aiofiles no longer exposes wrap from aiofiles.base. This ImportError occurs while loading __init__.py (which runs before config_flow.py can be registered), so HA cannot find the config flow handler and returns "Invalid handler specified".

Changes

• __init__.py: Replace aiofiles.ospath.exists with hass.async_add_executor_job(Path(...).exists) for key file validation — consistent with the HA-recommended pattern for non-blocking file I/O.

• coordinator.py: Remove aiofiles imports and replace async file operations with hass.async_add_executor_job(Path(...).exists) and hass.async_add_executor_job(Path(...).read_text) — the HA-recommended pattern for executor-based file I/O.

• manifest.json / requirements.txt: Remove the aiofiles==25.1.0 requirement entirely, eliminating the version conflict with HA's bundled aiofiles.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Error at initial setup</issue_title>
<issue_description>Fout
Config-flow kon niet geladen worden: {"message":"Invalid handler specified"}
</issue_description>

<agent_instructions>Any idea why this might happen?</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Error at initial setup #6

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[gensyn]

@copilot Revert those changes, they don't work. Then have another look at the issue, there is new information.

[Copilot]

@copilot Revert those changes, they don't work. Then have another look at the issue, there is new information.

Reverted the previous incorrect fix. The real error (from the HA logs) was cannot import name 'wrap' from 'aiofiles.base' — the aiofiles version in HA 2026.3.2's Python 3.14 environment doesn't expose wrap from aiofiles.base, causing an ImportError when loading __init__.py, which in turn prevents the config flow handler from being found.

Fixed in cc4a319 by removing the aiofiles dependency entirely:

• __init__.py: aiofiles.ospath.exists → os.path.exists
• coordinator.py: aiofiles.open + aiofiles.ospath.exists → hass.async_add_executor_job(Path.exists/read_text)
• Removed aiofiles==25.1.0 from manifest.json and requirements.txt

[gensyn]

@copilot In coordinator.py, hass.async_add_executor_job is used for path.exists; why not in __init__.py?

[Copilot]

@copilot In coordinator.py, hass.async_add_executor_job is used for path.exists; why not in __init__.py?

Good catch. _validate_service_data now takes hass as a parameter and uses hass.async_add_executor_job(Path(...).exists), consistent with coordinator.py. Fixed in 65ea9f4.

[gensyn]

@copilot Please fix the integration tests that broke in this branch.

[Copilot]

@copilot Please fix the integration tests that broke in this branch.

Fixed in b4624c3. The integration tests were patching module-level exists names (custom_components.ssh_command.coordinator.exists and custom_components.ssh_command.exists) that no longer exist after removing aiofiles. All those patches are now updated to "pathlib.Path.exists", which is the correct target for the Path(...).exists calls used in both coordinator.py and __init__.py.