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

Modifying pan ID, channel, and network key in zb_storage (TZ-1287) #477

Open
chi-lee-almagest opened this issue Nov 12, 2024 · 3 comments
Open
Labels

Comments

@chi-lee-almagest
Copy link

Question

I know that the API has provided a function for setting the pan ID once during runtime and a function for changing the network key. But I would like to persist the change so that I don't have to call those functions during runtime.

The situation is that we are providing home automation solutions to residential projects. Our technicians will grab a new gateway, form a network and then join all required devices to the network at our warehouse. And then the installers will go to the site and install everything without configuration.

One of the unit requires additional devices to be joined to the network but during the process we realized the pan ID and the network key the new devices using are different from the previous ones. So we use the functions to set it to the previous pan ID and network key as a temporary solution.

Now we want to eliminate those lines in the source code to prevent applying the parameters to other gateways. And also we don't want an OTA to accidentally switch our "special" gateway to use the wrong pan ID and network key some day.

Additional context.

No response

@github-actions github-actions bot changed the title Modifying pan ID, channel, and network key in zb_storage Modifying pan ID, channel, and network key in zb_storage (TZ-1287) Nov 12, 2024
@xieqinan
Copy link
Contributor

Hi,

If additional devices are expected to join the network created by the gateway, why not have the new devices leave their previous network and then join the current one?

@chi-lee-almagest
Copy link
Author

@xieqinan
The previously commissioned devices are installed above the false ceiling. And some of them are not easily reachable. That would be the last resort but we would like to see if there's a software solution to it.

@chshu
Copy link
Collaborator

chshu commented Dec 20, 2024

For any kind of software solution, you need to call the APIs to change the network parameters explicitly, right?

One possible solution is to push OTA to the installed devices, and switch to new network after reboot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants