Hi Olivier,
You have two options for your ConBee II, and neither requires you to re-pair your devices.
Option A: Gladys connects to HA’s Zigbee2mqtt
You don’t change anything: Zigbee2mqtt stays on HA and Gladys connects to it via MQTT. This is the quickest way to test.
- In HA, create an MQTT user for Gladys in the Mosquitto add-on (or use a dedicated HA user).
- In Gladys, go to Integrations → Zigbee2mqtt → Configuration and choose “Connect to an existing installation”.
- Enter:
- the broker URL:
mqtt://HA_IP:1883;
- the MQTT username and password;
- if you want, the URL of the Zigbee2mqtt web interface.
- Your devices appear in the discovery tab. You just have to add them in Gladys.
Gladys listens to the topic zigbee2mqtt/#: the base_topic of your Zigbee2mqtt must remain zigbee2mqtt, the default value of the add-on.
Advantages: 5 minutes of configuration, nothing to break, immediate rollback.
Disadvantage: you keep HA (Mosquitto + Zigbee2mqtt) running. This doesn’t solve the complete switch, and if it falls, your Zigbee falls too.
Option B: you migrate Zigbee2mqtt to Gladys
Gladys then manages Mosquitto and Zigbee2mqtt itself, and HA can be turned off. Your entire network is in the Zigbee2mqtt data folder, you just need to copy it.
- Stop the Zigbee2mqtt add-on in HA, and leave it stopped. Two Zigbee2mqtts must never run on the same network.
- With the Samba or SSH add-on, retrieve the Zigbee2mqtt folder (
/homeassistant/zigbee2mqtt/ or /config/zigbee2mqtt/ depending on the add-on version):
configuration.yaml, and any devices.yaml / groups.yaml;
database.db;
coordinator_backup.json;
state.json (optional).
- Place these files on the Gladys machine in
/var/lib/gladysassistant/zigbee2mqtt/z2m/. If you have already launched the Zigbee2mqtt integration in Gladys, stop the container first:
docker stop gladys-z2m-zigbee2mqtt
- Manually correct these lines in
configuration.yaml:
homeassistant: false
mqtt:
base_topic: zigbee2mqtt
server: mqtt://localhost:1884
server otherwise points to HA’s Mosquitto, and Gladys does not rewrite this line. The rest (MQTT credentials, serial port / adapter, web interface port) is automatically rewritten by Gladys on startup. The network key, PAN ID, and channel are preserved.
- Connect the ConBee II to the Gladys machine. In Integrations → Zigbee2mqtt → Configuration, choose “Installation from Gladys”, the USB mode and the model ConBee II, then launch.
Keep a copy of the original folder on the HA side: in case of trouble, you restart the add-on and go back.
You can chain both options. Start with option A to test Gladys on a daily basis, then move to option B when you’re ready to turn off HA. Devices are attached in Gladys by their Zigbee2mqtt name, and the migration keeps these names. Normally, you don’t have to re-add them in Gladys.
For the Sonoff / ZHA key
This is less simple:
- ZHA does not use MQTT. Gladys cannot connect to it, and option A does not work for these devices.
- Gladys only manages one Zigbee2mqtt, so one key. You won’t be able to run the ConBee and the Sonoff in parallel in Gladys.
The simplest and most reliable solution: migrate the ConBee network, then re-pair the devices that were under ZHA. It’s a bit of manipulation once, but after that you have a single clean network, and a mesh that is all the more solid 
No magic gift for Christmas this time, sorry 
Keep us posted!
Have a great weekend,