I am perplexed by the Debug node not showing any payloads although the device is transmitting and logging data on Losant. So far, I have used two devices and had this problem with both. First, with the Dark Sky API and second with a NodeMCU device. In both cases, the Debug tab doesn’t show any data at all.
It just doesn’t appear under the Debug node in the Workflow although I can find it under the Debug tab of the device. I have tried updating the packet size in the MQTT library as was suggested in another thread here.
It looks like the device whose state is being set in your workflow is not the same device you’re referencing in your other screenshot. In fact they are different applications.
I did notice that your workflows are all disabled; could it be that that is the issue? Your device reporting button state would still get a state report in the platform (which you see on the device page) but it would not fire the disabled workflow (meaning you wouldn’t see anything in the debug log).
I also have SMS notification in the workflow that extracts temperature data from the payload and embeds it in the message. That’s working fine which shows the workflow is operational.
We’ve seen cases before where, if a workflow is left open in your browser for a long time and then you return to it, the debugging stream detaches. Could you try refreshing your browser and seeing if that solves the problem?
If not, could you give me a little more information on your browser and operating system?
Sanjay, glad to hear the debugging is working under a different setup.
Regarding the original problem, our browser testing in Windows 7 Chrome still shows the debug panel working correctly. Can you let me know what specific version of Chrome you’re running on that machine?
The fact that this is a “corporate laptop” has me wondering if there is anything installed on the machine that would prevent the kind of continuous connection required in the debug log.
