Iot-bt-extra Bluetooth dongle experience

Hardware MikroTik hardware general
1

Hi,

I am looking for any experience with Bluetooth Dongle support with the iot-bt-extra package. Please share your experience with dongles that works for you, as MikroTik has not yet published a list of compatible peripherals and I am curious to see what works for the community..

I have tried a TP-Link U400, which is Bluetooth 4.0 on a L009UiGS-2HaxD. The dongle seems to be recognized as shown below, but the scanner is not receiving anything.

[] > system/resource/usb/print
Columns: DEVICE, VENDOR, NAME, SPEED
# DEVICE  VENDOR                NAME                           SPEED
0 1-0     Linux 5.6.3 xhci-hcd  xHCI Host Controller             480
1 1-1                           TP-Link Bluetooth USB Adapter     12
2 2-0     Linux 5.6.3 xhci-hcd  xHCI Host Controller            5000
[] > iot/bluetooth/print
Columns: NAME, PUBLIC-ADDRESS, RANDOM-STATIC-ADDRESS, ANTENNA
# NAME  PUBLIC-ADDRESS     RANDOM-STATIC-ADDRESS  ANTENNA
0 bt1   A8:6E:84:47:98:0E  00:00:00:00:00:00      internal

I have compared the config to a Knot standing next to it, that is receiving advertisements, so config should be alright :slight_smile:

2

Could you please try setting:
/iot/bluetooth/scanner/set own-address-type=public
to see if it helps?

Potentially, random-static (own-address) could be causing it, if the dongle does not have “an address”.

3

@denissMT
Thanks for getting back! Based on your feedback, I have tried entering a “random” address:

/iot/bluetooth> print
Columns: NAME, PUBLIC-ADDRESS, RANDOM-STATIC-ADDRESS, ANTENNA
# NAME  PUBLIC-ADDRESS     RANDOM-STATIC-ADDRESS  ANTENNA
0 bt1   A8:6E:84:47:98:0E  E5:7B:B3:01:AD:73      internal

I have tried both with the random and the public address, but got no result, even with the TG-BT5-OUT directly next to the dongle.

Currently the full Bluetooth config looks like this:

/iot bluetooth
set bt1 name=bt1 random-static-address=E5:7B:B3:01:AD:73
/iot bluetooth scanners
set bt1 disabled=no filter-policy=whitelist own-address-type=public
/iot bluetooth whitelist
add address=18:fd:74:*:*:* address-type=public device=bt1 disabled=yes
add address=D4:01:C3:*:*:* address-type=public device=bt1 disabled=yes
add address=*:*:*:*:*:* address-type=public device=bt1
4

We have tested one and can confirm that it does not work - it has to do with the kernel version of RouterOS. Currently, not supported, but! we will be working on adding it in the future patches. So please follow changelog. We can not guarantee anything yet, but it will be on our radar.

5

Thanks for the update! I will keep my eyes open, when new software is released :slight_smile:

Do you possibly have any recommendations on something that is known to work in the meantime?

6

I have same experience with TP-Link UB500.

>system/resource/usb/print
Columns: DEVICE, VENDOR, NAME, SPEED
# DEVICE  VENDOR                NAME                           SPEED
0 3-0     Linux 5.6.3 xhci-hcd  xHCI Host Controller             480
1 1-0     Linux 5.6.3 xhci-hcd  xHCI Host Controller             480
2 4-0     Linux 5.6.3 xhci-hcd  xHCI Host Controller            5000
3 2-0     Linux 5.6.3 xhci-hcd  xHCI Host Controller            5000
4 1-1                           TP-Link Bluetooth USB Adapter     12
> iot/bluetooth/print                                             
Columns: NAME, PUBLIC-ADDRESS, RANDOM-STATIC-ADDRESS, ANTENNA
# NAME  PUBLIC-ADDRESS     RANDOM-STATIC-ADDRESS  ANTENNA 
0 bt1   8C:90:2D:41:9E:05  00:00:00:00:00:00      internal
7

ROS 7.20beta7 supports the TP Link UB400 :eyes:

1 Like
8

TPlink UB500 also works, hurray!

11

Tried a MERCUSYS (TP-Link) MA530 and it's not recognized (ROS 7.20.4 and 7.21beta8).

ma530
ma5301085Ă—192 63.1 KB

It's strange, it should be very similar to the TP-Link UB500

Thank you for your feedback, I will purchase one UB500.