Troubleshooting

@CrankyCoder How far apart are the node and gateway? What is between them? Can you post any photos of of each with the wiring?

@novicit @bjacobse Good call!

Maybe they reflowed the chip on backwards (rotated 180 degrees)? You could compare the chips orientation to photos of known good breakout boards, or to the datasheet. If so, you'd definitely have a solid case for a refund if it's worth your time to pursue it with the seller.

http://learntohackit.com/intro/# it can be useful information ???

Just for others coming here in the future: I changed the connections as suggested by @mfalkvidd , restarted the node and now the radio runs from batteries and the Arduino is powered from USB (phone charger). Unfortunately this doesn't seem to have improved the radio communication, but this is another story... Stefano

Hi @Merlotmaker, If you want more reactions from members, you should provide more information. what for sensor do you have, because you are speaking about BMP280 and BME280 the lib you are referring to is a specific one for the https://www.sparkfun.com/products/13676 how did you connect your sensor to the UNO? did you follow this guide already? https://learn.sparkfun.com/tutorials/sparkfun-bme280-breakout-hookup-guide

@OldSurferDude I have since looked at various modules that are sold on the internet. My conclusion is that they are not all the same. Some seem to be much better than others. The price also shows that. I use this shield for the radio comms NANO V3 Wireless Shield. It has the caps already built in as well as some level shifting for the signal pins. [image: httprobotdyn.compubmedia0g-00005243nano-wireless-shieldphotophotoangle0g-00005243nano-wireless-shieldassembled.jpg]

Hi all, This is what I Simply ended up with to clear the eeprom, // load core modules only #define MY_CORE_ONLY #include <MySensors.h> void before(){ Serial.begin(115200); Serial.println("Started clearing. Please wait..."); for (uint16_t i=0; i<EEPROM_LOCAL_CONFIG_ADDRESS; i++) { hwWriteConfig(i,0xFF); } Serial.println("Clearing done."); } void setup() { Serial.begin(115200); Serial.println("Started clearing. Please wait..."); for (uint16_t i=0; i<EEPROM_LOCAL_CONFIG_ADDRESS; i++) { hwWriteConfig(i,0xFF); Serial.println(i); } Serial.println("Clearing done."); } void loop() { // Nothing to do here... }

If you have the wrong modules, it could give you problems yes. Check out the buying guide, there are recommendations for the modules to pick, for example the ebyte ones. The will work very reliable. Big advantage of NRF24 to RFM69 is the throughput and response time.

@Nigel31 glad you got a fix :+1:

Hi, thanks you so much for answer. I continue to search and I think I find what is wrong.. . .. It's because I use pin pitch female [image: 1652640171597-6d6ade87-7585-4789-97e1-2ed0689a769e-image.png] And the connection is very bad.. Sometime it's work, sometime don't.. . I sold it, and I correctly use 3 NRF now... I continue to compare but now I have a comparaison point... :) I continue to search but you're right, the parent ID is not setup same way on different sketch. I try it next week.

intermediary result: I have started a second gateway and now the nodes do communicate... puzzled... I remove the extra gateway... same situation... so reprogram gateway with: #define MY_RF24_PA_LEVEL RF24_PA_LOW so it seems this was the responsible for this ! thanks !

@epierre Yay, good job!

I found that timelib.h uses a tremendous amount of memory. You avoid using it by getting time string from the controller. I have also found that when you're using that amount of memory that bad things happen, as you noted. I use global variables to avoid the transient nature of function variables. I'll be looking forward to other comments as, I, too, do not know all the tricks;) OSD

Well done @ejlane, thanks for reporting back.

@electrik Going through the documentation of the Orangepi, I found out that the config should be --my-rfm69-irq-pin=71 --my-rfm69-cs-pin=233 but still no dice. I also get an error: Mar 28 14:11:14 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,FQ=NA,REL=0,VER=2.4.0-alpha Mar 28 14:11:14 DEBUG TSF:LRT:OK Mar 28 14:11:14 DEBUG TSM:INIT Mar 28 14:11:14 DEBUG TSF:WUR:MS=0 Mar 28 14:11:14 DEBUG TSM:INIT:TSP OK Mar 28 14:11:14 DEBUG TSM:INIT:GW MODE Mar 28 14:11:14 ERROR Interrupt handler error: Bad file descriptor Mar 28 14:11:14 DEBUG TSM:READY:ID=0,PAR=0,DIS=0 Mar 28 14:11:14 DEBUG MCO:REG:NOT NEEDED Mar 28 14:11:14 DEBUG Listening for connections on ▒]o:5003 Mar 28 14:11:14 DEBUG MCO:BGN:STP Mar 28 14:11:14 DEBUG MCO:BGN:INIT OK,TSP=1 Mar 28 14:11:14 DEBUG TSM:READY:NWD REQ Mar 28 14:11:16 DEBUG ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: The IRQ pin is connected alright, the RFM69 module works perfectly on a RaspberryPi or an OrangePi Zero. It just refuses to receive when used on the OrangePi Zero 2 Something with pin assignements or SPI... It is a a new SOC, so maybe I should wait for someone with more expertise than me to work it out...

Hi there and thank you for your help. The answers came later than I expected (never mind) and during a period as I am away from my arduinos and raspberry. I will try to make a sketch to show you the set up. But I am not interested to connect the sensor directly to raspberry pi by one-wire. The set up is like this Arduino with Dallas Temperature <> Serial interface <Serial cable> Moxa Serial to IP <Ethernet / virtual serial port> Raspberry pi as gateway with virtual serial port <Ethernet> Home assistant I will try to use SoftwareSerial, which is what I used already without mysensors on pin 00 et 1. What I am struggling with is the mysensors configuration for serial port and the gateway on raspberry with the virtual serial port. Keep you updated.