You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure exactly how to reproduce this but I found it when I needed to send a message to any connected node to be relayed to other nodes in the network.
I wanted to find a node that was connected and so I used MeshNetworkManager.proxyFilter.proxy and it worked fine. Except eventually it stopped working, and then sometimes would start working again.
I found that it was because sometimes but not always MeshNetworkManager.proxyFilter.proxy would be nil even though NetworkConnection.proxies contained several open bearers. I'm not sure why this is the case. It looks like sometimes the NetworkLayer.handle(proxyConfigurationPdu:) will sometimes fail to find a node here:
And it will send nil and the the ProxyFilter.proxy gets set to nil
I'm thinking that maybe me using ProxyFilter.proxy in this way is not a reliable way to get a connected node. If that's the case what is a better way? I know I can see open bearers in NetworkConnection.proxies but I'm not sure how to associate them with the corresponding Node so that I can use one of the MeshNetworkManager.send() variants to send a message to the Node.
Any help would be appreciated.
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
/// The connected Proxy Node. This may be `nil` if the connected Node is unknown
/// to the provisioner, that is if a Node with the proxy Unicast Address was not found
/// in the local mesh network database. It is also `nil` if no proxy is connected.
publicprivate(set)varproxy:Node?
Could you provide logs from Console app (filter with subsystem=com.nordicsemi.nRFProvision) or Xcode logs when it happens? I wonder what's going on there.
Where do you suspect the issue?
Issue in mesh library, e.g. packets being dropped
Version
4.2.0 (latest)
Describe the issue
I'm not sure exactly how to reproduce this but I found it when I needed to send a message to any connected node to be relayed to other nodes in the network.
I wanted to find a node that was connected and so I used
MeshNetworkManager.proxyFilter.proxy
and it worked fine. Except eventually it stopped working, and then sometimes would start working again.I found that it was because sometimes but not always
MeshNetworkManager.proxyFilter.proxy
would benil
even thoughNetworkConnection.proxies
contained several open bearers. I'm not sure why this is the case. It looks like sometimes theNetworkLayer.handle(proxyConfigurationPdu:)
will sometimes fail to find a node here:And it will send
nil
and the theProxyFilter.proxy
gets set tonil
I'm thinking that maybe me using
ProxyFilter.proxy
in this way is not a reliable way to get a connected node. If that's the case what is a better way? I know I can see open bearers inNetworkConnection.proxies
but I'm not sure how to associate them with the correspondingNode
so that I can use one of theMeshNetworkManager.send()
variants to send a message to the Node.Any help would be appreciated.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: