Skip to content
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

scanner_eddystone_example.py not working #34

Closed
YoussF opened this issue Jan 14, 2019 · 2 comments
Closed

scanner_eddystone_example.py not working #34

YoussF opened this issue Jan 14, 2019 · 2 comments
Labels

Comments

@YoussF
Copy link

YoussF commented Jan 14, 2019

Hello everyone,

I trying to use to example file for scanning EddystoneUID frames... but it looks like it doesn't work. I know that there are similar related closed issues for the same problem (#10 and #25) and @citruz has replied that this has been fixed in 1.3.0 but it does not seems to be the case (at least for me).

I removed only one line form the original example, the one that is used to filter the namespace.

device_filter=EddystoneFilter(namespace="12345678901234678901"),

So here is the code i used :

import time
from beacontools import BeaconScanner, EddystoneTLMFrame, EddystoneFilter, EddystoneUIDFrame

def callback(bt_addr, rssi, packet, additional_info):
    print("<%s, %d> %s %s" % (bt_addr, rssi, packet, additional_info))

# scan for all TLM frames of beacons
scanner = BeaconScanner(callback, 
    packet_filter=[EddystoneTLMFrame, EddystoneUIDFrame]
)
scanner.start()

time.sleep(10)
scanner.stop()

The console is not printing anything, i have several physical EddystoneUID beacons and also some that are emulated with the "Beacon Simulator" android app.

Can somebody please tell me what i am doing wrong ?

Thanks a lot.

@ruibrasfernandes
Copy link

Hi YoussF, have the same problem with a RPI zero w ... even without filtering nothing, UIF frames are not visible, only TLM.
Rui

@citruz citruz added the bug label Aug 25, 2020
@citruz
Copy link
Owner

citruz commented Aug 25, 2020

Could be the same problem as #39 which was fixed in 2.0.1. Can you please check again?

@citruz citruz closed this as completed Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants