Troubleshooting

@rasitd When i remove NRF24L01, i still get X=-1, Y=-1. anyone?

Same here. I had to go up to 5V to power my Arduino Pro Mini 3.3V sufficiently.

So I still haven't quite figured this out. There doesn't seem to be any information out there on this feature, at least not that I can find. I believe I've successfully transmitted "101;255;3;0;6;I\n" from my gateway, which from what I understand should set the sensor node to Imperial units. While watching the serial monitor on the sensor node, I did not see anything received and the units did not change. There is a possibility that my code did not transmit that code successfully, however the rule associated with the command was triggered successfully and I'm not sure of any way to verify. I know what I could easily modify the code on the sensor node to change the units, however I like the idea of being able to control multiple sensor nodes centrally. I also like the fact that the sensor code was written to include this functionality, and I'd like to take advantage of the well written code published by mysensors... Any help would be greatly appreciated.

Greetings Hek, I am never sending messages to my nodes, only requests for data from the analog sensors. As I am already receiving analog inputs 0 through 7, I have no need to present eight different sensors. What I am unable to get right is the message that I would send to a node (like the script above) that would cause it to unleash one round of sensor data. I know the first number is the node, itself. The second number is the sensor but that is weird here because all sensors are read in one shot. Should I simply call it sensor 0 to match the CHILD_ID_POWER? I know the third number is a request if it is a "2" and the fourth can be a "0" for no ack. As I call MyMessage msg with V_WATT, the fifth number is "17" so, in my mind (and nowhere else because it does not work;), the code my gateway should send to node 1 to request data is 1,0,2,0,17/n. I am wrong, of course, because it doesn't work. If anyone could set me straight, I would deeply appreciate it. Also, thanks to Chester for the IF statement advice.. As a PS, my nodes communicate well and my gateway notices when my node is activated.

@iask I am not able to measure anything accurate that low. I use the chargeable version of cr123 in many sensors. No long term results yet, but a lot of power

The DHCP example was with a different sketch. I had the Ethernet shield replaced and now both the DHCP sketch and the gateway sketch work! :-) (I had no packets coming from the broken shield at all when connecting it through a sniffer) /Carl

@BulldogLowell I just reinstalled arduino and now it is working... thank you for testing and telling me!

Well I solved the problem... I had a power supply tied to the board and should not have while communicating via USB! https://ketturi.kapsi.fi/2014/04/how-to-fix-moody-arduino-nano/

@lafleur I abandoned it due to the fact that my Nano cannot fit it together with signing support.

@dakky The following posts should provide enough guidance and examples for flashing your UNO with optiboot. You will need to specify -c usbtiny to avrdude to use your USBTinyISP3. http://www.instructables.com/id/Flashing-bootloader-into-Arduino-UNO-R3/ http://forum.arduino.cc/index.php?topic=57795.msg415941#msg415941

@hek Yes, I look into that and send a pull request as soon as there is a prototype.

@Ironbar Sorry, I was't clear on my previous post. Initially, I went through two (2) Uno's to test my connected sensors and received similar fail messages as yours. Thinking both Uno's were bad , I decided to used a Nano instead. And that's when everything started to work. It is obvious but it took me a while to figure this out. The Uno's consumes slightly more Amperage than the Nano's as a result the radio wasn't able to keep up with the power from the Arduino Uno. What I've learned is these radios don't work well when power is shared with the Arduino and you have bunch of sensor hook to it. Especially under burst transmission over a short period of time.

@BramWerbrouck Take a look at this thread for some troubleshooting ideas: http://forum.mysensors.org/topic/311/radio-problems Cheers Al

http://www.mysensors.org/download/serial_api_14 To do a REQ(uest) set message-type to 2. For example: 12;1;2;0;0;\n This requests a DOOR (0) -variable from sensor 1. Remember you must pick up this request in the callback of your sensors sketch.

@britcowboy take a look at the conversation a lot has been written on power and supplies

I think the something about order of initialisation was changed that fixed this problem. Try 1.4.1