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

Move accessory to another WiFi network? #678

Open
olavt opened this issue Apr 25, 2024 · 3 comments
Open

Move accessory to another WiFi network? #678

olavt opened this issue Apr 25, 2024 · 3 comments
Labels
new-feature New feature or request

Comments

@olavt
Copy link

olavt commented Apr 25, 2024

People need to re-configure their WiFi networks from time to time. Having to rebuild the Matter fabrics / networks as a consequence would be very painful.

I'm not sure how moving a Matter accessory device from one WiFi network to another would be done using the Matter SDK, but it looks like Apple Home makes this quite easy.

This should maybe be a function in the Python Matter Server too?

@marcelveldt marcelveldt added the new-feature New feature or request label Apr 29, 2024
@marcelveldt
Copy link
Contributor

Yes we should create functionality for this. I need to dive into the details how to do this and if all devices support it.

@prolicht-at
Copy link

any ideas how to implement this?

@Apollon77
Copy link

Apollon77 commented Jan 17, 2025

I would think. the following needs to happen:

  • establish a CASE session
  • arm failsafe timer
  • use NetworkCommissioning cluster to update and then connect to the new network
  • discover and re-establish a/the new CASE session
  • invoke commissioningComplete to "persist" the data

But said this: This all relies on the fact that you can still use the existing connection to update the details AND already can use the new connection in parallel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants