Update Coordinator firmware (or not)?

I’ve got a few odd things happening in my Z2M network. Generally ok but things dropping off and/or not responding, slow response etc.
I’ve tried all the easy stuff, Wi-Fi channels, interference, usb cables, adding more routers etc. without any real change.
It then struck me my coordinator firmware hasn’t been updated since I bought it over a year ago. It’s a ZZH (CC2652R) from Electrolama.

My main question is should I update it’s firmware ?
and
How do I find the version of firmware already installed on it ?

As a side issue to this the Electrolama install info says I must have the following in config.yaml
serial:
port: /dev/ttyUSB0
advanced:
rtscts: false

My current config doesn’t contain any of that. If I add the lines then I get:
Integration error: advanced - Integration ‘advanced’ not found.

Any idea what might be causing that and how critical these entries actually are ?
Thanks in advance

There should be a coordinator sensor

I think advanced: is not supported anymore

Thanks for the swift reply.
Well this is weird - I don’t seem to have a coordinator sensor entity.
Ive hunted through the list for anything similar but can’t find anything !

I’ve just taken advanced out of the the yaml and it’s happy now although the serial and port entry don’t seem to have had any effect

You can see the coordinator version in the Zigbee2MQTT frontend too

afbeelding

I’m still getting some weird results here.
I can now see the serial sensor as an entity but its status is “unknown”

However I can see the versions as you’ve shown in the Z2M screen so that is a big step forward - many thanks for that.

Just going to through this back out to the forum.

How dangerous is upgrading the firmware on my ZZH coordinator ?
Should it just work when I plug it back in ?
Will it pickup all of mu devices or will I have to re-pair everything ?
Thanks

If using Zigbee2MQTT, shutdown Zigbee2MQTT → a backup is made
Update the firmware
Restart Zigbee2MQTT → backup is restored

Nothing to re-pair.

I have done it several times without problem. Just make sure you take the correct firmware for your device.

That depends on the Zigbee Coordinator radio adapter type as Zigbee2MQTT currently only support backup and restore for Texas Instruments based Zigbee Coordinator radio adapter type today.

If you are using ConBee/RaspBee or Silicon Labs based adapter then recommend stop Zigbee2MQTT and first performing a manual backup to file using zigpy-cli → https://github.com/zigpy/zigpy-cli

If you have problems then you can restore that backup from file using zigpy-cli.

FYI, zigpy-cli can also be by Z2M users to migrate between TI, ConBee/RaspBee, and Silabs adapters:

Thanks both,

The ZZH Coordinator is based on a Texas Instruments CC2652R so it looks like I should be ok to go for a firmware update.

Gonna pick a quiet weekend just in case !

@Hedda
Just one final question before I leap off this cliff…
To create the Zigbee2mqtt backup am I just hitting stop on the Settings/Add-ons/Zigbee2mqtt screen or am I using Settings/Tools/Request z2M Backup from the Zigbee2mqtt frontend UI ?

Francis,

I was under the assumption that when updating fw on our coordinators, no repairing was necessary and that had been my experience in the past. However, today I updated the fw on my coordinator and a few devices seem to complain, among which Aqara ZNCLBL01LM seems to not be reachable.

Reviewing documentation I’ve seen this message: Xiaomi ZNCLBL01LM control via MQTT | Zigbee2MQTT

Note that if you have already paired the device you will need to repair it after upgrading your adapter firmware.

any idea on why this statement? should I expect this need to upgrade happen with other devices?

thanks!

The whole part reads :

Adapter firmware

In order for this device to work, at least the following firmware is required on your adapter:

    CC2530/CC2531: 20211115
    CC1352/CC2652: 20211114
    CC2538: 20211222
    Conbee II: 0x26720700
Note that if you have already paired the device you will need to repair it after upgrading your adapter firmware

So I suspect if your firmware is older then the version on this list, you need to repair.