You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a CC2538+CC2592 coordinator with firmware 20201010 and a CC2531 with router firmware CC2531_router_2020_09_29.
Unfortunately CC2538+CC2592 does not detect CC2531 router and not pair it.
What did you expect to happen?
I'd like to understand what the problem could be. I want to pair my CC2351 router with CC2538+CC2592 coordinator
How to reproduce it (minimal and precise)
I tried to change router firmware on the CC2531 but with no success
Zigbee2MQTT version
1.22.1
Adapter firmware version
20201010
Adapter
CC2538+CC2592
Debug log
Nothing in log because not recognized
The text was updated successfully, but these errors were encountered:
Did you use CC2531 as coordinator in same instance of zigbee2mqtt before ?
Today i had issue because i wanted to use usb stick (egony) as router but before i have used it as coordinator ( replaced it with sonoff usb dongle ) . Turns out zigbee2mqtt is cloning ieee address to new coordinator so we won't need to re-pair all devices after switching coordinator hardware. Downside is that now two devices have same ieee address. To resolve that i have assigned different secondary address to old usb stick and now it works as router.
Note that both usb sticks have CC2652P, no idea if same applies to CC2531
What happened?
I have a CC2538+CC2592 coordinator with firmware 20201010 and a CC2531 with router firmware CC2531_router_2020_09_29.
Unfortunately CC2538+CC2592 does not detect CC2531 router and not pair it.
What did you expect to happen?
I'd like to understand what the problem could be. I want to pair my CC2351 router with CC2538+CC2592 coordinator
How to reproduce it (minimal and precise)
I tried to change router firmware on the CC2531 but with no success
Zigbee2MQTT version
1.22.1
Adapter firmware version
20201010
Adapter
CC2538+CC2592
Debug log
Nothing in log because not recognized
The text was updated successfully, but these errors were encountered: