After trying alot of things, nothing worked. Using NVM doesnt work. But here is the solution:

vi /etc/opkg/base-feeds.conf

The file will be empty. Put this on the file and save:

src/gz all http://repo.opkg.net/edison/repo/all
src/gz edison http://repo.opkg.net/edison/repo/edison
src/gz core2-32 http://repo.opkg.net/edison/repo/core2-32

Now follow this commands:

opkg update
opkg install nodejs

After all the work, that is very fast, you will get this:

root@edison:~# node -v                                                                                                          
v0.12.7  

Now, let's see if the segmentation faults will stop. :)

Here is the source: http://alextgalileo.altervista.org/edison-package-repo-configuration-instructions.html

And here is the packages that you can get there: http://repo.opkg.net/edison/repo/core2-32/

i2cdetect -a -r 6 

This will result all the devices addresses that returned the scanning probe.

root@edison:/home# i2cdetect -a -r 6                                                                                                                                        
WARNING! This program can confuse your I2C bus, cause data loss and worse!                                                                                                  
I will probe file /dev/i2c-6 using read byte commands.                                                                                                                      
I will probe address range 0x00-0x7f.                                                                                                                                       
Continue? [Y/n] y                                                                                                                                                           
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f                                                                                                                         
00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --                                                                                                                         
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --                                                                                                                         
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --                                                                                                                         
30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- --                                                                                                                         
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --                                                                                                                         
50: -- -- -- 53 -- -- -- 57 -- -- -- -- -- -- -- --                                                                                                                         
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --                                                                                                                         
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --                                                                                                                         
root@edison:/home#    

This time I was look for the 0x57 device, that I recently connected to the i2c bus.

Get the device data:

i2cdump -y -f 6 0x57 

The result:

root@edison:~# i2cdump -y -f 6 0x57                                                                                             
No size specified (using byte-data access)                                                                                      
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef                                                         
00: 00 00 00 0f 00 00 03 00 00 00 00 00 00 00 00 00    ...?..?.........                                                         
10: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................                                                         
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
80: 00 00 00 00 00 ff af af af af af af af 01 af af    ......??????????                                                         
90: af af af af af af af af af af af af af af af af    ????????????????                                                         
a0: af af af af af af af af af af af af af af af af    ????????????????                                                         
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................                                                         
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff 05 11    ..............?? 

Get data from an address on the device:

i2cget -y -f 6 0x57 0x06  

Result:

root@edison:~# i2cget -y -f 6 0x57 0x06                                                                                         
0x03       

Send data to the device:

i2cset -y -f 6 0x57 0x06 0x03 

// I2C-6, endereço 57h, registrador 06h, escreve 03h

My NodeMCU are sending data using MQTT to the broker. Then this flow get the topic and the data and save on InfluxDB using its HTTP API.

Screenshot_11

http://flows.nodered.org/flow/5c96cc92d3171b6434bf

In function we have this code:
 

var tokens = msg.topic.split("/");
var dest = tokens[tokens.length-1];
msg.url ="http://localhost:8086/write?db=greenhouse";
msg.payload = tokens[2] + ",device=" + tokens[1] + " value=" + msg.payload;
return msg;

Here is a graphics sample:

Screenshot_12

Seems that the Texas SNB9024 is the man when we need an RTC. I will try to reach it using the Quark.
Ref.:
3.5 Power management IC (PMIC)
http://www.intel.com/content/dam/support/us/en/documents/edison/sb/edisonmodule_hg_331189004.pdf

4.13 V_VBAT_BKUP have some instructions about the register to configure the VBAT charging.

Datasheet: http://www.ti.com/product/TPS65910/datasheet

Today (23/02/16) I'm giving up from using Intel Edison's MCU for the prototype. I will start using Arduino to make the sensors work. When it get ready, I will see if Intel will have publicated more documentation ou if I need to abandon the internal MCU.

I posted a question on Edison's Forums but until now, nothing helped me. https://communities.intel.com/thread/99031

