I’m trying to migrate from HA 2022.X in an ubuntu server to HAOS 2025.3. I have a Mosquito broker with tons of devices configured, and I assigned them a friendly name. I have a configuration.yaml file that is in /opt/zigbee2mqtt/data in my old setup with that info. In HAOS, I added the mqtt addon and it works (it found the broker) but no device seems to be paired anymore. Is there a way to migrate this configuration so I can then migrate automations, groups, and so on ?
What do you want to do with Zigbee2MQTT ? Keep the old one, or migrate to the add-on ?
This is a question I hadn’t made miself, because I assumed I was forced to use the add-on in HAOS. Now, I think I would stick to the add-on because I want future upgrades to be as automatic and hassle free as possible, and my instinct tells me that an external package could be an obstacle to that, but I’m willing to listen to expert advice. In the case I keep the add-on, I found out there is a ‘customize’ option and a folder. Should I copy paste all the data files there ?
The Zigbee2MQTT add-on creates a folder zigbee2mqtt. You can paste the files fromyour existing data directory in there.
First of all, thanks for your help! Now, I couldn’t find that folder. I did a: find / | grep zigbee2mqtt and got an empty result. I sshed using the ssh add-on to the server, but I’m not quite sure if that lands inside a container or directly into the OS. Another theory that comes to my mind (for the absence of the folder) is that I installed the addon without the broker plugged into the server, and when I got home, I plugged it in and configured the add-on. It seems to be working, though.
Which add-on? I am confused because of the mention of Z2M, but it sounds like you have been using an MQTT broker separate from Home Assistant?
If so, that is perfectly OK. You can use any MQTT broker that you have access to. I have my broker (mosquitto) running on a Raspberry Pi 3. It’s always been there because I started with Node Red long before discovering Home Assistant. It would be way too much effort to change brokers now because the broker IP is hard-coded in most of my MQTT devices.
Did I read your question correctly?