thethingsarchive / nodered-app-node Goto Github PK

In the works by @romeovs at https://github.com/TheThingsNetwork/nodered-app-lib/tree/feature/downlink-node

Hi, I've been trying to get TTN working on a multitech gateway using node-red, I've got the files on there and have been able to get the quickstart on there, the only thing I'm missing is the ability to edit the app. I've seen from the quickstart that generally people are able to fix this by seeing anything in the console when they start node-red, however on a multitech gateway it comes preinstalled and is used using their internal GUI when you connect to the gateway.

I've tried testing the "node red.js" command to fix things, but I've fixed all the errors I can here and it still doesn't work. (Only warns are about "use of const in strict mode", not sure if that will have an effect, assuming not).

I did find that due to the way I installed it originally that the package.json files had where as a different file location, but after fixing that it's still not working. (Fixed 3 of these, could be more but can't find them).

Don't know if theres any ideas as to this or whether people know what worked for them in the past, thanks.

I've configured the TTN app, with access key, and deployed the flow. However it is not showing as connecting, and nothing comes on the debug.

Where can I look further to diagnose this?

We've had a report where after exporting and importing a flow the user had the No app set error. We need to check if in this scenario indeed the link to the config node breaks.

Somehow the node has disappeared from the Node-RED Library. Maybe because it's confused by the refactor-tagged versions I published?

After installing the app-node v2.05 in the node-red UI i see this error:

Flows stopped due to missing node types.
ttn app

The app nodes are not working any longer. In the app the drop down list disappeared.

The app nodes are listed under unknown nodes with this error:

This node is a type unknown to your installation of Node-RED.
If you deploy with the node in this state, it's configuration will be preserved, but the flow will not start until the missing type is installed.

