BLE Gateway sends non-existed beacon data

BLE Gateway
1

I’ve got a problem that two BLE gateways sent non-existed beacon data. The non-existed beacon here means these beacons were not in a reasonable distances from the gateways (maybe ~10km). May I know whether there are any reasons to cause the problem please?

Thank you.

2

Please provide information

  • Firmware version?
  • WiFi or wire connection?
  • Application HTTP/WebSocket/MQTT?
  • Please take a screenshot about config tool for pages Application, Dashboard and Network
3
  1. Fireware version 1.4.15
  2. Wifi connection
  3. Using HTTP Client

And here are the required screenshots as follows:

WechatIMG447
WechatIMG4471003×468 7.8 KB

WechatIMG448
WechatIMG448879×530 10 KB

WechatIMG449
WechatIMG449869×817 16.8 KB

4

Please test with our testing MQTT server. So we can check the data remotely.

Testing server:

  • Connection type: MQTT Client
  • MQTT Host: mqtt.bconimg.com
  • Port: 1883
  • Topic: gw/tonny
  • No username and password

Please also provide the UUIDs of your beacon. Which one is non-existed beacon data?

5

The case only happened three times after about one month’s correct data , so I’m afraid you will not find such a non-existed one in a short period. Therefore, I want to know whether there are any possibilities to cause the problem that I can work on them. Or, is there any data I should collect when the problem happens again to analyze it?

6

We haven’t got any similar reports from other user. Can you also try add an UUID filter?

7

I’ve got about 100 beacons with 10 gateways, so it is difficult to filter all those beacons with UUID.