Hi @frapell,

does the network id (MY_RFM69_NETWORKID) used on the node and the gateway match? Also other communication parameters like MY_RFM69_MODEM_CONFIGURATION, for example.

If, for example, your node has the following parameters...

#define MY_RFM69_NETWORKID 123
#define MY_RFM69_MODEM_CONFIGURATION RFM69_FSK_BR55_5_FD50

... you should pass the same parameters to the configure statement:

--extra-cxxflags="-DMY_RFM69_NETWORKID=\(123\) -DMY_RFM69_MODEM_CONFIGURATION=RFM69_FSK_BR55_5_FD50"

Also check if encryption settings match, if encryption is enabled.

@FarmerEd Sleep is not implemented for the ESPs - see (also for reasons): https://github.com/mysensors/MySensors/issues/968

Hi @frapell,

does the network id (MY_RFM69_NETWORKID) used on the node and the gateway match? Also other communication parameters like MY_RFM69_MODEM_CONFIGURATION, for example.

If, for example, your node has the following parameters...

#define MY_RFM69_NETWORKID 123
#define MY_RFM69_MODEM_CONFIGURATION RFM69_FSK_BR55_5_FD50

... you should pass the same parameters to the configure statement:

--extra-cxxflags="-DMY_RFM69_NETWORKID=\(123\) -DMY_RFM69_MODEM_CONFIGURATION=RFM69_FSK_BR55_5_FD50"

Also check if encryption settings match, if encryption is enabled.

@TriXwooD said in Double SPI Radio Raspberry Pi:

dtparam=spi=on
dtoverlay=spi1-1cs,cs0_pin=36

@TriXwooD : Thank you, this helped me a lot. I had to use a different pin number in /boot/cmdline.txt though for that it matches the pin number given in the configure statement:

dtparam=spi=on
dtoverlay=spi1-1cs,cs0_pin=16

./configure --my-rf24-cs-pin=36 ...

Configure wants the BCM pin number (36), but the dtoverlay wants the corresponding GPIO pin number (16).