Reinstallation of node-red and node.js did not help :-(

On installing this node, node-red just crashes on startup with the message Illegal Instruction.

if i delete this node node-red starts as normal. i think zero is arm6. Is this node for armv7?

I've installed from pallette manager as well as from command line in ~/.node-red$ npm install node-red-node-xyz and the same problem

The MQTT broker now published topics for specific fields:
https://github.com/TheThingsNetwork/ttn/tree/refactor/mqtt#uplink-fields

In the node's settings the user should be able to override the default messages topic alias (which is +/devices/+/up.

Hi, i had a working flow up and running and reinstalled the modules again for some reason. Now the ttn app node is missing. I tried to reinstall the module serveral times, restarted node etc. but still the problem remains.

Any idea on this?

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.

Node configuration does not work when both node-red-contrib-ttn and node-red-contrib-string are installed. Instead of the expected text entry fields for 'App ID', 'Access key', etc. I get a dropdown menu with a 'string' configuration node.

The issue is caused by the 'type: "string"' entry in every ttn node's html file. The type property is optional and should be removed.

Quite some changes:

• payload_raw is now decoded: TheThingsArchive/node-app-sdk#15
• sendBytes(payload) can now be array: TheThingsArchive/node-app-sdk#17
• Support for TLS: TheThingsArchive/node-app-sdk#20
• dev_id is no longer in payload but first argument of callbacks: TheThingsArchive/node-app-sdk#25

https://docs.travis-ci.com/user/deployment/npm/

See TheThingsArchive/ttn#252 (comment)

Current order is App ID, Access Key, Region, while Access Key is all the way down on the page.

If you redeploy a node-red flow with TTN message node connections then the connection is duplicated (i.e. original connection is not closed) resulting in duplicate messages being generated.

See https://github.com/TheThingsNetwork/ttn/tree/refactor/mqtt

Install 'node-red-contrib-ttn 2.0.5' in Node-red produced the following error:
2019-06-06T06:42:22.212Z Install : node-red-contrib-ttn 2.0.5

2019-06-06T06:42:21.841Z npm install --no-audit --no-update-notifier --save --save-prefix="~" --production [email protected]
2019-06-06T06:43:58.882Z [out]
2019-06-06T06:43:58.882Z [out] > [email protected] install /config/node-red/node_modules/grpc
2019-06-06T06:43:58.882Z [out] > node-pre-gyp install --fallback-to-build --library=static_library
2019-06-06T06:43:58.882Z [out]
2019-06-06T06:44:03.254Z [err] node-pre-gyp
2019-06-06T06:44:03.259Z [err]
2019-06-06T06:44:03.260Z [err] WARN
2019-06-06T06:44:03.260Z [err] Using request for node-pre-gyp https download
2019-06-06T06:44:04.406Z [err] node-pre-gyp
2019-06-06T06:44:04.406Z [err] WARN Tried to download(404): https://node-precompiled-binaries.grpc.io/grpc/v1.21.1/node-v64-linux-arm-musl.tar.gz
2019-06-06T06:44:04.407Z [err] node-pre-gyp
2019-06-06T06:44:04.407Z [err] WARN Pre-built binaries not found for [email protected] and [email protected] (node-v64 ABI, musl) (falling back to source compile with node-gyp)
2019-06-06T06:44:04.407Z [err]
2019-06-06T06:44:15.198Z [err] gyp
2019-06-06T06:44:15.206Z [err]
2019-06-06T06:44:15.207Z [err] ERR!
2019-06-06T06:44:15.207Z [err] build error
2019-06-06T06:44:15.208Z [err]
2019-06-06T06:44:15.212Z [err] gyp
2019-06-06T06:44:15.213Z [err] ERR!
2019-06-06T06:44:15.213Z [err] stack Error: not found: make
2019-06-06T06:44:15.213Z [err] gyp
2019-06-06T06:44:15.213Z [err] ERR!
2019-06-06T06:44:15.214Z [err] stack at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
2019-06-06T06:44:15.214Z [err] gyp ERR!
2019-06-06T06:44:15.215Z [err] stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
2019-06-06T06:44:15.215Z [err] gyp
2019-06-06T06:44:15.215Z [err] ERR! stack
2019-06-06T06:44:15.216Z [err] at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
2019-06-06T06:44:15.216Z [err] gyp
2019-06-06T06:44:15.216Z [err] ERR! stack
2019-06-06T06:44:15.216Z [err] at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
2019-06-06T06:44:15.216Z [err] gyp
2019-06-06T06:44:15.217Z [err] ERR!
2019-06-06T06:44:15.217Z [err] stack at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5
2019-06-06T06:44:15.217Z [err] gyp
2019-06-06T06:44:15.217Z [err] ERR!
2019-06-06T06:44:15.218Z [err] stack at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
2019-06-06T06:44:15.218Z [err] gyp ERR!
2019-06-06T06:44:15.219Z [err] stack at FSReqWrap.oncomplete (fs.js:154:21)
2019-06-06T06:44:15.220Z [err] gyp
2019-06-06T06:44:15.221Z [err] ERR! System
2019-06-06T06:44:15.221Z [err] Linux 4.14.98-v7
2019-06-06T06:44:15.222Z [err] gyp
2019-06-06T06:44:15.223Z [err] ERR! command
2019-06-06T06:44:15.223Z [err] "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--library=static_library" "--module=/config/node-red/node_modules/grpc/src/node/extension_binary/node-v64-linux-arm-musl/grpc_node.node" "--module_name=grpc_node" "--module_path=/config/node-red/node_modules/grpc/src/node/extension_binary/node-v64-linux-arm-musl" "--napi_version=3" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"
2019-06-06T06:44:15.223Z [err] gyp
2019-06-06T06:44:15.224Z [err] ERR! cwd
2019-06-06T06:44:15.224Z [err] /config/node-red/node_modules/grpc
2019-06-06T06:44:15.224Z [err] gyp
2019-06-06T06:44:15.225Z [err] ERR!
2019-06-06T06:44:15.225Z [err] node -v v10.14.2
2019-06-06T06:44:15.225Z [err] gyp
2019-06-06T06:44:15.226Z [err] ERR!
2019-06-06T06:44:15.226Z [err] node-gyp -v v3.8.0
2019-06-06T06:44:15.226Z [err] gyp
2019-06-06T06:44:15.227Z [err] ERR! not ok
2019-06-06T06:44:15.227Z [err]
2019-06-06T06:44:15.240Z [err] node-pre-gyp
2019-06-06T06:44:15.241Z [err] ERR! build error
2019-06-06T06:44:15.241Z [err]
2019-06-06T06:44:15.245Z [err] node-pre-gyp
2019-06-06T06:44:15.245Z [err] ERR! stack
2019-06-06T06:44:15.246Z [err] Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/config/node-red/node_modules/grpc/src/node/extension_binary/node-v64-linux-arm-musl/grpc_node.node --module_name=grpc_node --module_path=/config/node-red/node_modules/grpc/src/node/extension_binary/node-v64-linux-arm-musl --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)
2019-06-06T06:44:15.246Z [err] node-pre-gyp ERR!
2019-06-06T06:44:15.246Z [err] stack
2019-06-06T06:44:15.246Z [err] at ChildProcess. (/config/node-red/node_modules/grpc/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
2019-06-06T06:44:15.246Z [err] node-pre-gyp
2019-06-06T06:44:15.247Z [err] ERR! stack
2019-06-06T06:44:15.247Z [err] at ChildProcess.emit (events.js:182:13)
2019-06-06T06:44:15.247Z [err] node-pre-gyp
2019-06-06T06:44:15.247Z [err] ERR!
2019-06-06T06:44:15.253Z [err] stack at maybeClose (internal/child_process.js:962:16)
2019-06-06T06:44:15.253Z [err] node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
2019-06-06T06:44:15.253Z [err] node-pre-gyp ERR! System Linux 4.14.98-v7
2019-06-06T06:44:15.253Z [err] node-pre-gyp
2019-06-06T06:44:15.258Z [err] ERR! command "/usr/bin/node" "/config/node-red/node_modules/grpc/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--library=static_library"
2019-06-06T06:44:15.259Z [err] node-pre-gyp ERR! cwd /config/node-red/node_modules/grpc
2019-06-06T06:44:15.259Z [err] node-pre-gyp ERR! node -v v10.14.2
2019-06-06T06:44:15.259Z [err] node-pre-gyp ERR! node-pre-gyp -v v0.13.0
2019-06-06T06:44:15.259Z [err] node-pre-gyp ERR! not ok
2019-06-06T06:44:15.262Z [out] Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static_library --module=/config/node-red/node_modules/grpc/src/node/extension_binary/node-v64-linux-arm-musl/grpc_node.node --module_name=grpc_node --module_path=/config/node-red/node_modules/grpc/src/node/extension_binary/node-v64-linux-arm-musl --napi_version=3 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)
2019-06-06T06:44:20.081Z [err] npm
2019-06-06T06:44:20.082Z [err]
2019-06-06T06:44:20.083Z [err] ERR! code ELIFECYCLE
2019-06-06T06:44:20.084Z [err] npm
2019-06-06T06:44:20.085Z [err] ERR! errno
2019-06-06T06:44:20.085Z [err] 1
2019-06-06T06:44:20.095Z [err] npm
2019-06-06T06:44:20.096Z [err] ERR! [email protected] install: node-pre-gyp install --fallback-to-build --library=static_library
2019-06-06T06:44:20.096Z [err] npm
2019-06-06T06:44:20.096Z [err] ERR! Exit status 1
2019-06-06T06:44:20.097Z [err] npm
2019-06-06T06:44:20.097Z [err] ERR!
2019-06-06T06:44:20.098Z [err] npm ERR!
2019-06-06T06:44:20.098Z [err] Failed at the [email protected] install script.
2019-06-06T06:44:20.098Z [err] npm
2019-06-06T06:44:20.098Z [err] ERR! This is probably not a problem with npm. There is likely additional logging output above.
2019-06-06T06:44:20.481Z [err]
2019-06-06T06:44:20.483Z [err] npm ERR! A complete log of this run can be found in:
2019-06-06T06:44:20.483Z [err] npm ERR! /root/.npm/_logs/2019-06-06T06_44_20_345Z-debug.log
2019-06-06T06:44:20.562Z rc=1

Hi there,
I was using node-red ttn node to receive traffic from my ttn applications, it was working fine till it stopped working few days ago, although it still shows that the node is still connected, any thoughts ?

I can see my sensors traffic on the gateway from ttn console, but still no data received in node-red.
Thanks

On page https://www.npmjs.com/package/node-red-contrib-ttn, the Example-flow link is dead

Proposed enhancement. Add support for downlink scheduling as per the example below lifted from the TTN API documentation. Configure as msg inputs so that confirmed and schedule values can be set on a message by message basis.

{
  "port": 1,
  "confirmed": false,
  // payload_raw or payload_fields
  "schedule": "replace", // allowed values: "replace" (default), "first", "last"
}

Hi,

I installed nodered using docker on my RPI3b+. I tried to install nodered-contrib-ttn which gives also success message, but for some reasons ttn_app is missing. Therefore I can't connect to the network with my nodes.

I also removed the container for nodered and installed newly. Same result.

Do you have any advise how to solve that issue?

I'm running Nodered v0.20.7 and npm v5.03

Thanks in advance.

See TheThingsArchive/node-app-sdk#26

Initial situation, working ok: Windows10 + node-red 0.18.2 + node-red-contrib-ttn

After updating to version 0.18.4, manage palette, reports that contib-ttn needs to be reinstalled.

