-
Notifications
You must be signed in to change notification settings - Fork 94
Description
Every time the discovery process finds a node (including a node that has already been seen), it adds that node to the __last_search_dev_list (code).
The list is never emptied or maintained, and appears to only be used in one place (code).
I'm not entirely sure what the goal of the list is, but at a guess based on naming, it seems to be a list that should reflect nodes discovered during the last node discovery process. If that's correct, this problem could be resolved by clearing the list when node discovery is started.
A potential stopgap that I have yet to test is just manually emptying the list before starting discovery
My use case is long-running service on an embedded system where the discovery process is running constantly (XBeeNetwork.start_discovery_process() is called at the end of my discovery process finished callback). I'm using XBee Pro S3B modules in API mode with escapes.