ha-integration

Create a directory with manifest.json declaring the domain and config_flow, an __init__.py with async_setup_entry, a config_flow.py for user setup, and platform files like sensor.py. Use a DataUpdateCoordinator to poll external APIs and forward setup to platforms.

Subclass ConfigFlow with your domain and implement async_step_user to show a voluptuous form, validate input in try/except, and call async_create_entry on success. Set a unique ID with async_set_unique_id to prevent duplicate entries.

Duplicate entities occur when entity classes lack a unique_id property. Implement unique_id returning a stable identifier derived from device data, such as the device ID combined with the entity type.

No, synchronous calls like the requests library block the event loop and freeze the UI. Use aiohttp with async/await for all network I/O inside coordinators and entity methods.

Entities become unavailable when the coordinator update fails. Raise UpdateFailed in _async_update_data instead of generic exceptions, and expose coordinator.last_update_success through the entity's available property.

Do not use it for built-in Home Assistant components, Lovelace UI card development, or automation and template scripting. It targets custom component development with config flows and entity platforms only.