Unclear on Device / Executable Location steps in Getting Started

[heaversm]

Hi - trying to set this up and following along fairly well until this part:

Add the details of any iBeacons you have or other Bluetooth devices you want to track

sudo mkdir /etc/signswift
sudo cp config.json /etc/signswift/config.json
nano /etc/signswift/config.json

Here, my question is, is this just if you know you have a specific device you want look for? Will it only monitor for the devices you add here, or scan for any device?

And then this part:

edit the .service file to point to the scan executable location by editing the ExecStart and WorkingDirectory lines:

nano pi-sniffer.service

when I look in this file, I see the following:

[Service]
# Env Vars - set these using sudo systemctl edit pi-sniffer.service and NOT here
# Environment="HOST_NAME=<name of Pi, optional will use system hostname if not set>"
# Environment="HOST_DESCRIPTION=<explain where the sensor is located (for dashboard)>"
# Environment="HOST_PLATFORM=<Pi3b+ or some other platform id (for dashboard)>"
ExecStart=/opt/sniffer/scan
WorkingDirectory=/var/sniffer

My questions here:
the default paths listed for ExecStart and WorkingDirectory do not exist on my pi (/opt/sniffer/scan and /var/sniffer). Do I need to make them?

What does the "scan executable location" refer to?

I extracted your repo to ~/pi-sniffer. Would the scan executable be there?

If I run bash build.sh without making any changes to those paths, I currently get the following output:

Copy scan to /opt/sniffer
installing service
Created symlink /etc/systemd/system/multi-user.target.wants/pi-sniffer.service → /etc/systemd/system/pi-sniffer.service.
starting service
now tailing log, ctrl-c to stop but leave service running
log level use -p 6 for info level, -p 7 for debug level or remove it
-- Journal begins at Mon 2022-04-04 05:05:58 PDT. --
May 30 10:26:47 raspberrypi systemd[1]: Started Pi Sniffer.
May 30 10:26:47 raspberrypi scan[9481]: WARNING MESSAGE
May 30 10:26:47 raspberrypi scan[9481]: [120B blob data]
May 30 10:26:47 raspberrypi scan[9481]: Did not read beacons.jsonl
May 30 10:26:47 raspberrypi scan[9481]: [118B blob data]
May 30 10:26:47 raspberrypi scan[9481]: Did not read access.jsonl
May 30 10:26:47 raspberrypi scan[9481]: No UDP mesh port configured
May 30 10:26:47 raspberrypi scan[9481]: DBUS name acquired 'com.signswift.sniffer'

and lastly I'm confused about those .env vars in that file. It says:

edit pi-sniffer.service and NOT here

but that's what I'm doing - editing pi-sniffer.service - so does that mean I need to set these env vars?

Thanks for any help you can provide!

[alimpam]

i have the same problem. i followed the "Getting Started" Doc, i start the scan but its not finding any devices. i thought it scans ANY device?? @heikotroetsch