I’ve tested and I’m using the recent updates that allow the
#include "spark_disable_cloud.h" update, and they work as described. For some background, I’m running a TCP client that connects to a local Node.js TCP server and sends data from a couple sensors to the TCP server. From a high level, I use a UDP broadcast packet from the server out to the local network that the SparkCore will read to “discover” the IP of my server. The Core will then connect to the server via TCP and begin transmitting data from the sensors over TCP. I have WiFi enabled, but Spark Cloud disabled.
The issue I’m having is that now, after 30 seconds of transmission, my TCP connection to the server drops. It’s as close to 30 seconds as I can measure, every time. This is regardless of my “sample rate” that I use for my loop delay (right now, about 33ms).
Is there a chance that some of the other services (such as TCP) rely on the “heartbeat” that was maintained with the cloud prior to the recent changes that @satishgn committed recently? I did not have these issues prior to this update. But prior to the update, I was reliant on the connection to the Spark Cloud, which I have no dropped and now just use WiFi.