[Benjamin Ning]

And typically I have now solved the issue 10 minutes after posting on a forum after trying for 2 days.

A recent update must have stopped Dashboard being compatible with the Conduit. Using an older release (2.8.0) gets it working again.

In the following directory :

/var/config/app/install/development

run the following command :

npm install node-red-dashboard@2.8.0 -verbose

Restart Node-Red and it should now be working.

[Benjamin Ning]

After a bit more playing this morning I have discovered where I was going wrong. Two errors, one of which was due to my unfamiliarity with cURL.

So you can’t pass the cURL command a URL for retrieve the data, it has to be done in two steps, which can be entered in one command as below:

curl http://www.examplesite.co.uk/flows.json | curl -X POST -k https://localhost:1880/flows -H “Content-Type: application/json” -H “Node-RED-Deployment-Type: full” -H “Node-RED-API-Version: v1” -H “Authorization: Bearer ********” –data @- -v

Also I thought my Node-RED_Version type was v2, but in fact it was v1.

Hope this helps someone else out.

Ben.

[Benjamin Ning]

Hi Ajay.

Thanks for your reply.

Ideally I wish to write an application which will connect to the Conduit MQTT broker and subscribe/publish to the broker. For now I am testing with various existing MQTT Clients and failing at connecting to the Conduit broker.

I have setup a MQTT input node using your kindly provided information, and the node connects to the Conduit broker no problem and I can see endnodes joining ok when the input node is connected to a debug node.

So it seems as though the Conduit MQTT broker is accepting local clients OK, but not remotes ones?

This is probably a Firewall issue, but I *think* I have allowed incoming connections with the following active Input Filter Rule:

Allow Inbound ANY 1024-65535 TCP/UDP ACCEPT

Thanks again,

Ben.

[Author]

Posts