-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using a small ble usb transmitter #3
Comments
You won't see iBeacons in the standard If you run |
Hi Yes, it finds it:
(This, I think, is a different beacon from my first post.) |
So, is it possible to scan for both normal bluetooth devices and simultaneously for beacons? Or is it either/or? EDIT - oh yes, it is. So all I need to do is add the -b flag. Thanks! |
unless I've misunderstood, it seems that the ibeacons are working. yay! I'll close the issue. |
Hello Andrew
Following a suggestion on the HA forum, I purchased a few small ble transmitters, with a view to trying the in a car as an arrival sensor. This is the hardware
I am having some issues with the script recognising them. In particular, it doesn't! Though, looking at the logs, my suspicion is that the powering on of a device does trigger a scan.
If I run (on a Pi, not a Pi Zero running monitor) the command
sudo hcitool lescan & \; sudo hcidump
then I get the output
(Note that the first MAC address returned does not have a name, whereas the second returns the name of the device.)
If, on the same Pi, I run
hcitool name 98:7B:F3:49:BA:71
then nothing is returned.
This makes me wonder whether the device reliably returns its name to the monitor script. Do you have any thoughts on this behaviour? What information can I supply to assist with any diagnosis?
(FWIW my suspicion is that the transmit power on these things is going to be too low to usefully use in my car anyway.)
The text was updated successfully, but these errors were encountered: