Github Devices Community Docs Blog

RF2 gateway problems

Im having trouble with the RF2 gateway for my KAKU devices.

First I tested my schematic with the examples of the NewRemoteReceiver library. That works, i’m getting the expected list of info like unit, groupbit, period etc.

So after uploading the code with uncommenting the RF2 gateway, its connecting good (via serial monitor) but i’m not receiving any signal from my devices.

But when i’m uploading the code with only the RF gateway uncommented i’m getting these messages
“home/OpenMQTTGateway/433toMQTT {“value”:470412416,“protocol”:22,“length”:32,“delay”:1071}”

in both situations im getting data on the datapin of the receiver. I connected a led in parallel, it flashes when pressing my remote control.

Any idea what i’m doing wrong?

I’ve tested the 433Mhz reception in 2 different devices, Sonoff RF Bridge and Wemos ESP8266 board.

Both of them display the received code the same way you showed in the example:

For example, if the above is a motion sensor, the code you would use to integrate on automation systems (OpenHab, Hassio, etc), would be the 470412416.

That correct, but when using the RF2 code it should receive code like this:
home/OpenMQTTGateway/RF2toMQTT {"unit":0,"groupBit":0,"period":273,"address":8233228,"switchType":0}

That way I can also use this to control my KaKu devices. Now I can only receive the pressed button from the remote to start another action.

When uncommenting the RF2 gateway code i’m not receiving anything when pressing the remotebuttons.

still no solution found here, tried version 0.9.2

when RF and RF2 uncommented I receive commands from my KAKU remotes when subscribing to my MQTT broker.

Then after following
so commenting RF and reupload the code I get nothing when pressing my KAKU remote.

Is my kaku not compatible, i’m using the AYCT-102. Still the newest version of this kind remote.

No one else with the same problems?

I’m using an NodeMCU, and like mentioned before. With just the testcode from library NewRemoteReceiver its properly working.

with RF and RF2 uncommented I get this in my serial monitor

Pub json into:

instead I’m trying to get something like this so I could also transmit these messages to control my devices instead of only receiving:

And when using the newremoteswitch example are you able to control your device also or only to listen your remote?

im able to control and to listen, but the examples are not working on a esp8266, but im using it with a arduino mega. but then i’m getting this dataset (example)

only the showreceivedcode example is working on nodemcu, and this one is showing the correct data string with unit, groupbit, switchtype etc.

with RF2 it should receive the same, but im not receiving anything then…

Would it be possible to post a serial monitor extract when using RF2 please ?

im sorry, used my esp8266 for another prototype at the moment.

but i mentioned the outcome of the serial monitor before:

i’m using a newkaku remote, so its working correct with example ShowReceiveCode from NewRemoteLibrary which means I get the expected outcome which is in this format:

I try to explain my experience:

with RF and RF2 uncommented:
serial monitor output in the format of:

with RF2 uncommented i dont get any response at all, when it should be a response in the same format as with the ShowReceivedCode example

Same issue here. I’m build RF2 on ESP8266 but I receive on 433toMQTT and not in RF2toMQTT. Example are working, but not OMG.

So back to dev branch. I works only only RF2 is enable. if RF + RF2 it fails.


RF + RF 2 : Receive RF2 KO,Receive RF OK, Send RF2 OK,

If boith are un commented this is the expected behaviour:

Thanks, I have missed this point.
Where is the limitation in the code ?
RFlink or ESP with (espeasy for example) can handle both at the same time on RX.
Is it possible test if it’s a valid Kaku signal , if not fall back to rc-switch ?

This is due to the use of callbacks in both libraries. It seems that only one can be handled per pin.

I know for RFLink, but I’m curious that ESPEasy can support Kaku and other protocols at the same time. Do you have some resources to point me ?

it was the legacy version : I have not check with the new mega version.