Node-RED on Omega 1

[Pavils Jurjans]

I was happy to discover that Omega supports Node-RED, when I stumbled upon this tutorial: https://wiki.onion.io/Tutorials/node-red

However, my joy soon faltered: when I do

# opkg update
# opkg install onion-node-red

all I get is

Unknown package 'onion-node-red'.
Collected errors:
 * opkg_install_cmd: Cannot install package onion-node-red.

My OS version is: BusyBox v1.23.2; Ω-ware: 0.1.4 b330
The opkg package lists are fetched from
http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/base/
http://repo.onion.io/omega/packages/
http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/packages/

I am using Omega 1 hardware.

[Theodore Borromeo]

did you run opkg update and opkg install nodejs first? I don't know that that would help, but it would be in line with the tutorial

[Pavils Jurjans]

@Theodore-Borromeo Of course, I did! The thing is there is no such package as onion-node-red (one can check in those package list links)! Perhaps there has been earlier and then was removed due to some incompatibility issues? I have no idea.

[Joris Mulliez]

Hi,

I don't know node-red, but I just ran :

# opkg list | grep red
node-red-install-tool - 0.1-1

Perhaps this package could help you ?

++

[Pavils Jurjans]

@Joris-Mulliez I get several pages of text when I grep red, mostly because the opkg list outputs the package descriptions. But I don't find the package node-red-install-tool what you mention.

Can I ask you to show from where you get your package lists? I am not sure how to retrieve list of repository urls, but I see them when I do opkg update (I've included those urls in OP). At least in those repos there is neither onion-node-red nor node-red-install-tool package.

[Brian Robbins]

@Pavils-Jurjans
node-red-install-tool_0.1-1_mipsel_24kc.ipk
repo is at http://repo.onion.io/omega2/packages/

[Pavils Jurjans]

@Brian-Robbins said in Node-RED on Omega 1:

@Pavils-Jurjans
node-red-install-tool_0.1-1_mipsel_24kc.ipk
repo is at http://repo.onion.io/omega2/packages/

Ok, there's the catch. Omega2 packages. I guess that Omega1 does not support Node-RED then.

[Joris Mulliez]

Oh sorry... I didn't notice you had a omega 1... Perhaps you can add some extra respositories ? (I have no idea of which one...)

[Pavils Jurjans]

@Joris-Mulliez said in Node-RED on Omega 1:

Oh sorry... I didn't notice you had a omega 1... Perhaps you can add some extra respositories ? (I have no idea of which one...)

Can you please list the URLs of repositories that you see when you do opkg update?

[Joris Mulliez]

@Pavils-Jurjans

First you can see some advices here : https://community.onion.io/topic/1356/some-reminders-hints-about-using-opkg
I hope it is similar in omega 1 ?

And here is my disfeeds.conf :

# cat /etc/opkg/distfeeds.conf
#src/gz reboot_core http://downloads.lede-project.org/snapshots/targets/ramips/mt7688/packages
#src/gz reboot_base http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/base
#src/gz reboot_onion http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/onion
## src/gz reboot_luci http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/luci
## src/gz reboot_packages http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/packages
## src/gz reboot_routing http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/routing
## src/gz reboot_telephony http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/telephony
src/gz omega2_core http://repo.onion.io/omega2/packages/core
src/gz omega2_base http://repo.onion.io/omega2/packages/base
src/gz omega2_packages http://repo.onion.io/omega2/packages/packages
src/gz omega2_onion http://repo.onion.io/omega2/packages/onion

So only the "official" omega2 repositories are on (default configuration)

[Pavils Jurjans]

@Joris-Mulliez said in Node-RED on Omega 1:

src/gz omega2_onion http://repo.onion.io/omega2/packages/onion

Yeah, I thought I'd try and add this to my distfeeds.conf, but (as one could expect), the packages file did not pass the opkg signature check. I am pretty sure there are no specific restrictions that would not let the Node-RED be run on Omega1 hardware, but Onion apparently is now all-focused on the Omega2 and could not be bothered porting the Node-RED to the Omega1 repo. That would be shame if they abandon Omega1 just because there's now #2 in town.

I wish admins like @Lazar-Demin or @Boken-Lin could just say if they plan to add Node-RED to the Omega1 repo or not. That's a big deal, if it can be made to run on Omega1.

[Don DeGregori]

Could someone tell us about Node-Red? What it is, what is does, how it works, and how Omega2 could benefit from it. I tried to read about on their web site but didn't make much sense.

[Pavils Jurjans]

@Don-DeGregori Try some tutorials on YouTube, there are many. Node-RED is a tool for developing/prototyping internet-connected gadgets. At no time you can make a project that monitors twitter activity and blinks a LED when certain hashtag is detected. That's just a trivial example, of course. See the use cases from users in YouTube.

[Luciano S.]

@Don-DeGregori , wikipedia:

Node-RED is a software tool developed by IBM for wiring together hardware devices, APIs and online services as part of the Internet of Things.[2]

Node-RED provides a browser-based flow editor, which can be used to create JavaScript functions. Elements of applications can be saved or shared for re-use. The runtime is built on Node.js. The flows created in Node-RED are stored using JSON.