- From: keybukium via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Mar 2015 19:31:25 +0000
- To: public-web-bluetooth-log@w3.org
Sometimes the TX Power isn't placed in a standard field, but in manufacturer data (e.g. iBeacon) - in which case you'd need the RSSI to calculate path loss in your app after extracting the data yourself. On Thu, Mar 19, 2015 at 12:23 PM Jeffrey Yasskin <notifications@github.com> wrote: > @jhedberg <https://github.com/jhedberg> mentions that applications have > been able to give a rough distance estimate using *only* RSSI when TX > Power isn't available. This implies that many devices are transmitting at > similar powers: maybe we can document that assumed power so people can > combine lists sorted by path-loss and by just RSSI. > > This either seems like a good reason to keep the fields split out, or a > reason to use that assumed power in computing the pathLoss field. But > we'd need to add a marker that the pathLoss is approximate, which argues > more toward keeping the fields separate. > > — > Reply to this email directly or view it on GitHub > <https://github.com/WebBluetoothCG/web-bluetooth/issues/76#issuecomment-83727207> > . > -- GitHub Notif of comment by keybukium See https://github.com/WebBluetoothCG/web-bluetooth/issues/76#issuecomment-83732166
Received on Thursday, 19 March 2015 19:31:45 UTC