Troubleshooting

@nexus1212 You're using a 3V Arduino. It looks like all the patterns are correct, but it's just not getting things right. A lot of the unprintable characters in ASCII are at the start of the table, so I'm thinking maybe you have a serial connection that is expecting 5V as the 'high' voltage and what it's actually seeing is so borderline that it's not always registering correctly. So look if there's a setting on whatever you're using to read the serial data to set it to be 3V compatible. (Maybe a physical jumper on the board?) It's so close to getting it that I bet it's something super simple like that and your Arduino is really doing it's job pretty well.

I changed node arduino to mega and it worked first try. Thanks for help

@Nigel31 Maybe it's best to use the wait outside a while loop. With this I mean. Right now you're calling a function that does the resends within the same while loop - so basically it blocks the main loop. The only thing I can think of, is that MySensors doesn't get time to execute all it needs to do before you call the next request. So if you'd rewrite the code a little bit so it does all the requests in different execution of the main loop() method. It might work much better. As I do it in a MessageQueue I've written and don't have the problems you have. Also sometimes it takes a while before a node starts using the repeater. If it's close enough to the gateway to get some responses. Than - if understand correctly - it will not start using the repeater until the repeater sees x-time of failures.

One approach would be to create a separate task on the ESP32 that takes care of testing this sensor, than the gateway is not affected.

@BearWithBeard Thanks. That sounds like what I was thinking. Makes it clearer though.

mfalkvidd gave you a great link, but if you ever need to see any possible choices, you can run ./configure --help and it will show you. The extra flags section is one thing (of many) that it says. Actually, this is very timely for me, as I'm trying to troubleshoot my own radio issues, so I'll use those extra two flags that you mentioned and see what they say. Thank you!

@Njwyborn sorry, I don't know. If the stack is called recursively, something is seriously wrong and behavior is undefined I guess.

Also posting the wiring helps others to help you. Fitzing is easy for this task

@mfalkvidd Thank you!

@Ispandy, let resume some things because I'm lost You copied the sketch code from node 3 (= correctly running node with cardscans and remote control from openhab) to node 50 and you adapted the node id. This same sketch on node 50 is running correctly with cardscans but not with openhab? Correct? If above is correct: somewhere your openhab configuration for this node 50 is not correct. You say that node 50 is never receiving the openhab command, so there is a problem with your openhab configuration for node 50.

I am using the TMRh20 libraries (not the MySensors library) and have the same problem. I'm pretty sure that there are interrupts that are not being reset. One of my other symptoms is that when I try to load or reload a program, the program doesn't start. I have a program program that I run that works most of the time and gets me to the point of being able to reprogram the Arduino //cli(); // disable all interrupts WDTCSR = B00011000; // set watchdog timer into configuration mode WDTCSR = 0; // turn off watchdog time interrupt. //sei(); // allow interupts I use this technique to load the program: write program use Tool-->port and set the port on the device, press and hold reset button <ctl>+u or click on upload icon when compiling gas gauge is almost complete, release the reset button. You may have to do 3)-5) several times. You could put: Serial.begin(9600); Serial.println("WDT reset"); at the end of the program to know that the device got reset. I hope this helps you. I, too, would like something a little more controllable. OSD

@pw44 MY_DEBUG is usually enough. https://www.mysensors.org/build/debug#enabling-debug-and-monitoring-the-logs and https://forum.mysensors.org/topic/666/read-this-first-it-could-save-you-a-lot-of-time/ can be useful.

Upgrading to 2.3.2 has helped somewhat

@mfalkvidd may this problem be related with eeprom stored vars? i will clear the eeproms and flash gatewayand nodes again.

@bcdaus from what I understand, ! means failed while ? means unknown. Unknown is used when the radio hardware does not support ack at all (so there is no way to know whether the message was received by the next node) https://www.mysensors.org/apidocs-beta/group__MyTransportgrp.html has some documentation.

Hi @mariuszjozala , Thank you for reporting back. Glad that it works now! In my eyes, the good documentation (and availability of LTS options) is one of the really big plus points of the NanoPi/FriendlyARM products. I did save a local copy of their wiki, just in case it ever disappeared, because these references are really helpful. Best regards pragtich

@jlb said in Radio stops working: How to make the node detect this radio problem ? I don't think there is a function to do this, but maybe someone else can help with that. How do I get my sketch to do a cold restart of the radio ? It would be good to see how you wired this all up - a hand drawn sketch or fritzing would do. I suspect that by modifying the way power is applied may need arjusting and come capacitors may need adding - You can reboot by using a hardware watchdog circuit (web search for it).