Author
Topic: Turning off bluetooth auto detection (Read 4287 times)

Does anyone know how to do it? I've looked at every message on these boards that mentions bluetooth but can't find any hints on this.

My system is picking up devices from outside my house and since I live right next to a busy shopping street it's almost becoming a day job to tell the system to ignore them one by one. I figured it would get less after a while but that turned out to be wishful thinking, instead it has become a bit sluggish after litterally thousands of devices to ignore. It would be far easier for me to enable the auto detection temporarily whenever I actually want to add a new bluetooth device.

Does anyone know how to do it? I've looked at every message on these boards that mentions bluetooth but can't find any hints on this.

My system is picking up devices from outside my house and since I live right next to a busy shopping street it's almost becoming a day job to tell the system to ignore them one by one. I figured it would get less after a while but that turned out to be wishful thinking, instead it has become a bit sluggish after litterally thousands of devices to ignore. It would be far easier for me to enable the auto detection temporarily whenever I actually want to add a new bluetooth device.

Well I would guess you could disable the Bluetooth device in the divices tree in Web Admin. Or somewhat easier possibly go to Web Admin -> Wizard -> Devices -> Media Directors scroll to the MD with the Bluetooth dongle attached and click on 'Edit' software modules and then un-tick 'Bluetooth Dongle' and then click 'Save' in the pop-up window. The only problem is this will also disable all Bluetooth comms too!

So I guess the real solution is to have a on/off bluetooth detection capability in Web Admin so that when Bluetooth 'detection' is in the off mode no new devices are detected and offered for adding... but importantly existing devices that have been added already still work.

This should be feasible with some script changes and a small change in some php code i would think... i will dig into this next week :-)

As I got a little desperate that I'd never see the gui again for more then 10 seconds (on my production system no less), I have temporarily "fixed" this by getting a list of all mobile phone MAC numbers from the PnpQueue table, cleaning out the duplicates and inserting them into the UnknownDevices table. Very crude, but it worked for me.

Things work a lot smoother again, so clicking "always ignore" a few times every now and then isn't so much hassle anymore. I never would have guessed that there are such enormous amounts of bleutooth devices passing by my house every day (almost 4000 unique so far).

As I was writing this I figured the things I did might be kept in the shell's history so just for reference:

It can probably be done in a single SQL query, but I didn't feel like putting in more effort then needed. As you can see this is not for the fainthearted, and I wouldn't reccommend messing with the database directly unless you have no other option. Apart from that, this is likely not entirely the proper way of doing it anyway.

As I got a little desperate that I'd never see the gui again for more then 10 seconds (on my production system no less), I have temporarily "fixed" this by getting a list of all mobile phone MAC numbers from the PnpQueue table, cleaning out the duplicates and inserting them into the UnknownDevices table. Very crude, but it worked for me.

Things work a lot smoother again, so clicking "always ignore" a few times every now and then isn't so much hassle anymore. I never would have guessed that there are such enormous amounts of bleutooth devices passing by my house every day (almost 4000 unique so far).

As I was writing this I figured the things I did might be kept in the shell's history so just for reference:

It can probably be done in a single SQL query, but I didn't feel like putting in more effort then needed. As you can see this is not for the fainthearted, and I wouldn't reccommend messing with the database directly unless you have no other option. Apart from that, this is likely not entirely the proper way of doing it anyway.

What we need to do is find the code that is autodiscovering BT devices as the BT dongle detects them. Then we can check if there's already any API to turn off/on the autodiscovery. And then ensure there's a UI to that API.

Maybe grepping the source code for the SQL tablename that Zaerc found in the critical path to this feature.