@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.
@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.
@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?
@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 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.
@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.
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.
@Gauthier-Michoud @MultiDJRoni, did you succeed installing Node-Red? 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.
Dammit, the problem was from totally different department!
The actual error was caused by the Simple HTTP Server trying to output its log where there was no place where to output, as the script was launched by system at startup.
I have silenced the console logging by implementing log_message method in my HTTP handler. Tada! Everything works now.
class MyHandler(BaseHTTPServer.BaseHTTPRequestHandler):
def log_message(self, format, *args):
return
A somewhat brutal way to silence logging, so I'll replace it by logging to file, though.
@Boken-Lin Unfortunately I never succeeded in configuring my Omega project so that it launches a python Simple HTTP Server at startup without any user intervention. The server script is launched alright, but at first http request it dies with error it does not seem to be able to recover from.
I use python's Simple HTTP Server (BaseHTTPServer.HTTPServer), and run my script at startup by adding the following three lines to /etc/rc.local:
sleep 20
cd /root/myProjectRoot
python server.py &
When I log on remotely via ssh, I can check if the python process running by $ ps | grep python and I can see that my server script is running. But once I make the http request, my script immediately fails. I hooked up logging to log file to catch more info about the error, and I've got this:
[Errno 32] Broken pipe
I am not sure how that can be fixed. If I run the server.py script from ssh session, it behaves normally, but it's not good enough because it stops when I close the ssh session. I need it to run completely in background.