RF AND Pilight together #450

wimpie007 · 2019-08-31T10:56:25Z

as it seems impossible to use the RF (gatewayRF) and Pilight (gatewayPilight) togther on 1 device, any chance that it would work in the future?
(combining those 2 libraries would be great... i now have devices that work with RF, but not with pilight, and the other way around)
Thanks for openmqqtGW!

odis68 · 2019-09-12T08:20:37Z

I have the same problem. I bought a temperature sensor from a list of compatible devices. and now I can not see the motion sensors and remotes. I have to choose !!! what to use is extremely uncomfortable. Thanks for your work!!!!!

akasma74 · 2019-09-12T08:34:10Z

I'm in a similar situation - some of my 433 MHz devices are supported by Pilight, but others are not, and I asked a similar question in the past.
Apparently the author hopes for Pilight to extend support of RF devices so it covers gatewayRF AND adds some extra (hence this issue is kind of doomed to be closed as "won't happen").
However, at the moment it's far from that and it's unclear how to get there as adding support for new devices in Pilight is not trivial and requires time.
Also, I personally yet to find out how to control my 433 MHz devices (wall switches, for example) using Pilight - it's much harder that using RF, or I just don't know how (and there is no comprehensive documentation on the subject).

Anyway, currently because of that and coverage issues I run one OMG with Pilight on one floor of my house and one OMG with RF on the other. They work ok together.

1technophile · 2019-09-12T19:46:26Z

I understand the issue, I have worked to add gs-wds07 to Pilight and now it is done, I need to integrate more devices. But it is a lot of work...
Currently I'm focusing on BLE but more devices into Pilight is on my TODO

akasma74 · 2019-09-12T20:10:53Z

As I pointed out above, it's a slow process because requires plenty of time and knowledge (and because there is no way to simply "transfer" support for devices from RF to Pilight) and currently it mainly relies on the author of OMG.
Therefore it is crucial to the project's success to have a) more people willing to donate their time and b) clear instructions how to add support for new devices to OMG Pilight.

I'm happy to do my bit as still have some 433MHz devices that are supported by OMG RF only.

odis68 · 2019-11-08T08:49:27Z

Have an idea, maybe not a new one. RF and on different Pilight receivers. Use two independent receivers on different GPIO channels. please consider this opportunity.

odis68 · 2019-12-02T14:43:08Z

Please comment on my previous post !!!

1technophile · 2019-12-02T18:07:48Z

Have an idea, maybe not a new one. RF and on different Pilight receivers. Use two independent receivers on different GPIO channels. please consider this opportunity.

Why not, it should be tested to confirm

1technophile · 2019-12-02T18:10:01Z

As I pointed out above, it's a slow process because requires plenty of time and knowledge (and because there is no way to simply "transfer" support for devices from RF to Pilight) and currently it mainly relies on the author of OMG.
Therefore it is crucial to the project's success to have a) more people willing to donate their time and b) clear instructions how to add support for new devices to OMG Pilight.
I'm happy to do my bit as still have some 433MHz devices that are supported by OMG RF only.

Indeed adding a protocol to Pilight was a long process, I'm going to see also as an alternative if I can add easily protocols to rcswitch, if yes I will document it.

stale · 2020-01-31T18:57:43Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

odis68 · 2020-02-03T13:06:35Z

The problem is not outdated !!! We are patiently waiting !!!

1technophile · 2020-02-03T20:33:56Z

The problem is not outdated !!! We are patiently waiting !!!

Thanks for your patience, I keep that in mind

stale · 2020-04-03T21:10:29Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

cyraxxx · 2020-12-09T15:20:54Z

Hi, did someone actually test @odis68 's idea? If not, I can try it (adding 2 receivers and test on an ESP32), but I am not a programmer. Now my setup is using Pilight. If I modify config_RF.h (adding RF_RECEIVER_GPIO2) and ZgatewayRF.ino to use RF_RECEIVER_GPIO2 then enable ZgatewayRF and ZgatewayPilight, is it worth a shot or do I need to do much more then this?

