I have asked an help to the AI, to give you this instructions and about the translaction in English.
I hope that’s understandable
Hello,
to keep using the Konnected (Legacy) integration even after its official deprecation, you can use a local copy of the integration as a custom component in Home Assistant. Below you’ll find all the detailed steps.
1. Basic requirements
To get started, you need:
-
A running Home Assistant instance (any installation type: OS, Container, Supervised, or Core).
-
Access to your Home Assistant config folder (via Samba, SSH, File Editor, VS Code, etc.).
-
The ability to restart Home Assistant (required at the end).
You do not need to remove or reconfigure your existing Konnected integration: the configuration is stored in Home Assistant’s internal files and will be reused automatically.
2. Download the files from the repository
My copy of the Konnected integration is here:
https://github.com/trsdomo/konnected-legacy
You have two ways to download it:
ZIP method (simplest, recommended):
Git method (for users familiar with git):
From a terminal on your local machine, run:
git clone https://github.com/trsdomo/konnected-legacy
At the end, you’ll have:
konnected-legacy/custom_components/konnected
In both cases, the important folder is exactly:
custom_components/konnected
3. Create the folder in Home Assistant
Now you need to copy that folder into your Home Assistant configuration:
-
Access your Home Assistant config directory (usually the root containing configuration.yaml).
-
If it doesn’t exist, create a folder named custom_components (all lowercase):
config/custom_components
-
Inside custom_components, copy the entire konnected folder from the repository
You should end up with:
config/custom_components/konnected/ containing files like __init__.py, manifest.json, etc.
Do not rename the folder: the name must be exactly konnected, since it matches the official integration’s domain.
4. What happens with the official integration
The key point is that the domain is the same (konnected), so Home Assistant gives priority to the version inside custom_components over the built-in one.
This means:
-
Do not remove the Konnected integration from the UI (“Devices & Services”)
-
If you remove it, you will lose configuration, entities, and devices
You also don’t need to reconfigure your zones: Home Assistant will continue using the existing data stored in .storage/core.config_entries, since the domain remains konnected.
In practice:
-
You just copy the custom component folder
-
After a restart, Home Assistant will automatically use the code from my repository instead of the original, keeping all your existing configuration intact
5. Restart and verification
After copying the folder:
To verify the custom component is loaded:
If you see this, it means Home Assistant is using the code from custom_components/konnected.
You can also check that:
-
The old Konnected deprecation warning is gone (or changed)
-
Your Konnected entities (sensors, switches, etc.) are still working as before
6. Notes on versions and updates
In the manifest.json file of my copy, I’ve already set an updated version value to meet Home Assistant’s current requirements for custom components.
If future Home Assistant versions require changes, I’ll update the repository. You’ll just need to overwrite the custom_components/konnected folder with the new version.
7. Troubleshooting
If after these steps:
Contact me and include:
This will help determine whether it’s a version, configuration, or other issue.
If you tell me which installation type you’re using (Home Assistant OS, Docker, etc.), I can tailor the instructions with the exact paths and the easiest way to copy the files.
