From nobody Tue Aug 22 06:49:34 2023 X-Original-To: freebsd-bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RVKhv6Z2nz4qSNQ for ; Tue, 22 Aug 2023 06:49:51 +0000 (UTC) (envelope-from dmitry.medvedev@gmail.com) Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RVKhv5tp8z4cmK for ; Tue, 22 Aug 2023 06:49:51 +0000 (UTC) (envelope-from dmitry.medvedev@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-26f4bc74131so1359143a91.1 for ; Mon, 21 Aug 2023 23:49:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692686991; x=1693291791; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tZnVi6sjKl0d8TVrGjgX2FVsSbwWQ07aHJAjKErt708=; b=o7hW2b62h7HOg7NIGE0URYHEmL5ZUwLFWty2ZhVJkvPjEDev+YKeMkY9HFywEMwqs+ WYGd2iA4ZB/pHs5STsiEEHIH/TEy+6Kbv1wcDVV+m/z+xVoC9vA8DCtfeFsr4qZ3lLj5 1CppObH2w7s+ECmc2lRrZ3wwewFI1ICw+rm6HkiVhLqXBBfmkBKkmnaswq5lPbioM7Xd ICgqZMnQIecoBnE+Gp4/biwePsO3DG45i5i9fx3F9mzOwoJxSS6ZK2/jx8crOHSJHmdA wvy+WDoskzmYlQtFax0rPivFEQ89+FhLw3hYHuEH77uBx9IrAJNHLxupyLd3Jk16JO45 mxMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692686991; x=1693291791; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tZnVi6sjKl0d8TVrGjgX2FVsSbwWQ07aHJAjKErt708=; b=GFMjwpElRoIewI6rVTHK3eOlPKfiXlNobwbRvqXCr4ZYg2yqS5la73LE5YksEBOhuU o94lAhBiA3YZNffaz15QGuGLs+WisD7fYRv+MWyd1AL1yH/VrosSe8+xJgX7fwhMgrH0 jlIEgSywBESKLqMJpH6hfOZsgXdUbI1bEc7f/pspek3RQlbqWnfSFxGcCeQPJZw76ghv 9inA6XxRFXncWwPuV/3Vm7BYcGQW+fn0l8A8FLzqtHwm6sce2gCwg0a+ZPYkaolmRUvC lAm5BYAJSFmGqD+aJz5iFtPbT5O4YSIq6Tzd7oUN5FwEwh5YfLI8oaxQsLFVUTCrTYia 6OQw== X-Gm-Message-State: AOJu0Yz6DzTuXkvlYJcB6h5x+jWzFySz5niDRil9RuA3hXfcETo4Y3Ab l8QYJIZ15icjplKYWgfGQ9t6N9PCthSSOimlXjrLMmn6Ky0= X-Google-Smtp-Source: AGHT+IH6qQBl0XwLOWnrbfnNEjAfCKsJvcDjRIE70x8Z0bOHrCalW2mOnij9/rltIu0oLi82RbtmP+GrYq03mGcJvtk= X-Received: by 2002:a17:90b:1986:b0:268:798:a28b with SMTP id mv6-20020a17090b198600b002680798a28bmr12911309pjb.23.1692686990500; Mon, 21 Aug 2023 23:49:50 -0700 (PDT) List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@freebsd.org MIME-Version: 1.0 References: <0A093E3B-4F8F-4EB1-A1FD-461BF8293EAC@bumblingdork.com> In-Reply-To: From: "Dmitry N. Medvedev" Date: Tue, 22 Aug 2023 08:49:34 +0200 Message-ID: Subject: Re: FreeBSD won't see a specific bluetooth device To: Takanori Watanabe Cc: freebsd-bluetooth@freebsd.org Content-Type: multipart/alternative; boundary="000000000000c8e8b106037d66ec" X-Rspamd-Queue-Id: 4RVKhv5tp8z4cmK X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] --000000000000c8e8b106037d66ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable hi, thank you for your reply! I have tried your FreeBSD-BLE already :) The question is: do you have plans to support keyboards? best regards, Dmitry On Tue, Aug 22, 2023 at 5:35=E2=80=AFAM Takanori Watanabe wrote: > > On Mon, Aug 21, 2023 at 07:22:40PM +0200, Dmitry N. Medvedev wrote: > > not resolved yet, but this is what a Kinesis employee said: the Advanta= ge > > 360 Pro uses BLE. > > > > I have used the hccontrol to do le_ scan and I can clearly see the > keyboard > > in the list, > > but I have no idea on how to make it connect to my freeBSD host. > > > > any help would be appreciated! > > > > I have a tool for userland and work with Bluetooth LE mouse based on > bthidd, > but keyboard support is disabled. > > https://github.com/takawata/FreeBSD-BLE > > To recognize LE device. > 1. scan LE device and think > 2. invoke ./lepair ${BTHADDR} (-r option required if address is random > address) > 3. add hcsecd.conf in lesecd directory by copy-n-paste from lepair output= . > 4. ./lesecd > 3. in lehid directory, lehid -s ${BTADDR} > > Then keyboard may be recoginzed, but will not do useful thing. > > > > > On Wed, Aug 16, 2023 at 2:24=E2=80=AFPM Dmitry N. Medvedev < > > dmitry.medvedev@gmail.com> wrote: > > > > > good morning! > > > > > > *the context*: > > > 1. there is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2 > > > 2. there is a dell laptop with windows > > > 3. there is a macbook pro > > > 4. there is a bluetooth apple keyboard > > > 5. there is an Advantage 360 Pro bluetooth keyboard > > > > > > *the problem*: > > > using the *hccontrol -n ubt0hci inquiry* command I can list all the > > > bluetooth devices, but the Advantage 360 Pro. > > > > > > This I cannot understand. How can the said keyboard avoid being liste= d? > > > > > > I am struggling to pair the Advantage 360 Pro to my FreeBSD desktop. > > > > > > Literally any help/ideas/thoughts are welcome! > > > > > > With kind regards, > > > Dmitry N. Medvedev > > > > > > Tel.: > > > +49 176 65213116 > > > > > > --000000000000c8e8b106037d66ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
hi,
thank you for your=C2=A0reply!

I have tried your FreeBSD-BLE already :)

The= question is: do you have plans to support keyboards?

<= div>best regards,
Dmitry

On Tue, Aug 22, 2023 at 5:35=E2=80= =AFAM Takanori Watanabe <takaw= ata@init-main.com> wrote:

On Mon, Aug 21, 2023 at 07:22:40PM +0200, Dmitry N. Medvedev wrote:
> not resolved yet, but this is what a Kinesis employee said: the Advant= age
> 360 Pro uses BLE.
>
> I have used the hccontrol to do le_ scan and I can clearly see the key= board
> in the list,
> but I have no idea on how to make it connect to my freeBSD host.
>
> any help would be appreciated!
>

I have a tool for userland and work with Bluetooth LE mouse based on bthidd= ,
but keyboard support is disabled.

https://github.com/takawata/FreeBSD-BLE

To recognize LE device.
1. scan LE device and think
2. invoke ./lepair ${BTHADDR} (-r option required if address is random addr= ess)
3. add hcsecd.conf in lesecd directory by copy-n-paste from lepair output.<= br> 4. ./lesecd
3. in lehid directory, lehid -s ${BTADDR}

Then keyboard may be recoginzed, but will not do useful thing.



> On Wed, Aug 16, 2023 at 2:24=E2=80=AFPM Dmitry N. Medvedev <
> dmitry.= medvedev@gmail.com> wrote:
>
> > good morning!
> >
> > *the context*:
> > 1. there is an HP Z420 desktop with FreeBSD 13.2-RELEASE-p2
> > 2. there is a dell laptop with windows
> > 3. there is a macbook pro
> > 4. there is a bluetooth apple keyboard
> > 5. there is an Advantage 360 Pro bluetooth keyboard
> >
> > *the problem*:
> > using the *hccontrol -n ubt0hci inquiry* command I can list all t= he
> > bluetooth devices, but the Advantage 360 Pro.
> >
> > This I cannot understand. How can the said keyboard avoid being l= isted?
> >
> > I am struggling to pair the Advantage 360 Pro to my FreeBSD deskt= op.
> >
> > Literally any help/ideas/thoughts are welcome!
> >
> > With kind regards,
> > Dmitry N. Medvedev
> >
> > Tel.:
> >=C2=A0 +49 176 65213116
> >


--000000000000c8e8b106037d66ec--