Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp688449ybi; Fri, 31 May 2019 07:31:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqx5otu2A6iF1gcRCNiqHUtmFN8MN7zlEWrhKUwWJDtiiXnfqAKUxBwy4HqF503mr421mXPE X-Received: by 2002:a65:41c7:: with SMTP id b7mr9540640pgq.165.1559313087532; Fri, 31 May 2019 07:31:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559313087; cv=none; d=google.com; s=arc-20160816; b=HIul7OI8oSMRXR+e0lXJEjUB4sL/Qfc5PawXdD935DIMib6/u1OMvj/dDES6XFgwiL O4zHONQLXPdpkPZ1empfXfNGgbyw1+aYxc4UWbmocbgMau1hnrFtgbVGMFUaKhFIPHR5 QoBhS9FMmMmx1T6PgwYDU2GuynLNjkbOFajF/zJoFNmPEf/N5b1F2RKaRUeng6xjChHs 4qX0wrOWcHKigrqwtJj5YD5yqudAIWKEzc7aiVwQYdr5splyTk9oHx8gd1ZZjxaObkyd VrYu7em1IgH+sEBi6wGHJjMGm3OtLk1GPS9YbE/GVFa45oXAc2y8FjdmaU9s3RCUUKOq 1rsg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=haEx6zSIRMkTpzylOYcRsF9YOqvbgQyv21uXJLPRjvo=; b=Rv6ww49Zgfjp6JKP8/TfvNJHOasti7LYEwMaSthlBf9EGreBjUG4pDSVnrTrn1bXO+ JyPjsnw8yg4d23pZMuVIHLPVNtBq3/Qp7ol9Ss6kstOkW8eutqslbcae096beERAgQ9c UkviUHpeF6s7hOLDo5rEC5jJRPha/MtvwOSjdrJtAbrJ1wKRIXU6zc5+O2TeOo6lXnYm Ta/XrYbN/u6qGSAZ9mcWVuZsQaMjev32+kW60bvg/kfDs8+plbuiYVGw+u4vIhuNlDud vhCLw9Ltl2EE1TypRJx1MyKLAzjQJQXe3YCCcGm2To0f7pVPHetRHMHUC3AF2Mg3JFT8 7LCA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Mu9ooz2E; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x1si5289996pfx.152.2019.05.31.07.30.54; Fri, 31 May 2019 07:31:27 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Mu9ooz2E; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726555AbfEaOas (ORCPT + 99 others); Fri, 31 May 2019 10:30:48 -0400 Received: from mail-pg1-f175.google.com ([209.85.215.175]:46284 "EHLO mail-pg1-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726546AbfEaOas (ORCPT ); Fri, 31 May 2019 10:30:48 -0400 Received: by mail-pg1-f175.google.com with SMTP id v9so4135258pgr.13 for ; Fri, 31 May 2019 07:30:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=haEx6zSIRMkTpzylOYcRsF9YOqvbgQyv21uXJLPRjvo=; b=Mu9ooz2ER/MOKrBJNNxFIuqBxZe4IS3ZDDJPtOa2VPJ92MD2Nf8ldUs6I3M+GR+ML8 NftC0ZtYvCcUXcPBTIUDMooVG+za+5F8yWlV2R/N1Qm886zXAQexhipTmBinWNGxqf3t AJyXygjlhKI9+7qIhDS2lbugZ4iiXZfIdJInBiXSHdLSHTyZoNoQ6MaVuUEW9IiTvaPQ Sf1u5RniCJmZgi6fV8oGhBoSWTxq8+FLqBTH/am6LiDlP03LmzJS2WNgvt3g8P56J3ew CzQ3DBFQ1yj6IcxKmjMrqj+vY7Zs4TEeUWJbWg0dygUVhdjKloki7YwxzgoDxuHf310S 0cUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=haEx6zSIRMkTpzylOYcRsF9YOqvbgQyv21uXJLPRjvo=; b=Eahi4ZBwsZvZFnhv/ASLPG3MGAEWXUmmORekd6PDpckqC9tlA6Mhbc/Z+qdhcaScmc HL5BC0eeVsRQ++tDOFX/qip7y8zuSfhiV4EqCKGwGCbzkl3R1sLJg7mZAelWiropjMsY rCvhCpSl1bS1qxTDLBLj/QoR5NnvlwfzCYkBGoguamBpjzHAa7fdivex7ayfGZBIs6vs YWUi/S+cwxbt2OR+A7BKZEkmC2yLyRCinn7fUAjRKgOETJQc/uNLMhZWlHeD09LRIMyK Dm26i4x8JSyNt6dxbCXp/H/1jd5R7pgPRRm8/YKO9Ks4B32dxjQe+oXVGnd1ul5uJZqV pjLw== X-Gm-Message-State: APjAAAVJAcmEsJii2ouzhT1bXYgCevkOUWoAXCOZjEZhdHewg/KUWSrH FRI/HBlMjZFRJXJcvEDxB7dYj0IPggt0CYfN8LI= X-Received: by 2002:a63:4d5d:: with SMTP id n29mr9862932pgl.235.1559313047206; Fri, 31 May 2019 07:30:47 -0700 (PDT) MIME-Version: 1.0 References: <20190531122557.GA3176@griso> In-Reply-To: <20190531122557.GA3176@griso> From: Emil Lenngren Date: Fri, 31 May 2019 16:30:38 +0200 Message-ID: Subject: Re: Different respones to BLE scan from a Peripheral device? To: John Whitmore Cc: Bluez mailing list Content-Type: text/plain; charset="UTF-8" Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi John, Den fre 31 maj 2019 kl 14:27 skrev John Whitmore : > > Hello all, > > I'm running on two identical embedded Linux Gateway devices, both on > Ubuntu 16.04 and Bluez 5.37. That's certainly an older version, but > it's part and parcel of that version of Ubuntu. I'm having an issue > where the two identical gateway devices are getting different > responses from a BLE scan, and can't figure out what would be the > cause. In both cases it's the same peripheral device, a TI CC2650 > device. On one gateway I get a truncated response with just the MAC > address and in the other I get the MAC address plus the description > string "CC2650.." > > [bluepy.btle:37] Got: 'rsp=$scan\x1eaddr=b546C0E530068\x1etype=h1\x1erssi=h43\x1eflag=h0\x1ed=b020105030280AA06FF0D0003000011094343323635302053656E736F72546167051208002003020A00\n' > > [bluepy.btle:37] Got: 'rsp=$scan\x1eaddr=b546C0E530068\x1etype=h1\x1erssi=h28\x1eflag=h0\x1ed=b020105030280AA06FF0D00030000\n' > > I'm probably going to have to get a Bluetooth sniffer device to trace > this issue, but if anybody had any idea what this would be the case, > I'd love to hear. > > Perhaps even though the Gateways are running the same Hardware and > Software there might be a Hardware difference in the chipset used or > something. It's all I can think of. Hopefully get something to help > diagnose this issue. > > In those two messages there is a difference in RSS, is that signal > strength and could that be the issue? Have to open things up. > > Thanks in advance for any help, and apologies I'm at the wrong end of > a learning curve. > > John You could try running btmon in a terminal to show the HCI traffic. There you should see the raw advertising packets in form of LE Advertising Report packets. You should see both ADV_IND packets as well as SCAN_RSP packets. Maybe the software doesn't always combine them and that's why you get different results. And yes RSSI is signal strength. /Emi