-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
RFRecv not capturing signal correctly #10119
Comments
I have |
Try latest development version and disable not needed protocols. |
@Jason2866 ok, I will. But could you help me out a bit here. I cloned this repo and tried to compile in VSCode with platformio. What it did was compiled every iteration of firmware (>7GB), how do I work on just |
@Jason2866 I tried dev |
@bilogic rename |
@Jason2866 I did an OTA of http://ota.tasmota.com/tasmota/tasmota-sensors.bin.gz, but |
@Jason2866 I also tried compiling both
It's bed time now, will try again when I wake. |
I did the following:
I'm just not sure what I'm missing here, |
I placed |
Ok, found the issue. Tasmota GPIOs have to be configured with |
I disabled all but protocol 1 and it worked. Thank you. |
PROBLEM DESCRIPTION
I have a 32bit 433Mhz RF signal that is not being recognized by
RFRecv
Here is a sample of the received signal
My hardware works with
RC-Switch
, which is why I'm reporting the issue here.REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:(Please use
weblog 4
for more debug information)TO REPRODUCE
sonoff-sensor
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I expected Bits to be 32 and Protocol to be 1
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Are there any parameters available to config RC switch?
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: