ha-config-flow-options
Home Assistant ConfigFlow/OptionsFlow patterns—single-instance guard, schema validation, reload listeners, safe options handling without recursion.
Explorez les skills IA publiés de plebann et consultez leurs instructions source.
Skills indexés
9Étoiles des dépôts des skills indexés
12Forks du dépôt
0Moyenne des étoiles par skill indexé
1Les étoiles d’un dépôt peuvent se répéter entre ses skills.
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...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.