-
Notifications
You must be signed in to change notification settings - Fork 88
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
Ember dongle driver refactoring for multinetwork #1024
Comments
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. |
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. |
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. |
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. |
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. |
I plan to refactor the Ember dongle driver to split out functions that are specific to the NCP, and to a network. This is to allow support for multiple networks within a single dongle.
This is expected to look something along the following lines -:
The current
ZigBeeDongleEzsp
class will continue to work as it currently does, but this will be a simple class that calls functions in theEmberNcpHandler
andEmberNetworkHandler
classes.This is currently implemented, although I'm still trying to work out how to get the multi network NCP working (Silabs docs are non existent in this area for EZSP - they all assume you use their framework).
@hsudbrock @triller-telekom FYI
The text was updated successfully, but these errors were encountered: