Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not receiving any RF data using an ESP32 with MX-RM-5v and FS1000A #1669

Closed
heisenberg2980 opened this issue Jun 7, 2023 · 4 comments
Closed
Labels

Comments

@heisenberg2980
Copy link

Describe the bug
After following the steps and connecting the ESP32 board to MX-RM-5v and FS1000A according to the instructions here https://docs.openmqttgateway.com/setitup/rf.html#esp32-hardware-setup the Bluetooth data is received by the MQTT broker but no RF data (433Mhz) is received. I have flashed the ESP32 using esp32dev-ble, and I use MQTT Explorer to analyse the MQTT data.

Expected behavior
I would expect to receive messages into the topic home/OpenMQTTGateway_ESP32_BLE containing 433Mhz data.

Environment (please complete the following information):

  • OpenMQTTGateway version used: v1.5.1
@NorthernMan54
Copy link
Collaborator

The build you are using only supports receiving Bluetooth data, to receive RF you need to select a different build. To receive both you will need to create a custom environment. Please note that due to the resource requirements needed to receive and decode both RF and Bluetooth messages this may not work.

@heisenberg2980
Copy link
Author

Thank you very much, I hadn´t realised there was a esp32dev-rf option. After uploading this firmware I can see in the logs the esp32 is now setup for RF:

N: RF_EMITTER_GPIO: 12 
N: RF_RECEIVER_GPIO: 27 
N: Switching to RF Receiver
N: OpenMQTTGateway modules: ["WebUI","RF"]

Unfortunatelly I am still not receiving any RF data, even when pressing different buttons in a 433.92mhz blind remote controller near the receiver

@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Aug 31, 2023
@github-actions
Copy link

github-actions bot commented Sep 8, 2023

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as completed Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants