Troubleshooting

@dpcons I had similar issues which I called 'ghost' nodes and 'ghost' sensors. I was getting random nodes added mycontroller and even some existing nodes suddenly had children that simply didn't exist. I did so much over many months to get this sorted. In the end I added a lot of capacitors, took the gateway from directly connceted to pi to via serial USB. I even moved the whole lot to another room..... It's all been fine for a while. I still don't know the exact cause in my case (may be different for you), but power supply, radio nodes, cabling/connections all can play a part in some very wierd things..... ;)

Yes, that worked... I downloaded master.zip and replaced the current Liquid Crystal folder with the new one. Restarted IDE and was able to compile and upload the sketch. Thank you!

@mfalkvidd Great stuff - I didn't see the page, just the link title and it wasn't in there (but I was in a rush to take my Mum shopping).

I found a YouTube video that explained how to test them, but my multimeter must not be up to the job. So I created a single led dimmer sensor and hooked it up to the three MOSFETS one at a time to test, and they seem to work as they should. So my issue must be with the sketch. Mods, you can delete this thread if you like.

Thank you for your reply! I will do that.

I tried to reprogram the Arduino Nano but that didn't helped. Changed com port on computer and that seems to solve my problem

Sorry, it seems like I have misunderstood what the problem is. Would you mind explaining the problem in a different way? Or maybe I should just step back and let someone else (who understands the problem) answer.

Eureka...eureka... Mosquitto works.... Thanks to your contributions I have achieved what I wanted step by step.... for which I thank you. Indeed Mosquitto has worked in the beginning but I am expecting an opening window. Meanwhile, I have successfully send a message from the terminal window 1 to 2. Thanks to all who have taken the trouble to look at my question and send me a possible solution. See you later. JackDG

I believe that this was all due to a loose connection.

@tsjippy did you run sudo ./bin/mysgw ? Could you post the full log of what you did and what output you got?

Interesting. The pet friendly settings might be useful in my house. A couple of thoughts. This sensor wants 12 volts. I have had bad luck with the cheap Chinese Pro-Minis I normally use. They advertise being able to use power up to 12 volts, but they fail quickly at that voltage. You will probably need to power the arduino differently from the sensor. I'm not that familiar with the Mega 2560, but it appears to have several additional interrupt pins over the regular arduinos. You would just have to pick one and use that in the software. Did a quick google and someone said the two "T" pins are tamper detection. The NC are motion detection. The tamper detection just tells you if the sensor case has been opened. The two NC terminals appear to be a normally closed switch contact. You could use a simple button setup like this: https://www.mysensors.org/build/binary This setup doesn't use interrupts and instead polls the switch pin. The down side is you will not be able to sleep the node. There may be better ways, but the sample above would give you a quick way to experiment with it.

@gfink great work, thanks for reporting back

@creaky said in Recommendations for soldering temperature: Here is a super interesting article about the science of soldering and how soldering affects electronic components. Fun fact; ICs aren't watertight! Off cause IC are not watertight. In real production, IC are either stored in Nitrogen boxes, and/or baked according they MSL level, otherwise when those are running through the reflow-oven they will due to moist, as the moist are becoming damp, yes pop like pop-corn that pops, hence pop-corn effect https://en.wikipedia.org/wiki/Moisture_sensitivity_level And the reel (that have the components) are ALWAYS vacuum sealed (with an ESD bag), and MSL level is written on the outside, like lot/batch number and partnumber

Thank you so much for your help, that fixed it!!! My wife thanks you too! :-)

I ended up setting up some monitoring that if by some chance it does go belly up my monitoring will do a recovery action. But it does still happen from time to time, which is strange.

UPDATE: I power cycled the board by physically removing the USB power/data cable and the board came up on the network + MQTT session to the broker was established!! For what it's worth and for future reference if anyone finds this thread: It appears the official MySensors Hello World ethernet gateway basic tutorial works great for the Mega/2560 board paired with a 5100 Ethernet shield.

Thanks, I will have a look at your suggestions! I've had some stuff happen at home so I am a little under the pump, so I am currently putting together a list of things to look into when I have some more time in a week or so, and your suggestions have been included on that list! I appreciate your help!

@skywatch said in Adding sensor to controller when it's part of gateway: @Homer I am no expert in this but I have thought of something that you could try. If I understand correctly you have added one RF433 transmitter to the GW node? This then sends data (On/Off) to the 6 RF433 sockets. If so then the gateway only has one child, the RF433 transmitter, the sockets are not 'attached' to the GW. So instead of presenting all 6 sockets, just present the one RF433 transmitter and see if that helps? All the code for the actions is in the receive section anyway. This is how I did it with IR blaster and it works fine, changing IR for RF should not make a difference in the structure. Hold on - I think I got it.....!!!! You are using S_LIGHT in presentation - that is no longer supported. Change S_LIGHT to S_BINARY. Another thing is that although you are presenting your child(s), you do not define the type. I would expect a MyMessage in there somewhere at the start. So add MyMessage msgyourmessage (child_id, V_STATUS); And finally change V_LIGHT to V_STATUS in the receive function. Thanks! Yes, you got it lol!! The thing that is weird is that all I did was add the rf433 controlled devices from a working sketch to the gateway sketch, so why does it work when it's separate but not when it's part of the gateway sketch? If S_LIGHT is no longer supported, why does it work on a standalone sensor?