Project Description

WizFi310 captured the probe request packet of the WiFi terminal and proceeded to save it to the SD card it is already done previously. So link is http://wiznetmuseum.com/portfolio-items/visitor-tracking-via-wi-fi/

Components:

  • WIZwiki-W7500ECO’s Ethernet
  • WizFi310
  • MQTT Broker
  • Raspberry PI

 

In this post, Next proceeded to a project to store MAC information of nearby WiFi terminals on a cloud server (MQTT Broker) using WIZwiki-W7500ECO’s Ethernet, not SD card.

The MQTT Broker to use is    https://io.adafruit.com   .

 

The topic to use when publishing to the broker was used as the MAC of the device, and the message was taken as the RSSI value. (ex: topic: jehoon / f / 0008dc123456, message: 80)

In doing so, it is possible to know the existence of a certain WiFi device in the vicinity of WizFi310, the approximate stay time, and the like.

First, after running the MQTT broker on Raspberry PI, I checked to see if MQTT Publish is working properly.

raspberry

 

Since then io.adafruit.com saw to try to Publish Broker, adafruit Broker is a topic people tried to remove and then re-Publish: ” In the MAC and then verify that Publish does not contain any “.”

 

Here are some of the things we learned from the project and analyzing the data:

  1.  You can see if a specific device is around the WizFi310. The graph below compares the two devices. The left device was a long way from WizFi310 during the morning hours and came in the afternoon.

On the right side of the graph, the device was not scanned during lunchtime in a certain pattern.

 

pattern

 

1. On the other hand, since the MAC is assigned a MAC range for each smartphone vendor, it can be filtered by each vendor’s smartphone.

vender

 

The circuit configuration is the same as the previous project, and the source code is

3_component

 

https://developer.mbed.org/users/jehoon/code/WiFiTracker/

Author:  daniel

Original Source: https://wizdaniel.wordpress.com/2016/06/03/visitor-tracking-via-wifi-2/