How to change the z2m channel correctly?

Hi, I’m thinking to switch the z2m channel from 11 to 26 with the idea of having better stability network.

I stopped the z2m addon then changed the channel through the z2m addon configuration and start up the addon again. And surprisingly, all devices seems connected itself without re-pairing.

Then, I checked the z2m gui, it is still showing channel 11.

So, I’m bit confused. Have the zigbee channel been successfully changed to 26? If not, what’s the right way of changing it?

Thanks.

Delete coordinator_backup.json and restart z2m.

What about the entities in HA? Do we have delete them first?

Have no first-hand experience with that, but I would expect Z2M to continue with previously created entities, incl. their names in HA.

I changed once… had to repair a lot …but not all., and I donot understand that too

I changed Zigbee channel myself a while back. I managed to get through the process ok - I couldn’t find a more elegant solution than the following. I only had 6 devices so not a huge amount of time and effort involved, and I didn’t mind losing any history/stats for any of the devices. Obviously take a backup first before anything else.
What I did was within the Z2M Web ui, delete each of my 6 devices. Then go to ‘Dashboard’, ‘Settings’, ‘Advanced’, change the Zigbee channel ( I changed from 15 to 25) and then scroll to the bottom of the page and click ‘Submit’.
My devices then disappeared from HA under the MQTT integration also. I then restarted my HA instance and also rebooted my Zigbee coordinator.
Next I opened Z2M Web ui again and clicked on ‘Permit join’, and went through the pairing of each device, and confirmed that my Zigbee channel had indeed changed to channel 25 under Settings. Everything worked fine afterwards.
The only very minor oddity I noticed is that the text in the ‘Availability’ column in Z2M is no longer green when the devices are online, however it does still flash red when a device is offline. Not sure if anyone has seen that before, or it might well have been within a Z2M update that I failed to notice in a list of changes perhaps?