Troubleshooting

@hek said: You can do a simple msg.isAck() in the message callback to check if it is a ack message. How the received acks can be matched with the sent messages?

@korttoma Thanks for the tip. I will check the wiring (once again). Still it would be interesting to know if arduino can restart itself since for increased reliability (if any?) that could be done every night.

Does this help: http://forum.mysensors.org/topic/748/manual-assigning-node-id-s-for-network-with-repeaters I agree with you that the serial messages are not perfectly documented, but realise that this site has been made (as far as I know) by a bunch of people that share their 'love' for home automation..... boozz

What version are you using. The current MQTT gateway code states: #define RADIO_CE_PIN 5 // radio chip enable #define RADIO_SPI_SS_PIN 6 // radio SPI serial select #define RADIO_ERROR_LED_PIN 7 // Error led pin #define RADIO_RX_LED_PIN 8 // Receive led pin #define RADIO_TX_LED_PIN 9 // the PCB, on board LED*/ This works for me (sorry for the large font size, came from cut-and-paste from the Arduino code and I have found no way of changing it.)

Look like the problem all along was the sketch that I copied from Codebender. In the end it appears that I wasn't the only problem with the issue, and this is where I found the fix : http://forum.mysensors.org/topic/737/uno-w5100-shield-not-pinging

Thanks for the reply. Not sure how I translated that to the battery level. That is what I get for trying to figure it out late at night.

@C.r.a.z.y. is this confirm? coz i'm having the same problem. and Yes, i'm using serial for my gateway and usb for my sensor. Please share if there's possible answer for this problem. thanks

MQQT Gateway works with V1.4.1, SoftSPI enabled in RF24_config.h and workaround mentionned (#define digitalio.h in main ino) but radio dialog with nodes in V1.4.1 fails (for Nodes , SoftSPI is not enabled). If i rollback nodes to V1.4 , it works!

@Hacker007 I tried adding #include DigitalIO.h and sure enough it allowed the code to compile. I still am unsure if it will work due to incorrect radios from "Alice". Thanks for the comment.

I have the same problem. Work goes through a repeater. Everything works, other than time. Setup: sensor started, id=4, parent=0, distance=1 send: 4-4-0-0 s=255,c=0,t=17,pt=0,l=5,st=fail:1.4.1 send: 4-4-0-0 s=255,c=3,t=6,pt=1,l=1,st=fail:0 read: 0-0-4 s=255,c=3,t=6,pt=0,l=1:M send: 4-4-0-0 s=255,c=3,t=11,pt=0,l=18,st=fail:Temperature Sensor send: 4-4-0-0 s=255,c=3,t=12,pt=0,l=3,st=fail:1.0 send: 4-4-0-0 s=0,c=0,t=6,pt=0,l=5,st=fail:1.4.1 lost parent find parent send: 4-4-255-255 s=255,c=3,t=7,pt=0,l=0,st=bc: read: 3-3-4 s=255,c=3,t=8,pt=1,l=1:1 new parent=3, d=2 read: 0-0-4 s=255,c=3,t=8,pt=1,l=1:0 new parent=0, d=1 send: 0-4-0-4 s=255,c=3,t=8,pt=1,l=1,st=fail:0 send: 4-4-0-0 s=2,c=0,t=8,pt=0,l=5,st=fail:1.4.1 send: 4-4-0-0 s=3,c=0,t=3,pt=0,l=5,st=fail:1.4.1 send: 4-4-0-0 s=4,c=0,t=1,pt=0,l=5,st=fail:1.4.1 gw.getStatus CHILD_ID_VIRT_Relay: 1 send: 4-4-0-0 s=255,c=3,t=1,pt=0,l=5,st=fail:1.4.1 lost parent read: 0-0-4 s=255,c=3,t=8,pt=1,l=1:0 new parent=0, d=1 requestTemperatures: requestTemperatures done: temperature done: 13.70 temperature: 13.70 send: 4-4-0-0 s=0,c=1,t=0,pt=7,l=5,st=fail:13.7 send: 4-4-0-0 s=2,c=1,t=4,pt=7,l=5,st=fail:279 send: 4-4-0-0 s=255,c=3,t=1,pt=1,l=1,st=fail:0 gw.requestTime:0

@BulldogLowell That's it! Thank you :+1: if (message.sensor==1 && message.getBool()==true) {....

@C.r.a.z.y. yeah.... those are VERY bouncy. are you interrupt triggering or just using a state change? post your code, let's make sure you have it de-bounced enough.

@hek : it happens that I have currently the same setup (3.3v mini pro as serial gw via FTDI); and am suffering from exactly the same symptoms (no reaction when I push commands to the GW). Reception, however, is ok. I plan to add a capacitor for the ripple; but given incoming reception is ok, I doubt it will make a difference? Needless to say that uploading the sketch works fine, and that upon writing the TX led flimmers. EDIT : nevermind, solved.

okidoki, will do , thanks, Cor

Hello. Thanks for all the fast responses. I will look at my gateway code and see if I have missed something. Best regards Andreas

Bluetooth indeed hops around in the 2.4 GHz band split in 100 kHz bands but Bluetooth has an algorithm to stay out channel that are occupied. For that to work, Bluetooth has off coarse to see the other "user" and if the channel is not used that often that can take time or will not work. But .. provided that Bluetooth stays out the band you are using for MySensors there is still a possible problem in that the nRF24L01+ (like almost all 2.4 receiving IC's) has a wide-band LNA followed by a mixer followed by filtering and more gain. The wide-band will see both the Bluetooth and the Signal Of Interest (SOI) and if the level of Bluetooth if much larger than the SOI things will also go wrong. So if you have Bluetooth at 50 cm, it will probably come in around -30 dBm, the nRF24L01+ can receive signals up to -85/-94 dBm and this kind of level differences can give problems, see also Table 7 of the nRF24L01+ datasheet.

Yes i made several reset, exclusions, inclusions, vera reset and clear EPROM but nothing worked... I made a new sensor and it works perfectly Strange... I will try again when i will have more time. Thanks for the help :D

Baran, just wondering, but did you try to copy and past JUST the library folder from the zip file into the same folder where your Arduino IDE's library folder is located. Let me make it clear that I'm not talking about pasting it into the Arduino library folder itself, but into the same folder that the Arduino's library folder is located. When you do this the computer will bring up a box that says you can't have two folders named library in this location and then ask if you want to consolidate them. You say yes and then they become one folder making it's so your Arduino IDE can find the now one library file.