Skip to content

Clarification: firmware change can leave all devices out? #282

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

Closed
subzero79 opened this issue Aug 13, 2018 · 10 comments
Closed

Clarification: firmware change can leave all devices out? #282

subzero79 opened this issue Aug 13, 2018 · 10 comments
Labels
feature request Feature request stale Stale issues

Comments

@subzero79
Copy link

Just yesterday i attempted to flash the sniffer firmware into the dongle to some traffic capture, I don't if the firmware wasn't the correct one or i was just using the wrong software so it didn't work properly. Anyway after I gave up, i flashed the coordinator firmware, latest by pulling the repo so it wasn't the same original i was using with before i flashed the sniffer one.

Once i started zigbee2mqtt again, all devices where not recognised any more. I had to repair them again one by one. Tomorrow i have to do the plugs in the attic.

Is this expected behaviour? Whats the issue here? transport keys? should it be warned in the wiki maybe?

For know i learn, and I've already ordered another dongle for this kind of testing.

@cmille34
Copy link

I learned this the hard way as well. I reflashed my CC2531 to fix an "unknown 17" error. I was told if you reflash the usb dongle, you'll have to repair the devices.

@Koenkk
Copy link
Owner

Koenkk commented Aug 13, 2018

Reflashing = clearing memory of CC2531 -> repair all devices.

@subzero79
Copy link
Author

Thanks for the info. Is it possible to backup the current loaded memory with the cc-debugger?
Also what does it get lost by flashing? The transport keys ?

@tb-killa
Copy link
Contributor

tb-killa commented Aug 14, 2018

@Koenkk @ptvoinfo
I don´t know if this could help but this seems to be a good way:
https://sunmaysky.blogspot.com/2016/01/how-to-clone-existing-z-stack.html?m=1

Maybe this could help too ???
Edit: i found some informations for the defined symbols:
https://github.com/Tropicao/zigbridge/blob/master/doc/firmware_instructions.md

NV_RESTORE : allow basic network data persistence, needed to rejoin network without issue when ZNP is restarted

@Koenkk
Copy link
Owner

Koenkk commented Aug 14, 2018

@tb-killa that looks good! We could use cc-znp library to read and write.

@matchett808
Copy link
Contributor

Is that now on the new firmware?

@tb-killa
Copy link
Contributor

Actually no work. We are all busy, if i got some free time next week i could take a Look at this.

@ciotlosm ciotlosm added problem Something isn't working feature request Feature request and removed problem Something isn't working labels Sep 3, 2018
@lolorc
Copy link
Contributor

lolorc commented Oct 2, 2018

even without unplugging or reflashing cc2531 it can refuse to reuse the previous panId it was using. It refuses to use it even if you specify it in the config, it then use panid+1 => have to repair everything.

edit: I managed to re-use my panid:

  • reflashed cc2531
  • unplugged all router
  • put paper towel around cc2531 then a lot of tin foil connected to usb connector to act as a shield
  • plugged cc2531/started zigbee2mqtt
    => yeeepeeeee ! good panid ! all devices back ! :-)

@lolorc
Copy link
Contributor

lolorc commented Oct 17, 2018

the same way, I've replaced my cc2531 by a cc2530+cc2590 without repairing all devices. Just need to unplugged routers and shield the coordinator so that it doesn't detect the chan/panid is already used.

@stale
Copy link

stale bot commented Dec 16, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issues label Dec 16, 2018
@stale stale bot closed this as completed Dec 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature request stale Stale issues
Projects
None yet
Development

No branches or pull requests

7 participants