# Riot-nodes error

**URL:** <https://discourse.nodered.org/t/riot-nodes-error/47239>\
**Category:** General\
**Created:** [16 June 2021 12:59 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239 "2021-06-16T12:59:14Z")\
**Posts on this page:** 20\
**Page:** 8

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [11 July 2021 15:49 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/171 "2021-07-11T15:49:15Z")

</div>

I deleted the flows. So, do I have to go on with the installation of riot project, or i have to do something else first?

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 10:40 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/172 "2021-07-12T10:40:34Z")

</div>

I deleted the flows. So, do I have to go on with the installation of riot project, or i have to do something else first?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 July 2021 10:42 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/173 "2021-07-12T10:42:25Z")

</div>

@Martin10 if your goal is to install the riot nodes, despite all the issues you've been having, then try installing them and see where you get to.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 July 2021 10:44 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/174 "2021-07-12T10:44:44Z")

</div>

Martin, as I said before...

> [@Steve-Mcl](#):
>
> I would suggest you clean up your flows, get node-red running smoothly then try installing the nodes you need one at a time & checking node-red still works. Post errors as and when they happen.

so have you got node-red running cleanly without errors?

If so...

- try installing the nodes you need one at a time - checking node-red still works (restart node-red after install each node you need)
- Post errors as and when they happen - stop and wait for us to help with a particular error before installing next contrib node

PS: do not install those mqtt-env / mqttssql nodes - they are broke.

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 11:59 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/175 "2021-07-12T11:59:48Z")

</div>

This is part of the results from the installation. Is it everything normal?

```auto
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Linux 5.4.51-v7l+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /home/pi/.node-red/node_modules/fs-ext
gyp ERR! node -v v12.18.4
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok 
npm WARN node-red-contrib-ui-led@0.3.3 requires a peer of node-red-dashboard@2.23.x but none is installed. You must install peer dependencies yourself.
npm WARN tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/zigbee-herdsman/node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/zigbee-herdsman/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bufferutil@1.2.1 (node_modules/bufferutil):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: bufferutil@1.2.1 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fs-ext@0.5.0 (node_modules/fs-ext):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fs-ext@0.5.0 install: `node-gyp configure build`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

+ riot-xbee@0.0.1
updated 1 package and audited 1972 packages in 72.96s

65 packages are looking for funding
  run `npm fund` for details

found 351 vulnerabilities (73 low, 68 moderate, 209 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

```

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 July 2021 12:13 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/176 "2021-07-12T12:13:21Z")

</div>

The honest answer @Martin10 is - we don't know. We don't use the riot nodes module, so we don't know what amount error messages are 'expected'.

You have shared some of the log output - it starts with `build error` - but because of where you start the log output, we don't know what has had an error.

The log then says `SKIPPING OPTIONAL DEPENDENCY` - so the build error is probably coming from one of those. They fact they are "optional" means that despite the error, it is carrying on.

```auto
+ riot-xbee@0.0.1
updated 1 package and audited 1972 packages in 72.96s

```

And this tells us that the module has installed "successfully" - even though some optional dependencies failed.

What we simply don't know is what the failed optional dependencies might mean for what the node wants to do.

Now try running Node-RED and see if you get any errors when it starts up.

If there are errors, then maybe those optional dependencies were not so optional after all. The next steps would be to look back at the install log, identify exactly what failed to install and decide if its worth the effort to get working given everything else.

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 12:24 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/177 "2021-07-12T12:24:02Z")

</div>

I can't upload full report, because it is too big.  
NR work good (no errors), but can't find anything new. How i supposed to ''call'' this new nodes?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 July 2021 12:25 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/178 "2021-07-12T12:25:50Z")

</div>

> [@Martin10](#):
>
> How i supposed to ''call'' this new nodes?

Just to confirm, does this mean you do now have the riot nodes in your palette?

If you have questions about how to _use_ those nodes, you'll have to direct them to the author of the module.

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 12:38 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/179 "2021-07-12T12:38:34Z")

</div>

This is what i've got. Should i ''enable all''

 ![2021-07-12-152752_1024x768_scrot](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/0/70272c8080fcd5cdafd109d37a204c86cb85648c.png)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 July 2021 12:41 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/180 "2021-07-12T12:41:13Z")

</div>

Martin, must you use that particular node - considering it is about 5y old.

Have you tried [node-red-contrib-xbee (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-xbee)?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 July 2021 12:41 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/181 "2021-07-12T12:41:49Z")

</div>

@Martin10 there is a huge error message there.

That error would have been logged when Node-RED started.

So when you said `NR work good (no errors),` - were you ignoring those errors?

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 12:59 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/182 "2021-07-12T12:59:49Z")

</div>

