Correct deduplicate of received RF and IR signals

Regression introduced when introducing the name of the gateway into the topic
This commit is contained in:
Florian committed 2018-06-07 20:17:50 +02:00
1 parent b568e7137c
commit eb15898228
3 files changed
+3 -3

No files matched your search

+1 -1
View File
@@ -33,7 +33,7 @@
#define subjectIRtoMQTTbits Base_Topic Gateway_Name "/IRtoMQTT/bits"
#define subjectIRtoMQTTRaw Base_Topic Gateway_Name "/IRtoMQTT/raw"
// subject monitored to listen traffic processed by other gateways to store data and avoid ntuple
#define subjectMultiGTWIR "+/IRtoMQTT"
#define subjectMultiGTWIR "+/+/IRtoMQTT"
#define IRbitsKey "IRBITS_" // bits will be defined if a subject contains IRbitsKey followed by a value of 2 digits
#define IRRptKey "RPT_" // repeats will be defined if a subject contains IRRptKey followed by a value of 1 digit
#define repeatIRwMQTT false // do we repeat a received signal by using mqtt
+1 -1
View File
@@ -46,7 +46,7 @@ RF supported protocols
*/
#define RFpulselengthKey "PLSL_" // pulselength will be defined if a subject contains RFprotocolKey followed by a value of 3 digits
// subject monitored to listen traffic processed by other gateways to store data and avoid ntuple
#define subjectMultiGTWRF "+/433toMQTT"
#define subjectMultiGTWRF "+/+/433toMQTT"
//RF number of signal repetition
#define RF_EMITTER_REPEAT 20
+1 -1
View File
@@ -46,7 +46,7 @@ RF supported protocols
*/
#define RF315pulselengthKey "PLSL_" // pulselength will be defined if a subject contains RFprotocolKey followed by a value of 3 digits
// subject monitored to listen traffic processed by other gateways to store data and avoid ntuple
#define subjectMultiGTWRF315 "+/315toMQTT"
#define subjectMultiGTWRF315 "+/+/315toMQTT"
//RF number of signal repetition
#define RF315_EMITTER_REPEAT 20