-
Notifications
You must be signed in to change notification settings - Fork 638
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
RF/RFBRIDGE Update #1693
RF/RFBRIDGE Update #1693
Conversation
- remove optional RFRAW - enable module when RF_SUPPORT=1, optionally enable RCSwitch - reorder ifdef checks to treat RFB_DIRECT and old RF_SUPPORT the same - remove RF_PIN
In relay.ino, can "#if RELAY_PROVIDER == RELAY_PROVIDER_RFBRIDGE" around rfbStatus() calls be replaced with check for RF_SUPPORT? |
The RF section is missing in web image due to this check:
|
MQTT messages is working for my nodemcu device as before. I saw this explicit check for ITEAD_SONOFF_RFBRIDGE (in migrate.ino), does it need to be adjusted? |
IDK about that. The way providers work now, it will force you to use RELAY_PROVIDER_RELAY with real pins. Maybe for some other PR.
Nope. That is a copy of defines from hardware.h (which I'd like to replace with #1680 instead of duplicating data manually) Some fixes. (kinda delayed, because I could not find rf receiver / transmitter yesterday)
I was having trouble receiving anything with rc-switch. It worked for some time, but then suddenly stopped and I could no longer see data. Even with rc-switch ReceiveDemo example :/ Sending worked ok. |
The new changes work as intended. Is configuring the Rx/Tx pins from WebUI really useful? I mean it can be useful when prototyping but pin configuration would probably need a new image. "Repeats" value is only relevant for RFBridge, right? It is always 1 for RFB_DIRECT. |
> Is configuring the Rx/Tx pins from WebUI really useful? I mean it can be useful when prototyping but pin configuration would probably need a new image.
True, but it can always be moved. At least it is a place outside terminal (or config backup) to disable / enable them. Although, seeing it again, i did mess up the placement and should've added a hint text.
> "Repeats" value is only relevant for RFBridge, right? It is always 1 for RFB_DIRECT.
"Repeat" means different thing depending on context. For sonoff, it will send serial command N times, because EFM8 does repeats on it's own (~4 times, i think). RCSwitch has a setting for repeats though:
https://github.com/xoseperez/espurna/blob/056f7ebf079bad9cde4bd3f529b04a5a83695fdd/code/espurna/rfbridge.ino#L800
(which was previously hard coded as 6)
Tested with Sonoff, everything works too.
edit: but I still don't understand why I can't make external receivers work...
|
I see what you were referring to; I was referring to the times setting on message which put it back on the queue > 1. I am using an 315Mhz external tx/rx and it works fine. My switch is a bit weird though and based on some suggestions ended up using a special version of RCSwitch (https://github.com/Martin-Laclaustra/rc-switch.git#protocollessreceiver). |
Right. This was added here: Unspecified, it defaults to 10: Or it can be a separate option altogether. |
fixes #1590
fixes #1586
maybe #1014
I have only tried building itead-sonoff-rfbridge bin with RFB_DIRECT=0/1, to see if everything is in place. No live testing done yet.
cc @induprakash (#1014 (comment))