Bluetooth on Windows

[spudwebb]

I'm trying to pair a device (Tapo mini smart plug) using BLE and matter-node-shell,js on my Windows PC, but it looks like it fails to discover the device. The same device can be paired just fine when already on the network so that BLE is not needed.

Does matter.js support BLE on windows? Has this been successfully tested by anyone? If so can you recommend a bluetooth dongle to use? The one I'm testing with is quite old so that may be the problem.

Here is the debug log of my attempt:

2024-09-26 12:41:51.078 INFO Node matter.js shell controller started for node 0
2024-09-26 12:41:51.080 DEBUG MatterServer Adding CommissioningController using storage key "0".
2024-09-26 12:41:51.080 DEBUG MatterServer Mdns instances not yet created, delaying node preparation.
2024-09-26 12:41:51.092 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2024-09-26 12:41:51.097 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2024-09-26 12:41:51.102 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2024-09-26 12:41:51.104 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2024-09-26 12:41:51.109 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:undefined localAddress: 0.0.0.0:64578
2024-09-26 12:41:51.110 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:undefined localAddress: :::64579
2024-09-26 12:41:51.121 DEBUG RootCertificateManager Loaded root certificate with ID 0 from storage
2024-09-26 12:41:51.147 DEBUG NobleBleClient Error resetting BLE device via noble (can be ignored, we just tried): this._bindings.reset is not a function
2024-09-26 12:41:51.148 INFO MatterController Commissioning device with identifier {"shortDiscriminator":4} and 2 scanners and knownAddress "undefined"
2024-09-26 12:41:51.149 INFO ControllerDiscovery Start Discovering devices using identifier {"shortDiscriminator":4} ...
2024-09-26 12:41:51.150 DEBUG MdnsScanner Registered waiter for query _S4._sub._matterc._udp.local with timeout 30 seconds
2024-09-26 12:41:51.152 DEBUG NobleBleClient noble state is not poweredOn ... delay scanning till poweredOn
2024-09-26 12:41:51.153 DEBUG MdnsScanner Set 2 query records for query _S4._sub._matterc._udp.local: [{"name":"_matterc._udp.local","recordClass":1,"recordType":12},{"name":"_S4._sub._matterc._udp.local","recordClass":1,"recordType":12}]
2024-09-26 12:41:51.153 DEBUG BleScanner Registered waiter for query SD:4 with timeout 30 seconds
2024-09-26 12:41:51.169 DEBUG MdnsScanner Sending 2 query records for 1 queries with 0 known answers. Re-Announce in 1.5 seconds
2024-09-26 12:41:51.188 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2024-09-26 12:41:51.189 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2024-09-26 12:41:51.190 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2024-09-26 12:41:51.191 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2024-09-26 12:41:51.192 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2024-09-26 12:41:51.193 DEBUG UdpChannelNode Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2024-09-26 12:41:51.201 DEBUG UdpChannelNode Initialize multicast address: 192.168.1.159:5353 interface: Ethernet type: udp4
2024-09-26 12:41:51.205 DEBUG UdpChannelNode Initialize multicast address: ::%5:5353 interface: Ethernet type: udp6
2024-09-26 12:41:51.214 DEBUG UdpChannelNode Initialize multicast address: 192.168.56.1:5353 interface: VirtualBox Host-Only Network #2 type: udp4
2024-09-26 12:41:51.218 DEBUG UdpChannelNode Initialize multicast address: ::%14:5353 interface: VirtualBox Host-Only Network #2 type: udp6
2024-09-26 12:41:51.225 DEBUG UdpChannelNode Initialize multicast address: 172.24.0.1:5353 interface: vEthernet (WSL) type: udp4
2024-09-26 12:41:51.230 DEBUG UdpChannelNode Initialize multicast address: ::%23:5353 interface: vEthernet (WSL) type: udp6
2024-09-26 12:41:51.235 DEBUG NobleBleClient Noble state changed to poweredOn
2024-09-26 12:41:51.235 DEBUG NobleBleClient Start BLE scanning for Matter Services ...
2024-09-26 12:41:52.684 DEBUG MdnsScanner Sending 2 query records for 1 queries with 0 known answers. Re-Announce in 3 seconds
2024-09-26 12:41:55.683 DEBUG MdnsScanner Sending 2 query records for 1 queries with 0 known answers. Re-Announce in 6 seconds
2024-09-26 12:42:01.700 DEBUG MdnsScanner Sending 2 query records for 1 queries with 0 known answers. Re-Announce in 12 seconds
2024-09-26 12:42:13.710 DEBUG MdnsScanner Sending 2 query records for 1 queries with 0 known answers. Re-Announce in 24 seconds
2024-09-26 12:42:21.152 DEBUG MdnsScanner Finishing waiter for query _S4._sub._matterc._udp.local, resolving: true
2024-09-26 12:42:21.153 DEBUG MdnsScanner Removing last query _S4._sub._matterc._udp.local and stopping announce timer
2024-09-26 12:42:21.154 INFO ControllerDiscovery Found 0 devices using identifier {"shortDiscriminator":4}
2024-09-26 12:42:21.155 DEBUG BleScanner Finishing waiter for query SD:4, resolving: true
2024-09-26 12:42:21.156 DEBUG NobleBleClient Stop BLE scanning for Matter Services ...

