ha-migration

Guide Home Assistant integration upgrades through config entry version migration and deprecation fixes.

6|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill ha-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ha-migration
Source: https://github.com/L3DigitalNet/Claude-Code-Plugins/tree/main/plugins/home-assistant-dev/skills/ha-migration
Command: npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill ha-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of upgrading Home Assistant integrations by providing guidance on config entry version migration and fixing deprecation warnings.

Core Features & Use Cases

  • Config Entry Migration: Assists in updating the schema for stored configuration data when integration settings change.
  • Deprecation Fixes: Helps resolve issues arising from deprecated APIs or patterns when upgrading Home Assistant core.
  • Use Case: You've updated your custom Home Assistant integration and are seeing warnings about deprecated services. This skill guides you through the necessary code changes to resolve them and ensure compatibility with the latest Home Assistant version.

Quick Start

Use the ha-migration skill to fix deprecation warnings in your Home Assistant integration code.

Frequently Asked Questions about ha-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix deprecated API warnings in my Home Assistant integration?

To fix deprecated API warnings in your Home Assistant integration, you need to update your code to replace outdated service calls with current patterns. This skill guides you through identifying and resolving these deprecation issues to ensure compatibility.

What is a config entry version migration in Home Assistant?

A config entry version migration in Home Assistant is the process of updating the stored schema for integration settings when changes occur. This ensures your integration's configuration data remains compatible with newer core versions.

How do I update my custom Home Assistant integration after a core schema change?

To update your custom Home Assistant integration after a schema change, you must migrate the config entry data and options. This skill provides step-by-step guidance for applying the necessary code changes to match the latest schema.

When do I need to perform a config entry migration for Home Assistant?

You need to perform a config entry migration for Home Assistant when your integration's stored settings schema changes. This typically happens during an upgrade where entry data or options require structural updates to function correctly.

Does this guide help with both config entry data and options schema changes?

Yes, this guide helps with both config entry data and options schema changes. It supports scenarios involving structural updates to stored configuration data, ensuring your integration settings remain valid after an upgrade.

Why does my Home Assistant integration break after upgrading the core version?

Your Home Assistant integration may break after upgrading the core version due to deprecated APIs or changed config entry schemas. This skill helps resolve these compatibility issues by guiding you through the required migration and code fixes.