Received: by 2002:a25:2c96:0:0:0:0:0 with SMTP id s144csp234466ybs; Tue, 26 May 2020 07:59:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzAjZhx7+a17wWLcxJfkbVDhtxB/GN9ecKOHCkfKjC35dePDYDj1pkekgc6CAn0E786lWgb X-Received: by 2002:a17:906:c10f:: with SMTP id do15mr1528908ejc.249.1590505144409; Tue, 26 May 2020 07:59:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590505144; cv=none; d=google.com; s=arc-20160816; b=WUgTwq1nCkK3SLKVU1a4tYuMkNkSwt+b9p3TTImjmpS4u3Y+supBr+ZfjPJky4vvSp YXOpDFTCLF5Xd+DjL0uxFleFuXRZvf7RzQYCGesrzsZic37cPvMhdRQxnb+3v9xZ9/wi Z8jSqlff891u8zB46A3AtH+ARHHM2rU92Pws5Gf9y2J6HfjsikC/5l4XeWvYCImI237q oUq6UyDVQQiwfwvMOaSl9ZLLCr0nsQnAGYTxGjaumrWV9aUGOgqfaZqr+9cwY61SB37L gop3r+58mmP2OacMIq1/Jpm93j7BTj9imVMnzhrJV63xEY3HVNSj2j4vRoEIEJo1wWC9 XN4w== 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=6dOBMXdnmfj6Q0O+nJ9WjTu7+Mm1dWjFRhqxkQonC8k=; b=qQu8zlUxIOzO+7e+WMhidcgWXbokcRtOF4Hdi1B7Zd+Gkw31FCrgB3avrJkhaUp2+T C2w5aezqiPKgRP/6c7KL6XVgzYvsG7VpKY1of7JyN4DI8wDItfAoGgjo6OHTleshNk8c 6S+wcw7lBurp9zvpo+idNrZZ8W8hbQIMK2ykrB34gFtx1SmBUerGnVUEWz5oZSYv0zph nFt5b5jcgjm4VIP1y0T/ibe/DysfHnpzHN1KQektZq+a7CbIJwQjwwrDY+9mHg/HKMdG YNNNX1NnZnnSCyTYnRcVjZLNpW9oacE13GqyF0Ud46bBouvq/q+0FsPVAVLP/bCby8ff s+cg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=MhaJhRtx; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f12si18210edy.546.2020.05.26.07.58.39; Tue, 26 May 2020 07:59:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=MhaJhRtx; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729473AbgEZO5w (ORCPT + 99 others); Tue, 26 May 2020 10:57:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728110AbgEZO5v (ORCPT ); Tue, 26 May 2020 10:57:51 -0400 Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F340BC03E96D for ; Tue, 26 May 2020 07:57:50 -0700 (PDT) Received: by mail-lf1-x131.google.com with SMTP id r125so12455109lff.13 for ; Tue, 26 May 2020 07:57:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6dOBMXdnmfj6Q0O+nJ9WjTu7+Mm1dWjFRhqxkQonC8k=; b=MhaJhRtxTu129l8Ry9xvBqt4zolq0y28S7AZZtx7QMvhtqS13ysYgjnSoKSddrff8z Aawn8q6OVYEZCyHULq6yS/FhMhpd9CpJ2AkNNFYx+TZFwfnNjpvlisyYy8UBhcunh4TR Q/sayylz3xdHPnixpMHt6tVZV8o++RS2l74Z4vWNdSr16AypPyzx/XcSSadlgE/pzyK0 Z/8utcqqjSMRvj0W0teH/ZR6XZOb2ULaesG/zNBA0PDd/3R08OgtVZD1SumufATvy1Bd haXzGWQM3ih6XBFP63YxYRHoJj87iH63sUZeqYI+8A63+9L5lEY0c8Yrs1AsNlnoKHKs 9oqA== 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=6dOBMXdnmfj6Q0O+nJ9WjTu7+Mm1dWjFRhqxkQonC8k=; b=ik75aaUIFg/F1B3bMCfV/xqKUl5wts3zms6mgD074dMUoFPFxktcBmq7Wh4j0Hl7JL E1i3++3mnK5qNGBM21MLAGF0Zfoyu7O6VpXY7rY5qRw3AiZRqVS8wogjPODtLvC7AZIi 9H3y1fPz4aQSGME3wx0B9aN/r2wn0vnDfj8XkurAHzCa2r1BJslvFlS7kzj+IXGCoKLX TAte+mx1aGp4kBI0QQxrS3js6Fv7K2yfANKxS1yxDj0q2Fsc/Lllp9TiniztFUOYR0Tw 0ozJuuhTebFvVXcBvmvfQSAGMmyApCNB5TmOG2JP9NmHIuk9UQnif1gJNDXBaGo53sES Z7Uw== X-Gm-Message-State: AOAM531AktN7W0D7Z7hBcqd5ukgUioXnBacHEHKgj/+hLBmlEXdynw3u wVQvq+CABOc1F6ab909Uq1SM4N3oQp1bC+DiYrh+6w== X-Received: by 2002:a19:c751:: with SMTP id x78mr728559lff.82.1590505069163; Tue, 26 May 2020 07:57:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alain Michaud Date: Tue, 26 May 2020 10:57:36 -0400 Message-ID: Subject: Re: UUIDs for every single physical peripheral's service and characteristics? To: Christopher de Vidal Cc: BlueZ 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 Christopher, The term "unique" will vary based on context. In the context of a Gatt Service and Characteristic, it is intended to uniquely identify the "contract" defined by the service/characteristics. For example a Temperature Service would have a UUID that universally defines the contract/interface defined by that service. So for your custom service, you'll need to define a set of 20 128 bit UUID (16 bit uuids are reserved for SIG defined uuids) that uniquely identify the contract that's defined by your service/characteristics. The devices can uniquely be identified/addressed by their respective addresses. I hope this is helpful. Thanks! Alain On Tue, May 26, 2020 at 10:38 AM Christopher de Vidal wrote: > > Help a newbie? I'm seeking to build a niche product for sale, a > Raspberry Pi-based device which during the initial setup acts a BLE > peripheral. (Python using dbus to Bluez.) It has a single service and > 19 characteristics. I get that the first "U" in UUID stands for > unique. Must that be unique among each physical product, or may it be > unique among the product line? > > So if I sell 1,000 units (which would be a success), would I need to > obtain 1,000 service UUIDs and 19,000 characteristic UUIDs? Or just 20 > total, for the entire product line? > > The goal is so that the iOS/Android app can have that pre-set in the > code and quickly discover the device, pair it automagically. > > I suppose the risk is of a conflict of two similar devices which are > in the same vicinity of the phone, and both set into peripheral mode > at the same time. But that would be a minimal risk which I could > accommodate for. > > Christopher de Vidal > > Would you consider yourself a good person? Have you ever taken the > 'Good Person' test? It's a fascinating five minute quiz. Google it.