Currently, the area discovery ignores any area that has the field IsLeaf: False
Unfortunately, this leads to a broken area tree for RA3/HWQSX if the area's don't contain any control stations or devices.
In the example below, both "tree 1" and "tree 2" areas are reported as having "None" parent, because the isLeaf field is False as a consequence of not containing any devices/control stations.
"tree 3" correctly reports it's parent as "tree 2"
This update ignores the IsLeaf field, and discovers all areas defined on the bridge/processor, maintaining the correct parent/child relationship.
Currently, the area discovery ignores any area that has the field IsLeaf: False
Unfortunately, this leads to a broken area tree for RA3/HWQSX if the area's don't contain any control stations or devices.
In the example below, both "tree 1" and "tree 2" areas are reported as having "None" parent, because the isLeaf field is False as a consequence of not containing any devices/control stations. "tree 3" correctly reports it's parent as "tree 2"
This update ignores the IsLeaf field, and discovers all areas defined on the bridge/processor, maintaining the correct parent/child relationship.