Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp537013ybi; Fri, 31 May 2019 05:26:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqzbYfPxDD3ZPcNs4nnGvAA5Wh+lLcj7hYxbFTy81z1kezAREic+zhVZ6WVT55L6SfvF+cJu X-Received: by 2002:a65:52c8:: with SMTP id z8mr8766924pgp.10.1559305598001; Fri, 31 May 2019 05:26:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559305597; cv=none; d=google.com; s=arc-20160816; b=JSuj4wFmcbwgZ+Q3ETHN2kaZUAZVuIwX8szSxZ61g2NakNb42w2gox5LIvlekusp1o 4pv7ku5qfaMT4lfG1cFAl1OVyWQXOMbNRd5ha6oHEUhw7n/59wc9mzUGn3FndD7p4jAk YwomLN/SxYJYRbyadjO596VWOB07dirBM1dtb6rWzh8dXNQ5cicOfUVWMPz17cbmhHy1 OyQm719UCedlR5YnUlJAM3YX+LytjqpVR0jSjU5y5VEM1XOHMZK7sz4T7q30FEfsE7Bt iYxHJRKuAuvz9Nk7rvvnTw79r3or73S3pEkD4OpvmcvKutV1oX2NkAOqZe4m6B35blPu oYDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:to:from:date:dkim-signature; bh=aMbmxFRaYYw4ak2ZOoUZUfj7MueBcRf8sV1vSM6fuak=; b=XguyRcIohV+5iK31TIMDy74139IN3jASAXwFPPI3nDe1Qwhk9MK9rTWDgJR/DtWP4G i9zNhsJ9dh97+y2lGhEQiZS18EQlnDmYvpCUsOdzB+mu9hDEn88rUX/0bKpyNRCCS1ZD 6OOVl5vWjnlQgQ42MX+tf91dpiPIUJaN0mdBz72r+YSBmU+SMTap5Vi8pfpddwRbPoMv s3I74LFsrhRzRPqyqD4sDPa5pSas+Rn+7EKejO6zx8TXkmaC6uK/VjpAUmIOYk0Ej3EE 7ZPF6ueFEiUHGqHhHGZNgGK9EDtZpbdxhemPgacZ7QFQUkLZz29Tnz8ztI8Usa8IEXmr PuSQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=nQnVZVlH; 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 d31si3548465pgm.575.2019.05.31.05.26.03; Fri, 31 May 2019 05:26:37 -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=nQnVZVlH; 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 S1727158AbfEaM0D (ORCPT + 99 others); Fri, 31 May 2019 08:26:03 -0400 Received: from mail-ed1-f45.google.com ([209.85.208.45]:46783 "EHLO mail-ed1-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726330AbfEaM0C (ORCPT ); Fri, 31 May 2019 08:26:02 -0400 Received: by mail-ed1-f45.google.com with SMTP id n12so6323665edt.13 for ; Fri, 31 May 2019 05:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=aMbmxFRaYYw4ak2ZOoUZUfj7MueBcRf8sV1vSM6fuak=; b=nQnVZVlH+C6AJCjMQz4Mm6Ld9cgOYvGCbrlyX+LFfl0fIdnI+PK678/fSyhdEEfDb8 JTrnnnNIA0+QA5bOsBC3nmR0gG3ccNSPpFrSFkEbQDiZNWFtjjEF19H77EeD1dxxpzRC ZAT74rWJCEbWgNDk5S8YtCE230JX+psy3EzkJpgVb/YWVbipPA60a8Kbe85x2V3vslow FccFhmEVWkWAu/0dz5SJmK0mrsvZRdcFjN9msRGjAfzeKQpqdtnGI/5xYcRQMUcGBMcx mVoE6rIGxMXOYKrlcyG1b4Erz5/+/upQuNQ52pPoth/3S/JNFMOkF1/brm+kGZN3uS2F VEnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=aMbmxFRaYYw4ak2ZOoUZUfj7MueBcRf8sV1vSM6fuak=; b=S9U+p68ob44MTaqbgOeNyfJSBSU4bQERfdAFrHWQWmL4H1PK6AQGDkDQcrNFHY80ew K/6lmOHToNB/iwBfuzClNxF7pDvHHCv0mLCwvpCkfWeCR60408dolqU0Nx7VptAemPIZ 0cVaiH3vvTUdoFt/jyqjQtYwDoXl+yNVdZ9kObpuDbxEPoiwR2G2hdx7l3MdFQxAvJlM 67vEs4gZZM1mZuk2OIB/OObqYmhCoOLje2cXrhTZb6lAaxDMYQzizB8hiRze5BRqN7fO NYTBpt/6df7CWn58CvtWfWPHPpF6qxJjVkGesozXw3J27NqJut/dKpRNJa6hoBKtvxer QxcA== X-Gm-Message-State: APjAAAXYPnR8Q0FnYbwLUHy1ptkqq4+pbAOcuS6E3bBac+myeQm3BfTC YrWvG0eYIega6qa2cDBtHQcbclQt X-Received: by 2002:a17:906:2e55:: with SMTP id r21mr8795668eji.88.1559305561212; Fri, 31 May 2019 05:26:01 -0700 (PDT) Received: from griso ([212.129.72.108]) by smtp.gmail.com with ESMTPSA id 44sm1588166eds.90.2019.05.31.05.26.00 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 May 2019 05:26:00 -0700 (PDT) Date: Fri, 31 May 2019 13:25:58 +0100 From: John Whitmore To: linux-bluetooth@vger.kernel.org Subject: Different respones to BLE scan from a Peripheral device? Message-ID: <20190531122557.GA3176@griso> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org 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