Zigbee2mqtt, if I replace the CC2530 or CC1352-P2 with an identical

Configuration
1

Hi,

Running zigbee2mqtt with a CC1352-P2 as coordinator. I suspect there is a hw fault in my device and have a brand new one available. Can I simply replace the running one with the new one, or do I have to re-pair all my sensors?

2

I’ve swapped my CC2531/CC2530 many times without repairing.

I think your safe.

1 Like
3

I switched between CC1352-P2’s without any problem. No need for repairing.

1 Like
4

Hi @nanobra1n

I tried to simply replace my CC1352-P2 today followed by a reboot of hassio. It did not connect to any of my zigbee devices on restart.

Do I have to edit something in the configuration.yaml for zigbee2mqtt when I replace the CC ?

5

What was the original z2m adapter ? It can be difficult if you replace a CC2530 or CC2531 with a CC1352-P2. You have to look in the log what the problem is.

6

The original is also a CC1352-P2

Running Z2M as standalone docker on a NUC.

The reason for replacing is that I suspect the soldering for switching to external antenna was not successful so I wanted to swap the original CC1352-P2 with a brand new one (of course, flashed with the correct firmware) to compare link quality.

7

Normally you don’t have to repair.

8

If you used something like this in your configuration.yaml (the one of zigee2mqtt)

serial:
  port: >-
    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001949EE9C-if00

The port will have changed.

9

My port config is simply:

serial:
  port: /dev/ttyACM0
10

As @francisp suggested, make sure that the port didn’t change. Using the /dev/serial/by-id/ path is a good idea because it won’t change through reboots. Note that you will want the .. if00 name. I also found that the first time I started a new CC1352 z2m was spewing error messages for a while. After a few minutes they went away and z2m connected to the coordinator. No repairing was necessary.

11

What do you use for port config ?

12

I got two devices when I run ls -l /dev/serial/by-id t

lrwxrwxrwx 1 root root 13 Mar  6 11:17 usb-Texas_Instruments_XDS110__03.00.00.05__Embed_with_CMSIS-DAP_L4300170-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Mar  6 11:17 usb-Texas_Instruments_XDS110__03.00.00.05__Embed_with_CMSIS-DAP_L4300170-if03 -> ../../ttyACM1

Why do I have it on both ACM0 and ACM1 ? I only have one device currently connected and my configurattion.yaml points to /dev/ttyACM0

13

You want the one that ends in if00.

14

Without trying yet, are they unique, meaning when I swap the CC1352 it will change ?
Or is this the ‘solution’ so the adapters can be changeable without any editing, just unplug and replug?

15

The /dev/serial/by-id name will be unique to the CC1352. But regardless what value for port you use, the log content should give you an idea what is going wrong.