Tried to do the installation from manage palette, without success.
Tried to reinstall the command line node (npm install node-red-contrib-ttn),
but I get many error reports, reinstallation is not successful.

Attached installation errors log
2018-03-01T21_39_35_174Z-debug.log

node-red environment versions
1 Mar 22:42:46 - [info] Node-RED version: v0.18.4
1 Mar 22:42:46 - [info] Node.js version: v8.9.4
1 Mar 22:42:46 - [info] Windows_NT 10.0.16299 x64 LE
1 Mar 22:42:47 - [info] Loading palette nodes
1 Mar 22:42:50 - [info] Dashboard version 2.8.2 started at /ui
.........

Note:
In the raspbian environment, raspberry PI3, updated to version 0.18.4 with node node-red-contrib-ttn,
works correctly

Thanks

The events node should pass the event type as part of msg (i.e. msg.eventType). This is especially useful when subscribing to events #.

References #46.

The node ttn up link works for few minutes then stops ,i get this error please help

pi@raspberrypi:~/.node-red $ sudo npm install node-red-contrib-ttn
[sudo] password for pi:
npm ERR! code ENOGIT
npm ERR! Error while executing:
npm ERR! undefined ls-remote -h -t https://github.com/thethingsnetwork/api.git
npm ERR!
npm ERR! undefined
npm ERR! No git binary found in $PATH
npm ERR!
npm ERR! Failed using git.
npm ERR! Please check if you have git installed and in your PATH.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-11-07T15_50_21_721Z-debug.log
pi@raspberrypi:~/.node-red $

Hi There,

I have installed locally on my mac latest version of node-red with npm.
When I try to open the flow editor (localhost:1880) the top bar shows up for few seconds than the browser returns the error:
Aw, Snap!
Something went wrong while displaying this web page.
Can't see any error in Terminal, can't see any error in Chrome debug or network as devtools disconnect.
If I open the same page in Firefox, it just works fine.
I tried to completely wipe out node-red and reinstall but nothing changed.

Really puzzled by the situation.

Cheers.

After installation of the nodes and copying the example flow my Node-RED reports error on the ttn app node: "This node is a type unknown to your installation of Node-RED."

The other nodes (ttn send, ttn device, ttn message) are properly installed and work.

All nodes use lib/init.js which can throw an No app set error. In the console you can see what node threw it, but in Node-RED's debug sidebar you can't. So the message should include the (custom) name of the node.

It appears that git must be installed in order to install this node. It would be helpful if this were mentioned in the readme.

The application is not properly copied.

The access key should not be part of the copy.

@johanstokking This is a weird case again. It's not an SDK. Should we call it an integration maybe? So nodered-integration like we'll have azure-integration?

Brand new Stretch Pi install on Pi 3, then run the install script bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered) Node v11.1.0 npm V 6.4.1 So far so good. The ttn- install using the GUI install fails or on the second attempt loads the three node BUT when trying to configure Node Properties there is no edit/add option in the App option box. Using the text install option in ~/.node-red and the installation completes providing the add/edit (little pen icon) option. The who thing appears to function correctly (using the gui) BUT the log complains that no appId, accessKey or discovery address has been recorded.. Nothing therefore functions. Any ideas folks?

Is there a was to receive the TTN metadata of a message?

During the workshops, I often see people connecting the second output of the ttn node and expecting uplink messages to come out of that as well.

I think we can alleviate this problem by creating a new node: the ttn activations node.
The client can be shared via the configuration node that is introduced by #8 so this does not
create any configuration / connection overhead.