Delta between connection status events for LoRaWAN gateways and status from console (LoRaWAN specific details)

0

Hello,

We use connection status events for LoRaWAN gateways to store the state and display the connectivity gateway status in our application. We observe that the last stored connection status differs from the console (LoRaWAN specific details).

Do these two tools correspond to the same "functionality"? Has the problem already been reported to you?

Best regards

Steve
已提问 1 年前222 查看次数
3 回答
0

They are supposed to come from the same source. But if you see some event notification being dropped. We can look into it. We will use some internal hardware to test it now. You can also contact our customer support and give the gateway ID so that we can search the logs with a narrower query.

AWS
已回答 1 年前
  • Did you test it ? Have you some results to share ?

0

The status on the console (LoRaWAN specific details) should be same as the status you receive from the status events. When you mention that the console status differs, do you see different status from the events even after refreshing the window ? I tested by powering off my gateway and i got event status "Disconnected" and the console page remains "connected" until i refresh the browser. Is that the same issue ? Ideally these two functionalities are same.

AWS
专家
sunrise
已回答 1 年前
0

Even if I refresh the window, I still see this desynchronization (between LoRaWan specific details and event notifications). From the console (LoRaWan specific details) the information is still valid, the problem comes from the events status (AWS IOT>Settings>LoRaWAN and Sidewalk event notifications), I don't know if we lost some notifications or if these notifications are not sent.

Steve
已回答 1 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则