Connecting to Watson IoT platform

[iurly]

Hi,
I have a few remote systems connected to the Internet through a 3G dongle running nodered and publishing data to the Watson IoT platform. I'm experiencing some issues with the nodes provided by node-red-contrib-ibm-watson-iot.
What happens is that for some reason the nodes get disconnected (perhaps connectivity goes down for some time) and don't automatically reconnect, as if giving up after a certain amount of time or retries,or after getting into a weird state. Redeploying the flow actually fixes the connection.
I haven't been able to reproduce the
issue in the lab (even with subtle triggered disconnections) as it only happens in the field.
First of all, am I using the right node for this purpose or should I use node-red-contrib-scx-ibmiotapp instead?
My understanding is that the latter should be used for simulating events...
Second of all, if I'm using the right one, how can I extract some information to help diagnose this problem?
Thanks!

[Nick O'Leary]

Hi,

node-red-contrib-ibm-watson-iot is the right set of nodes to be using as a Device or Gateway connection.

node-red-contrib-scx-ibmiotapp is what you'd use to connect as an Application.

The node should be logging what it's doing to the node-red log. If it isn't provided enough information, please raise an issue against the node here where the team will be able to advise - https://github.com/ibm-watson-iot/node-red-contrib-ibm-watson-iot

Nick

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send an email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/a78f3956-98e6-4bd1-83af-a75dd4d6fce4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[iurly]

Hi Nick,

thanks for your feedback.
As you suggested, I was able to obtain some details and opened an issue https://github.com/ibm-watson-iot/node-red-contrib-ibm-watson-iot/issues/6. (I'm running node-red-contrib-ibm-watson-iot 0.2.8)
However, after having a closer look I now suspect the issue might lie within https://github.com/ibm-watson-iot/iot-nodejs. (I have ibmiotf 0.2.34)
As a matter of fact, I also had a look there and the responsible one might be mqtt (I got mqtt 1.5.0).

That's a pretty long chain of dependencies and it's caused me a headache already.
Any ideas how I could sort that out?
Thanks!

Il giorno martedì 26 settembre 2017 17:55:19 UTC+2, Nick O'Leary ha scritto:

Hi,

node-red-contrib-ibm-watson-iot is the right set of nodes to be using as a Device or Gateway connection.

node-red-contrib-scx-ibmiotapp is what you'd use to connect as an Application.

The node should be logging what it's doing to the node-red log. If it isn't provided enough information, please raise an issue against the node here where the team will be able to advise - https://github.com/ibm-watson-iot/node-red-contrib-ibm-watson-iot

Nick

On 26 September 2017 at 16:51, iurly <gerlando...@gmail.com> wrote:

Hi,
I have a few remote systems connected to the Internet through a 3G dongle running nodered and publishing data to the Watson IoT platform. I'm experiencing some issues with the nodes provided by node-red-contrib-ibm-watson-iot.
What happens is that for some reason the nodes get disconnected (perhaps connectivity goes down for some time) and don't automatically reconnect, as if giving up after a certain amount of time or retries,or after getting into a weird state. Redeploying the flow actually fixes the connection.
I haven't been able to reproduce the
issue in the lab (even with subtle triggered disconnections) as it only happens in the field.
First of all, am I using the right node for this purpose or should I use node-red-contrib-scx-ibmiotapp instead?
My understanding is that the latter should be used for simulating events...
Second of all, if I'm using the right one, how can I extract some information to help diagnose this problem?
Thanks!

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[iurly]

Hi Nick,

looks like you had found the same issue about a year ago:
https://github.com/ibm-watson-iot/iot-nodejs/issues/25
(this means I'm not the only one who can't possibly remember EVERYTHING) ;-)

I retested after updating node-red-contrib-ibm-watson-iot (though already at the latest version)
which as a side effect updates to ibm...@0.2.39 which updated mqtt to 2.13.00.
Now everything works fine.
Thank you!