Hi hek, you nailed it!

Yes, it was problem with old eeprom entries.. Cleared eeprom and everything is fine now. Direct routing (RSN parent address is at 0) did not help

Repeater output:

read: 200-200-0 s=255,c=0,t=17,pt=0,l=5:1.4.1
send: 200-100-0-0 s=255,c=0,t=17,pt=0,l=5,st=ok:1.4.1
read: 200-200-0 s=255,c=3,t=6,pt=1,l=1:100
send: 200-100-0-0 s=255,c=3,t=6,pt=1,l=1,st=ok:100
read: 200-200-0 s=255,c=3,t=11,pt=0,l=20:SN to RSN to GW node
send: 200-100-0-0 s=255,c=3,t=11,pt=0,l=20,st=ok:SN to RSN to GW node
read: 200-200-0 s=5,c=0,t=23,pt=0,l=5:1.4.1
send: 200-100-0-0 s=5,c=0,t=23,pt=0,l=5,st=fail:1.4.1
read: 200-200-0 s=5,c=1,t=24,pt=2,l=2:1
send: 200-100-0-0 s=5,c=1,t=24,pt=2,l=2,st=ok:1
read: 200-200-0 s=6,c=1,t=25,pt=2,l=2:1
send: 200-100-0-0 s=6,c=1,t=25,pt=2,l=2,st=ok:1

Gateway output:

0;0;3;0;9;read:0;0;3;0;14;Gateway startup complete.
0;0;3;0;9;read: 200-100-0 s=255,c=0,t=17,pt=0,l=5:1.4.1
200;255;0;0;17;1.4.1
0;0;3;0;9;read: 200-100-0 s=255,c=3,t=6,pt=1,l=1:100
200;255;3;0;6;100
0;0;3;0;9;read: 200-100-0 s=255,c=3,t=11,pt=0,l=20:SN to RSN to GW no
200;255;3;0;11;SN to RSN to GW node
0;0;3;0;9;read: 200-100-0 s=5,c=0,t=23,pt=0,l=5:1.4.1
200;5;0;0;23;1.4.1
0;0;3;0;9;read: 200-100-0 s=5,c=1,t=24,pt=2,l=2:1
200;5;1;0;24;1
0;0;3;0;9;read: 200-100-0 s=6,c=1,t=25,pt=2,l=2:1
200;6;1;0;25;1

Edit: Forgot, to say thank you!

Hi everyone,

1. I've setted one node address 200 to be a sensor node (SN) with defined parent node at address 100.

   node.begin(NULL, 200, true, 100);
   

2. I've setted one node to be the repeater node (RSN) at address 100, default repeater sketch with fixed address.

   node.begin(NULL, 100, true);
   

3. Third node is setted as a gateway (GW) with a default sketch.

So messages from SN are sent to RSN who should relay these messages to GW.

I receive a RSN message on a GW terminal:

  0;0;3;0;9;read: 100-100-0 s=255,c=3,t=11,pt=0,l=13:RSN Node
  100;255;3;0;11;RSN Node
  0;0;3;0;9;read: 100-100-0 s=255,c=3,t=12,pt=0,l=3:1.0
  100;255;3;0;12;1.0
  
  ### nothing more from RSN to GW is been received!

I receive a SN message on a RSN terminal:

 read: 200-200-0 s=255,c=3,t=11,pt=0,l=20:SN to RSN to GW node
 send: 200-100-1-0 s=255,c=3,t=11,pt=0,l=20,st=fail:SN to RSN to GW node
 read: 200-200-0 s=5,c=0,t=23,pt=0,l=5:1.4.1
 send: 200-100-1-0 s=5,c=0,t=23,pt=0,l=5,st=fail:1.4.1
 read: 200-200-0 s=6,c=0,t=23,pt=0,l=5:1.4.1
 send: 200-100-1-0 s=6,c=0,t=23,pt=0,l=5,st=fail:1.4.1
 read: 200-200-0 s=5,c=1,t=24,pt=2,l=2:1
 send: 200-100-1-0 s=5,c=1,t=24,pt=2,l=2,st=fail:1
 read: 200-200-0 s=6,c=1,t=25,pt=2,l=2:1
 send: 200-100-1-0 s=6,c=1,t=25,pt=2,l=2,st=fail:1
 read: 200-200-0 s=5,c=1,t=24,pt=2,l=2:2
 send: 200-100-1-0 s=5,c=1,t=24,pt=2,l=2,st=fail:2
 read: 200-200-0 s=6,c=1,t=25,pt=2,l=2:2
 send: 200-100-1-0 s=6,c=1,t=25,pt=2,l=2,st=fail:2   
.....

Output of SN:

