I’m jumping on the topic: would it be possible to propose a tool to facilitate the migration from Home Assistant to Gladys?
I imagine that many people currently using Home Assistant hesitate to take the plunge, especially because they are afraid of having to manually reconfigure everything.
I don’t know what would be the best solution: a standalone application, an integration directly into Gladys, or another system that automatically retrieves part of the existing configuration.
The idea would be to make the transition as easy as possible, for example by allowing the retrieval of devices, rooms, names, and possibly some automations, without having to start from scratch.
I don’t know what is technically feasible, nor how far we could go in retrieving the data, but I think it would be an interesting path to explore to attract new users to Gladys.
Good question! I looked (well, Claude did ) at Gladys’ code and the integration catalog. In short: yes, it’s doable, and a good part of the building blocks already exist. We just need to break down the problem, because each piece is handled in a different place.
What already exists
@guim31’s Home Assistant bridge (gladys-homeassistant, Gladys 5.3 or later): it imports HA devices in the Discovery tab and controls them through HA. HA must therefore remain on, and HA rooms are not recreated in Gladys (they are used for filtering and added to the name).
Device migration (the “Migrate” button of deprecated integrations): it moves the history, rewrites scenes and dashboards, and takes the room. The destination can be any device, including Zigbee2MQTT.
Zigbee2MQTT backup in the database: Gladys already knows how to restore a Z2M folder zip when it installs the container.
Gladys’ MCP server can create scenes, and Gladys’ AI chat uses the same tools.
What we could add
Import a Z2M backup (.zip) from the Zigbee2MQTT integration. HA’s Z2M frontend provides this zip (Settings → Tools → Download data folder backup). Gladys would correct homeassistant: false and server: mqtt://localhost:1884 itself, then start the installation. This would be option B of Olivier’s topic, without SSH. Warning: you must keep the same dongle, as the coordinator backup does not pass from one chip to another.
Display the “Migrate” button on devices from external integrations. The API already exists. We could then switch a device from the HA bridge to its native Z2M equivalent without losing scenes, dashboards, room, or history.
Add a “suggested room” to the contract of external integrations. Today, an integration cannot create or assign a room, and that’s intentional: it’s the user’s choice. If it could suggest a room, the Discovery screen would pre-fill it and offer to create it. This would serve the HA bridge, but also the Jeedom, Homey, Domoticz, and eedomus bridges.
For automations, rather a tutorial than a converter: an AI agent connected to both a Home Assistant MCP and Gladys’ MCP. HA’s official MCP does not read automations: you need a community MCP like ha-mcp, or simply paste your automations.yaml. Simple cases (triggered by a state, a time, or the sun, then action on a device) should translate directly. Jinja templates, blueprints, and choose will have to be redone manually.
The path this would give
Install the HA bridge: everything appears in Gladys, you create your rooms, scenes, and dashboards, and HA keeps running.
Import the Z2M zip: Zigbee goes native in Gladys.
“Migrate” each device from the bridge to its Z2M equivalent.
Recreate the remaining automations with AI.
You never start from scratch, and you can go back as long as step 2 is not done. The following will remain manual: ZHA devices (to re-pair), HA integrations without equivalents in Gladys (they remain behind the bridge), and Lovelace dashboards.
@pierre-gilles, what do you think? Importing the Z2M zip and the “Migrate” button on external integrations seem quite small since they reuse the existing Z2M restore and migration API. The suggested room touches the contract of external integrations, so it needs to be validated with you. If you’re okay with it, I can propose the PR for importing the Z2M zip.
@guim31, would the suggested room interest you for your bridge? According to the README, it has been mainly tested with HA’s demo integration: feedback on real installations would surely be useful.