Its still a problem in V2.xx and occurs when you have more than one sensor. Not battery related - all my sensors are mains powered. One of my nodes has 5 sensors - 2 others only have two. One is a sensebender - the other two are nano's. All exhibited this behaviour. Using mysensors 2.3.2 and a wifi gateway. wait( 50 ) between presentations fixes the problem every time.
Posts made by Jonnyd
RE: Sensor presentation failure
RE: Sensebendermicro.ino verify errors
@BearWithBeard had the same issues when I tried to recompile existing sketch and dug out the above libraries. My problem is that I then get a compile error "'atsha204Class' does not name a type; did you mean 'atsha204_read'?" at this line "atsha204Class sha204(sha204Pin);" Was just going to update working sketch to new mysensors library - but I guess not.
RE: Values which gateway reads are others then sensor sends???
I have same problem using sensebender as node and ESP8266 as wifi gateway with the sense bender node reporting HUM as a 10 digit number. Mysensors 1.5 lib and 2.0.0 ESP8266 (no diff with 2.0.3). Only affects the HUM reading - not the temp or batt voltage. Interestingly a standard mysensors DHT11 node reports HUM correctly in the gateway while simultaneously the sensebender node does not. Will try the Dev library next.