• BLE support in phones

    From Don Y@3:633/10 to All on Friday, July 24, 2026 08:16:07
    How ubiquitous is (or isn't!) this? Is there a general
    (temporal) cutoff point where its support is "expected"
    before which it is a rarity?

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, July 24, 2026 09:20:52
    On Fri, 24 Jul 2026 08:16:07 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    How ubiquitous is (or isn't!) this? Is there a general
    (temporal) cutoff point where its support is "expected"
    before which it is a rarity?

    What's a BLE?


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Wolferl@3:633/10 to All on Friday, July 24, 2026 18:37:17
    Am 24.07.2026 um 18:20 schrieb john larkin:
    How ubiquitous is (or isn't!) this? Is there a general
    (temporal) cutoff point where its support is "expected"
    before which it is a rarity?

    What's a BLE?

    I think Don is referring to:
    https://en.wikipedia.org/wiki/Bluetooth_Low_Energy

    --
    From-address is spam trap
    Use: wolfgang (dot) mahringer (at) sbg (dot) at


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lasse Langwadt@3:633/10 to All on Saturday, July 25, 2026 01:42:03
    On 7/24/26 18:20, john larkin wrote:
    On Fri, 24 Jul 2026 08:16:07 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    How ubiquitous is (or isn't!) this? Is there a general
    (temporal) cutoff point where its support is "expected"
    before which it is a rarity?

    What's a BLE?


    Bluetooth Low Energy, basically low-speed low power wireless for small do-thats that run on batteries, like fitness trackers, heart rate monitors

    any smart phone last ~12 years have it

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Friday, July 24, 2026 18:08:19
    On 7/24/2026 4:42 PM, Lasse Langwadt wrote:
    Bluetooth Low Energy, basically low-speed low power wireless for small do-thats
    that run on batteries, like fitness trackers, heart rate monitors

    any smart phone last ~12 years have it

    The *API* has been in place. But, it's not a first class service
    like BT. You'd have to find and install an app to make use
    of it -- even if you were surrounded by BLE devices.

    I don't think the user base is ready for this to the same
    extent they are BT earbuds, etc. Else, it would be prominently
    noted in the "factory installed" apps.

    Imagine requiring a user to install an app to use his BT earbuds;
    how ubiquitous would they be, in that case (the bar to entry is too high)

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lasse Langwadt@3:633/10 to All on Saturday, July 25, 2026 04:24:53
    On 7/25/26 03:08, Don Y wrote:
    On 7/24/2026 4:42 PM, Lasse Langwadt wrote:
    Bluetooth Low Energy, basically low-speed low power wireless for small
    do-thats that run on batteries, like fitness trackers, heart rate
    monitors

    any smart phone last ~12 years have it

    The *API* has been in place.˙ But, it's not a first class service
    like BT.˙ You'd have to find and install an app to make use
    of it -- even if you were surrounded by BLE devices.

    I don't think the user base is ready for this to the same
    extent they are BT earbuds, etc.˙ Else, it would be prominently
    noted in the "factory installed" apps.

    Imagine requiring a user to install an app to use his BT earbuds;
    how ubiquitous would they be, in that case (the bar to entry is too high)

    best give up then

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Friday, July 24, 2026 19:27:21
    On 7/24/2026 7:24 PM, Lasse Langwadt wrote:
    On 7/25/26 03:08, Don Y wrote:
    On 7/24/2026 4:42 PM, Lasse Langwadt wrote:
    Bluetooth Low Energy, basically low-speed low power wireless for small do- >>> thats that run on batteries, like fitness trackers, heart rate monitors

    any smart phone last ~12 years have it

    The *API* has been in place.˙ But, it's not a first class service
    like BT.˙ You'd have to find and install an app to make use
    of it -- even if you were surrounded by BLE devices.

    I don't think the user base is ready for this to the same
    extent they are BT earbuds, etc.˙ Else, it would be prominently
    noted in the "factory installed" apps.

    Imagine requiring a user to install an app to use his BT earbuds;
    how ubiquitous would they be, in that case (the bar to entry is too high)

    best give up then

    Exactly. Find a solution that is more mainstream. Less
    "customer support" involved.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From olaf@3:633/10 to All on Saturday, July 25, 2026 06:04:28
    Don Y <blockedofcourse@foo.invalid> wrote:

    (temporal) cutoff point where its support is "expected"
    before which it is a rarity?

    From Android 4.3 (API 18) it is present.

    Olaf



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Friday, July 24, 2026 23:31:59
    On 7/24/2026 9:04 PM, olaf wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    >(temporal) cutoff point where its support is "expected"
    >before which it is a rarity?

    From Android 4.3 (API 18) it is present.
    As I said elsewhere, support is present in the kernel.
    But, have any phones been shipped with an app that
    exposes it -- as "data", SMS, WiFi and BT are in most
    phones?



    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From John R Walliker@3:633/10 to All on Saturday, July 25, 2026 08:13:38
    On 25/07/2026 07:31, Don Y wrote:
    On 7/24/2026 9:04 PM, olaf wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    ˙ >(temporal) cutoff point where its support is "expected"
    ˙ >before which it is a rarity?

    ˙From Android 4.3 (API 18) it is present.
    As I said elsewhere, support is present in the kernel.
    But, have any phones been shipped with an app that
    exposes it -- as "data", SMS, WiFi and BT are in most
    phones?


    It is just part of Bluetooth. No need to do anything
    special at all.
    John


    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Saturday, July 25, 2026 00:39:45
    On 7/25/2026 12:13 AM, John R Walliker wrote:
    On 25/07/2026 07:31, Don Y wrote:
    On 7/24/2026 9:04 PM, olaf wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    ˙ >(temporal) cutoff point where its support is "expected"
    ˙ >before which it is a rarity?

    ˙From Android 4.3 (API 18) it is present.
    As I said elsewhere, support is present in the kernel.
    But, have any phones been shipped with an app that
    exposes it -- as "data", SMS, WiFi and BT are in most
    phones?

    It is just part of Bluetooth.˙ No need to do anything
    special at all.
    So, every IoT device (using BLE) near your phone is *visible* in
    the BT settings? I can dig up a 10 year old phone and see
    all of these??

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From olaf@3:633/10 to All on Saturday, July 25, 2026 10:17:42
    Don Y <blockedofcourse@foo.invalid> wrote:

    So, every IoT device (using BLE) near your phone is *visible* in
    the BT settings? I can dig up a 10 year old phone and see
    all of these??

    What does "see" mean in your contect? I wrote BLE Apps than can work
    on old Android 4.3 and on new phones. Okay, on new mobiles there opens
    some windows and ask me to contact the programmer for a news version,
    but I can ignore it and it still works.
    And I also think a BLE device can try to hide, so is only visible for
    the app of the device. .-)

    This gives you an overview:

    https://devzone.nordicsemi.com/guides/short-range-guides/b/bluetooth-low-energy/posts/ble-characteristics-a-beginners-tutorial

    BLE is not a serial port or something like this. It is much more
    complicated.

    Olaf

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Saturday, July 25, 2026 02:00:48
    On 7/25/2026 1:17 AM, olaf wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    >So, every IoT device (using BLE) near your phone is *visible* in
    >the BT settings? I can dig up a 10 year old phone and see
    >all of these??

    What does "see" mean in your contect?

    If you open the BT settings on a phone, the "nearby"
    (classic) BT devices are discovered. You can select
    one to pair with, etc.

    Or not.

    Just like you can see all of the available SSIDs when you
    open the WiFi settings.

    No "special app".

    I wrote BLE Apps than can work
    on old Android 4.3 and on new phones. Okay, on new mobiles there opens
    some windows and ask me to contact the programmer for a news version,
    but I can ignore it and it still works.

    Your app expects to talk to some BLE device, right>?

    Remove the app from your phone. Can your phone "see"
    the device -- i.e., can it tell you that such a
    device is nearby?
    And I also think a BLE device can try to hide, so is only visible for
    the app of the device. .-)

    This gives you an overview:

    https://devzone.nordicsemi.com/guides/short-range-guides/b/bluetooth-low-energy/posts/ble-characteristics-a-beginners-tutorial

    BLE is not a serial port or something like this. It is much more
    complicated.
    As is classic BT. I (as the user) don't have to know that I'm looking
    for nearby BT devices that support A2DP in order for devices supporting
    it to be visible to my phone. Nor AVRCP, HFP, PBAP, HSP, etc.

    I don't have to install a "special app" to *see* these devices.

    And, I can "see" such devices using very old phones -- people are
    accustomed to seeing such things.

    Can you see my BLE garage door opener? Or, do you first have to
    install "my app" that LOOKS for it?

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lasse Langwadt@3:633/10 to All on Saturday, July 25, 2026 13:49:50
    On 7/25/26 11:00, Don Y wrote:

    Can you see my BLE garage door opener?˙ Or, do you first have to
    install "my app" that LOOKS for it?

    what would be the point? if you don't have the app you can't use it

    BLE keyboard/mouse and such recognized universal devices will show up

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Saturday, July 25, 2026 04:52:21
    On 7/25/2026 4:49 AM, Lasse Langwadt wrote:
    On 7/25/26 11:00, Don Y wrote:

    Can you see my BLE garage door opener?˙ Or, do you first have to
    install "my app" that LOOKS for it?

    what would be the point? if you don't have the app you can't use it

    BLE keyboard/mouse and such recognized universal devices will show up

    "What would be the point?> If you can't see the device, you
    don't need the app?"

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lasse Langwadt@3:633/10 to All on Saturday, July 25, 2026 19:09:53
    On 7/25/26 13:52, Don Y wrote:
    On 7/25/2026 4:49 AM, Lasse Langwadt wrote:
    On 7/25/26 11:00, Don Y wrote:

    Can you see my BLE garage door opener?˙ Or, do you first have to
    install "my app" that LOOKS for it?

    what would be the point? if you don't have the app you can't use it

    BLE keyboard/mouse and such recognized universal devices will show up

    "What would be the point?>˙ If you can't see the device, you
    don't need the app?"

    if you don't have the device in front to of you you wouldn't know what
    to look for and you wouldn't need the app because you couldn't do
    anything with it anyway

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Saturday, July 25, 2026 13:09:38
    On 7/25/2026 10:09 AM, Lasse Langwadt wrote:
    On 7/25/26 13:52, Don Y wrote:
    On 7/25/2026 4:49 AM, Lasse Langwadt wrote:
    On 7/25/26 11:00, Don Y wrote:

    Can you see my BLE garage door opener?˙ Or, do you first have to
    install "my app" that LOOKS for it?

    what would be the point? if you don't have the app you can't use it

    BLE keyboard/mouse and such recognized universal devices will show up

    "What would be the point?>˙ If you can't see the device, you
    don't need the app?"

    if you don't have the device in front to of you you wouldn't know what to look
    for and you wouldn't need the app because you couldn't do anything with it anyway

    You've got yourself trapped inside the box! <frown>

    BLE isn't just "an invisible 30 ft cord" used to connect "you"
    to "some THING".

    You can use them to indicate proximity to a specific location.
    Or, the availability of a particular service.

    E.g., I could set a device in front of each bathroom in an airport,
    identifying itself as "BATHROOM" and you would know you were within
    30 ft of a bathroom whenever you saw a service bearing that name.

    Or, a device advertising itself as "Text HOWDY for latest sale items"

    And, you wouldn't have to power them from the mains OR replace
    batteries with any frequency.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Lasse Langwadt@3:633/10 to All on Sunday, July 26, 2026 00:54:40
    On 7/25/26 22:09, Don Y wrote:
    On 7/25/2026 10:09 AM, Lasse Langwadt wrote:
    On 7/25/26 13:52, Don Y wrote:
    On 7/25/2026 4:49 AM, Lasse Langwadt wrote:
    On 7/25/26 11:00, Don Y wrote:

    Can you see my BLE garage door opener?˙ Or, do you first have to
    install "my app" that LOOKS for it?

    what would be the point? if you don't have the app you can't use it

    BLE keyboard/mouse and such recognized universal devices will show up

    "What would be the point?>˙ If you can't see the device, you
    don't need the app?"

    if you don't have the device in front to of you you wouldn't know what
    to look for and you wouldn't need the app because you couldn't do
    anything with it anyway

    You've got yourself trapped inside the box!˙ <frown>

    no, but I know how it usually goes here. You ask a question and for
    every answer you get you invent a new reason why that's wrong

    BLE isn't just "an invisible 30 ft cord" used to connect "you"
    to "some THING".

    You can use them to indicate proximity to a specific location.
    Or, the availability of a particular service.

    E.g., I could set a device in front of each bathroom in an airport, identifying itself as "BATHROOM" and you would know you were within
    30 ft of a bathroom whenever you saw a service bearing that name.

    Or, a device advertising itself as "Text HOWDY for latest sale items"

    And, you wouldn't have to power them from the mains OR replace
    batteries with any frequency.


    so if you want that you install an app for that

    why anyone in their right mind want a phone to by default have something
    that notifies of every random BLE device you pass, and getting spammed
    with annoying ads on top of that ?






    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Saturday, July 25, 2026 17:00:39
    On 7/25/2026 3:54 PM, Lasse Langwadt wrote:
    On 7/25/26 22:09, Don Y wrote:
    On 7/25/2026 10:09 AM, Lasse Langwadt wrote:
    On 7/25/26 13:52, Don Y wrote:
    On 7/25/2026 4:49 AM, Lasse Langwadt wrote:
    On 7/25/26 11:00, Don Y wrote:

    Can you see my BLE garage door opener?˙ Or, do you first have to
    install "my app" that LOOKS for it?

    what would be the point? if you don't have the app you can't use it

    BLE keyboard/mouse and such recognized universal devices will show up >>>>
    "What would be the point?>˙ If you can't see the device, you
    don't need the app?"

    if you don't have the device in front to of you you wouldn't know what to >>> look for and you wouldn't need the app because you couldn't do anything with
    it anyway

    You've got yourself trapped inside the box!˙ <frown>

    no, but I know how it usually goes here. You ask a question and for every answer you get you invent a new reason why that's wrong

    Because I've likely thought about these things more than any
    respondant. If I ennumerate all of the things that are wrong in
    my initial post, then you'll complain its too lengthy.

    BLE isn't just "an invisible 30 ft cord" used to connect "you"
    to "some THING".

    You can use them to indicate proximity to a specific location.
    Or, the availability of a particular service.

    E.g., I could set a device in front of each bathroom in an airport,
    identifying itself as "BATHROOM" and you would know you were within
    30 ft of a bathroom whenever you saw a service bearing that name.

    Or, a device advertising itself as "Text HOWDY for latest sale items"

    And, you wouldn't have to power them from the mains OR replace
    batteries with any frequency.

    so if you want that you install an app for that

    So, when you fly into JFK, you install the JFK app so it
    can tell you where you are on the concourse and how
    long the walk is to your gate or baggage claim or the nearest
    bathroom.

    When you fly into Dulles, you install the Dulles app.
    Atlanta, the Atlanta app.

    When you book a room at a Hilton, the Hilton app tells you where
    your room is, lets you interface to *your* HVAC, schedule a
    wakeup call, etc. Do the same for Marriott with the Marriott app. etc.

    When you shop at Target, the Target app guides you around the store
    and highlights sale items. Costco, the Costco app. Walmart, the
    Walmart app.

    etc.

    And, you keep ALL of these updated so they are usable when you
    next might need them.

    Or, you access the *up-to-date* web page for each of these
    WHILE you need said access and your phone is unburdened by
    them once you close the browser.

    <https://webbluetoothcg.github.io/web-bluetooth/scanning.html>
    why anyone in their right mind want a phone to by default have something that
    notifies of every random BLE device you pass, and getting spammed with annoying
    ads on top of that˙ ?
    You obviously would have controls -- just like your phone doesn't
    notify you of every WiFi AP that you pass.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Theo@3:633/10 to All on Sunday, July 26, 2026 15:38:59
    Don Y <blockedofcourse@foo.invalid> wrote:
    And, you keep ALL of these updated so they are usable when you
    next might need them.

    Or, you access the *up-to-date* web page for each of these
    WHILE you need said access and your phone is unburdened by
    them once you close the browser.

    <https://webbluetoothcg.github.io/web-bluetooth/scanning.html>
    why anyone in their right mind want a phone to by default have something that
    notifies of every random BLE device you pass, and getting spammed with annoying
    ads on top of that˙ ?
    You obviously would have controls -- just like your phone doesn't
    notify you of every WiFi AP that you pass.

    I don't know a whole lot about BLE but AFAIK it provides *communication* but doesn't define the *semantic meaning* in the way you want.

    In other words your garage door opener has two messages, 'open' and 'close'. BLE lets you send message A or message B, but it doesn't define the meaning that says 'you send message A to open the door' and 'message B means close'. Without that, you can't construct a UI with buttons for open and close.

    Zigbee, to use another example, does provide enough meaning that you can
    make those open and close buttons from a generic UI without needing to run
    code from the manufacturer. I don't think BLE does. You have make a device expect a HID profile (ie a keyboard) and maybe decide that 'Enter' means
    open and 'Delete' means close or something, but again you need manufacturer code to make that work (or somebody else has reverse engineered that).

    There are various BLE profiles like fitness and audio where these things
    have been specified and they can be interpreted by generic code, but if you don't map to one of those profiles then generic support isn't possible.

    https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles

    Theo

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Don Y@3:633/10 to All on Sunday, July 26, 2026 09:12:29
    On 7/26/2026 7:38 AM, Theo wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:
    And, you keep ALL of these updated so they are usable when you
    next might need them.

    Or, you access the *up-to-date* web page for each of these
    WHILE you need said access and your phone is unburdened by
    them once you close the browser.

    <https://webbluetoothcg.github.io/web-bluetooth/scanning.html>
    why anyone in their right mind want a phone to by default have something that
    notifies of every random BLE device you pass, and getting spammed with annoying
    ads on top of that˙ ?
    You obviously would have controls -- just like your phone doesn't
    notify you of every WiFi AP that you pass.

    I don't know a whole lot about BLE but AFAIK it provides *communication* but doesn't define the *semantic meaning* in the way you want.

    What a stream of bits "means" can be interpreted any way you want.
    We tend to agree on what the bits that have been mapped to these characters mean. But, they could easily be interpreted to mean ANYTHING else.

    I can set my SSID to "Dr Alonzo's Cardiology" and convey (deceptive) information to passersby looking at available BT connections.

    In other words your garage door opener has two messages, 'open' and 'close'. BLE lets you send message A or message B, but it doesn't define the meaning that says 'you send message A to open the door' and 'message B means close'. Without that, you can't construct a UI with buttons for open and close.

    That's up to whomever defines that interface. A and B might, instead,
    be "turn on the light that is part of the opener mechanism" and
    "prevent any other WIRED controls from being recognized by the opener".

    The FIRST issue to address is how ubiquitous the underlying technology
    is and how familiar it is to users:
    "How ubiquitous is (or isn't!) this? Is there a general
    (temporal) cutoff point where its support is "expected"
    before which it is a rarity?"
    The *hardware* and OS support has been around. But, it hides behind
    specific applications tied to specific peripherals -- a small subset
    of how it CAN be used.

    Folks think of Bluetooth (Classic) and WiFi as "connectors". You "plug in" your earbuds and "plug your phone" into the internet. *YOU* control that action, for the most part. Unless you wander too far from your phone
    (or the AP), you EXPECT the connection to persist (barring hardware
    failures)

    They don't think of it as something that they can have fleeting interactions with and still extract value. Waiting for a table at a restaurant and
    "seeing" YOUR expected wait time updated dynamically (you will NEVER connect
    to that instance again yet it has value NOW). Or, navigating a hospital
    or other semi-public facility for the first (only?) time. Or,
    standing in an endless line at Disney{Land,World} and receiving an updating notification "Wait time from this point is 45 minutes" -- which obviously changes the nearer you get to the destination.

    It's only when people become accustomed to such interactions that they
    start *looking* for them. Otherwise, the technology has no value to them.

    Appliances now have the ability to alert their users of significant
    events. But, do so using heavy protocols that often rely on (external)
    third parties (why can't my washing machine contact me directly without
    having to go through a manufacturer's server?)

    Zigbee, to use another example, does provide enough meaning that you can
    make those open and close buttons from a generic UI without needing to run code from the manufacturer. I don't think BLE does. You have make a device expect a HID profile (ie a keyboard) and maybe decide that 'Enter' means
    open and 'Delete' means close or something, but again you need manufacturer code to make that work (or somebody else has reverse engineered that).

    There are various BLE profiles like fitness and audio where these things
    have been specified and they can be interpreted by generic code, but if you don't map to one of those profiles then generic support isn't possible.

    If you can't *see* that BLE devices are present, then you don't consider looking to use them.

    If I walk into a coffee shop, store, doctor's office, etc. there is no guarantee that they will DISPLAY an access point that I can use, there
    (as a courtesy). If my phone couldn't show me the SSIDs that it was encountering while there, I likely wouldn't notice the one named
    "Joe's Coffee Shop" so would not avail myself of that capability.

    One wouldn't know the airport had beacons strewn about at known locations
    to assist with pedestrian navigation unless you could *see* those. Seeing
    them once might encourage you to investigate what sort of apps can
    exploit them and how to acquire those.

    As I said upthread, you definitely wouldn't want to be bothered with
    installing an *app* to take advantage of these as their use frequency
    would likely approach zero. But, (as also indicated) referencing
    them in a web page that a facility can serve via a URl broadcast by
    a beacon (cf Eddystone) makes a lot of sense -- IF you are savvy
    enough to look for them.

    From the informal survey I've done, most phones don't NATIVELY report
    the existence of proximate BLE devices. One has to install a scanner
    if you want to see what's available. And, tolerate the battery drain
    if one wanted to *follow* the signals available as one wanders about.

    And, Average Joe's likely would just find this information confusing.
    They aren't sophisticated enough -- YET -- to see its value. If
    they've opted to buy a fitness tracker or watch, then their knowledge
    of BLE is hidden inside that product offering; they know nothing of
    what *else* it can do for them.

    https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles
    Yes, but you can always create a custom profile -- for Classic or LE.
    Nothing forces you to use a technology in a particular manner.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)