1. Home
  2. Omega Talk
  3. Omega2 Pro w/ Node-Red but no Manage Palette [resolved]

Omega2 Pro w/ Node-Red but no Manage Palette [resolved]

  • D

    I installed Node-Red using the console and it seems to start up and work just fine. But there is no Manage Palette in the menu, needed for installing additional nodes.

    I assume this is because NPM is not installed. I tried installing NPM w/ opkg install npm. The install began and I believe there was a dependency on nodejs, which then conflicted with node. Possibly the node that Node-Red runs on. So the install failed.

    Any ideas on how to get NPM installed w/ Node-Red?

    Thanks -d

    0 Lazar Demin 1 Reply
  • Lazar Demin
    administrators

    @dklinkman See our Node-Red documentation: http://docs.onion.io/omega2-docs/node-red-article.html

    EDIT: updated link

    0
  • D

    Well there you go. I'm pretty familiar with Node-Red so I didn't bother to read the Onion docs on it. But the answer was right there plain as day. Installed, rebooted, and Manage Palette appears.

    Thanks for the pointer.

    -d

    1
  • J

    I configured my Omega 2 Pro but can's install node-RED, either from the Onion OS GUI or the command line.

    I am told my firmware is up-to-date:
    root@Omega-B668:~# oupgrade -c

    Device Firmware Version: 0.3.1 b211
    Checking latest version online...
    url: https://api.onioniot.com/firmware/omega2pro/stable
    Repo Firmware Version: 0.3.1 b211
    Comparing version numbers
    Device firmware is up to date!

    I check my file systems:
    root@Omega-B668:~# df -h
    Filesystem Size Used Available Use% Mounted on
    /dev/root 7.8M 7.8M 0 100% /rom
    tmpfs 29.3M 232.0K 29.0M 1% /tmp
    /dev/mtdblock6 6.6M 388.0K 6.2M 6% /overlay
    overlayfs:/overlay 6.6M 388.0K 6.2M 6% /
    tmpfs 512.0K 0 512.0K 0% /dev

    Overlay is pretty empty. But then when I run the update from the ssh session it fails:

    root@Omega-B668:~# opkg install oos-app-nodered
    Installing oos-app-nodered (1.0.0-1) to root...
    Downloading http://repo.onioniot.com/omega2/packages/onion/oos-app-nodered_1.0.0-1_mipsel_24kc.ipk
    Installing node (v8.10.0-3) to root...
    Downloading http://repo.onioniot.com/omega2/packages/packages/node_v8.10.0-3_mipsel_24kc.ipk
    Installing onion-node-red (0.19.5-1) to root...
    Configuring node.
    Collected errors:

    • verify_pkg_installable: Only have 540kb available on filesystem /overlay, pkg onion-node-red needs 10506
    • opkg_install_cmd: Cannot install package oos-app-nodered.

    So overlay is now full.

    Suggestions welcome.

    0 Lazar Demin 1 Reply
  • Lazar Demin
    administrators

    @James-Solderitsch judging by the df output, it looks like your Omega2 Pro is operating from the internal flash and not the emmc.
    Please try upgrading the firmware with oupgrade -l -f, it will rerun all of the initialization procedures and should then run the OS from the emmc. Note that this might take up to 5 minutes

    EDIT: fixed oupgrade command, thanks for the pointer @György-Farkas

    0 G J 2 Replies
  • G

    @Lazar-Demin @James-Solderitsch oupgrade -l -c won't upgrade your firmware. Please try oupgrade -l -f instead.

    0
  • J

    @Lazar-Demin No success after this attempt.
    root@Omega-B668:~# oupgrade -v

    Device Firmware Version: 0.3.2 b217
    root@Omega-B668:~#

    And then my attempt:

    root@Omega-B668:~# opkg install oos-app-nodered
    Installing oos-app-nodered (1.0.0-1) to root...
    Downloading http://repo.onioniot.com/omega2/packages/onion/oos-app-nodered_1.0.0-1_mipsel_24kc.ipk
    Installing node (v8.10.0-3) to root...
    Downloading http://repo.onioniot.com/omega2/packages/packages/node_v8.10.0-3_mipsel_24kc.ipk
    Installing onion-node-red (0.19.5-1) to root...
    Configuring node.
    Collected errors:

    • verify_pkg_installable: Only have 532kb available on filesystem /overlay, pkg onion-node-red needs 10506
    • opkg_install_cmd: Cannot install package oos-app-nodered.

    I did run this first:

    root@Omega-B668:~# oupgrade -l -f

    Device Firmware Version: 0.3.1 b211
    Checking latest version online...
    url: https://api.onioniot.com/firmware/omega2pro/latest
    Repo Firmware Version: 0.3.2 b217
    New firmware version available, need to upgrade device firmware
    Downloading new firmware ...
    --2019-03-01 23:57:51-- http://repo.onioniot.com/omega2/images/omega2pro-v0.3.2-b217.bin
    Resolving repo.onioniot.com... 52.216.229.242
    Connecting to repo.onioniot.com|52.216.229.242|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 9699511 (9.2M) [application/octet-stream]
    Saving to: '/tmp/omega2pro-v0.3.2-b217.bin'

    /tmp/omega2pro-v0.3.2-b217.bin 100%[==================================================================================>] 9.25M 2.38MB/s in 3.9s

    2019-03-01 23:57:55 (2.38 MB/s) - '/tmp/omega2pro-v0.3.2-b217.bin' saved [9699511/9699511]

    Starting firmware upgrade....
    Saving config files...
    Commencing upgrade. Closing all shell sessions.
    Connection to omega-b668.local closed by remote host.
    Connection to omega-b668.local closed.

    After the reboot I tried again with the failure as shown above.

    Any more things to try?

    Jim

    0 Lazar Demin 1 Reply
  • Lazar Demin
    administrators

    @James-Solderitsch try running o2-pro-init to manually run the initialization and then check if you're running on emmc by running df -h. The overlay should have 6.3GB free if you're on emmc

    0 J 1 Reply
  • J

    @Lazar-Demin I did a power cycle to the Omega Pro. Now I see:

    root@Omega-B668:~# df -h
    Filesystem Size Used Available Use% Mounted on
    /dev/root 7.8M 7.8M 0 100% /rom
    tmpfs 61.0M 216.0K 60.8M 0% /tmp
    /dev/mmcblk0p1 7.1G 437.0M 6.3G 6% /overlay
    overlayfs:/overlay 7.1G 437.0M 6.3G 6% /
    tmpfs 512.0K 0 512.0K 0% /dev
    /dev/mmcblk0p1 7.1G 437.0M 6.3G 6% /mnt/mmcblk0p1
    /dev/mtdblock6 6.6M 6.1M 504.0K 93% /mnt/mtdblock6
    root@Omega-B668:~#

    So this seems like what I should have been seeing, correct?

    1
  • J

    I seem to be able to work with node-RED as expected now.

    Anyway to restart it after installing node-red modules using the ssh terminal? On the raspberry pi you have node-red-start and node-red-stop.

    Are such commands available on the omega 2 pro?

    Also, I have an Omega 2+ If I add SD card storage and upgrade the firmware, then I can run node-RED there too? Is there any configuration to do to have the Omega 2+ use the SD Card storage like the Pro uses the emmc storage when installing software?

    0
  • J

    I have updated my Omega2+ to Firmware 0.3.2 b218.

    I see the new Onion OS.

    If I do add SD storage to the 2+ to have a memory footprint in the overlayfs to be comparable to what I have in the Omega Pro, will I be able to run node-RED there as well? I see that the App Manager says that node-RED os only available to the Omega Pro, but I wonder if an ssh terminal session would allow node-RED to be installed manually?

    0
  • J

    Reporting on my own request.

    I was able to figure out how to get the SD card to be allocated to the overlay file system and from the ssh session I could install node-RED, node-npm and the IBM flows from John Walicki at IBM.

    Seems to work OK so far.

    I had an expansion dock and an OLED screen and these respond as expected from the node-RED logic.

    0
omega2 pro 41 node-red 22 npm 18
Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.