Troubleshooting

I had quite similar issue with sensor and gateway not communicating. Solved today

@BartE, Thanks your solution worked like a charm. I modified the RGBController created as part of the MIOS RGBController plugin itself as a child of MySensor RGB tile and everything started working as expected. Once again thank you so much for your help.

(SOLVED) PROBLEM CAUSE: some sort of unclear data in the memory of the board(sparkfun redboard), i think.. SOLUTION: uploading mock-sensor sketch and afterwards the wanted sketch i soldered the de-CAP and tried within 2 meters range, but it didnt change. than i got back to my office and uploaded serial gateway sketch to one board while the other board was still with repeater sketch. the serial gateway showed correct log at the IDE like in the thread that Wijbe-Fryslan mentioned, but the repeater still didnt receive its data. than i uploaded mock-sensor sketch to the second board and than the data appeared at the serial gateway log. so i did the same procedure of uploading mock sketch , and than uploading the wanted sketch for each board (repeater and humidity) and went to the controller to check it and it worked!! thanks to the new original domoticz app i could check the log online for "sketch version" lines and afterwards i did reception distance metering with battery powered repeater node. now all is working fine but there is something that disturbs me - the domoticz log showed same node number for the repeater and the new humidity sketch. is that ok? or i should define manual node number inside the sketch? HUGH THANKS TO EVERYBODY

Did the self-test pass before you re-flashed it?

I was using a different approach for smoke sensor read, if you are interested please take a look here: http://forum.mysensors.org/topic/2747/home-automation-multi-sensor-nodes There are examples includes of single sensor node and multi-sensor node that include also MQ2 sensor and example how to read the associated MQTT message into HomeAssistant.

Yeah -right on! In my sketch ive set them to use unused analogue pins #define MY_DEFAULT_TX_LED_PIN A0 #define MY_DEFAULT_RX_LED_PIN A1 #define MY_DEFAULT_ERR_LED_PIN A2 ...problem went away. ;-)

Another thing you can do is use the MockSensor sketch - it makes it pretty easy to make fake sensors so you can test out radio range or controller behavior for different sensor types.

Hello, In MySensors example there is no attachInterrupt so sure it's not useful. Your problem occurred also when battery are full ? May I asked you some question on your design ? On this post or by private message (could be in French ;)) ? David.

Playing with my Arduino IDE and mysensors download on my computer with Windows 7, I can make the following conclusion: Arduino-1.6.5-r2-windows works fine; Arduino-1.6.7-windows gives described UIPEthernet warning.

http://forum.mysensors.org/topic/1424/resend-if-st-fail might be relevant http://forum.mysensors.org/topic/2189/serial-api-noack-when-sending-with-ack-failed started by @SiLeX has a longer discussion on resending

In your first sketch, the node accepts incoming messages. The second sketch does not have a function for incoming messages, so you have no function to give gw.begin as argument. You tried giving ge.begin a message instead, but that's not what gw.begin expects so you got a warning. When you don't want to use incoming messages you simply give NULL to gw.begin, as ericvdb suggested.

Hi! Nope - the MySensors GW does not assign any ID but if you use a static ID like (3 in this example) that would work. gw.begin(NULL,3)

OK:) - Good news I have resolved the issues and thought I would update :) As mentioned I used the UNO's as my micro controllers - I decided to use the Pro Minis instead. I set it up on the breadboard and for some reason they worked. I noticed in the code that there was an interrupt command for the Pro Mini and I am not at the coding experience to understand if this might have been the problem when I used the UNO's?? attachInterrupt(1, PushButton, RISING); //May need to change for your Arduino model Anyway the code worked like a charm except now the LCD display kept crashing the system. After MUCH hours trying to figure out why and lots of experiments, I swapped out the Pro Mini for another one and this worked 100%. Having a closer look at my soldering on the A4 and A5 pins became clear where the issue was :) Anyway - its up and running 100% and am very happy. I can now control all the zones from my Domoticz (Raspberry Pi), notifications through Clikatell (SMS) and e-mail works well and I am very chuffed it works!! Thanks to Pete and Bulldog as well as the forum for the help !! You guys rock!! My next project is my Gargage door (open/closed) with the ultrasonic sensors - the wife is always leaving it open!! Cheers Wallis

Oh. Sorry. I wasn't aware of the do-while construct. Thanks for teaching me.

Got delayed.. I had to order a IR reciver to find out my remote codes, didnt thought I would find them easily on the internet but nope! :)

@sundberg84 Ok, I will try changing the cap values. Thanks.

@bjacobse said: @flopp This is the correct way, to sleep and use interrupt for this :-) so you are using interrupt http://forum.mysensors.org/topic/417/gw-sleep-and-milis Thanks

Thanks, I thin that fixed the issue. I set the Repeater node ID to 100. The Arduino sketch has the ID set to AUTO which I think initially set the Repeater Node ID to 255. :-) Tony

Thanks a lot for pointing me to the right place! Now it compiles correctly. It's only to understand if it works. Cannot test it here right now. I'll do it soon! Thank you ;) Simon