TheThingsArchive / nodered-app-node

Node-RED Library for TTN Applications
https://www.thethingsnetwork.org/docs/node-red/
MIT License
20 stars 14 forks source link

Events not known #46

Closed goofy2k closed 6 years ago

goofy2k commented 6 years ago

It is not clear which values are accepted by the event field. Although the documentation tells that a wildcard (#) can be used, the node does not accept this.

johanstokking commented 6 years ago

Can you elaborate on "does not accept this"?

goofy2k commented 6 years ago

Hi Johan, when I enter a # sign as the event, the node responds that this is not a valid entry.

BUT, yesterday I updated the nodes to a current version. I noticed that the names of the nodes have changed. Also I need to discover the new behavior. So it is best to withdraw the issue.

Apparently, the node info on nodered.org, npm and Github was not valid for my version of the nodes! Thanks Fred

Op di 10 jul. 2018 05:13 schreef Johan Stokking notifications@github.com:

Can you elaborate on "does not accept this"?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TheThingsNetwork/nodered-app-node/issues/46#issuecomment-403686056, or mute the thread https://github.com/notifications/unsubscribe-auth/AZCNzuzcS5bbJDzs7-G6Zm-qynfnvaIqks5uFBu9gaJpZM4VIPzG .

johanstokking commented 6 years ago

OK thanks for the heads up and glad to hear it's working now! Indeed that was a major update.

goofy2k commented 6 years ago

Hi Johan, I have the nodes up and running. I see activation events coming in in the events node (with event set to #).

By careful reading, and following the events link in the Quickstart I also discovered somewhat more on possible settings for events.

Unfortunately the messages generated by the events node do not contain info on the type of event (am I correct?). I also use the method to communicate via MQTT. The advantage of that approach is that for every incoming message the information on the type of event is in the topic of the message. This helps to see whats going on in my application.

Fred

johanstokking commented 6 years ago

Isn't that information put in msg (not in msg.payload)?

goofy2k commented 6 years ago

No... unfortunately not. You can also see it in the example responses in the Quickstart.

Especially if one wants to discover what's going on (like me 😊) it is useful to learn to what replacement of the wildcard the system is actually responding.

Fred

Op di 10 jul. 2018 12:42 schreef Johan Stokking notifications@github.com:

Isn't that information put in msg (not in msg.payload)?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TheThingsNetwork/nodered-app-node/issues/46#issuecomment-403779896, or mute the thread https://github.com/notifications/unsubscribe-auth/AZCNzuVe4SB9yOdT6UGAPkhdT3yrp_qhks5uFIUggaJpZM4VIPzG .

johanstokking commented 6 years ago

You are right, indeed. This should be added. I'm creating a new issue.