Not able to send any RF data


#1

Hi guys,
first of all thank you for your great work. I am using the gateway in combination with Openhab and it works great!

Unfortunately I have a problem that I could not solve, although I tried different things and studied all the instructions on git.

I also checked the transmitter on a raspberry pi it it is working fine.

My board is a NodeMCU V3. Receiving a signal is no problem. My pin configuration in configRF.h is as follows:

#ifdef ESP8266
    #define RF_RECEIVER_PIN 4 // D3 on nodemcu
    #define RF_EMITTER_PIN 16 // RX on nodemcu if it doesn't work with 3, try with 4 (D2)

I also tried pin 3 (RX) but that didn´t work either.
I want to switch some plugs of different brands.If I press the button on the remote I receive the following code:

home/OpenMQTTGateway/433toMQTT
{"value":4543825,"protocol":1,"length":24,"delay":315}

I tried to send that one with the follwong command:
mosquitto_pub -t home/OpenMQTTGateway/MQTTto433 -m 4543825

but nothing happens.

This is only a received code I wanted to send but nothing happend:

home/OpenMQTTGateway/433toMQTT
{"value":5651376,"protocol":2,"length":24,"delay":724}

Is there anybody here who could give me a hint what I am doing wrong?
Thanks in advance!


#2

Hello,

Did you tried with Emitter on D2 = 4 and receiver on D3 = 0?


#3

Yes I have already tried this constellation but unfortuately then the receive command doesn´t work either.


#4

Are you using the beta? If so try version 0.8 - I ran into troubles with beta.


#5

Yes you are right, I just downloaded the repository and not the release version 🤦
I will give a try this afternoon and see if it’s works now.


#6

Also check @1technophile’s answer in my thread: RF commands not working in beta if you want the beta to be working.


#7

I got the 0.8 working now and it shows up that the commands are sent out but my plugs are not switching.

Should there be a receive log in the console (on the serial interface) after I send out the data? Is the syntax I use correct?


#8

Could you post what you get on the serial monitor?


#9

Yes, sure:

That´s the command I sent out:
mosquitto_pub -t home/OpenMQTTGateway/commands/MQTTto433 -m 6086208

Hey I got a callback 
08:08:59.940 -> MQTTtoRF dflt
Ack pub.
Hey I got a callback 
08:09:00.878 -> Storing signal
08:09:00.878 -> Min ind: 
08:09:00.878 -> 6
08:09:00.878 -> store code :
08:09:00.878 -> 6086208/185588
08:09:00.878 -> Col: val/timestamp
08:09:00.878 -> 0:4539732/114850
08:09:00.878 -> 1:128/126879
08:09:00.878 -> 2:6086208/130594
08:09:00.878 -> 3:4539729/143612
08:09:00.878 -> 4:4539729/143748
08:09:00.878 -> 5:6086208/160702
08:09:00.878 -> 6:6086208/185588
08:09:00.878 -> 7:4539729/112064
08:09:00.878 -> 8:4539743/112332
08:09:00.878 -> 9:4543839/112364
08:09:00.878 -> 10:4543839/112389
08:09:00.878 -> 11:4539732/114684
08:09:00.878 -> Data stored

Another command:
mosquitto_pub -t home/OpenMQTTGateway/commands/PLSL_724/433_2/BITS_24 -m 5841296

Hey I got a callback 
08:14:20.814 -> RF Protocol:
08:14:20.814 -> 2
08:14:20.814 -> RF Pulse Lgth:
08:14:20.814 -> 724
08:14:20.814 -> MQTTtoRF usr par.
08:14:20.814 -> 2
08:14:20.814 -> 724
08:14:20.814 -> 24
MQTTtoRF ack pub.
08:14:21.986 -> 5841296
08:14:21.986 -> Hey I got a callback 
08:14:21.986 -> Storing signal
08:14:22.033 -> Min ind: 
08:14:22.033 -> 0
08:14:22.033 -> store code :
08:14:22.033 -> 5841296/506742
08:14:22.033 -> Col: val/timestamp
08:14:22.033 -> 0:5841296/506742
08:14:22.033 -> 1:128/126879
08:14:22.033 -> 2:6086208/130594
08:14:22.033 -> 3:4539729/143612
08:14:22.033 -> 4:4539729/143748
08:14:22.033 -> 5:6086208/160702
08:14:22.033 -> 6:6086208/185588
08:14:22.033 -> 7:2/335595
08:14:22.033 -> 8:6086208/458382
08:14:22.033 -> 9:6086208/458628
08:14:22.033 -> 10:5841296/485648
08:14:22.033 -> 11:5841296/494965
08:14:22.033 -> Data stored

In both cases the plugs do not switch.


#10

Are there only certain protocols available? Or should resending the received signal work (like in Pilight raw)?
Maybe that is the reason why the plugs not switch.


#11

When you listen your remote control signal did you get only one code or severals?


#12

On MQTT only one. In the serial monitor it looks similar to send message I have posted.
This is what it shows on serial monitor:

Rcv. RF
21:02:51.822 -> isAduplicate?
21:02:51.822 -> Adv data RFtoMQTT
21:02:51.822 -> Sending RFtoMQTT
21:02:51.822 -> 5982064
21:02:51.822 -> RFtoMQTT OK
Hey I got a callback 
21:02:51.869 -> Storing signal
21:02:51.869 -> Min ind: 
21:02:51.869 -> 3
21:02:51.869 -> store code :
21:02:51.869 -> 5982064/46894
21:02:51.869 -> Col: val/timestamp
21:02:51.869 -> 0:5440560/32668
21:02:51.869 -> 1:5774752/35696
21:02:51.869 -> 2:5774752/35961
21:02:51.869 -> 3:5982064/46894
21:02:51.869 -> 4:0/0
21:02:51.869 -> 5:0/0
21:02:51.869 -> 6:0/0
21:02:51.869 -> 7:0/0
21:02:51.869 -> 8:0/0
21:02:51.869 -> 9:0/0
21:02:51.869 -> 10:0/0
21:02:51.869 -> 11:0/0
21:02:51.869 -> Data stored
21:02:51.869 -> Rcv. RF
21:02:51.869 -> isAduplicate?
21:02:51.869 -> --don't pub. duplicate--
Rcv. RF
21:02:51.915 -> isAduplicate?
21:02:51.915 -> --don't pub. duplicate--

#13

Did you tried these different messages:
5440560
5774752
5774752
5982064


#14

No but I can try this tomorrow. Thanks in advance for you help.
Do you have an explanation what the values mean after the /?

One short OT question: Which channel do I have to subscribe if I want to get data from a DHT sensor? I uncommented the DHT sensor and plugged it to the NodeMcu but do not see any data.


#15

yes this is the time of reception from omg start.

you have to uncomment zsensordht, verify the pins & dht model in config_DHT.h, and if you subscribe to :
mosquitto_sub -t +/# -v
you should see the values.