[CSE-66]() Still receiving (old) data even if my device is shut down

[SivaDev1038]

Atlassian Ticket Link

https://r161038.atlassian.net/browse/CSE-66

Issue Description

Thanks for your replies. (and sorry for not giving you all the needed informations, I’m a fairly unexperienced forum user) I am using a Feather 32u4 and I indeed did disconnect it from USB and also from the battery (so I’m sure it is not sending data anymore) I do not have any own gateway (I relay on the many other gateways in my region, what was working fine until yesterday…) So after disconnecting my feather I was expecting no more traffic in the console of my application (Live data) but still i get data every 2 minutes or so. All coming from the same gateway. (Valid data came from other gateways too, but this data only come from gateway iot-gw-sc-c01) And the data come from the future! (2023-11-25T16:19:59.314845678Z see below)

Metadata: “rx_metadata”: [ { “gateway_ids”: { “gateway_id”: “iot-gw-sc-c01”, “eui”: “2CF7F1102440004F” }, “time”: “2023-11-25T16:19:59.314845678Z”, “timestamp”: 3189283163, “rssi”: -114, “channel_rssi”: -114, “snr”: 1.8, “location”: { “latitude”: 47.1315, “longitude”: 7.2213, “altitude”: 480, “source”: “SOURCE_REGISTRY” }, “uplink_token”: “ChsKGQoNaW90LWd3LXNjLWMwMRIILPfxECRAAE8Q27Li8AsaCwiWg5qeBhCy6L5+IPiW3IDppLMR”, “channel_index”: 2, “received_at”: “2023-01-17T11:08:06.215816270Z” } ],

Each packet gets (automatically) answered by: downlink transmission failed with result TOO_EARLY

Does this help for further trouble-shooting/suggestions?

What did we understand from the customer issue?

...

What doubts do we have?

...

Clarifications needed from the customer

...

Insights:

...

Supporting Internal Logs/Metrics

...

Approach/Next Steps

...

Environment

...

Checklist

• [ ] Referred Issue Debugging Flow Chart
• [ ] Gone through the SOP/Product Documentation
• [ ] Gone through the Previous Issues/Github issues, if applicable
• [ ] Approach Review Taken
• [ ] The appropriate labels have been assigned.

[SivaDev1038]

Update from the Customer

[Mat_Lynx|https://www.thethingsnetwork.org/forum/u/Mat_Lynx]

[1d|https://www.thethingsnetwork.org/forum/t/still-receiving-old-data-even-if-my-device-is-shut-down/60986/6]

One more information: This (in my eyes) strange behaviour showed up for the first time at 15. January 2023 at 23:50:03 CET (every approx. 2 Minutes since then, still ongoing)

Any idea?

[SivaDev1038]

Update from the Customer

Indeed - but I and I know many others - have added SC’s to various systems in the past to smooth out hit to lower capacity/higher internal resistance batteries to extend life and mitigate for slower chemical recovery after TX spike - so just asking

!slight_smile.png_v=12|width=72,height=72,alt=":slight_smile:"!

As you say would be a DIY mod… agree with other asks which is why I pointed OP to look at the TX metadata so we know what he is actually saying vs guessing. Guess its a case of New Year New Crystal Balls!

!rofl.png_v=12|width=72,height=72,alt=":rofl:"!

[SivaDev1038]

Update from the Customer

{quote}Does this mean that your device web console is only showing you new traffic that you are expecting?{quote}

Yes after changing the NWKSKEY and the APPSKEY only expected traffic is showing up.

I do not (intentionally) send downlink to the device. (it’s not implemented on the feather) I can not tell you if and when the feather sent f_cnt range 1178 to 1188 (I have no means to look it up)

[SivaDev1038]

Does this mean that your device web console is only showing you new traffic that you are expecting?

Yes after changing the NWKSKEY and the APPSKEY only expected traffic is showing up.

I do not (intentionally) send downlink to the device. (it’s not implemented on the feather) I can not tell you if and when the feather sent f_cnt range 1178 to 1188 (I have no means to look it up)

[SivaDev1038]

Update from the Customer fdssfklsf

[SivaDev1038]

Update from the Customer

fdssfklsf

[SivaDev1038]

Update from the Customer asgygda

[SivaDev1038]

Update from the Customer

asgygda

[SivaDev1038]

Update from the Customer zxzcd

[SivaDev1038]

Update from the Customer dsdse

[SivaDev1038]

Update from the Customer fsfdf

[SivaDev1038]

Internal Comment

wadad

[SivaDev1038]

Update from the Customer dssdesd

[SivaDev1038]

Internal Comment

dssdds

[SivaDev1038]

Update from the Customer zdzdf

[SivaDev1038]

Update from the Customer adsdAZ

[SivaDev1038]

Update from the Customer dtd

[SivaDev1038]

Update from the Customer asdd

[SivaDev1038]

Internal Comment

asS

[SivaDev1038]

Internal Comment

sasda

[SivaDev1038]

Update from the Customer dasd

[SivaDev1038]

Update from the Customer dfsdf

[SivaDev1038]

Update from the Customer wsasd

[SivaDev1038]

Internal Comment

sdfsd

[SivaDev1038]

Update from the Customer xZ

[SivaDev1038]

Internal Comment

dsa

[SivaDev1038]

Internal Comment

sff

[SivaDev1038]

Update from the Customer sfd