sensor started, id 200
send: 200-200-100-0 s=255,c=0,t=17,pt=0,l=5,st=ok:1.4.1  
send: 200-200-100-0 s=255,c=3,t=6,pt=1,l=1,st=fail:100
send: 200-200-100-0 s=255,c=3,t=11,pt=0,l=20,st=ok:SN to RSN to GW node
send: 200-200-100-0 s=255,c=3,t=12,pt=0,l=3,st=fail:1.0
send: 200-200-100-0 s=5,c=0,t=23,pt=0,l=5,st=ok:1.4.1
send: 200-200-100-0 s=6,c=0,t=23,pt=0,l=5,st=ok:1.4.1    
send: 200-200-100-0 s=5,c=1,t=24,pt=2,l=2,st=fail:1
send: 200-200-100-0 s=6,c=1,t=25,pt=2,l=2,st=ok:1
send: 200-200-100-0 s=5,c=1,t=24,pt=2,l=2,st=ok:2
send: 200-200-100-0 s=6,c=1,t=25,pt=2,l=2,st=fail:2
.....

But I don't receive SN messages on GW.

On the SN side sensor is trying to send messages through RSN to GW:

read: 200-200-100-0 .... 

But then RSN is trying to relay these to GW through node with address 1 which is not defined:

send: 200-100-1-0

Can someone explain what is happening here? Maybe I'm am doing something wrong here,

Yes, and there are minor tweeks to be done.
MongoDb can't be cross-compiled for router (my atheros chip uses big endian, and mongo only supports little endian) , so there are two possibilities:

• connect to mongodb which is located somewhere else (Just change address of db in code, I use my pc)
• use TingoDb which has compatible api with MongoDb (Just change "dbc.connect()"), tingo could be used when mongo is down (I use that kind of setup, and am working on tingo to mongo script).

Requestify library uses 35MB of dynamic memory so I commented it out ("require" takes for ~3 minutes or so to load), I really don't understand how does it load new firmware on the gateway so not using that part, could you tell me whats the idea behind that? Could it flash other nodes, I really don't get it.

Think there is a bug in "sendNextAvailableSensorId()" response to gateway. It will newer increment id unless some "id" is larger than numbers of sensors in the "node" collection. I changed that it itereates over items and saves the largest id, and increment the largest node. Maybe the best solution would be to get the largest id with a mongo querry object.

Pinging this post because now NodeJsController could be used on OpenWrt router, I'm running it on my TP-Link WR-703N router :).

I used automated script from mr. Nelson github repo and successfully cross-compiled V8 and nodejs for mips arhitecture, there are even pre-compiled binaries if you don't want to do that cross-compiling process.

Npm packets should be cross-compiled (if they use some c++ code) with npm which comes with Node v0.10.5 (Stable).

Because WR-703N has only 32MB of RAM, and 4MB of flash memory you should do ext-root to an USB stick, and should add some linux SWAP to boost that poor RAM space.

If somebody is curious about this, please ask.

Hi, I bought these MQ sensors collection from ebay and soldered them on their boards.

Connected them this way:
Arduino VCC ---> MQ2 VCC
Arduino GND ---> MQ2 GND
Arduino A0 ----> MQ2 AOUT
not connected ---- MQ2 DOUT

I tried AirQuality.ino, MQ2.ino, and http://sandboxelectronics.com/?p=165.
Serial monitor outputs 0ppm on every parameter. Tried blowing cigarette smoke in MQ2 with no luck.

MQ2 PCB SMD board has four outputs like the one on the MySensors store , and it has a pot on it. Sketch from http://sandboxelectronics.com/?p=165 after calibration outputs R0 resistance (3.65kohm). Should I tune that pot to the point when the sketch outputs ~10kohm?

I have read on Arduino playground that MQ sensors should have burn-in period (12-24 h) to make their readings more consistent. But if there are no readings I shold not expect readings from it.

Does someone have any advice to get this sensor reading? Cheers, Dario.

Seems like your node is requuesting a id from a controller. Have you added node address to UNO?
Here is an example of how to add node id without controller: Node IDs should be between 1-254, because 0 and 255 are reserved.

int node_id = 1;
void setup()  
{
   gw.begin(NULL, node_id);
   //....
}

I would like to notice that this setup of sharp dust sensor outputs highly unreliable measurements.

Sensor should be connected as recommended in application note.
If that is so then:

• turn on IR LED (logical 0 on sharp pin 3, and optionally pause for 0.28ms),

• then analog read,

• turn off IR LED ( (logical 1).

Application note recommends taking reads 0.28ms after turning IR LED on.
Is there a reason why you skipped RC components and do not delay in microseconds?

Hi everyone, this is my first post on this forum.
MySensors looks very powerful, I appreciate your efforts on it and will explore it.

Couldn't find information on this topic, so I made it. I haven't found clues on MySensors site either.

I would like to use the NodeJsController :

• on my PC (running linux mint 17) instead of using it with raspberry-raspbian combo.

• If this is possible then I would like to do the same on a router (TL-WR703N) running OpenWrt linux.

Is this possible? I will explore both serial and ethernet gateway.

This is off-topic, I've found two libraries that have to do something with mysensors via npm, but they don't have no description. Maybe authors of those libs are here and could give some basic info on their libraries.
Here they are:

• mysensornode,
• mysensors_kash

My best, Dario