SenseCAP Watcher Doesn't Send Any Traffic to Node-RED

Products & Technology SenseCAP
3

Hello @PJ_Glasso,

Thanks for chiming in on Xmas day! Appreciate it. :christmas_tree:

Here is the snippet for the versions:

$ node-red --version
Node-RED v4.0.8
Node.js v18.19.0
Linux 6.6.59-v7+ arm LE
$ npm -v
9.2.0
$

Yes, I’m using “an” API key, but perhaps there are other mandatory parameters too?

I do believe that I have entered the values for the following fields correctly:

  • EUI
  • Organization ID
  • API Key

The device transmits messages (as seen at the Seeed Global server logs), but for some reason the sensecap-config node is unable to read these entries? The PaaS portal has two entries. I created a second entry without a name/label for test purposes, but none of the API Keys cut-and-pasted (to avoid fat-fingering) into the corresponding node properties field to enable the node into Connected mode (as illustrated in the Seeed tutorial) make any difference to the status of the sensecap-config node.

Perhaps, owing to the absence of any entry in the Device Overview section of the Dashboard at the portal, do I need to use Bind Device explicitly even though I do not plan to view the data on a map? Thanks.

Regards.

1 Like