@Yvan-Gagnon
Well it turns out that you don't need the Onion blynk-library, you can just use the standard one. So you don't need to wait for @Lazar-Demin.
Just follow the blynk 2 bullet Tuesday example with some minor modifications.
In the section "Let’s switch over to the Omega", substitute what is there with the following (assuming that you are running a b2xx firmware):
opkg update
opkg install node-npm
NOTE - This requires a fair amount of space.[1]
Test that node and npm are working:
root@Omega-BFC9:~# node --version
v8.10.0
root@Omega-BFC9:~# npm version
{ npm: '5.6.0',
ares: '1.10.1-DEV',
http_parser: '2.7.0',
modules: '57',
nghttp2: '1.25.0',
node: '8.10.0',
openssl: '1.0.2p',
uv: '1.19.1',
v8: '6.2.414.50',
zlib: '1.2.11' }
NOTE - npm takes a bit of time to get going, so be patient.
Then install the blynk-library using npm:
root@Omega-BFC9:~# npm install -g blynk-library
/usr/bin/blynk-client -> /usr/lib/node_modules/blynk-library/bin/blynk-client.js
/usr/bin/blynk-ctrl -> /usr/lib/node_modules/blynk-library/bin/blynk-ctrl.js
+ blynk-library@0.5.4
added 1 package in 22.028s
Create the test.js file as described, except you must change the source of the blynk-library in the first line of the file:
var BlynkLib = require('/usr/lib/node_modules/blynk-library');
var blynk = new BlynkLib.Blynk('YOUR AUTH TOKEN HERE'); // !!!
var v1 = new blynk.VirtualPin(1);
v1.on('write', function(param) {
console.log('Hi! Pin V1 is: ', param);
});
Remember to use your own blynk auth token as described in the 2 bullet Tuesday article.
Then run and test:
root@Omega-BFC9:~# node test.js
___ __ __
/ _ )/ /_ _____ / /__
/ _ / / // / _ \/ '_/
/____/_/\_, /_//_/_/\_\
/___/
Give Blynk a Github star! => https://github.com/vshymanskyy/blynk-library-js
Connecting to: blynk-cloud.com 443
SSL authorization...
Connected
Authorized
Hi! Pin V1 is: [ '1' ]
Hi! Pin V1 is: [ '0' ]
Hi! Pin V1 is: [ '1' ]
Hi! Pin V1 is: [ '0' ]
^C
root@Omega-BFC9:~#
[1] - Here is a before and after snapshot of my free space when installing node-npm and node:
root@Omega-BFC9:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 8.0M 8.0M 0 100% /rom
tmpfs 61.0M 220.0K 60.8M 0% /tmp
tmpfs 61.0M 112.0K 60.9M 0% /tmp/root
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock6 22.3M 692.0K 21.6M 3% /overlay
overlayfs:/overlay 22.3M 692.0K 21.6M 3% /
root@Omega-BFC9:~# opkg install node-npm
Installing node-npm (v8.10.0-3) to root...
Downloading http://repo.onioniot.com/omega2/packages/packages/node-npm_v8.10.0-3_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
Configuring node.
Configuring node-npm.
root@Omega-BFC9:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 8.0M 8.0M 0 100% /rom
tmpfs 61.0M 220.0K 60.8M 0% /tmp
tmpfs 61.0M 112.0K 60.9M 0% /tmp/root
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock6 22.3M 14.0M 8.3M 63% /overlay
overlayfs:/overlay 22.3M 14.0M 8.3M 63% /
root@Omega-BFC9:~#
If you do like I did the first time I tried this and install on an O2+ with insufficient space, you will run out of space during the installation. Thereafter it can be a bit of a PITA to regain space because opkg won't allow you to remove the packages that it didn't successfully install.
In this case, there is a very handy utility here: opkg-cleanup.sh (Albeit, FOR OpenWRT 18.06 ONLY) that will get you out of trouble and manually remove the packages. You'll probably have to delete a file or two in /overlay/upper first so that you can create enough space to create the cleanup tool.