Doing some more experimentation with RPC. I noticed that after a certain period of time the device on the Golioth Console will show up as “offline” despite still being on and sending regular messages to the log (which show up in the console). When this switch to offline occurs, the device no longer …

I appreciate you reporting the issue. We’re currently investigating and will report back with more info.

Update here. It appears that periodically calling the function “wifi_wait_for_connected_with_timeout(5);” will allow RPC to go through even when the console shows as “offline” for the device.

We drilled down on this and found an edge case where observations were occasionally being prematurely garbage collected on the server side. The gist of it is that if a device reconnected, two observations existed (a defunct one and a current one) and under just the right circumstances both were garb…

Sounds good. Let me know when you have an ETA the fix for the “online”/“offline” indicator. As a side note I am also seeing that the “online”/offline" indicator light does not update to “offline” for a long time after shutting off a device as well.

An update to the Golioth has changed the connection status behavior to address the connected/not connected issue. [image] Here’s the gist of it: Session Established: the last time the device had a new handshake with server Last Report: the last time a communication was received from the device f…

Just a quick follow-up: we’ve added documentation for the status behavior: Status | Golioth

Thanks for the update mike. I will be experimenting a bit with the new update this week.

Golioth Forums

Remote Procedure Calls stop functioning when device is left on for about an hour

Golioth Device Help