Hi,
I have noticed that the Insights dashboard suddenly stops presenting values at a random point in time. I had a board connected on 29th Sept at 8:55am and was sending data through until 1st Oct at 2:46am. The board is still functioning and I can control it etc, but Insights doesn't display anymore informatino from teh 01/10/2024 onwards.
Node ID = Uo9LGDhnqiHom72seFCYdZ
I am only sending a custom parameter every 2 minutes and Wifi metrics. The wifi metrics sends every 30 seconds but I have not found a way of altering the frequency of that. Either way I should be affecting the fair use policy so not sure why it suddenly stops connection. The board is not connected to a PC so I can't see the logs and I was hoping you could check if something is happening in your backend that stops this data being displayed?
Insights suddenly stops getting updates
-
- Posts: 309
- Joined: Wed Feb 20, 2019 7:02 am
Re: Insights suddenly stops getting updates
Hello, sorry for not responding earlier, but we indeed see that there was no data received in Insights for a few days but it started again on 12th. Did anything change on your side making it work again?
Re: Insights suddenly stops getting updates
I power cycled the device.
Re: Insights suddenly stops getting updates
@ESP_Piyush
It suddenly stopped again. I just noticed it this morning and looking into Insights it shows it suddenly just stopped yesterday: In esp_idf it jsut shows that wifi metrics failed to add, also the parameters aren't being sent either, however the esp_rmaker_param_update_and_report doesn't seem to throw an error. The node is still connected to Rainmaker because I can still send control messages and they are received successfully. Any idea what might be causing this?
It suddenly stopped again. I just noticed it this morning and looking into Insights it shows it suddenly just stopped yesterday: In esp_idf it jsut shows that wifi metrics failed to add, also the parameters aren't being sent either, however the esp_rmaker_param_update_and_report doesn't seem to throw an error. The node is still connected to Rainmaker because I can still send control messages and they are received successfully. Any idea what might be causing this?
Who is online
Users browsing this forum: No registered users and 80 guests