Beantwoord

payload send twice

Eddy Tick
Rank
Some of the uplink message are devlivered twice. The logging showed that these messages have been send twice with the same payload.

{"ADRbit":"1","AppSKey":null,"Channel":"LC4","CustomerData":{"alr":{"pro":"Static","ver":"1"}},"CustomerID":"XXXXXX","DevEUI":"XXXXX","DevLrrCnt":"9","FCntDn":"5","FCntUp":"478","FPort":"1","Lrcid":"0059AC01","LrrLAT":null,"LrrLON":null,"LrrRSSI":"-94.000000","LrrSNR":"15.000000","Lrrid":"FF010342","Lrrs":null,"MType":"2","ModelCfg":"0","SpFact":"12","SubBand":"G2","Time":"\/Date(1519734364348+0100)\/","mic_hex":"de86cc19","payload_hex":"2190f3020f5161"}

{"ADRbit":"1","AppSKey":null,"Channel":"LC4","CustomerData":{"alr":{"pro":"Static","ver":"1"}},"CustomerID":"XXXXXX","DevEUI":"XXXXX","DevLrrCnt":"1","FCntDn":"5","FCntUp":"478","FPort":"1","Lrcid":"0059AC02","LrrLAT":null,"LrrLON":null,"LrrRSSI":"-122.000000","LrrSNR":"0.000000","Lrrid":"FF01021F","Lrrs":null,"MType":"2","ModelCfg":"0","SpFact":"12","SubBand":"G2","Time":"\/Date(1519734364348+0100)\/","mic_hex":"de86cc19","payload_hex":"2190f3020f5161"}

The time is the samen but the LrrRSSI, LrrSNR and Lrrid values differ.

How is this possible?

regards

Eddy

commented out the customerid and DevEUI
icon

Beste antwoord door Tim 6 maart 2018, 10:48

Hello all,

This issue isn't fixed yet, I just got a confirmation. The workaround for the problem, resetting the LRC regularly, was done too late this time. Resulting in double messages for a short period.
Right now it should work again as it should and we will continue with the workaround untill a definitive fix is implemented!

"There is a known issue in the network, which results in Gateways sending messages to the second LRC. As a result, some messages are send to your Application Server twice. While no definitive fix is available, we do have a workaround which we have implemented and this means that you should no longer encounter this issue from this point onwards."

Bekijk origineel

8 reacties

H
Rank
Reputatie 1
Badge
More interesting is that Lrcid values differ. So, some gateways send uplinks to one network server, and some other gateways send uplinks to another one.
Eddy Tick
Rank
Should the server(s) that sends uplinks to our server not solve this problem.
Now i need to handle this myself but don't know that this is the way to go. Simply checking that the time field is the same for the device is reliable?

When is a fix for this available? 😀
H
Rank
Reputatie 1
Badge
If I were you I would track FCntUp value (for many reasons).
Tim
Rank
Reputatie 7
Badge +11
Hi @Eddy Tick,

I recognize the problem. Please read below for more information:

"An issue has been running for some time now, with Gateways using one of our core servers, allowing customers to receive double messages.
Actility is currently working on a solution to this problem, but in the meantime the core (the LRC) must be restarted daily to keep the network as stable as possible. During this restart the consequences in the network are limited, but most gateways will shortly switch to the other LRC."

I'm not sure about the current status of this issue. I will get back to you when I've received more information.
Do you experience this issue all the time?
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
D
Rank
Hello all,

This issue isn't fixed yet, I just got a confirmation. The workaround for the problem, resetting the LRC regularly, was done too late this time. Resulting in double messages for a short period.
Right now it should work again as it should and we will continue with the workaround untill a definitive fix is implemented!

There is a known issue in the network, which results in Gateways sending messages to the second LRC. As a result, some messages are send to your Application Server twice. While no definitive fix is available, we do have a workaround which we have implemented and this means that you should no longer encounter this issue from this point onwards.
Tim
Rank
Reputatie 7
Badge +11
Hello all,

This issue isn't fixed yet, I just got a confirmation. The workaround for the problem, resetting the LRC regularly, was done too late this time. Resulting in double messages for a short period.
Right now it should work again as it should and we will continue with the workaround untill a definitive fix is implemented!

"There is a known issue in the network, which results in Gateways sending messages to the second LRC. As a result, some messages are send to your Application Server twice. While no definitive fix is available, we do have a workaround which we have implemented and this means that you should no longer encounter this issue from this point onwards."
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
Eddy Tick
Rank
The issue is better now, thanh you for the reaction.

Regards

Eddy
Tim
Rank
Reputatie 7
Badge +11
Great to hear Eddy! Thanks for your confirmation. Hope we receive the definitive fix soon.
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -

Reageer