[Apollon77]

I think it basically works, but I do not tested tit myself. In fact we use noble as also stated in the Readme ... so relevant details might be https://github.com/stoprocent/noble?tab=readme-ov-file#windows ... do you checked and followed this?

[spudwebb]

Using the same bluetooth dongle and the same device, it works on Linux but it doesn't on Windows:

Linux:

2024-10-08 14:48:59.885 DEBUG  NobleBleClient       Found peripheral 30:de:4b:db:7f:24 (undefined): {"localName":"undefined","txPowerLevel":"undefined","manufacturerData":"undefined","serviceData":[{"uuid":"fff6","data":{"type":"Buffer","data":[0,206,4,136,17,1,1,1]}}],"serviceUuids":["8641","fff6"],"solicitationServiceUuids":[],"serviceSolicitationUuids":[]}
2024-10-08 14:48:59.889 DEBUG  BleScanner           Discovered device 30:de:4b:db:7f:24 00ce048811010101
2024-10-08 14:48:59.893 DEBUG  BleScanner           Discovered device 30:de:4b:db:7f:24 data: {"deviceIdentifier":"30:de:4b:db:7f:24","D":1230,"SD":4,"VP":"4488+257","CM":1,"addresses":[{"type":"ble","peripheralAddress":"30:de:4b:db:7f:24"}]}

Windows:

2024-10-08 15:13:19.756 DEBUG  NobleBleClient       Found peripheral 30:de:4b:db:7f:24 (): {"localName":"","txPowerLevel":0,"manufacturerData":{"type":"Buffer","data":[]},"serviceData":[],"serviceUuids":["8641","fff6"]}
2024-10-08 15:13:19.757 INFO   NobleBleClient       Peripheral 30:de:4b:db:7f:24 does not advertise Matter Service ... ignoring

What do you need from me to report this as a bug in noble?

[Apollon77]

Ok, I would propose to open an issue in https://github.com/stoprocent/noble/issues and propose these details. It seems that on windows the "manufacturer service data" are not correctly parsed and passed back, but these are required by the Matter standard

[spudwebb]

issue created: stoprocent/noble#11

[leonardocavagnis]

Hi @Apollon77, @spudwebb
I'm experiencing the same issue. On macOS, service data is parsed correctly, but on Windows 10, it isn't.
Any updates?

[Apollon77]

Hey. The latest matter.js nightly contains the newest noble version from @stoprocent which includes the service data enhancement for windows.

Sooo... install matter.js using npm tag @dev and try and please report back.