jojiiofficial / bluetooth-serial-port-async Goto Github PK

Hi Jojii,
Please tell me one thing. I can see that in current linux stack the rfcomm utility is deprecated.
In some distros (Arch) one can still install eg bluez-deprecated-tools, while eg in Debian or Raspberry Pi OS it is still there but I think it is just a matter of time.

I need to communicate using RFCOMM with my bluetooth OBD dongle to connect to my electric car (imported from your country, btw ;))
So far I was using rfcomm + socat utility on the raspberry pi and on server I was running regular x86 rust app using tokio::net::TcpStream.

Today I switched to your crate (it was quite easy as your UnixSocket was almost a drop-in replacement for TcpStream) and I successfully crosscompiled the binary (I had to prior copy libbluetooth.a from raspberry to /usr/aarch64-linux-gnu/lib to be able to crosscompile it).

It is communicating as before, but I am really happy with this as I got rid of two additional utilities (rfcomm and socat) and I can directly use the BT dongle on the pi using your crate! :)

Am I right, that using your lib is the right choice for the future (I mean it is not using some deprecated API as rfcomm tool)?

When I run your example It can't find any devices, I have literally dozens of bluetooth devices advertising packets. What is this looking for when it scans for devices? do you have an example of a server?