@dbemowsk Initially I uses an AS5030 encoder, but then I switched to the EM-3242 as it's much cheaper and smaller and does the same. My board has an Op-amp inverter to change the sense of angle to voltage so that the magnet can run on the top of the chip rather than on the bottom. Only problem we had with the EM-3242 was that it has no hysteresis which shows up at the 360/0 junction.
I did some wind speed and direction sensor boards that I use in my own weather station design. All solid state and high resolution with analog signal readout, voltage for direction, 8 pulse per rev for speed. For inspiration see http://wws.us.to. Gary
@Yveaux So I found the problem now.
The disconnect between the sniffer and the network running V2.1 stemmed from the change in the way the NETWORK_BASE_ID is defined.
In the sniffer and V1.51 of the lib it is defined as a single uint64_t but in the V2.1 lib it is defined as a list of 5 individual bytes which are then later used to initialize a 5 byte char array via a macro.
Since earlier I had chosen a different NETWORK_BASE_ID from the default this uint64_t defined ID was now used to initialize the 5 byte array, except of course that only the first location got assigned anything. Luckily all of this happened without a compiler warning or error...
After I changed the NETWORK_BASE_ID in my nodes & gateway to use the 5 individual bytes format in the correct order everybody is all 
again. Even my V1.51 sensors that have not been recompiled yet seem to be just fine with the network.
Thanks
And I forgot to mention that the data rate in the sniffer and the network match as well..
Re: 
NRF24 Sniffer
I have been using Version 1.51 very successfully with the sniffer, but when upgrading to V2.1 I find that the (v1.51) sniffer doesn't see any traffic anymore even though the PAN-ID and RF channels match in the config files.
What has changed at the RF link layer that makes the sniffer not detect any traffic and what do I have to do to it to make it work again?
tnx
Maybe you can setup a RF sniffer as seen here http://forum.mysensors.org/topic/242/wireless-nrf24l01-sniffer-for-mysensors and observe what traffic you see when the system or node fails to give you some clues as to what is going on ?
You can do it ! Tweezers and magnifying goggles ( from Harbor Fright ) and you are in business.
Don't forget to set the Arduino to internal clock 8 mhz via fuse settings when rinning at 3V -- Most of them run without it but some might not be happy running 16mhz of the xtal at 3V .Gary
I made a little PCB that connects an Arduino ProMini i.e. see here with a nRF24L module and contains two LEDs one Switch and a voltage divider to measure the battery voltage. The board can be ordered from here OSH PCBs for about $3 for 3 PCBs, in the US at least.
Send me a message if you want the Eagle PCB files.
See schematic below -- follow notes on schematic -- Do not power with 5V serial adapter, radio will not like 5V.
There is a slight silkscreen mistake on the pcb near SV2: Mosi should read Miso.
Pro mini used : 
Yes, changing the "switch type" to Motion helped a great deal. I would never have thought of a motion detector to be considered a switch. I guess it works in a backwards kind of way. I get the source on my RPi next and have fun with that and trying to figure out why the simplest of Blockly events all fail to execute with error message. Have not found much deliberate documentation on their site, such is opens source I guess ..... Seems to be snappy though.
How is your own script tying into the system?
G
@hek @AWI Ahhh beta feed! Yes, that helped. Now I need to figure out Why I get LUA / Blockly errors on all events. Something about a nil utilitidevice . Thanks !
