Hi Isak, On Tue, 2022-01-25 at 15:20 +0000, Isak Westin wrote: > Hi all, > > In my company we are building a Bluetooth Mesh application on top of the bluetooth-mesh daemon, using the > DBUS interface. > We want to use the RSSI value of mesh messages received from provisioned nodes as part of evaluating the > general quality of a bigger mesh network. Also, e.g. to decide which nodes should have the relay feature > enabled. > The RSSI value is delivered in the LE Advertising Reports via HCI, but there seems to be no way to make the > daemon pass this information further to the application. > The only messages currently with RSSI propagated up to the application are the Unprovisioned Beacons, which are used to indicate signal level of devices seeking to be provisioned. The RSSI measurement is really only useful for determining signal strength of direct neighbors, or the "last hop" of a mesh path, so from a perspective of measuring the larger quality of the mesh network, it won't really tell you what you are looking for. > Is there an easy way, that I have missed, to get the RSSI values for received mesh messages? If not, what are > your thoughts about making the information available somehow, perhaps as part of the DBUS methods > MessageReceived and DevKeyMessageReceived? A tool that measures the signal strength of each hop would require not only DBus API changes, but also a Vender style application that resides on each node, and collects measurements, forwarding them to a central data collection point. This would require controlling the software of *every* node in the meash network, making it impractical for an end customer setup that has nodes from multiple manufacturers. > > Thank you and best regards, > Isak > --Brian
