Where is retry logic? Some dupes arriving

Hardware
1

Some of my sensors are sending duplicates, and sometimes the messages are out of order as well. Below is one set of recent data. Curious to know how the retry works, and where retry is occuring.

{
“dateTime”: “2024-02-29T21:32:40.0000000Z”,
“counter”: 134,
“rssi”: 86,
},
{
“dateTime”: “2024-02-29T21:30:15.0000000Z”,
“counter”: 131,
“rssi”: 40,
},
{
“dateTime”: “2024-02-29T21:13:10.0000000Z”,
“counter”: 118,
“rssi”: 87,
},
{
“dateTime”: “2024-02-29T21:03:24.0000000Z”,
“counter”: 110,
“rssi”: 87,
},
{
“dateTime”: “2024-02-29T20:51:12.0000000Z”,
“counter”: 100,
“rssi”: 88,
},
{
“dateTime”: “2024-02-29T20:51:12.0000000Z”,
“counter”: 100,
“rssi”: 88,
},
{
“dateTime”: “2024-02-29T20:46:19.0000000Z”,
“counter”: 96,
“rssi”: 87,
},
{
“dateTime”: “2024-02-29T20:46:19.0000000Z”,
“counter”: 96,
“rssi”: 87,
},
{
“dateTime”: “2024-02-29T20:30:28.0000000Z”,
“counter”: 83,
“rssi”: 73,
},
{
“dateTime”: “2024-02-29T20:30:28.0000000Z”,
“counter”: 83,
“rssi”: 73,
},
{
“dateTime”: “2024-02-29T20:18:16.0000000Z”,
“counter”: 73,
“rssi”: 87,
},
{
“dateTime”: “2024-02-29T20:18:16.0000000Z”,
“counter”: 73,
“rssi”: 87,
},
{
“dateTime”: “2024-02-29T20:03:38.0000000Z”,
“counter”: 61,
“rssi”: 88,
},
{
“dateTime”: “2024-02-29T20:03:38.0000000Z”,
“counter”: 61,
“rssi”: 88,
},
{
“dateTime”: “2024-02-29T19:52:39.0000000Z”,
“counter”: 52,
“rssi”: 88,
},
{
“dateTime”: “2024-02-29T19:52:39.0000000Z”,
“counter”: 52,
“rssi”: 88,
},
{
“dateTime”: “2024-02-29T19:50:13.0000000Z”,
“counter”: 50,
“rssi”: 66,
},
{
“dateTime”: “2024-02-29T19:50:13.0000000Z”,
“counter”: 50,
“rssi”: 66,
},

2

Can you provide more information?

What are you using as the receiver device(Modem, Gateway, etc)?

What software are you using to parse sensor data? node-red-enterprise-sensors, custom, etc?

3

We’re using the Enterprise IIoT Gateway model EG5120 and Node-red.

Node-red

4

Hi,

Can you confirm these are all from the same sensor? The RSSI is changing pretty substantially.

5

I’ve added two more and updated files, each a separate sensor. And yes, the above was one sensor, apologies for not labeling

Is there a unique message ID field I should add to the output to confirm/verify messages with the same counter are true duplicate resends?

Sensor 3.txt (1.2 KB)
Sensor 21.txt (2.5 KB)
.

6

I’m not sure these are duplicates. The reason I say that is the Duplicate transmissions have different RSSIs:

{
    "dateTime": "2024-03-01T17:15:47.0000000Z",
    "counter": 196,
    "rssi": 59
},

{
    "dateTime": "2024-03-01T17:17:02.0000000Z",
    "counter": 196,
    "rssi": 40
},

Also the timestamp is slightly different so they came in at two separate times. Are these records stored on the Gateway or is this a database on a remote server? If it’s on a remote server are there two Gateways on the site?

7

Its stored on a remote server and currently there is only one gateway running at the site. The sensors are currently set to send every one minute. There’s just two seconds difference in the timestamp. What would explain the same counter on these?

Also, question for u: If there’s dupes, will the _msgid be identical?

8

is the sensor doesn’t get an ACK within the allotted time it will try to resend the packet. the re transmitted packet will be same and thus result into same counter value.