Posts made by Daniel Sitnik

Great to finally see a public roadmap of when we can expect features to be released.
This was one of things I asked in the survey.

Great!! Let's see if Blynk works now!

I'd like to know as well. The last comment from Boken stated they needed 2-3 weeks, and this was already 2 months ago!

I still can't use Blynk on the Omega, even with the latest opkg nodejs package.

I have installed Blynk through NPM in another machine and just copied over the node_modules folder to the Omega.
When trying to run a simple script I get an error when it's trying to connect to the blynk cloud:

events.js:146
      throw err;
      ^

Error: Uncaught, unspecified "error" event. (ENOTFOUND)
    at emit (events.js:144:17)
    at Blynk.error (/root/blynk/node_modules/blynk-library/blynk.js:569:8)
    at null.<anonymous> (/root/blynk/node_modules/blynk-library/blynk.js:532:48)
    at emitOne (events.js:77:13)
    at emit (events.js:169:7)
    at Socket.<anonymous> (/root/blynk/node_modules/blynk-library/blynk-node.js:56:7)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at connectErrorNT (net.js:997:8)
    at nextTickCallbackWith2Args (node.js:437:9)

I manually changed some code in the library to print out the real error and this is what I found:

getaddrinfo ENOTFOUND http://cloud.blynk.cc http://cloud.blynk.cc:8442

I'm guessing it might be related to the problem some people is having when trying to install stuff through NPM.

@Matt-Ogborne check this topic, it has a precompiled executable to read data from DTH11/DHT22 in the Omega.

Finally!! This is some great news!

I was starting to get a little worried because as a Kickstarter backer I still haven't seen many of the things that were promised during the campaign. Even things like the Cloud and App Store that were supposed to be released in February (as stated in many topics in this forum) are still unavailable.

But this nodejs 4.3 and npm support is surely great!
Can't wait to do some tests with Blynk now.

Keep up the good work guys.

That was me. Indeed I got the Omega + expansion dock + oled display and was not charged any extra taxes.

I remember the 3 little boxes came all in a small envelope but I don't remember what was written on it. I have an order placed for the BLE and GPS expansions, let's see how that goes.

You could install it on your PC and then transfer the node_modules folder over to the Omega.

I've done it myself but unfortunatelly it doesn't work. I don't know if it's because of the nodejs version on the Omega or something else, but it doesn't keep the connection with Blynk cloud open. Right now it's pretty much useless.

@Luciano-S I live in Brazil as well. I was a backer in the Kickstarter campaign, got my Omega with expansion dock + oled display without any problems with customs.

The app store has not been released yet. The Onion guys say it's being tested and will be available soon.

@Rudy-Trujillo you must enable the less secure apps feature directly on your Google account, you cannot work around it just with the Python code.

Did you enable the "less secure apps" feature on your account as instructed by @chris-mccaslin?

Mine works too!!

I have not tested this, but did you try with TLS and 587 port?

server = smtplib.SMTP('smtp.gmail.com', 587)
server.starttls()
server.login("your.email@gmail.com", "PASSWORD")

msg = "YOUR MESSAGE!"
server.sendmail("SENDER ADDRESS", "RECIPIENT ADDRESS", msg)
server.quit()

If you're going to use Blynk you don't really need to setup a server on the Onion, you just need to write a NodeJS script that will run on the Onion (using the Blynk library) and respond to the inputs sent by the Blynk app on your smartphone (eg: button press).

Blynk works through the Blynk Cloud, this is how the Blynk app on your smartphone and the NodeJS script running on your Onion can communicate with each other.

The sad news here is that NodeJS support on the Onion is still very premature right now. I have been trying to run Blynk on my Onion for some time now but it has some issues, for istance it can't keep itself connected to the Blynk Cloud, so it's pretty much unusable now. The folks over at the Blynk forums are also still waiting for Onion to provide a better NodeJS support.

The OpenWrt wiki has some info on this but I don't have my Omega with me right now to test it.

Also, don't know if this configuration is preserved between upgrades.

Maybe search under OpenWrt? There's documentation, wiki and forums at their website.

Yay!! Cool!

Run opkg update first, then opkg install nodejs to install.
Unfortunatelly it is still using an old version (0.10.5) of Node, there's no npm and not all packages can be installed (at least the ones that need to be compiled since the Onion processor is MIPS architecture).

We know that Onion team is working in providing adequate Nodejs support together with the libraries and SDKs to interface with the GPIO pins. However, since the roadmap has not been published yet, we don't know when we can expect these features to be available.

As a complement to Jeff's post, be advised that most of the folders are erased during firmware updates, so you run the risk of losing your scripts.

One possible solution is adding the /root folder to the /etc/sysupgrade.conf file, as described in this topic.

Another option would be to use an external USB storage device.