Sorry for my NRF24 clone post yesterday. The ACK bit was an issue with the NRF5 platform. I had switched the memory region to handle TX/RX/ACK packages separately. Sometimes the received packages are written in the wrong region. I had seen my testing ACK bit. Now, I have changed my NRF5 code and I can't see no difference between the modules, I have. ACK and timing are exactly at the same level.

hello, i know it is late, but others could see it too. i had the same problem running small (LOW POWER) modules on power banks, because the battery or power bank has a built in power meter, while it is charging and consuming power, there will be power on the USB port, but the arduino's consumption is very tiny regarding charging a phone. you need to disable this feature somehow.

following this thread loosely. I have the following sensors and they seem to be accurate to some degree: http://www.aliexpress.com/item/DFRobot-Capacitive-Analog-Soil-Moisture-Sensor-3-3-5-5V-Corrosion-Resistant-with-Gravity-3-Pin/32574020064.html?spm=2114.01010208.3.2.P99ddH&ws_ab_test=searchweb201556_0,searchweb201602_1_10037_10017_507_10033_10032_10040,searchweb201603_1&btsid=8d3b5e46-a069-441a-a1f7-491ae7e317e1 and they are much easier to work with Arduino compared to Watermark stuff. Anyone agree?

@ServiceXp you said in this post: That was it!!!!! I tried 22uF, was still doggie, so I thought why not move up to 47uF wink and what do you know, that seems to be the winning value. I have some more testing, but looking pretty good so far. This sounds to me that the issue is solved... I can imagine that 1.4 requires a bigger cap while 1.3 doesn't. 1.4 uses auto acknowledge which can send burst packets. This could put a bigger load on your power supply.