Github Devices Community Docs Blog

RF Receiver SRX882 not working with NodeMCU

after I successfully setup an ESP32 based Bluetooth Gateway with latest OpenMQTTGateway esp32dev-ble-firmware.bin to get the measured weights I also tried already to do the same with RF ggateway, e.g. to get the values of a bunch of 433MHz devices (Humidity sensors, RF remote controls etc), without success.
As I had only an RX470B in my fundus, but I did already many attempts and tried the binary version for RF, RF2 and PILight versions on NodeMCU, but no data was seen. So I ordered the SRX882 to have a compatible / tested version. That part arrived today, but also here with that hardware I still have no success, with none of the RF, RF2 or PILight gateways

The RF Gateways confirm in their logs
that Receiver PIN is on GPIO0=D3 NodeMCU. But when I compared with its the datasheet SRX882 Data Sheet then there is a difference between the shown picture on esp8266-hardware-setup. In the Picture for ESP8266 the D3 is connected to CS (pin near Vcc) and not - as the datasheet documents requires - to the datapin. I saw elder different sites which states that both pin are equivalent useable for data, but according to the latest datasheet that is wrong.
Anyway, I already tried all three RF Gateway versions with D3 connected to Data or CS but in non of the cases I ever saw any of the 433 Mhz telegrams received. I also tried with an Sonoff RM433, also without luck.

On the last link cited above I also saw under “ESP8266 Hardware setup” the comment

*If the gateway works only when serial monitor is connected don't use D3 use D2 instead (gpio 4) and modify config_RF.h accordingly.*
  • With SRX882 some users reported that D3 is not working use D1 instead in this case and modify config_RF.h accordingly."*

So it looks as if I have to compile the sources myself to get the proposed changed. Wouldn’t it be better to use the proposed changes (using D1/D2 instead) already as defaults for the RF binaries?

Sorry for these Rookie questions but I’m currently stuck here.


To give you more infos here is the different pins you can use on a nodemcu:

Indeed D3 is not compatible in some case (nodemcu V1 are ok nevertheless)
this is coming from the history on where we were searching for a way to put the maximum modules on a nodemcu.
And I agree with you, that the default RF receiver pin should be changed on ESP8266, nevertheless I’m quite sure that there is some hardware already done like that.
Maybe proposing an alternative firmware with another pin or on the fly changing could help.

No problem, are you able to compile the firmware yourself?

I hope so. Unfortunately I had to replace my Linux notebook and now have to fallback to Windows10
Where / In which header do I have to set the PINs? Is it only config_RF.h, for all 3 variants RF, RF2 and RF_Pilight?
I changed it now RF_RECEIVER_PIN from 0 to 5 (D3 to D1), but I still see any incoming tickets in the serial monitor.
Is there a simple test? I do have Sonoff RM433 but I see no incoming token on RF or RFPilight

Meanwhile I had more success: After using the Data pin (as in Datasheet) and not the CS Pin (as in OpenMQTT picture) I meanwhile get data with the RF module when using RM433. However none of my various devices (like temperature and humidity sensors) are visible, neither when using RF, RF2 or RF_PiLight :expressionless:
Is there any trick to see what’s flying around?

This depends on your sensors models, could you precise them ?

Great !

Actually I do have a 4 sensor Temperature / Humidity sensor from ELV called Raumklimastation RS100. Other elder similar Temperature sensors are also still laying around, but the vendor is not know anymore.

Is there any 101 / best practices documentation who to add new devices to the OpenMQTT?
Also for additional