Thanks for dropping by. To be honest, it might have been a case of BlueProximity being TOO good. It was a while ago now, but I think I found that the program had too many options, most of them seemed to relate to the proximity of the phone, rather than simply there being an simple On/Off choice. I guess I just found the interface and options a little confusing and couldn’t work out how to do exactly what I wanted to do with it. This was most likely me being dumb, rather than any problems with your program. And in any case, it gave me an excuse to learn a little bit more about Bash, something I have been keen to learn for a long while, so it was a good learning experience for me.

So, in the end, your program is very powerfull, but it did too many things. I just wanted to do one simple thing, run a command if the phone is not found, and then run another when it is.

Hope that sheds some light on the reasons for my little script

I am somewhat puzzled that you cannot do what you describe with BlueProximity. There are “lock” and “unlock” commands.

As I am the author I would like to know what my program is missing so I can make it better.

Bye
Lars

cd /home/user

Then to run the script, you need to type the following in a Terminal:

./bluetoothscan.sh

You might need superuser privalages to run it, so in this case you type:

sudo ./bluetoothscan.sh

You can also set up a cron job to run it every five minutes or so, by editing /etc/crontab