ha-config-flow-options
Home Assistant ConfigFlow/OptionsFlow patterns—single-instance guard, schema validation, reload listeners, safe options handling without recursion.
Browse published AI skills maintained by plebann. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
9Repository stars across indexed skills
12Repository forks
0Average repository stars per indexed skill
1Repository stars may repeat across skills from the same repository.
Home Assistant ConfigFlow/OptionsFlow patterns—single-instance guard, schema validation, reload listeners, safe options handling without recursion.
Home Assistant translation_key and identifier practices—entity/device naming via translations, stable unique IDs, and migration tips.
Layered Home Assistant custom entity architecture—CoordinatorEntity bases, platform/category bases, registry-only platform files, translation-backed naming, stable IDs, and options reload wiring.
Diagnostics for Modbus in Home Assistant custom components—framing/extra-data errors, unit_id mismatches, pacing/timeouts, write contention, and logging patterns.
Testing patterns for Home Assistant custom components—coordinator and entity unit tests, register map coverage, write-path tests, and unique_id/device stability checks.
Patterns for building Home Assistant custom integrations that talk Modbus (TCP/RTU-over-TCP/serial): pymodbus device_id usage, safe polling/writing, pacing/backoff, encoding multi-register values, cached fallba...
Run code snippets in 30+ programming languages including JavaScript, Python, TypeScript, Java, C, C++, Go, Rust, Ruby, PHP, and more. Use when the user wants to execute code, test algorithms, verify output, run...
Home Assistant + HACS maintenance for the Heat Pump Predictor integration. Use when adding or updating config flow, coordinator, entities, services, translations, recorder/statistics compatibility, dashboards,...
Build or modify Home Assistant sensors/entities that must persist native values and custom attributes across restarts using RestoreSensor/RestoreEntity plus ExtraStoredData (e.g., history, timestamps, scenarios...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.