I tried to use this example ([xBee transmit and recieve (flow) - Node-RED](https://flows.nodered.org/flow/a10d1cce0344d0cd839e37a35c1291f1)), but I can't send a message through it, not to mention sensor data (i please for help here, but nothing). Also this example only uses a transmit/ receive type of connection and the riot project says it uses a mesh network (i hope).

In NR i have this

```auto
Welcome to Node-RED
===================
12 Jul 15:02:09 - [info] Node-RED version: v1.3.5
12 Jul 15:02:09 - [info] Node.js version: v12.18.4
12 Jul 15:02:09 - [info] Linux 5.4.51-v7l+ arm LE
12 Jul 15:02:09 - [info] Loading palette nodes
12 Jul 15:02:27 - [info] Dashboard up and running
12 Jul 15:02:32 - [info] Dashboard version 2.20.0 started at /ui
12 Jul 15:02:33 - [warn] ------------------------------------------------------
12 Jul 15:02:33 - [warn] [node-red-contrib-usb/adkinit] SyntaxError: Invalid or unexpected token (line:59)
12 Jul 15:02:33 - [warn] [node-red-qnap-blockly/blockly] Type already registered
12 Jul 15:02:33 - [warn] [riot-xbee/riot-xbee] Error: Cannot find module '/home/pi/.node-red/node_modules/riot-xbee/riot-xbee.js'
Require stack:
- /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/loader.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/index.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/index.js
- /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/index.js
- /usr/lib/node_modules/node-red/lib/red.js
- /usr/lib/node_modules/node-red/red.js
12 Jul 15:02:33 - [warn] ------------------------------------------------------
12 Jul 15:02:33 - [info] Settings file : /home/pi/.node-red/settings.js
12 Jul 15:02:33 - [info] Context store : 'default' [module=memory]
12 Jul 15:02:33 - [info] User directory : /home/pi/.node-red
12 Jul 15:02:33 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Jul 15:02:33 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
12 Jul 15:02:33 - [info] Server now running at http://127.0.0.1:1880/
12 Jul 15:02:33 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
12 Jul 15:02:33 - [info] Starting flows
12 Jul 15:02:33 - [info] Started flows

```

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 July 2021 13:12 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/183 "2021-07-12T13:12:06Z")

</div>

> [@Martin10](#):
>
> `12 Jul 15:02:33 - [warn] [riot-xbee/riot-xbee] Error: Cannot find module '/home/pi/.node-red/node_modules/riot-xbee/riot-xbee.js'`

So there _is_ still an error with the riot nodes.

I have tried looking at their source code on github, but the code there is for version 0.0.1 - but the latest published version is 0.0.6.

To be frank - we cannot keep spending our time on this. The Riot nodes have not been updated for years. They are broken. We have done what we can get past the generic install issues, but clearly the issues run deep here.

I strongly suggest you stop trying to make the riot nodes work.

As Steve has suggested, there are other xbee nodes available. You may have more luck with them.

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 13:25 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/184 "2021-07-12T13:25:07Z")

</div>

I tried to use this example ([xBee transmit and recieve (flow) - Node-RED](https://flows.nodered.org/flow/a10d1cce0344d0cd839e37a35c1291f1)), but I can't send a message through it, not to mention sensor data (i please for help here, but nothing).

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 July 2021 13:27 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/185 "2021-07-12T13:27:13Z")

</div>

That example flow appears to be using [node-red-contrib-xbee (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-xbee)

It has nothing to do with the riot-xbee module.

I don't know what else to say. Have you got `node-red-contrib-xbee` installed?

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 13:34 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/186 "2021-07-12T13:34:57Z")

</div>

Yes, i install anything for this flow. i have topic in this forum for this flow with pics.

> [@XBee collect/send data](https://discourse.nodered.org/t/xbee-collect-send-data/40867):
>
> Hi, i use XBee modules and i try this example ([xBee transmit and recieve (flow) - Node-RED](https://flows.nodered.org/flow/a10d1cce0344d0cd839e37a35c1291f1)), in order to send/collect data, and i've got this in the debug node, but i can't see the message ''Hello'', that supposed to come up (according to the example). Any help?

> [@XBee collect data](https://discourse.nodered.org/t/xbee-collect-data/38706):
>
> Hi, i use XBee modules with breadboard on which i can connect sensors and i want to collect this data via Node-red. I saw this video, which use XBee with NR, but don't understand how to collect sensor data from the XBee. Any help? [[Creating a Node-RED MySQL Connection and writing JSON from XBee] ](https://www.youtube.com/watch?v=K-jov9Cvxcw)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 July 2021 13:41 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/187 "2021-07-12T13:41:45Z")

</div>

There is an example towards the bottom of the [readme](https://github.com/ramonmata/node-red-contrib-xbee)

I imagine you need to set `id`, `destination64` and `destination16` to something that matches your setup.

As we have said, we dont use xbee and your other threads got no answers - the only thing we can suggest is [raise a new issue](https://github.com/ramonmata/node-red-contrib-xbee/issues) asking the author for assistance.

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 13:57 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/188 "2021-07-12T13:57:07Z")

</div>

I fulfilled every requirement. I send several questions, but no help.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 July 2021 14:16 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/189 "2021-07-12T14:16:33Z")

</div>

> [@Martin10](#):
>
> I send several questions, but no help

You did not raise an issue on the github repo.

---

<div class="post-metadata">

**Author:** ![Martin10](https://avatars.discourse-cdn.com/v4/letter/m/a587f6/32.png) [@Martin10](https://discourse.nodered.org/u/Martin10)\
**Post date:** [12 July 2021 14:18 UTC](https://discourse.nodered.org/t/riot-nodes-error/47239/190 "2021-07-12T14:18:37Z")

</div>

Yes, i'm. It is in ''closed'' section

[Previous page](https://discourse.nodered.org/t/riot-nodes-error/47239.md?page=7)

[Next page](https://discourse.nodered.org/t/riot-nodes-error/47239.md?page=9)