iWildStyle · 2021-03-06T21:07:34Z

Faced a problem - RF and Pilight do not work at the same time. They do not work, since the libraries use attachInterrupt to the same pin, which cannot be done.
I did the following - instead of installing a second receiver, I divided the data line from the receiver into two input pins D8 and D7
Then I split the config_RF.h configuration file into two (config_Pilight.h) and in the second I brought out all the settings for Pilight.
Also changed the settings a bit in ZgatewayPilight.ino and main.ino and voila:

N: Subject: / PilighttoMQTT
N: Received json: {"message": {"id": 86, "channel": 1, "battery": 1, "temperature": 18.0, "humidity": 41}, "protocol": "nexus", "length": "86", "value": "86", "repeats": 2, "status": 2}
N: Subject: / 433toMQTT
N: Received json: {"value": 15145729, "protocol": 1, "length": 24, "delay": 391}

the first object is processed by Pilight, the second is processed by RF
PS: I have Wemos D1 mini module and cheap RX470B 433 receiver

melyux · 2021-11-29T10:46:58Z

@iWildStyle Would you share all the code/settings you changed to get this to work? Specifically ZgatewayPilight.ino and main.ino? And why splitting config_RF.h was necessary?

melyux · 2021-11-30T07:46:10Z

I too made modifications that let me run both Pilight and RF together on my Wemos D1 mini as well, but when I connect the 433MHz receiver's DATA pin to two separate pins on the Wemos (D7 and D8, like @iWildStyle suggested), I stop receiving data on both. As soon as I make it so the receiver's DATA pin only has contact with one pin on the Wemos, I start receiving signals again.

Software-wise, it should work, but I'm at a loss.

I divided the data line from the receiver into two input pins D8 and D7

How exactly did you do this?

melyux · 2021-12-01T09:39:20Z

I got it to work! This is incredible! Both Pilight and RF (RCSwitch) working at the same time using a single receiver. For some reason pins D3, D4, and (maybe) D8 didn't work and would simply smother the data. I tried pins D6 and D5 and they both worked. So seems you can use D5, D6, and D7 for the receiver inputs at the same time, but not D3 or D4...

