Posts made by Sweebee

@rollercontainer the plug-in works fine with 2.0. You dont have to change the protocol value in the plug-in.

Hi downloaded your sketch and i want to use it in the 2.0 mysensors library, but i got problems getting it work at the point of sleep:

void WallRemote_Sleep() {
  //Custom Function that puts ATMega and NRF24L01 into sleep mode.
  //This was necessary because PinChange Interrupts have been used.
  sensor_node.RF24::powerDown();  //Power Down NRF24
  Serial.flush(); // although there should be nothing in the Serial cue, Let serial prints finish (debug, log etc)
  LowPower.powerDown(SLEEP_FOREVER, ADC_OFF, BOD_OFF); //power everything down, wake up only by (PinChange) interrupts
}

How to call rf24 power down without sensor_node in front of it?

And i get:

WallRemote4x.ino: In function 'void WallRemote_Sleep()':
WallRemote4x:120: error: 'LowPower' was not declared in this scope
WallRemote4x:120: error: 'ADC_OFF' was not declared in this scope
WallRemote4x:120: error: 'BOD_OFF' was not declared in this scope
'LowPower' was not declared in this scope

After including LowPower:

Users/Wiebe/Documents/Arduino/libraries/LowPower/LowPower.h:4:6: error: multiple definition of 'enum period_t'
 enum period_t
      ^
In file included from /Users/Wiebe/Documents/Arduino/libraries/MySensors/core/MyHwATMega328.cpp:22:0,
                 from /Users/Wiebe/Documents/Arduino/libraries/MySensors/MySensor.h:69,
                 from WallRemote4x.ino:20:
/Users/Wiebe/Documents/Arduino/libraries/MySensors/core/MyHwATMega328.h:78:6: error: previous definition here
 enum period_t
      ^

The example you posted uses a irlz44n. According the data sheet it can handle 55v, so that should work. To power the arduino you can look for a stepdown module.

Btw, i'm testing with a sensor on 2.0 and its logging messages from other sensors like:

read and drop: 1-1-0 s=1,c=1,t=16,pt=2,l=2,sg=0:1

With repeater enabled:

read and forward: 5-5-0 s=1,c=1,t=16,pt=2,l=2,sg=0

In mysensors 1.5 I don't get this? It only repeats if the sensor asks for it or something like that. Now every repeater repeats the signal? Like a mesh netwerk or something?

The sketches you have don't work. You have to modify some stuff.

But the nodes that are already in your network and your gateway are working fine with 2.0 nodes.

@gerritv I tested with some esp examples, like the http server. They work fine.
Edit: yes 2.0 is working, thanks

Ive tested my ESP and it works fine with sample sketches, but with the ESP gateway it keeps booting:

?�F�x��D�H!�ȩLR�@H��0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta)
0;255;3;0;9;Radio init successful.
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 5
cnt 

connected with Nieuwenhuis, channel 1
dhcp client start...
.ip:192.168.1.41,mask:255.255.255.0,gw:192.168.1.1
.IP: 192.168.1.41
����
�@��0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta)
0;255;3;0;9;Radio init successful.
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 5
cnt 

connected with Nieuwenhuis, channel 1
dhcp client start...
.ip:192.168.1.41,mask:255.255.255.0,gw:192.168.1.1
.IP: 192.168.1.41
H!�ȩL��@H��0;255;3;0;9;Starting gateway (RNNGE-, 2.0.0-beta)
0;255;3;0;9;Radio init successful.
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 5
cnt 

connected with Nieuwenhuis, channel 1
dhcp client start...
.ip:192.168.1.41,mask:255.255.255.0,gw:192.168.1.1
.IP: 192.168.1.41

First check where your usb device is.

Open the terminal and type:

ls -l /dev/ttyU*

You should see something like:

crw-rw---- 1 root dialout 188, 0 Apr  6 18:36 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Apr  6 07:00 /dev/ttyUSB1

In my case it is /dev/ttyUSB1 (other one is my homeduino).

add this to the plugins:

{
      "plugin": "mysensors",
      "driver": "serialport",
      "protocols": "1.5.1",
      "driverOptions": {
        "serialDevice": "/dev/ttyUSB1",
        "baudrate": 115200
      }
    },

Then start pimatic and see if you can find the connected message:

Connected to MySensors Gateway

@fahrettine How does your sketch look? Does pimatic receive anything in de log?

I had a dimmer on node id 6. but I removed this one and created a pir on node id 6.

Now when the pir starts up, the gateway presents the dimmer and the pir. Is this normal?

I integrated auto discovery in pimatic for mysensors but this way its not very neat.

This one:

https://i.imgur.com/jKQLQgZ.png

Already got it.

Used the normal clear eprom. and nog ClearEepromConfig. Somehow the normal one doesn't erase everything?

My sensor doesn't ask for a id from the gateway?

send: 0-0-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=ok:1.5.4
send: 0-0-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
sensor started, id=0, parent=0, distance=0
send: 0-0-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:1.0
send: 0-0-0-0 s=255,c=3,t=1,pt=0,l=0,sg=0,st=ok:

I cleared the eprom and have set gw.begin();

@Maciej-Kulawik removed the pull-up and they are all working fine Don't know why i have added it, in one of my oldest sketches i havent enabled it.

@Maciej-Kulawik in my calculations it is 6uA. The pirs use around 15-20 uA in sleep.

I removed the left capacitor since it's not needed in 3.3v hack. And I moved the right one because otherwise it didn't fit into the case.

My sketch:

#include <MySensor.h>
#include <SPI.h>
#include <readVcc.h>