Ubuntu users can install the latest stable version of InfluxDB using the apt-get package manager. For Ubuntu users, you can add the InfluxData repository configuration by using the following commands:

curl -sL https://repos.influxdata.com/influxdb.key | sudo apt-key add -
source /etc/lsb-release
echo "deb [ arch=amd64 ] https://repos.influxdata.com/${DISTRIB_ID,,} ${DISTRIB_CODENAME}  stable" | sudo tee /etc/apt/sources.list.d/influxdb.list

And then to install and start the InfluxDB service:

sudo apt-get update && sudo apt-get install influxdb
sudo service influxdb start

I just add [ arch=amd64 ] to the original command, to make it work. Without it, the apt-get will search for i386 packages too and then give an error. 

Source

Installing Golang

First we need a C compiler:

apt-get update
apt-get install build-essential git

Now we need to add Go PATH to ~/.bashrc.

nano ~/.bashrc

Copy and paste this on the bottom of the ~/.bashrc file:

export GOPATH=$HOME/go
export GOBIN=$GOPATH/bin
export PATH=$PATH:$GOBIN

Press Control + X to exit from Nano, it will ask you to press Y and then ENTER. Now the file is saved.

Let's reload the ~/.bashrc:

source ~/.bashrc

With those settings, the Go repositories will be downloaded in $HOME/go/src
And Go builds will be installed in $HOME/go/bin

Now, let's download, compile and install Go:

cd /tmp/
wget https://storage.googleapis.com/golang/go1.4.2.src.tar.gz
tar -xvf go1.4.2.src.tar.gz
cd go/src
./all.bash #install Golang
hash -r    #refresh PATH

Compiling latest InfluxDB

go get github.com/influxdb/influxdb
cd $GOPATH/src/github.com/influxdb/
go get ./...
go install ./...

Starting InfluxDB

InfluxDB binaries will be located in $HOME/go/bin/influxd and $HOME/go/bin/influx
As it is already in your PATH you can start InfluxDB with influxd command

root@IoT:~# influxd

 8888888           .d888 888                   8888888b.  888888b.
   888            d88P"  888                   888  "Y88b 888  "88b
   888            888    888                   888    888 888  .88P
   888   88888b.  888888 888 888  888 888  888 888    888 8888888K.
   888   888 "88b 888    888 888  888  Y8bd8P' 888    888 888  "Y88b
   888   888  888 888    888 888  888   X88K   888    888 888    888
   888   888  888 888    888 Y88b 888 .d8""8b. 888  .d88P 888   d88P
 8888888 888  888 888    888  "Y88888 888  888 8888888P"  8888888P"

2016/01/08 17:07:31 InfluxDB starting, version 0.9, branch unknown, commit unknown, built unknown
2016/01/08 17:07:31 Go version go1.4.2, GOMAXPROCS set to 1
2016/01/08 17:07:31 no configuration provided, using default settings
[metastore] 2016/01/08 17:07:31 Using data dir: /root/.influxdb/meta
[metastore] 2016/01/08 17:07:31 Skipping cluster join: already member of cluster: nodeId=1 raftEnabled=true peers=[localhost:8088]

Now open the web admin at http://influxdb-ip:8083

Source

Open the .bashrc file:

nano ~/.bashrc

Add the below lines to the opened .bashrc file and then save it.

imgur() {
    for i in "$@"; do
        curl -# -F "image"=@"$i" -F "key"="4907fcd89e761c6b07eeb8292d5a9b2a" imgur.com/api/upload.xml|\
        grep -Eo '<[a-z_]+>http[^<]+'|sed 's/^<.\|_./\U&/g;s/_/ /;s/<\(.*\)>/\x1B[0;34m\1:\x1B[0m /'
    done
}

Source the .bashrc file,so that the changes can take effect,

source ~/.bashrc

The above script requires curl package to work.So install it by running

sudo apt-get install curl

Then run the below command to upload the image stored in the ~/Pictures folder to imgur.com,

imgur ~/Pictures/filename.png

Get the link of uploaded image

rasp

 

Source