Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CC2538+CC2592 not recognize CC2531 with ROUTER firmware #10449

Closed
manny199 opened this issue Dec 30, 2021 · 2 comments
Closed

CC2538+CC2592 not recognize CC2531 with ROUTER firmware #10449

manny199 opened this issue Dec 30, 2021 · 2 comments
Labels
problem Something isn't working stale Stale issues

Comments

@manny199
Copy link

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

@manny199 manny199 added the problem Something isn't working label Dec 30, 2021
@kaweksl
Copy link

kaweksl commented Jan 3, 2022

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

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2022

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working stale Stale issues
Projects
None yet
Development

No branches or pull requests

2 participants