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

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

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
                  +----+

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?

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

@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.

@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.