// ********** CONFIG **********************************

    #define NODE_ID AUTO          // ID of node
    #define CHILD_ID 1            // ID of sensor
    #define PIR_PIN 3             // Pin connected to the PIR
    
    #define MIN_V 2000            // empty voltage (0%)
    #define MAX_V 3200            // full voltage (100%)

// ****************************************************

MyMessage msg(CHILD_ID, V_TRIPPED);
MySensor node;

int oldBatteryPcnt;
int sentValue;
int forceSend = 0;

void setup()
{
  node.begin(NULL, NODE_ID, false);
  node.sendSketchInfo("PIR Sensor", "1.2");
  node.present(CHILD_ID, S_MOTION);
  pinMode(PIR_PIN, INPUT);
  digitalWrite(PIR_PIN, HIGH);
}

void loop()
{
  
  // Get PIR
  int value = digitalRead(PIR_PIN); // Get value of PIR
  if (value != sentValue) { // If status of PIR has changed
    resend(msg.set(value), 5); // Send PIR status to gateway
    sentValue = value;
  }

  // Send batterylevel
  sendBattery(); 

  // Sleep until something happens with the sensor
  node.sleep(PIR_PIN-2, CHANGE); 
}

// FUNCTIONS

void sendBattery() // Send battery percentage to GW
{
  forceSend++;
  int batteryPcnt = min(map(readVcc(), MIN_V, MAX_V, 0, 100), 100); // Get VCC and convert to percentage      
  if (batteryPcnt != oldBatteryPcnt || forceSend >= 20) { // If battery percentage has changed
    node.sendBatteryLevel(batteryPcnt); // Send battery percentage to gateway
    oldBatteryPcnt = batteryPcnt; 
    forceSend = 0;
  }
}

void resend(MyMessage &msg, int repeats) // Resend messages if not received by GW
{
  int repeat = 0;
  int repeatDelay = 0;
  boolean ack = false;

  while ((ack == false) and (repeat < repeats)) {
    if (node.send(msg)) {
      ack = true;
    } else {
      ack = false;
      repeatDelay += 100;
    } 
    repeat++;
    delay(repeatDelay);
  }
}

@Yveaux the pirs work fine if you only have interrupts with CHANGE. I don't use a sleep timer. If you wake it up every minute or so its unreliable yes. but only with interrupts from the pir it works fine. I have 10 pirs like this. Oldest one is from march 2015 and still running.

ordered the pro mini shields and I'm not disappointed As small as you can get:

I can't even get the RFM69HW working on my nano's (with shifter & regulator). On 3.3v pro mini's they worked fine. So i just use an arduino pro mini with ftdi adapter. Cheaper than the monteino's.

I'm also having this issue at 3V. It gets triggered if there is a (little) voltage drop. All my pirs only wake with an interrupt and no timer, then it works fine. But with a sleep timer it won't work the normal way.

At 5V everything works fine.

Maybe @fifipil909 's solution works.

Yes thanks, totally forgot that.

My gateway receives this:

0;0;3;0;9;read: 1-1-0 s=1,c=3,t=16,pt=0,l=0,sg=0:

while it should receive?

0;0;3;0;9;read: 1-1-0 s=1,c=3,t=16,pt=0,l=0,sg=0:1

My sketch:

#include <SPI.h>
#include <MySensor.h>
#include <MyTransportRFM69.h>
#include <MySigningAtsha204Soft.h>

#define NODE_ID 1

#define PIN_G 4
#define PIN_O 5
#define PIN_R 6

int sentG = 1;
int sentO = 1;
int sentR = 1;

//Construct MySensors library
MyHwATMega328 hw;
MyMessage groen(1, V_TRIPPED);
MyMessage oranje(2, V_TRIPPED);
MyMessage rood(3, V_TRIPPED);
MyTransportRFM69 transport;
MySensor gw(transport, hw);


/**************************************************************************************/
/* Initialization                                                                     */
/**************************************************************************************/
void setup()
  {
    
    pinMode(PIN_G, INPUT);
    digitalWrite(PIN_G, HIGH);
    pinMode(PIN_O, INPUT);
    digitalWrite(PIN_O, HIGH);
    pinMode(PIN_R, INPUT);
    digitalWrite(PIN_R, HIGH);
    
    gw.begin(NULL, NODE_ID, false);
  }

/**************************************************************************************/
/* Main loop                                                                          */
/**************************************************************************************/
void loop(){  
  
  // GROENE KNOP
  int valueG = digitalRead(PIN_G); 
    if (valueG != sentG) {
      Serial.println("GROEN");
      gw.send(groen.set(1));
      sentG = valueG;
  }

  // ORANJE KNOP
  int valueO = digitalRead(PIN_O); 
  if (valueO != sentO) {
    Serial.println("ORANJE");
    gw.send(oranje.set(1));
    sentO = valueO;
  }

  // RODE KNOP
  int valueR = digitalRead(PIN_R); 
  if (valueR != sentR) {
    Serial.println("ROOD");
    gw.send(rood.set(1));
    sentR = valueR;
  }
  
}

I tried the samples from the RFM69 library and they all work fine on any arduino.

Maybe someone can upload their library and some RFM69 mysensors samples that are working?

I'm trying to create my gateway with a arduino nano. Attached everything and on the serial output I get:

0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;14;Gateway startup complete.

But nothing happens when i try to send something.

When I try to send something with a sensor it gets fail:

send: 1-1-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,st=fail:1.5.1
send: 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
sensor started, id=1, parent=0, distance=0
send: 1-1-0-0 s=1,c=1,t=16,pt=2,l=2,sg=0,st=fail:1

On a arduino uno it works fine. But the gateway won't work on a pro mini or a nano?

@tbowmo Got it! thanks. Stupid me. There was some lost soldering in the header.

@tbowmo Can't find any bridges. On the atmega it's hard to see, but the pins that are connected to each other aren't close to each other.

@hek Every nrf pin has a connection to the atmega. But is it normal that the VCC and CSI are connected to each other?

I measured a mysensors pir and they don't have a connection to each other.

@hek yes, the sockets are fine. Maybe i have to measure directly between the atmega and the socket?

I have used this nrf with other arduino's and there they work fine.

This is a close-up picture: https://i.imgur.com/CLnR6p6.jpg

I checked them, but they are all the + version nrf24l01+

I attached the nrf to the sense bender but i get: check wires.

Can't see whats wrong?

https://i.imgur.com/WNLenAb.jpg
https://i.imgur.com/nW5Jubw.jpg

I tried 5 different nrfs

I finally got the RFM's working.

I tested the range. The gateway was inside my house and i could walk around 70m away (outside). After that the connection dropped. I tested this also with the NRF's and the range is about the same.

The RFM69HW 433mhz should be much better? I attached a 17.3 cm wire as antenna. Any tips to increase the range?

Disabling the signing helped a little.

Thanks! it working great now.

Why does signing not work? Because of the controller? or is this handled by the gateway?

Edit: Oh it was disabled on the gateway, now it works

Its working now!

Gateway doesn't work on the pro mini, but your sensor sketch is working

now the next thing, i get a lot of fails:

send: 10-10-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=fail:GHAS sensor
send: 10-10-0-0 s=255,c=3,t=12,pt=0,l=5,sg=0,st=fail:1.1.5
send: 10-10-0-0 s=0,c=0,t=7,pt=0,l=0,sg=0,st=fail:
find parent
send: 10-10-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
send: 10-10-0-0 s=1,c=0,t=6,pt=0,l=0,sg=0,st=fail:
send: 10-10-0-0 s=2,c=0,t=16,pt=0,l=0,sg=0,st=fail:
send: 10-10-0-0 s=3,c=0,t=30,pt=0,l=0,sg=0,st=fail:
[Setup duration: 7385 ms]
send: 10-10-0-0 s=0,c=1,t=1,pt=7,l=5,sg=0,st=fail:0.0
send: 10-10-0-0 s=1,c=1,t=0,pt=7,l=5,sg=0,st=fail:0.0
send: 10-10-0-0 s=2,c=1,t=37,pt=2,l=2,sg=0,st=fail:9
find parent
send: 10-10-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
send: 10-10-0-0 s=3,c=1,t=38,pt=7,l=5,sg=0,st=fail:3.30
send: 10-10-0-0 s=255,c=3,t=0,pt=1,l=1,sg=0,st=fail:100
0.0 degC   0.0 %   9 lx   3.30 v   [4851 ms]

but the gateway receives everything fine?

22:13:05.403 [pimatic-mysensors] debug: <- Presented Node  [ '10', '0', '0', '0', '7', '' ]
22:13:05.451 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
22:13:05.497 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
22:13:05.538 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
22:13:05.980 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;send: 0-0-10-10 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
22:13:06.115 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;send: 0-0-10-10 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
22:13:06.246 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;send: 0-0-10-10 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
22:13:07.594 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=1,c=0,t=6,pt=0,l=0,sg=0:
22:13:07.594 [pimatic-mysensors] debug: <- Presented Node  [ '10', '1', '0', '0', '6', '' ]
22:13:07.635 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=1,c=0,t=6,pt=0,l=0,sg=0:
22:13:07.639 [pimatic-mysensors] debug: <- Presented Node  [ '10', '1', '0', '0', '6', '' ]
22:13:07.680 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=1,c=0,t=6,pt=0,l=0,sg=0:
22:13:07.680 [pimatic-mysensors] debug: <- Presented Node  [ '10', '1', '0', '0', '6', '' ]
22:13:07.729 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=2,c=0,t=16,pt=0,l=0,sg=0:
22:13:07.729 [pimatic-mysensors] debug: <- Presented Node  [ '10', '2', '0', '0', '16', '' ]
22:13:07.774 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=2,c=0,t=16,pt=0,l=0,sg=0:
22:13:07.775 [pimatic-mysensors] debug: <- Presented Node  [ '10', '2', '0', '0', '16', '' ]
22:13:07.815 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=2,c=0,t=16,pt=0,l=0,sg=0:
22:13:07.816 [pimatic-mysensors] debug: <- Presented Node  [ '10', '2', '0', '0', '16', '' ]
22:13:07.864 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=3,c=0,t=30,pt=0,l=0,sg=0:
22:13:07.865 [pimatic-mysensors] debug: <- Presented Node  [ '10', '3', '0', '0', '30', '' ]
22:13:07.909 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=3,c=0,t=30,pt=0,l=0,sg=0:
22:13:07.909 [pimatic-mysensors] debug: <- Presented Node  [ '10', '3', '0', '0', '30', '' ]
22:13:07.950 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=3,c=0,t=30,pt=0,l=0,sg=0:
22:13:07.954 [pimatic-mysensors] debug: <- Presented Node  [ '10', '3', '0', '0', '30', '' ]
22:13:10.060 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=0,c=1,t=1,pt=7,l=5,sg=0:0.0
22:13:10.105 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=0,c=1,t=1,pt=7,l=5,sg=0:0.0
22:13:10.150 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=0,c=1,t=1,pt=7,l=5,sg=0:0.0
22:13:10.244 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=1,c=1,t=0,pt=7,l=5,sg=0:0.0
22:13:10.289 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=1,c=1,t=0,pt=7,l=5,sg=0:0.0
22:13:10.342 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=2,c=1,t=37,pt=2,l=2,sg=0:9
22:13:10.383 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=2,c=1,t=37,pt=2,l=2,sg=0:9
22:13:10.428 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=2,c=1,t=37,pt=2,l=2,sg=0:9
22:13:10.477 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
22:13:10.522 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
22:13:10.563 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
22:13:10.903 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;send: 0-0-10-10 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
22:13:11.038 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;send: 0-0-10-10 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
22:13:11.174 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;send: 0-0-10-10 s=255,c=3,t=8,pt=1,l=1,sg=0,st=fail:0
22:13:12.583 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=3,c=1,t=38,pt=7,l=5,sg=0:3.30
22:13:12.628 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=3,c=1,t=38,pt=7,l=5,sg=0:3.30
22:13:12.673 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=3,c=1,t=38,pt=7,l=5,sg=0:3.30
22:13:12.722 [pimatic-mysensors] debug: <- I_LOG_MESSAGE  0;0;3;0;9;read: 10-10-0 s=255,c=3,t=0,pt=1,l=1,sg=0:100

Yes i have the HW versions, so i replaced bool isRFM69HW=false by bool isRFM69HW=true

added a capacitor.

refreshed and still no feedback after sending.

I get a serial output from the pro mini on start. but no more serial messages when i try to send a message.

The problem is on the uno everything seems to work fine.

for the sensor i attached the RFM to a arduino pro mini 3.3v

double checked the wiring, tried 2 different RFM's, tried 2 arduino pro mini's.

uploaden the gateway to it and i get:

0;0;3;0;9;gateway started, id=0, parent=0, distance=0

but when i try to send something with the pro mini i get nothing back, while on the UNO I get:

0;0;3;0;9;send: 0-0-10-10 s=1,c=1,t=2,pt=0,l=1,sg=0,st=fail:1

So on the pro mini i get the init message, but no message when i try to send something.

I think the gateway works now, i removed the separate 5-3.3v converter and used the arduino 3.3v.

Now the sensor, i uploaden your sketch, but i get no init message?

@carlierd 1.5 https://github.com/mysensors/Arduino/tree/master

@carlierd I tried to compile your gateway but i get this error:

Arduino: 1.6.5 (Mac OS X), Board:"Arduino Uno"

SerialGateway:52: error: no matching function for call to 'MySensor::MySensor(MyTransportRFM69&, MyHwATMega328&, MySigningAtsha204Soft&, int, int, int)'
SerialGateway.ino:52:91: note: candidates are:
In file included from SerialGateway.ino:37:0:
/Users/Wiebe/Documents/Arduino/libraries/MySensors/MySensor.h:158:2: note: MySensor::MySensor(MyTransport&, MyHw&)
  MySensor(MyTransport &radio =*new MyTransportNRF24(), MyHw &hw=*new MyHwDriver()
  ^
/Users/Wiebe/Documents/Arduino/libraries/MySensors/MySensor.h:158:2: note:   candidate expects 2 arguments, 6 provided
/Users/Wiebe/Documents/Arduino/libraries/MySensors/MySensor.h:149:7: note: MySensor::MySensor(const MySensor&)
 class MySensor
       ^
/Users/Wiebe/Documents/Arduino/libraries/MySensors/MySensor.h:149:7: note:   candidate expects 1 argument, 6 provided
no matching function for call to 'MySensor::MySensor(MyTransportRFM69&, MyHwATMega328&, MySigningAtsha204Soft&, int, int, int)'

Thanks, will try it

The RFM is powered by the regulator. Havent tried to power it from the 3v from the arduino yet.

Arduino uno > level shifter > RFM69HW

the level shifter / RFM is powered by a separate 5 > 3.3v converter.

Gateway:

/**
 * The MySensors Arduino library handles the wireless radio link and protocol
 * between your home built sensors/actuators and HA controller of choice.
 * The sensors forms a self healing radio network with optional repeaters. Each
 * repeater and gateway builds a routing tables in EEPROM which keeps track of the
 * network topology allowing messages to be routed to nodes.
 *
 * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
 * Copyright (C) 2013-2015 Sensnology AB
 * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
 *
 * Documentation: http://www.mysensors.org
 * Support Forum: http://forum.mysensors.org
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * version 2 as published by the Free Software Foundation.
 *
 *******************************
 *
 * DESCRIPTION
 * The ArduinoGateway prints data received from sensors on the serial link. 
 * The gateway accepts input on seral which will be sent out on radio network.
 *
 * The GW code is designed for Arduino Nano 328p / 16MHz
 *
 * Wire connections (OPTIONAL):
 * - Inclusion button should be connected between digital pin 3 and GND  
 * - RX/TX/ERR leds need to be connected between +5V (anode) and digital pin 6/5/4 with resistor 270-330R in a series
 *
 * LEDs (OPTIONAL):
 * - To use the feature, uncomment WITH_LEDS_BLINKING in MyConfig.h
 * - RX (green) - blink fast on radio message recieved. In inclusion mode will blink fast only on presentation recieved
 * - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
 * - ERR (red) - fast blink on error during transmission error or recieve crc error 
 * 
 */

#define NO_PORTB_PINCHANGES  

#include <MySigningNone.h>
#include <MyTransportRFM69.h>
#include <MyTransportNRF24.h>
#include <MyHwATMega328.h>
#include <MySigningAtsha204Soft.h>
#include <MySigningAtsha204.h>

#include <SPI.h>  
#include <MyParserSerial.h>  
#include <MySensor.h>  
#include <stdarg.h>
#include <PinChangeInt.h>
#include "GatewayUtil.h"

#define INCLUSION_MODE_TIME 1 // Number of minutes inclusion mode is enabled
#define INCLUSION_MODE_PIN  3 // Digital pin used for inclusion mode button
#define RADIO_ERROR_LED_PIN 4  // Error led pin
#define RADIO_RX_LED_PIN    6  // Receive led pin
#define RADIO_TX_LED_PIN    5  // the PCB, on board LED

// NRFRF24L01 radio driver (set low transmit power by default) 
//MyTransportNRF24 transport(RF24_CE_PIN, RF24_CS_PIN, RF24_PA_LEVEL_GW);
MyTransportRFM69 transport;

// Message signing driver (signer needed if MY_SIGNING_FEATURE is turned on in MyConfig.h)
//MySigningNone signer;
//MySigningAtsha204Soft signer;
//MySigningAtsha204 signer;

// Hardware profile 
MyHwATMega328 hw;

// Construct MySensors library (signer needed if MY_SIGNING_FEATURE is turned on in MyConfig.h)
// To use LEDs blinking, uncomment WITH_LEDS_BLINKING in MyConfig.h
#ifdef WITH_LEDS_BLINKING
MySensor gw(transport, hw /*, signer*/, RADIO_RX_LED_PIN, RADIO_TX_LED_PIN, RADIO_ERROR_LED_PIN);
#else
MySensor gw(transport, hw /*, signer*/);
#endif

char inputString[MAX_RECEIVE_LENGTH] = "";    // A string to hold incoming commands from serial/ethernet interface
int inputPos = 0;
boolean commandComplete = false;  // whether the string is complete

void parseAndSend(char *commandBuffer);

void output(const char *fmt, ... ) {
   va_list args;
   va_start (args, fmt );
   vsnprintf_P(serialBuffer, MAX_SEND_LENGTH, fmt, args);
   va_end (args);
   Serial.print(serialBuffer);
}

  
void setup()  
{ 
  gw.begin(incomingMessage, 0, true, 0);

  setupGateway(INCLUSION_MODE_PIN, INCLUSION_MODE_TIME, output);

  // Add interrupt for inclusion button to pin
  PCintPort::attachInterrupt(pinInclusion, startInclusionInterrupt, RISING);


  // Send startup log message on serial
  serial(PSTR("0;0;%d;0;%d;Gateway startup complete.\n"),  C_INTERNAL, I_GATEWAY_READY);
}

void loop()  
{ 
  gw.process();

  checkButtonTriggeredInclusion();
  checkInclusionFinished();
  
  if (commandComplete) {
    // A command wass issued from serial interface
    // We will now try to send it to the actuator
    parseAndSend(gw, inputString);
    commandComplete = false;  
    inputPos = 0;
  }
}


/*
  SerialEvent occurs whenever a new data comes in the
 hardware serial RX.  This routine is run between each
 time loop() runs, so using delay inside loop can delay
 response.  Multiple bytes of data may be available.
 */
void serialEvent() {
  while (Serial.available()) {
    // get the new byte:
    char inChar = (char)Serial.read(); 
    // if the incoming character is a newline, set a flag
    // so the main loop can do something about it:
    if (inputPos<MAX_RECEIVE_LENGTH-1 && !commandComplete) { 
      if (inChar == '\n') {
        inputString[inputPos] = 0;
        commandComplete = true;
      } else {
        // add it to the inputString:
        inputString[inputPos] = inChar;
        inputPos++;
      }
    } else {
       // Incoming message too long. Throw away 
        inputPos = 0;
    }
  }
}

Sensor (default binaryswitchsleep):

/**
 * The MySensors Arduino library handles the wireless radio link and protocol
 * between your home built sensors/actuators and HA controller of choice.
 * The sensors forms a self healing radio network with optional repeaters. Each
 * repeater and gateway builds a routing tables in EEPROM which keeps track of the
 * network topology allowing messages to be routed to nodes.
 *
 * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
 * Copyright (C) 2013-2015 Sensnology AB
 * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
 *
 * Documentation: http://www.mysensors.org
 * Support Forum: http://forum.mysensors.org
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * version 2 as published by the Free Software Foundation.
 *
 *******************************
 *
 * DESCRIPTION
 *
 * Interrupt driven binary switch example with dual interrupts
 * Author: Patrick 'Anticimex' Fallberg
 * Connect one button or door/window reed switch between 
 * digitial I/O pin 3 (BUTTON_PIN below) and GND and the other
 * one in similar fashion on digital I/O pin 2.
 * This example is designed to fit Arduino Nano/Pro Mini
 * 
 */


#include <MySensor.h>
#include <SPI.h>

#define SKETCH_NAME "Binary Sensor"
#define SKETCH_MAJOR_VER "1"
#define SKETCH_MINOR_VER "0"

#define PRIMARY_CHILD_ID 3
#define SECONDARY_CHILD_ID 4

#define PRIMARY_BUTTON_PIN 2   // Arduino Digital I/O pin for button/reed switch
#define SECONDARY_BUTTON_PIN 3 // Arduino Digital I/O pin for button/reed switch

#if (PRIMARY_BUTTON_PIN < 2 || PRIMARY_BUTTON_PIN > 3)
#error PRIMARY_BUTTON_PIN must be either 2 or 3 for interrupts to work
#endif
#if (SECONDARY_BUTTON_PIN < 2 || SECONDARY_BUTTON_PIN > 3)
#error SECONDARY_BUTTON_PIN must be either 2 or 3 for interrupts to work
#endif
#if (PRIMARY_BUTTON_PIN == SECONDARY_BUTTON_PIN)
#error PRIMARY_BUTTON_PIN and BUTTON_PIN2 cannot be the same
#endif
#if (PRIMARY_CHILD_ID == SECONDARY_CHILD_ID)
#error PRIMARY_CHILD_ID and SECONDARY_CHILD_ID cannot be the same
#endif
 
MySensor sensor_node;

// Change to V_LIGHT if you use S_LIGHT in presentation below
MyMessage msg(PRIMARY_CHILD_ID, V_TRIPPED);
MyMessage msg2(SECONDARY_CHILD_ID, V_TRIPPED);

void setup()  
{  
  sensor_node.begin();

  // Setup the buttons
  pinMode(PRIMARY_BUTTON_PIN, INPUT);
  pinMode(SECONDARY_BUTTON_PIN, INPUT);

  // Activate internal pull-ups
  digitalWrite(PRIMARY_BUTTON_PIN, HIGH);
  digitalWrite(SECONDARY_BUTTON_PIN, HIGH);
  
  // Send the sketch version information to the gateway and Controller
  sensor_node.sendSketchInfo(SKETCH_NAME, SKETCH_MAJOR_VER"."SKETCH_MINOR_VER);

  // Register binary input sensor to sensor_node (they will be created as child devices)
  // You can use S_DOOR, S_MOTION or S_LIGHT here depending on your usage. 
  // If S_LIGHT is used, remember to update variable type you send in. See "msg" above.
  sensor_node.present(PRIMARY_CHILD_ID, S_DOOR);  
  sensor_node.present(SECONDARY_CHILD_ID, S_DOOR);  
}

// Loop will iterate on changes on the BUTTON_PINs
void loop() 
{
  uint8_t value;
  static uint8_t sentValue=2;
  static uint8_t sentValue2=2;

  // Short delay to allow buttons to properly settle
  sensor_node.sleep(5);
  
  value = digitalRead(PRIMARY_BUTTON_PIN);
  
  if (value != sentValue) {
     // Value has changed from last transmission, send the updated value
     sensor_node.send(msg.set(value==HIGH ? 1 : 0));
     sentValue = value;
  }

  value = digitalRead(SECONDARY_BUTTON_PIN);
  
  if (value != sentValue2) {
     // Value has changed from last transmission, send the updated value
     sensor_node.send(msg2.set(value==HIGH ? 1 : 0));
     sentValue2 = value;
  }

  // Sleep until something happens with the sensor
  sensor_node.sleep(PRIMARY_BUTTON_PIN-2, CHANGE, SECONDARY_BUTTON_PIN-2, CHANGE, 0);
} 

And i have set the RFM in the config.h to: #define RFM69_FREQUENCY RF69_433MHZ

I created a gateway with the RFM69 and a sensor with it. When i look at the serial monitor from the gateway i get

0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;14;Gateway startup complete.

Now i try to send something like: 10;1;1;1;2;0

then i get the startup message again:

0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;14;Gateway startup complete.
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;14;Gateway startup complete.
0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;14;Gateway startup complete.

When i try to send something with the sensor i get the know fail message.

When uploading the serial gateway i enabled the RFM69:

//MyTransportNRF24 transport(RF24_CE_PIN, RF24_CS_PIN, RF24_PA_LEVEL_GW);
MyTransportRFM69 transport;

How can i set this for the sensors?

I'm making remotes with 3 buttons that have to transmit the signal to the central receiver. These remotes are in different locations in a building with a lot of walls.

Which radio should i use?

I had some nrfs but they aren't strong enough (tested with the LNA PA)

How about the RFM69HW 433mhz? And is there a way to lower the bandwidth with mysensors, so the range will be increased?

I use it at max and it works fine. How do you feed the 3.3V of the nrf? I use a AMS1117 (up to 800mA).

Opened all my pir/light sensors to look what batteries were inside. I have 1 node thats on 38% with zinc philips batteries and still work fine. the ones with panasonic zinc batteries died around 40-45%. I have some with GP alkaline that are still around 70-80% so have to wait what they will do (looks like they don't drop as quickly as the zinc batteries).

Bod is disabled. And the proccessor is running On 1 MHz (custom bootloader).

Thanks, I will try that.

I have some sensors running for months. The sensors send their battery life to the controller. 3.3V = 100% 1.9V = 0%.

But the sensors stop working around 40-45%. The voltage is around 2.5V. I tested all the sensors on 1.9V and they all worked fine. But i think the current is the problem. The batteries can't deliver enough power to let the sensor send data with the NRF.

I used zinc chloride batteries. Don't know if Alkalines are better? All the sensors use 10-20uF capacitors.

Is there a way to improve this?

I'm trying to burn the gateway but i get this:

/Users/Wiebe/Documents/Arduino/libraries/MySensors/MyGateway.cpp:13:30: fatal error: utility/MsTimer2.h: No such file or directory
 #include "utility/MsTimer2.h"
                              ^
compilation terminated.

@epierre which box and solar panel is that?

You could also save the value every time in the eeprom, so when the sensor loses power it can recover the value.

@Oitzu https://github.com/sweebee/Arduino-home-automation/tree/master/2.4Ghz (MySensors)/Attiny/button-switch

Well i could save it every 10th pulse and check if its higher than the 10 pulses before that? if not, current pulse is the pulse that was saved 10 pulses before?

Today my pulsemeter reset itself today (pulse count):

10:36:45.054 <- I_LOG_MESSAGE  0;0;3;0;9;read: 8-8-0 s=1,c=1,t=24,pt=5,l=4:115944
10:37:25.039 <- I_LOG_MESSAGE  0;0;3;0;9;read: 8-8-0 s=1,c=1,t=24,pt=5,l=4:4

How can this happen? The controller didn't send a 0. I created a little sketch that sended the old value back and now it works again. But i don't want this to happen again.

today i burned a second regulator on a 5V pro mini. I use a car 5V adapter now, but its quite large :P. Any1 experience with good 5V regulators that can handle 12V?

I have some and all I did was removing the regulator (desoldering) and it works fine. So no cutting wires. If you want to program it make sure you have a vcc connected to the side pins since the vcc on the ftdi header doesn't work anymore.

Inside:

boxes:
http://www.ebay.com/itm/150866356642?rmvSB=true
http://www.aliexpress.com/item/75-25mm-electronics-housing-plastic-box-for-power-supply-box-for-led-abs-plastic-project-box/1873655189.html
http://www.aliexpress.com/item/Popular-Plastic-Enclosure-Case-DIY-Electronics-Project-Box-Drop-Shipping/32281646902.html

I have used these:

Some pirs:
my gateway:
pirs for on the ceiling:
and my 12v led strip dimmer:

A tip for much better batterylife: burn a new bootloader for 1mhz. Now you can attach the arduino and nrf directly to the batteries and you can measure the battery with the Internal voltage meter of the 328p. If you use a dht you attach the step-up conv. And only attach the dht to it.

I'm using the normal NRFs right now, also on the gateway. But sometimes it can't receive some sensors (95/100 times its going fine).

If i use a NRF LNA PA will it receive also better? Or does it only matter for sending?

@Mickey Nice, can you show the inside of the box?

If a switch works than the only could be the pir itself. You have enabled the pull-up resistor so an open collector should not give floats.

You already told that a sketch with a pir only worked fine?

Well, i can test what happens with my dht22 and a pir tomorrow (with your sketch).

This can't work well. Your interrupt is set on pin1 - 2 = int-1?

What happens when you remove the pir and use a switch instead?

@rvendrame When the PIR is connected to PIN3 the interrupt is INT1. Pin 1 does not have an interrupt.

Only pin 2 and pin 3 have an interrupt.

Pin 2 = int0
pin 3 = int1

@rvendrame Pir sensor is defined as 3

interrupt pin is defined as INT1: 3 - 2 = 1

@rvendrame well, for the price i could burn one once in a while

But i guess there must be something wrong even before i put 12v on the raw input. I made like 10 sensors now and never had this before that i couldn't upload a sketch with the nrf connected.

normally i don't use the raw input. Or if i do i use 5V. But i'm making a 12V led strip dimmer.

Threw the arduino and nrf away and took new ones and they are working fine

In sleep its using 1,68mA. powerLED is still on the arduino.

Tried to give it some external power. So I connected 12V to the raw input. But now the NRF is dead. :S really don't know whats going wrong.

There is coming 10V out of the Vcc when i connected 12V to the RAW.

Just a normal FTDI basic.

I have connected a NRF to my arduino. But when the vcc and gnd are conneccted to the NRF i can't program the arduino anymore. When i remove the vcc or gnd it works fine. After reconnecting the wires again i can read from the serial and the sensor is working fine, but programming doesn't.

The arduino and nrf uses around 20mA constant with my test sketch which is sending every 5 seconds.

the error from arduino IDE:

avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x85
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0xa7
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0xa7
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0xa4
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x84
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x85
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x84
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x86
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x86
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x84

Everything looks fine.

this is send to the gw send: 1-1-0-0 s=255,c=3,t=0,pt=1,l=1,st=ok:102

Maybe the controller doesn't accept higher than 100.

Your voltage is higher than 3.363V so thats why its 102%.

add this just after int batteryPcnt - sensorValue / 10;

if(batteryPcnt > 100)
{
   batteryPcnt = 100;
}

or

batteryPcnt = min(batteryPcnt, 100);

I tested it on my Rpi B+ its working fine, but the cpu load is always 100%. Is this normal?

I have a mysensors dimmer. I couldn't switch it on till i moved the dimmer about 2 cm's. Then it worked great. When i move it back 2 cm's it stops working. What causes this? I have a capacitor on the nrf.

I just found out that my gateway is not working great. I made a new one but i don't know why the other is not working good?

Solved it, it was not the gateway, it was a repeater node that couldn't pass the messages all the time.

I have a simple pir sensor with battery sensor. It just worked fine for about 1 month till today. The gateway does not always receive the message. some times it receives the ON signal and some times not, sometimes it receives only the battery and the status of the pir is not received.

I already tried to replace the batteries but it made no difference. What could this be?

@BulldogLowell Nice I didn't know that. But what happens if the dimvalue is higher that 100? does it still translate to 100/15?

You can use Var1, the easiest way is to keep the sended string always the same length so you can cut in the variable in pieces: http://www.arduino.cc/en/Tutorial/StringRemove

to change 0-100 to 0-15

int kakuDimLevel = (dimLevel / 100) * 15

You can use that AVRISP or use an other arduino as ISP. You have to change the BOD bit. Are you using windows or mac? On mac its quite easy with AVRFuses app. On windows you need AVR Studio.

info for mac: http://www.leonardomiliani.com/en/2014/avrfuses-una-gui-per-modificare-i-fuse-delle-mcu-atmel-os-x/
Windows: http://letsmakerobots.com/content/setting-arduino-fuses-manually-avr-studio

You have to burn the fuses like this:

LOW: 0xff
HIGH: 0xda
EXTENDED: 0x06

I wrote some more battery information here: http://forum.pimatic.org/topic/383/tips-battery-powered-sensors

I managed to measure the Vcc with the atmega with this script:

long readVcc() {
  // Read 1.1V reference against AVcc
  // set the reference to Vcc and the measurement to the internal 1.1V reference
  #if defined(__AVR_ATmega32U4__) || defined(__AVR_ATmega1280__) || defined(__AVR_ATmega2560__)
    ADMUX = _BV(REFS0) | _BV(MUX4) | _BV(MUX3) | _BV(MUX2) | _BV(MUX1);
  #elif defined (__AVR_ATtiny24__) || defined(__AVR_ATtiny44__) || defined(__AVR_ATtiny84__)
    ADMUX = _BV(MUX5) | _BV(MUX0);
  #elif defined (__AVR_ATtiny25__) || defined(__AVR_ATtiny45__) || defined(__AVR_ATtiny85__)
    ADMUX = _BV(MUX3) | _BV(MUX2);
  #else
    ADMUX = _BV(REFS0) | _BV(MUX3) | _BV(MUX2) | _BV(MUX1);
  #endif  
 
  delay(2); // Wait for Vref to settle
  ADCSRA |= _BV(ADSC); // Start conversion
  while (bit_is_set(ADCSRA,ADSC)); // measuring
 
  uint8_t low  = ADCL; // must read ADCL first - it then locks ADCH  
  uint8_t high = ADCH; // unlocks both
 
  long result = (high<<8) | low;
 
  result = 1125300L / result; // Calculate Vcc (in mV); 1125300 = 1.1*1023*1000
  return result; // Vcc in millivolts
}

I have currently this formula to set it to percentage:

  float batteryV  = readVcc();
  int batteryPcnt = (((batteryV - 2000) / 1200) * 100 );

readVcc outputs the vcc voltage. I want to set it to percentage. @ what voltage should I cut it off to 0%? What is the best formula?

Full AA alkalines are around 1.6V?

So it should be okay? Even when my meter shows around 180-200 uA with pir only?

I'm using a UNI-T UT136B. Should be quite accurate according EEV.

@Andreas-Maurer no, not really. Around 160 uA should be fine? Don't know if there is some1 else with a pir sensor on batteries? maybe he can share his experience.

No, I havent. lets try...

Edit: I removed the HT7133. The power consumption is not jumping a lot anymore. Sometimes it went from 250 - 320. but now its more stable around 260 uA (with arduino and NRF).

I have a HC-SR501 with an arduino pro mini 3.3v. I want to run it on batteries as long as possible. In sleep the setup draws around 280 uA. Thats quite a lot?

I already removed the power led on the arduino and i use the PIR 3.3v Hack.

The datasheet of the pirs tells me that it uses around 50 uA (@ 5v). When I only measure the pir it uses around 200 uA. The arduino with NRF around 70 uA without the PIR.

Is there a way to reduce it? With this setup and 2 AA batteries it won't last a year.

Not yet. Maybe next week. To much work at school right now ^^. But when it works i'll post it here.

Oitzu and I (testing :P) are currently working on the Attiny support. To test you can download this library (the same as the original one except that it includes the attiny).

Its working so far.

Bugs:
Your node id is the same as child id (if you set a different child id, somehow the attiny ignores it and makes it the same as your node id).
Sleep is working with interrupt but it does the setup again after wake.
Sleep / timer is not yet working.

library: https://github.com/Oitzu/Arduino/tree/master/libraries/MySensors (You can replace it with your existing mysensors library)
example sketch thats working: http://pastebin.com/xRu2JNQ9

wiring:

                  +-\/-+
                 1|o   |8  VCC/CE  RED/ORANGE
 YELLOW  CSN     2|    |7  SCK     GREEN
 -       SENSOR  3|    |6  MOSI    BLUE
BLACK    GND     4|    |5  MISO    VIOLET
                  +----+

Thank you. And what about the low ESR capacitors?

I'm testing with sensors now and i have a question about the decoupler capacitor.

Is it better to put always a capacitor on the nrf? And i have some 10uF. Does it matter if its 4.7uF or 10uF?

Oh and on the troubleshoot page i read 47uF and on the radio connector page 4.7uF.

I had it finally working on my Pi2, but its very unstable. sometimes weird values, crashes and fails.

switched to a usb serial arduino and that works great.

@mhortman Didn't work for me:

sudo wget http://repo.mosquitto.org/debian/mosquitto-wheezy.list~
--2015-03-27 10:46:51--  http://repo.mosquitto.org/debian/mosquitto-wheezy.list~
Resolving repo.mosquitto.org (repo.mosquitto.org)... 85.119.83.194, 2001:ba8:1f1:f271::2
Connecting to repo.mosquitto.org (repo.mosquitto.org)|85.119.83.194|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2015-03-27 10:46:51 ERROR 403: Forbidden.'

Thanks, working now. With PiGateway i can run the gateway, is there a wat to daemonize it and start at boot?

I'm trying to install the NRF24l01+ to my gpio pins from the raspberry with https://github.com/mysensors/Raspberry

But when i run 'make' i get this error:

root@pimatic:/home/pi/Raspberry# make
g++ -o PiGateway MyGateway.o MySensor.o MyMessage.o PiEEPROM.o PiGateway.o -Wall -Ofast -mfpu=vfp -lpthread -g -D__Raspberry_Pi -mfloat-abi=hard -march=armv6zk -mtune=arm1176jzf-s -I. -Ilibrf24-bcm/ -lrf24-bcm
/usr/bin/ld: cannot find -lrf24-bcm
collect2: ld returned 1 exit status