I’m trying to get the SRX882 to work with my ESP32. I’m compiling the software myself using PlatformIO.
I tried two different models of SRX882 without any success. No signals received. To my surprise, once I connected a generic MX-RM-5V I had lying around, I started receiving RF signals on ZgatewayRF…
I couldn’t find any configuration examples with SRX882. I know there are some specific settings for CC1101, so perhaps I’m missing something. Is anyone using ESP32 with SRX882?
The board I’m using is OLIMEX ESP32-POE-ISO and the SRX882 V1.3 (ZTA31900). I have 5V and GND connected and checked with a multimeter. The DATA pin is connected to GPIO 13, at least for testing purposes. The CS pin on STX882 is not connected, which according to the documentation should mean the module is active.
While I’m not exactly sure where you problem lies, how did you build up your ‘test’ configuration?
You have ${libraries.decoder}, but no ‘${libraries.ble}’ and ‘-DZgatewayBT=“BT”’ to make Decoder work properly with Bluetooth, if you actually want BLE on this gateway as well.
Also which RF library are you interested in for your devices, as you seem to have them all thrown in currently, possibly taken from the …multi_receiver environment in platformio.ini, which would then require for you to define which RF library you want to be active, as only one can be active at one time, as described in
Also ${libraries.rtl_433_ESP} requiring a CC1101, not being able to work with your SRX882.
Not really knowing the OLIMEX ESP32-POE-ISO myself, does it have IR, or have you also connected IR receiver and transmitter - re the '${libraries.irremoteesp}`?
I’m also not sure about the two ZsensorGPIO build flags here.
Those are just a few things I’m seeing at first glance.
I’m sure if you reduce the configuration environment to only the few necessary lib_deps and build_flags, especially with only using a single RF library, at least for initial testing for the devices you have, the receiving will work fine. At a later stage, if you require additional RF protocols you can extend it to a multi RF gateway, but with the knowledge of having to switch between the different modules as described above.
Thank you for the suggestions. I appreciate it. You are absolutely right about messy configuration. This is the effect of my inexperience. I cleaned it up.
That said, everything else is working flawlessly. IR receiver and emitter are working as intended, although range of the IR emitter could be better.
RF emitter (STX882) is working great. I was able to read RF codes using MX-RM-5V. It’s not ideal, but served the purpose for now.
That said, the problem still remains. There is no communication with SRX882.
EDIT: OLIMEX ESP32-POE-ISO does not have IR. I connected external modules. There is another model from OLIMEX which does have built-in IR. It’s called ESP32-EVB. Sadly, EVB model does not have PoE, although it has Ethernet.
Please find attached the pictures below. I use a small breadboard for VCC (5V) and GND distribution. The ESP32 itself is powered via PoE. The green wires are just direct connection to GPIO 13, 14, 15 and 16.
I intended to read the codes of a generic 433MHz remote control.
The expected behavior is to receive a message with the code on “home/OpenMQTTGateway/433toMQTT” once I press a button on the remote. With SRX882 there is no reaction. Nothing. Once I replace SRX882 with MX-RM-5V, without changing anything else, same wiring, same config, I receive a message at “home/OpenMQTTGateway/433toMQTT”. The remote needs to be in close proximity to the MX-RM-5V, but it works as expected.
I read the messages using Home Assistant. Not the best tool for the job, but it works. Thank you for recommending MQTT-Explorer. I will give it a try.
I do have other ESP32 boards. To be honest at this point I’m just tired of testing. I will return to it at some point. Let’s park it for now.
I do appreciate all the support I received. Thank you once again.
If I may jump into this quite old topic:
I checked the IC datasheet, like for example here:SRX882
and it requires to connect CS to high to activate the receiver. For me that helped me out of the same problem.