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

NetworkSerialization #34

Closed
Mr-Markus opened this issue Feb 13, 2019 · 1 comment
Closed

NetworkSerialization #34

Mr-Markus opened this issue Feb 13, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Mr-Markus
Copy link
Owner

There have to be a solution for NetworkStateSerialization, which means that if network is shutdown or startup all known devices should still be there

@Mr-Markus Mr-Markus added the enhancement New feature or request label Feb 13, 2019
@Mr-Markus Mr-Markus self-assigned this Feb 13, 2019
@Mr-Markus
Copy link
Owner Author

There is now a property named NetworkStateSerializer in ZigBeeNetworkManager which can be set by the caller to let him implement his own logic or database for the ZigBeeNodes

If a node is added, updated or removed the Serialize or Deserialize Method of the implemented class is called.

I implemented an example in the PlayGround project, and the after network startup my known devices are in the NetworkManager.Nodes List

So it is now possible to restart the network and restore all known devices to send them messages again without a DeviceAnnce Message received

Mr-Markus added a commit that referenced this issue Jun 27, 2019
- See #47 for supported devices
- NetworkSerialization #34
- XBee implemented #41
- Updated bind request to return #51
- .editorconfig added #57
- UnitTests added #20
- ZigBeeNet with auto generated cluster classes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant