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

Provide API to allow user to perform a scan #958

Open
cdjackson opened this issue Jan 12, 2020 · 8 comments
Open

Provide API to allow user to perform a scan #958

cdjackson opened this issue Jan 12, 2020 · 8 comments
Labels
enhancement pinned Will not be closed, even if stale

Comments

@cdjackson
Copy link
Member

It would be useful to allow users to perform a scan when creating a network to allow a clear channel to be selected prior to forming the network.

@stale
Copy link

stale bot commented Mar 12, 2020

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.

@stale
Copy link

stale bot commented May 12, 2020

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.

@stale stale bot added the wontfix label May 12, 2020
@cdjackson cdjackson removed the wontfix label May 12, 2020
@stale
Copy link

stale bot commented Jul 11, 2020

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.

@tejas-n
Copy link
Contributor

tejas-n commented Aug 25, 2020

Hi, is anyone already working on this? I asked a related question about setting a channel mask here #1051 (comment) and heard back from @triller-telekom that it's not been implemented.

I can pick this up if no one's working on it. Are you thinking of exposing methods for doing energy scan in ZigBeeNetworkManager which under the hood calls the transport layer?

@cdjackson
Copy link
Member Author

Hi @tejas-n . I don't think anyone is working on this, and for sure, it would be great to do so.

Are you thinking of exposing methods for doing energy scan in ZigBeeNetworkManager which under the hood calls the transport layer?

Yes, basically the same as my thinking - we probably want the following API in both the ZigBeeNetworkManager and ZigBeeTransportTransmit .

  • setChannelMask(): to set the channel mask used within the system. This is used for the scan, but may also be used for any subsequent channel changes etc.
  • performScan(options), or performEnergyScan() and performActiveScan or something - to actually kick off the scan.

Exposing it through the network manager rather than just through the dongle provides the possibility later to do something smarter with changing channels automatically.

I don't think this is too hard to implement the scanning - for the Ember at least that you're using, all the code is there in the dongle, it's just a case of hooking it up :)

Thanks @tejas-n

@tejas-n
Copy link
Contributor

tejas-n commented Aug 27, 2020

Thanks, @cdjackson. I'll have a crack at it on the weekend :)

@stale
Copy link

stale bot commented Oct 27, 2020

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.

@stale stale bot added the wontfix label Oct 27, 2020
@cdjackson cdjackson removed the wontfix label Oct 27, 2020
@stale
Copy link

stale bot commented Dec 26, 2020

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.

@stale stale bot added the wontfix label Dec 26, 2020
@cdjackson cdjackson added pinned Will not be closed, even if stale and removed wontfix labels Dec 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement pinned Will not be closed, even if stale
Projects
None yet
Development

No branches or pull requests

2 participants