Still editing the ttn device node, enter activations in the Event field.
Click Add to create the node.
I don’t know what is meant by ‘add to create the node’. If I ‘enter activations’ field I have to fill in a text (don’t know what to fill in here), there is no scroll list to choose from or a new popup window showing up. I presume something is still missing in my setup.
Can anyone help me on ?
Thanks,
Update1:
Okay I presume I have to understand 'enter activations in the Event field´ literally (Presumption 1). So i filled in the text ‘activations’ in the textfield labeled ‘Event’.
In my ‘ttn device node’ in Node-red I filled in the following:
Name: random name
App: clicked the edit icon and got a new screen
…App ID: I use the ‘Application ID’ on ttn console
…Region or broker: tried both ‘eu’ and ‘ttn-handler-eu’ (in ttn console Handler is ‘ttn-handler-eu’)
…Access key: ttn-account-v2.xxxxx… I used the same key as ‘default key’ under ‘ACCESS KEYS’ in ttn console.
Device ID: I use the ‘Device ID’ on ttn console
Event: I fill in the text ‘activations’
If I now do ‘Deploy’ I get a warning ‘the workspace contains some nodes that are not properly configured’ and if I do ‘Deploy’ anyway I get a warning ‘Flows stopped due to missing node types. check logs for details’. If I check the logs (/var/log/syslog on ubuntu16.04) no (new) logs are to be seen.
Update 2
I still get lots of error messages when doing deploy. I managed to get a ttn-message connected to a debug-node to give expected output in the debug window. But even if I delete all nodes in the desktop on ’ Deploy’ the error messages in debug window keeps arriving. Very annoying, I presume I should ignore them from now on (Presumption 2).
.3. Drag a debug node from the output category of the toolbox.
.4. Drag the output of the ttn device node to the input of the debug node
.5. Click Deploy to deploy the flow.
.6. In the right sidebar select the debug tab.
.7. Restart a device by briefly disconnecting power or upload a sketch.
.8. Soon, you should see the activation message coming in like ’ my-uno’ :
Well, I don’ t see anything in the debug window. And changing debug-node to ’ complete message output’ does not change anything.
Thanks for replying. Meanwhile I made some progress. I am able to create output with ttn-message connected to a debug-node. In debug-window I see output I recognize. But if I do the same with a ttn-device I don’t see any ouput. But under the ttn-device it says ‘connected’. I probably miss what the difference is between ttn-device and ttn-message.
If I empty node-red desktop completely, do deploy, I get the familiar error messages in debug window again. If I stop .node-red and restart again I get in the console same errors:
15 Jun 15:28:44 - [error] [ttn app:a2e6db4d.72d8b] No appId, accessKey or region set
15 Jun 15:28:44 - [error] [ttn app:21ab774d.8a086] No appId, accessKey or region set
…
Don’t know why node-red is still calling those apps as I removed all my nodes and node-red desktop is empty. Update: I deleted ‘flows_nodered.json’ and restarted node-red again. It now made a new empty flows_nodered.json and I finally got rid of those annoying errors.
You might need to take a look in the config nodes section of node-red. There might be config nodes of ttn that’s still running in your flow.
Depends on your node-red version, go to the top right menu button, then select ‘configuration nodes’, and you can see some configuration nodes that still exist in your flow.
TTN is for the public network and handler for Australia is ttn-handler-asia-se.
If you are using a private network hosted by Meshed the ttn nodes are not going to work. You may have more luck setting up a forward in the Meshed environment to a MQTT or HTTP node in Red.
Actually, Meshed is one of our routing partners (indicated by the public label in the console). That means they host a public TTN cluster under the same conditions as the clusters hosted by The Things Network Foundation. If you’re in Australia, Mashed will definitely have the lowest latency.