So in summation, I modified the code to allow the RF and Pilight modules to not be mutually exclusive (pretty trivial, including splitting the RF_RECEIVER_GPIO into multiple variables so you can assign a separate GPIO input for RF and Pilight, since like @iWildStyle said, you can't do attachInterrupt() to the same pin twice), and then simply connected the DATA pin of my 433MHz receiver to both D5 (or D6) and D7 of the Wemos D1 mini. And it works!

I didn't try D8 (I use it for my transmitter) or D0 or D1 (I use it for another sensor) or D2 (I use it for another sensor). But D3 and D4 definitely don't work for some reason.

I didn't try with anything other than Wemos D1 mini since I don't own anything else, so I can't test it for other microcontrollers. I can provide the code and maybe we can get a pull request going. Essentially I replaced a switch statement with multiple if statements so you can have both RF and Pilight going at the same time, split the RF GPIO variable like I mentioned above, and changed the Active Receiver Module from an integer to a bitmask so it can be ORed together to indicate multiple RF gateways running simultaneously. I also haven't tried doing the new on-the-fly gateway switching, though it should work if you provide it a bitmask integer instead of the old plain integer.

I'm going to try getting RF2 to work too, but I don't have any KAKU devices to test that with. But seems like there's some more complex thing that won't let RF and RF2 work together according to the docs (?), so I don't know if that'd work. But you can probably also run RF2 and Pilight at the same time too just like this.

Given how difficult it is to add new protocols to both RCswitch and Pilight though, I really think the future is with RTL_433 for 433MHz stuff. I need to get my hands on one of those builds.

@1technophile

melyux · 2021-12-02T06:27:26Z

This is my code patch for now:

diff --git a/main/ZgatewayPilight.ino b/main/ZgatewayPilight.ino
index a998376..1ec491b 100644
--- a/main/ZgatewayPilight.ino
+++ b/main/ZgatewayPilight.ino
@@ -85,10 +85,10 @@ void setupPilight() {
   ELECHOUSE_cc1101.SetRx(CC1101_FREQUENCY);
 #  endif
   rf.setCallback(pilightCallback);
-  rf.initReceiver(RF_RECEIVER_GPIO);
+  rf.initReceiver(RF_PILIGHT_RECEIVER_GPIO);
   pinMode(RF_EMITTER_GPIO, OUTPUT); // Set this here, because if this is the RX pin it was reset to INPUT by Serial.end();
   Log.notice(F("RF_EMITTER_GPIO: %d " CR), RF_EMITTER_GPIO);
-  Log.notice(F("RF_RECEIVER_GPIO: %d " CR), RF_RECEIVER_GPIO);
+  Log.notice(F("RF_PILIGHT_RECEIVER_GPIO: %d " CR), RF_PILIGHT_RECEIVER_GPIO);
   Log.trace(F("ZgatewayPilight command topic: %s%s%s" CR), mqtt_topic, gateway_name, subjectMQTTtoPilight);
   Log.trace(F("ZgatewayPilight setup done " CR));
 }
@@ -224,7 +224,7 @@ extern void enablePilightReceive() {
   ELECHOUSE_cc1101.SetRx(receiveMhz); // set Receive on
 #  endif
   rf.setCallback(pilightCallback);
-  rf.initReceiver(RF_RECEIVER_GPIO);
+  rf.initReceiver(RF_PILIGHT_RECEIVER_GPIO);
   pinMode(RF_EMITTER_GPIO, OUTPUT); // Set this here, because if this is the RX pin it was reset to INPUT by Serial.end();
 };
 #endif
diff --git a/main/ZgatewayRF.ino b/main/ZgatewayRF.ino
index a4e8fae..93e638c 100644
--- a/main/ZgatewayRF.ino
+++ b/main/ZgatewayRF.ino
@@ -109,7 +109,7 @@ void RFtoMQTTdiscovery(SIGNAL_SIZE_UL_ULL MQTTvalue) {
 void setupRF() {
   //RF init parameters
   Log.notice(F("RF_EMITTER_GPIO: %d " CR), RF_EMITTER_GPIO);
-  Log.notice(F("RF_RECEIVER_GPIO: %d " CR), RF_RECEIVER_GPIO);
+  Log.notice(F("RF_RF_RECEIVER_GPIO: %d " CR), RF_RF_RECEIVER_GPIO);
 #  ifdef ZradioCC1101 //receiving with CC1101
   ELECHOUSE_cc1101.Init();
   ELECHOUSE_cc1101.SetRx(receiveMhz);
@@ -120,7 +120,7 @@ void setupRF() {
   mySwitch.enableTransmit(RF_EMITTER_GPIO);
 #  endif
   mySwitch.setRepeatTransmit(RF_EMITTER_REPEAT);
-  mySwitch.enableReceive(RF_RECEIVER_GPIO);
+  mySwitch.enableReceive(RF_RF_RECEIVER_GPIO);
   Log.trace(F("ZgatewayRF command topic: %s%s%s" CR), mqtt_topic, gateway_name, subjectMQTTtoRF);
   Log.trace(F("ZgatewayRF setup done" CR));
 }
@@ -235,7 +235,7 @@ void MQTTtoRF(char* topicOri, char* datacallback) {
 #    ifdef ZradioCC1101 // set Receive on and Transmitt off
   ELECHOUSE_cc1101.SetRx(receiveMhz);
   mySwitch.disableTransmit();
-  mySwitch.enableReceive(RF_RECEIVER_GPIO);
+  mySwitch.enableReceive(RF_RF_RECEIVER_GPIO);
 #    endif
 }
 #  endif
@@ -329,7 +329,7 @@ void enableRFReceive() {
   ELECHOUSE_cc1101.SetRx(receiveMhz);
 #  endif
   mySwitch.disableTransmit();
-  receiveInterupt = RF_RECEIVER_GPIO;
-  mySwitch.enableReceive(RF_RECEIVER_GPIO);
+  receiveInterupt = RF_RF_RECEIVER_GPIO;
+  mySwitch.enableReceive(RF_RF_RECEIVER_GPIO);
 }
 #endif
diff --git a/main/ZgatewayRF2.ino b/main/ZgatewayRF2.ino
index aadab47..6e82048 100644
--- a/main/ZgatewayRF2.ino
+++ b/main/ZgatewayRF2.ino
@@ -61,9 +61,9 @@ void setupRF2() {
   ELECHOUSE_cc1101.setMHZ(receiveMhz);
   ELECHOUSE_cc1101.SetRx(receiveMhz);
 #  endif
-  NewRemoteReceiver::init(RF_RECEIVER_GPIO, 2, rf2Callback);
+  NewRemoteReceiver::init(RF_RF2_RECEIVER_GPIO, 2, rf2Callback);
   Log.notice(F("RF_EMITTER_GPIO: %d " CR), RF_EMITTER_GPIO);
-  Log.notice(F("RF_RECEIVER_GPIO: %d " CR), RF_RECEIVER_GPIO);
+  Log.notice(F("RF_RF2_RECEIVER_GPIO: %d " CR), RF_RF2_RECEIVER_GPIO);
   Log.trace(F("ZgatewayRF2 command topic: %s%s%s" CR), mqtt_topic, gateway_name, subjectMQTTtoRF2);
   Log.trace(F("ZgatewayRF2 setup done " CR));
   pinMode(RF_EMITTER_GPIO, OUTPUT);
@@ -357,7 +357,7 @@ void enableRF2Receive() {
   disableRFReceive();
 #  endif
 
-  NewRemoteReceiver::init(RF_RECEIVER_GPIO, 2, rf2Callback);
+  NewRemoteReceiver::init(RF_RF2_RECEIVER_GPIO, 2, rf2Callback);
 #  ifdef ZradioCC1101
   ELECHOUSE_cc1101.SetRx(receiveMhz); // set Receive on
 #  endif
diff --git a/main/ZgatewayRTL_433.ino b/main/ZgatewayRTL_433.ino
index 907a817..e50edbe 100644
--- a/main/ZgatewayRTL_433.ino
+++ b/main/ZgatewayRTL_433.ino
@@ -68,7 +68,7 @@ void rtl_433_Callback(char* message) {
 }
 
 void setupRTL_433() {
-  rtl_433.initReceiver(RF_RECEIVER_GPIO, receiveMhz);
+  rtl_433.initReceiver(RF_RTL_433_RECEIVER_GPIO, receiveMhz);
   rtl_433.setCallback(rtl_433_Callback, messageBuffer, JSON_MSG_BUFFER);
   Log.trace(F("ZgatewayRTL_433 command topic: %s%s%s" CR), mqtt_topic, gateway_name, subjectMQTTtoRTL_433);
   Log.notice(F("ZgatewayRTL_433 setup done " CR));
@@ -102,7 +102,7 @@ extern void MQTTtoRTL_433(char* topicOri, JsonObject& RTLdata) {
       int debug = RTLdata["debug"] | -1;
       Log.notice(F("RTL_433 set debug: %d" CR), debug);
       rtl_433.setDebug(debug);
-      rtl_433.initReceiver(RF_RECEIVER_GPIO, receiveMhz);
+      rtl_433.initReceiver(RF_RTL_433_RECEIVER_GPIO, receiveMhz);
       success = true;
     }
     if (RTLdata.containsKey("status")) {
@@ -132,7 +132,7 @@ extern void enableRTLreceive() {
   disablePilightReceive();
 #  endif
   ELECHOUSE_cc1101.SetRx(receiveMhz); // set Receive on
-  rtl_433.enableReceiver(RF_RECEIVER_GPIO);
+  rtl_433.enableReceiver(RF_RTL_433_RECEIVER_GPIO);
   pinMode(RF_EMITTER_GPIO, OUTPUT); // Set this here, because if this is the RX pin it was reset to INPUT by Serial.end();
 }
 
diff --git a/main/config_RF.h b/main/config_RF.h
index e088a5d..ba77414 100644
--- a/main/config_RF.h
+++ b/main/config_RF.h
@@ -122,15 +122,48 @@ float receiveMhz = CC1101_FREQUENCY;
 #endif
 
 /*-------------------PIN DEFINITIONS----------------------*/
-#ifndef RF_RECEIVER_GPIO
+#ifndef RF_PILIGHT_RECEIVER_GPIO
 #  ifdef ESP8266
-#    define RF_RECEIVER_GPIO 0 // D3 on nodemcu // put 4 with rf bridge direct mod
+#    define RF_PILIGHT_RECEIVER_GPIO 0 // D3 on nodemcu // put 4 with rf bridge direct mod
 #  elif ESP32
-#    define RF_RECEIVER_GPIO 27 // D27 on DOIT ESP32
+#    define RF_PILIGHT_RECEIVER_GPIO 27 // D27 on DOIT ESP32
 #  elif __AVR_ATmega2560__
-#    define RF_RECEIVER_GPIO 1 //1 = D3 on mega
+#    define RF_PILIGHT_RECEIVER_GPIO 1 //1 = D3 on mega
 #  else
-#    define RF_RECEIVER_GPIO 1 //1 = D3 on arduino
+#    define RF_PILIGHT_RECEIVER_GPIO 1 //1 = D3 on arduino
+#  endif
+#endif
+#ifndef RF_RF_RECEIVER_GPIO
+#  ifdef ESP8266
+#    define RF_RF_RECEIVER_GPIO 0
+#  elif ESP32
+#    define RF_RF_RECEIVER_GPIO 0
+#  elif __AVR_ATmega2560__
+#    define RF_RF_RECEIVER_GPIO 0
+#  else
+#    define RF_RF_RECEIVER_GPIO 0
+#  endif
+#endif
+#ifndef RF_RF2_RECEIVER_GPIO
+#  ifdef ESP8266
+#    define RF_RF2_RECEIVER_GPIO 0
+#  elif ESP32
+#    define RF_RF2_RECEIVER_GPIO 0
+#  elif __AVR_ATmega2560__
+#    define RF_RF2_RECEIVER_GPIO 0
+#  else
+#    define RF_RF2_RECEIVER_GPIO 0
+#  endif
+#endif
+#ifndef RF_RTL_433_RECEIVER_GPIO
+#  ifdef ESP8266
+#    define RF_RTL_433_RECEIVER_GPIO 0
+#  elif ESP32
+#    define RF_RTL_433_RECEIVER_GPIO 0
+#  elif __AVR_ATmega2560__
+#    define RF_RTL_433_RECEIVER_GPIO 0
+#  else
+#    define RF_RTL_433_RECEIVER_GPIO 0
 #  endif
 #endif
 
@@ -153,15 +186,15 @@ float receiveMhz = CC1101_FREQUENCY;
  * Active Receiver Module
  * 1 = ZgatewayPilight
  * 2 = ZgatewayRF
- * 3 = ZgatewayRTL_433
- * 4 = ZgatewayRF2
+ * 4 = ZgatewayRTL_433
+ * 8 = ZgatewayRF2
  */
 int activeReceiver = 0;
 #  define ACTIVE_RECERROR 0
 #  define ACTIVE_PILIGHT  1
 #  define ACTIVE_RF       2
-#  define ACTIVE_RTL      3
-#  define ACTIVE_RF2      4
+#  define ACTIVE_RTL      4
+#  define ACTIVE_RF2      8
 
 #  ifdef ZradioCC1101
 bool validFrequency(float mhz) {
@@ -207,32 +240,22 @@ void enableActiveReceiver(bool isBoot) {
 
   // if (currentReceiver != activeReceiver) {
   Log.trace(F("enableActiveReceiver: %d" CR), activeReceiver);
-  switch (activeReceiver) {
 #  ifdef ZgatewayPilight
-    case ACTIVE_PILIGHT:
-      enablePilightReceive();
-      break;
+  if ((activeReceiver & ACTIVE_PILIGHT) == ACTIVE_PILIGHT)
+    enablePilightReceive();
 #  endif
 #  ifdef ZgatewayRF
-    case ACTIVE_RF:
-      enableRFReceive();
-      break;
+  if ((activeReceiver & ACTIVE_RF) == ACTIVE_RF)
+    enableRFReceive();
 #  endif
 #  ifdef ZgatewayRTL_433
-    case ACTIVE_RTL:
-      enableRTLreceive();
-      break;
+  if ((activeReceiver & ACTIVE_RTL) == ACTIVE_RTL)
+    enableRTLreceive();
 #  endif
 #  ifdef ZgatewayRF2
-    case ACTIVE_RF2:
-      enableRF2Receive();
-      break;
+  if ((activeReceiver & ACTIVE_RF2) == ACTIVE_RF2)
+    enableRF2Receive();
 #  endif
-#  ifndef ARDUINO_AVR_UNO // Space issues with the UNO
-    default:
-      Log.error(F("ERROR: unsupported receiver %d" CR), activeReceiver);
-#  endif
-  }
   currentReceiver = activeReceiver;
 }
 #endif

NorthernMan54 · 2021-12-04T01:36:22Z

Would this potentially cause resource contention from having too many interrupts contending for cpu resources?

Pro Tip - For testing of RF2/KAKU, I used a ESP32 connected to a CC1101 as a transmitter with the RF2 module enabled. And had it transmit KAKU signals for testing the receive function. Seemed to work pretty well.

melyux · 2022-02-23T10:35:00Z

I noticed my code isn't complete for the "active receiver" thing despite me converting it into a bitmask; there is still code in main.ino that treats it as a simple integer, and MQTT still shows actRec as showing only Pilight even though both RF and Pilight are in fact working together perfectly without missing anything. Now that I look at it, enablePilightReceive() calls disableRFReceive so I don't get how I got it working in the first place...

But it is working flawlessly somehow on my ESP8266. I'll try to clean up the code. @1technophile Are you interested in getting this merged somehow?

1technophile · 2022-02-23T22:56:32Z

@melyux yes of course !

piano-thomas · 2023-01-19T21:45:16Z

@melyux would you be able to share your ZgatewayPilight.ino file for making both Pilight and RF (RC-switch) work? I'm trying to get the same result, but since I have little experience I'm having a hard time in easily replacing my code with yours.

melyux · 2023-01-19T22:23:51Z

@piano-thomas I'm creating a pull request to enable multi-gateway support in the next few days (hopefully). I'm updating the code to work with latest master, but the ZGatewayPilight.ino changes in the patch I posted above should still be working

melyux · 2023-01-19T22:26:29Z

Code doesn't seem to work with RTL433 (I think the CC1101 just doesn't support multiple gateways because it's a single device over SPI and can't do multiple interrupts and you can't attach the receiver pin to multiple pins on the ESP like you can with the regular 433MHz receivers; I tried it and it didn't work), so I'm working on excluding it and just having RF and Pilight working together (and probably RF2, but don't have any RF2 devices to test with)

piano-thomas · 2023-01-20T16:14:09Z

updating

@melyux that would be great! The only thing I am struggling with is implement the ZGatewayPilight.ino changes in the patch. I'm lacking a lot of experience and experimenting with everything, couldn't figure out how to use the git diff feature to create a custom .ino file. Changing everything by hand will for sure cause errors ;)..

rinie · 2024-02-17T09:21:50Z

I have a rough Lilygo working with the other RF libraries…

[“LilyGo_SSD1306”,“WebUI”,“RF”,“RF2”,“Pilight”,“rtl_433”]

github.com
GitHub - rinie/OpenMQTTGateway at ZradioSX127x
ZradioSX127x

I isolated the decoding of the libraries from the receiving by RTL_433_ESP…
As the other libs assume direct OOK signal on input pins, and SX127x must be initialized...
Now struggling to get transmitting to work?..

NorthernMan54 · 2024-02-17T11:53:02Z

Fyi - rtl_433_esp and pilight libraries have conflicting names and can not be used together

rinie · 2024-02-17T12:09:18Z

Fyi - rtl_433_esp and pilight libraries have conflicting names and can not be used together

https://github.com/rinie/ESPiLight/tree/ZradioSX127x
And
https://github.com/rinie/rtl_433_ESP/tree/ZradioSX127x
And
https://github.com/rinie/OpenMQTTGateway/tree/ZradioSX127x
And
https://github.com/rinie/NewRemoteSwitch/tree/ZradioSX127x
And
https://github.com/rinie/rc-switch/tree/ZradioSX127x

I modified this to fix that.
Difficult to get EspPiLight compling...
Replaced interrupt handlers/direct IO in the none RTL_433 libs and added decodePulseGapDurationCallback...

If you have any clues to get transmitting working?...

NorthernMan54 · 2024-02-17T12:26:20Z

I never looked at the transmit capability of the sx127x chipset, but you need to find a mode where a pin can control the transmitter output. Similar to direct mode I use for receiving signals

also the common rf functions should be placed into commonRF ( I’m not sure if you did this as I’m on mobile)

rinie · 2024-02-18T07:21:37Z

I thought DIO2 could be used for Transmit as for Receiving...
For now I added this to your rtl_433_ESP as that does the actual receiving. Just using the decoding of the other modules...
RFLINK32 seems to support transmit, but I get no output.
https://github.com/SevenW/embapps/blob/master/ArduinoRFM69/rfm69-RF12demo-ook-TX/rfm69-RF12demo-ook-TX.ino uses packetmode/FIFO timing ...

gerashk · 2024-05-10T18:48:03Z

I have a rough Lilygo working with the other RF libraries…

[“LilyGo_SSD1306”,“WebUI”,“RF”,“RF2”,“Pilight”,“rtl_433”]

github.com GitHub - rinie/OpenMQTTGateway at ZradioSX127x ZradioSX127x

I isolated the decoding of the libraries from the receiving by RTL_433_ESP… As the other libs assume direct OOK signal on input pins, and SX127x must be initialized... Now struggling to get transmitting to work?..

I tried to run your code. but for some reason I got an error

"Compilation error: declaration of template parameter 'T' shadows template parameter"

github-actions · 2024-08-09T00:48:35Z

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

github-actions · 2024-08-24T00:48:31Z

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

melyux · 2024-12-11T11:06:02Z

I made a draft PR where I share my code for how I implemented RF and Pilight together, simply by enabling both of them at once: #2130

rinie · 2024-12-11T12:22:10Z

But you still need 2 receivers instead of using 1 for different purposes? Op wo 11 dec 2024 om 12:06 schreef melyux ***@***.***>:

…

I made a draft PR where I share my code for how I implemented RF and Pilight together, simply by enabling both of them at once: #2130 <#2130> — Reply to this email directly, view it on GitHub <#450 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABK33OTZTUFBX5IKAU7UQT2FAMDFAVCNFSM4ISTK5Z2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENJTGU2TIMRSGQ4Q> . You are receiving this because you commented.Message ID: ***@***.***>

-- Met vriendelijke groeten, Rinie Kervel. Don't walk behind me, I may not lead. Don't walk in front of me, I may not follow. Just walk beside me and be my friend.

melyux · 2024-12-11T19:44:32Z

I use a single receiver, but its data pin is connected to multiple pins on the ESP, as @iWildStyle talked about above.

rinie · 2024-12-12T07:06:12Z

Ok, but would it not make sense to do that in software instead of hardware. 1 Physical receiver using 2 or more RF decoders? Op wo 11 dec 2024 om 20:44 schreef melyux ***@***.***>:

…

I use a single receiver, but its data pin is connected to multiple pins on the ESP, as @iWildStyle <https://github.com/iWildStyle> talked about above. — Reply to this email directly, view it on GitHub <#450 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABK33JNCAE5PJB2SM7ADML2FCI3PAVCNFSM4ISTK5Z2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENJTGY4TMNBUHA4A> . You are receiving this because you commented.Message ID: ***@***.***>

-- Met vriendelijke groeten, Rinie Kervel. Don't walk behind me, I may not lead. Don't walk in front of me, I may not follow. Just walk beside me and be my friend.

melyux · 2024-12-12T09:23:53Z

It is a single receiver. But you have to attach its DATA pin to multiple pins on the ESP because the ESP uses hardware interrupts per-pin, and OMG uses those hardware interrupts. Just add a second DuPont cable to another pin, that's it

stale bot added the wontfix label Jan 31, 2020

stale bot removed the wontfix label Feb 3, 2020

stale bot added the wontfix label Apr 3, 2020

stale bot closed this as completed Apr 11, 2020

NorthernMan54 reopened this Feb 17, 2024

stale bot removed the wontfix label Feb 17, 2024

github-actions bot added the stale label Aug 9, 2024

github-actions bot closed this as completed Aug 24, 2024

melyux mentioned this issue Dec 11, 2024

Allow multiple RF modules simulatenously #2130

Draft

3 tasks

RF AND Pilight together #450

RF AND Pilight together #450

Comments

wimpie007 commented Aug 31, 2019

odis68 commented Sep 12, 2019

akasma74 commented Sep 12, 2019

1technophile commented Sep 12, 2019

akasma74 commented Sep 12, 2019

odis68 commented Nov 8, 2019

odis68 commented Dec 2, 2019

1technophile commented Dec 2, 2019

1technophile commented Dec 2, 2019

stale bot commented Jan 31, 2020

odis68 commented Feb 3, 2020

1technophile commented Feb 3, 2020

stale bot commented Apr 3, 2020

cyraxxx commented Dec 9, 2020

iWildStyle commented Mar 6, 2021 • edited Loading

melyux commented Nov 29, 2021 • edited Loading

melyux commented Nov 30, 2021

melyux commented Dec 1, 2021 • edited Loading

melyux commented Dec 2, 2021

NorthernMan54 commented Dec 4, 2021

melyux commented Feb 23, 2022 • edited Loading

1technophile commented Feb 23, 2022

piano-thomas commented Jan 19, 2023

melyux commented Jan 19, 2023

melyux commented Jan 19, 2023

piano-thomas commented Jan 20, 2023

rinie commented Feb 17, 2024 • edited Loading

NorthernMan54 commented Feb 17, 2024

rinie commented Feb 17, 2024 • edited Loading

NorthernMan54 commented Feb 17, 2024 • edited Loading

rinie commented Feb 18, 2024

gerashk commented May 10, 2024

github-actions bot commented Aug 9, 2024

github-actions bot commented Aug 24, 2024

melyux commented Dec 11, 2024

rinie commented Dec 11, 2024 via email

melyux commented Dec 11, 2024

rinie commented Dec 12, 2024 via email

melyux commented Dec 12, 2024 • edited Loading

iWildStyle commented Mar 6, 2021 •

edited

Loading

melyux commented Nov 29, 2021 •

edited

Loading

melyux commented Dec 1, 2021 •

edited

Loading

melyux commented Feb 23, 2022 •

edited

Loading

rinie commented Feb 17, 2024 •

edited

Loading

rinie commented Feb 17, 2024 •

edited

Loading

NorthernMan54 commented Feb 17, 2024 •

edited

Loading

melyux commented Dec 12, 2024 •

edited

Loading