Service 识别BLE信标服务(启用通知,如果可用)

Service 识别BLE信标服务(启用通知,如果可用),service,notifications,bluetooth-lowenergy,beacon,Service,Notifications,Bluetooth Lowenergy,Beacon,刚刚开始使用BLE信标,并编写了一个小程序来定位信标和列出一些服务等。下面是我可以在console.log中打印的结果 BLE service: Service handle: 43 uuid: 00001800-0000-1000-8000-00805f9b34fb characteristic: 00002a00-0000-1000-8000-00805f9b34fb characteristic: 00002a01-0000-1000-8000-00805f9b3

刚刚开始使用BLE信标,并编写了一个小程序来定位信标和列出一些服务等。下面是我可以在console.log中打印的结果

BLE service: 
  Service handle: 43
  uuid: 00001800-0000-1000-8000-00805f9b34fb
    characteristic: 00002a00-0000-1000-8000-00805f9b34fb
    characteristic: 00002a01-0000-1000-8000-00805f9b34fb
    characteristic: 00002a02-0000-1000-8000-00805f9b34fb
    characteristic: 00002a03-0000-1000-8000-00805f9b34fb
    characteristic: 00002a04-0000-1000-8000-00805f9b34fb
BLE service: 
  Service handle: 44
  uuid: 00001801-0000-1000-8000-00805f9b34fb
    characteristic: 00002a05-0000-1000-8000-00805f9b34fb
      descriptor: 00002902-0000-1000-8000-00805f9b34fb
BLE service: 
  Service handle: 45
  uuid: 0000180a-0000-1000-8000-00805f9b34fb
    characteristic: 00002a25-0000-1000-8000-00805f9b34fb
    characteristic: 00002a26-0000-1000-8000-00805f9b34fb
    characteristic: 00002a29-0000-1000-8000-00805f9b34fb
BLE service: 
  Service handle: 46
  uuid: 0000c050-0000-1000-8000-00805f9b34fb
    characteristic: 0000c051-0000-1000-8000-00805f9b34fb
    characteristic: 0000c052-0000-1000-8000-00805f9b34fb
    characteristic: 0000c053-0000-1000-8000-00805f9b34fb
    characteristic: 0000c054-0000-1000-8000-00805f9b34fb
    characteristic: 0000c055-0000-1000-8000-00805f9b34fb
    characteristic: 0000c056-0000-1000-8000-00805f9b34fb
    characteristic: 0000c057-0000-1000-8000-00805f9b34fb
    characteristic: 0000c058-0000-1000-8000-00805f9b34fb
    characteristic: 0000c059-0000-1000-8000-00805f9b34fb
    characteristic: 0000c05a-0000-1000-8000-00805f9b34fb
      descriptor: 00002902-0000-1000-8000-00805f9b34fb
    characteristic: 0000c05b-0000-1000-8000-00805f9b34fb
    characteristic: 0000c05c-0000-1000-8000-00805f9b34fb
    characteristic: 0000c05d-0000-1000-8000-00805f9b34fb
BLE service: 
  Service handle: 47
  uuid: 0000c090-0000-1000-8000-00805f9b34fb
    characteristic: 0000c091-0000-1000-8000-00805f9b34fb
      descriptor: 00002902-0000-1000-8000-00805f9b34fb
    characteristic: 0000c092-0000-1000-8000-00805f9b34fb
    characteristic: 0000c093-0000-1000-8000-00805f9b34fb
    characteristic: 0000c094-0000-1000-8000-00805f9b34fb
    characteristic: 0000c095-0000-1000-8000-00805f9b34fb
BLE service: 
  Service handle: 48
  uuid: f000ffc0-0451-4000-b000-000000000000
    characteristic: f000ffc1-0451-4000-b000-000000000000
      descriptor: 00002902-0000-1000-8000-00805f9b34fb
      descriptor: 00002901-0000-1000-8000-00805f9b34fb
    characteristic: f000ffc2-0451-4000-b000-000000000000
      descriptor: 00002902-0000-1000-8000-00805f9b34fb
      descriptor: 00002901-0000-1000-8000-00805f9b34fb
这些信标基本上传输两个值——信标本身的温度和电压。当我读更多的笔记时,我想知道是否有人能指出我需要关注的UUID/特性中的哪一个,以便能够获得温度和电压读数?当我做更多的阅读和研究时,如果有经验的开发人员能给我一些建议,我会非常感激?基本上,我需要启用有关温度和电压服务的通知。我可以从BLE库中找出如何启用通知,但如何定位/指向正确的服务/特征/描述符等?再次感谢

我有一个Arduino板,可以扫描和捕获信标上的数据

[ADV    22587] Packet received from 50:65:83:10:E6:3A
       PAYLOAD 30 bytes
               02-01-06-1A-FF-6A-00-0F-75-E9-D5-AD-15-DF-FB-48-01-52-4E-8A-4B-B9-3D-0F-00-1E-3B-9E-FF-2C
          RSSI -68 dBm
      ADV TYPE Connectable undirected
 MAN SPEC DATA 6A-00-0F-75-E9-D5-AD-15-DF-FB-48-01-52-4E-8A-4B-B9-3D-0F-00-1E-3B-9E-FF-2C

[SR     22618] Packet received from 50:65:83:10:E6:3A
       PAYLOAD 22 bytes
               12-09-69-57-45-45-43-41-52-45-20-54-65-6D-70-20-50-61-6C-02-0A-00
          RSSI -68 dBm
      ADV TYPE Connectable undirected
 COMPLETE NAME Temp mini Sensor
  TX PWR LEVEL 0

有没有关于我应该如何从这里继续下去的建议?试着掌握它的窍门。。。就是那个难以捉摸的线索。。。我想我已经了解了发生了什么:)

蓝牙Gatt服务只允许您在蓝牙外围设备上读写特征。通常,外围设备的设计是为了将某些模式写入某些特性来控制外围设备的功能

以您的问题为例,将一些模式写入某些特征可能会控制所连接的Bluetooth central是否会收到温度和/或电压变化的通知(基于超过阈值或以固定间隔)

需要了解的关键是配置蓝牙外围设备的方式完全取决于其系统设计。它不是标准的。您确实需要制造商的文档来告诉您如何操作。如果没有这些文档,您基本上是在对蓝牙外围设备进行反向工程


确定此信标设备的制造商和型号可能有助于更好地回答您的问题。如果您在制造商的网站上看不到任何文档,则制造商可能会直接回答此问题,或者其他对设备进行反向工程的人也会这样做。

谢谢您提供的信息。我向制造商发送电子邮件,但他们方面完全沉默。我开始认为,制造商热衷于推广自己的应用程序,尽管他们在任何地方都没有明确提到这一点。我现在有点蛮力,在我能发现的每项服务上都写/启用通知:)幸运的是,这个信标只做了2个,所以我可能需要一些尝试和错误才能达到目的。再次感谢这些指针——至少给了我一些线索并确认了某些事情。前三个服务是通用访问、通用属性和设备信息(请参见此处:)。其余的都是特定于制造商的,只有制造商才能告诉你那里发生了什么。好的,谢谢Nebr。我正在尝试隔离服务(就像你刚才提到的那些,还有3个,我认为可能是嫌疑犯:)它可能不是服务句柄:48 uuid:f000ffc0-0451-4000-b000-000000000000,所以我将进一步调查剩下的两个。看来我越来越近了。谢谢