-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Not an issue: Theoretical questions about pairing storage #728
Comments
|
Ok, it is more clear now... so:
|
Hi Guys, Since somebody has started this theme I would like also to ask a question that bothers me a lot: When a device is removed from pairing by zigbee2mqtt, is it removed from database only or from CC2531 as well? The reason I ask is I read somewhere on this site that people encountered problems with reaching the device count limit when they tried to re-pair the device after first removing as if after each re-pairing a device occupied new memory in CC2531. I am planning to change my channel and am almost certain this would require to re-pair all devices but at the same time I am afraid to get stuck with the device count limit. |
I cant answer that question but you can use the network map endpoint to get a list of devices and then use the remove endpoint to remove any that no longer appear in config |
@danpowell88 , thanks for the answer. |
submit it via the mqtt endpoint |
@Koenkk so to upgrade to a newer version of the firmware I would just need to specify panid/channel in the config? Do I also need to be out of the range of the network, and if so is unplugging the co-ordinator enough to do that? If I didnt set it originally how do I find out what it needs to be? |
To upgrade to a new firmware without having to repair everything (no guarantees):
|
Hi @Koenkk , The problem is I want to use those Livolo zigbee switches that were shown to connect only on channel 26. Is it possible to change the channel without re-paring? |
@Ton1965 channel switching requires repairing. |
@Koenkk , thanks a lot for your reply. |
Hi, |
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. |
Koenkk,
Just have a few questions regarding the pairing "memory".
I'm interested in internal workings, because now it seems a bit complicated with lots of layers,
and no clear understanding from my side "where-what-is"...
layers are: CC2531 <-> firmware <-> zigbee-shepherd <-> zigbee-shepherd-converters <-> zigbee2mqtt <-> HA.
in case of *.db file then any stick can pick it up and have all the pairings immediately?
And do the paired devices store it inside themselves (end devices)?
Basically here i ask if pairing is two-way process:
Stick stores paired devices and end-device also stores paired coordinator?
So lots of questions, but main thing is: are the pairings stored inside firmware or inside *.db file
and if end devices will communicate with new stick with same PAN-ID as old had or something else is needed?
I hope you have some free time to give some answers - if not then i'll close this issue after a while. Thanks!
The text was updated successfully, but these errors were encountered: