Another Board Layout RF Bridge

[michaelmassee]

Today i get my "new" Bridge, successfully flashed with help of the good work here. Thanks for that.

I want to share my experience

What i did differnt from the description:

1. The Box is Screwed together.

2. To get to the Switch, just bend slightly the large Led on the Top

3. Then Flash it from Bottom Side

regards

[tedsluis]

I promised to let you guys know how it goes. I managed to get it working!

I tried other flash tools (Arduino, esptool and espeasy), several Sonoff Tasmota firmware versions and several configuration without luck. In all cases it looked like the RF bridge was successfully flashed (without errors), but I could not connect to it via WIFI. Believe me, I was getting more and more frustrated every day ;-)

As a last attempt I did cut the copper traces, as explained in the wiki, and powered the RF bridge using the micro USB during flashing, but that also did not worked out. (I have two Sonoff RF bridges, so I dared to do this experiment.)

At some point I read a dutch blog post about an Sonoff RF bridge on flash voltage (3v3 or 5v). This guy also was not able to flash his RF bridge with a CH340G based USB serial adapter. He switched from 3v3 to 5v (against all recommendations) and it worked (at least for him). He reported that with 5v the green LED was much brighter.

I had high hopes, because his serial CH340G USB adapter looked like mine. Unfortunately his solution did not work for me.

Something that I kept thinking about was that his green LED was bright and mine was not. May be my serial USB adapter is the cause of the issue.

This afternoon I tried another CH340G based USB serial adapter and the LED shine bright and it immediately worked! It tried my VSCode with PlatformIO setup, as well as my Arduino setup and my esptool setup. They all worked! Even my second modified RF bridge (on which I did cut the copper traces) now works ;-)

Below my CH340G based serial USB adapters. The upper one (SDS011_USB2TTL_004) works for both the Sonoff RF bridge and other Sonoff devices.

The lower one (HW-597) does not work with the RF bridge, but I am still able to flash other Sonoff devices (like the Basic, S26 and the Pow R2) with this adapter.

Thank you everybody for all your tips and support. It helped me trying new tools, but most of all: excluding possible causes! Very useful! Thanks a lot!

edit: How did I noticed that flashing was successful? Immediately after flashing, with the serial cable still connected and before I set the switch to ON, the blue WIFI LED on the board started flashing.

[LucReynders]

With the standard Tasmota flash the RFBridge is limited in detecting codes. After flashing the standard Tasmota package you can upgrade the bridge with Portisch software. This can be done via the console (but first you need to connect the extra wires to the board

• IO5<->C2CK and IO4<->C2D as explained in the previous discussions for the R2.). For the upgrade you need first to download the portisch hex file. https://github.com/arendst/Sonoff-Tasmota/tree/development/tools/fw_efm8bb1. In the console you can then "flash" upgrade by selecting this file.

After the portisch upgrade I was able to sniff remote codes from Chacon and my Novy cooker hood with the Rfraw 177 command. The sniffed B1 commands need to be converted to B0 first as explained in github before sending these over the bridge (with bitbucketconverter tool).

[antocorr]

Hi guys, First of all thanks for all the support and the great work. I want to start with what always works for me when flashing sonoff's esp8255/66 that's not covered in any guide.

1. Avoid connecting 3.3v between the programmer and the sonoff (bridge, basic, dual). Try always to get external power. I used a Breadboard power adapter.
2. Share the grounds. I tried different setups, but what always works for me is to share GND between the sonoff, the breadboard adapter and the FTDI adapter.

Now unfortunately all the remotes I used with ewelink, are not working with Tasmota. The console sniffs the code but pairing fails always. IDK if I should upgrade the RF chip with Portisch firmware, because as I said everything was fine with ewelink. Has someone had the same problem?

[sndipz]

I have successfully flashed my R2 V1.0 without resoldering/cuttiing traces, but the bridge is not receiving any signals from my RF devices. The switch is definitely set back to the on position, still nothing. Anyone have a similar problem?

Hi, I am facing same issue. Have you figured out an alternate?

[TurboTronix]

I flashed everything as described, I did manage to get the codes but not to send them. I am now trying to reflash the hex file but keep getting: error "Magic byte is not 0xE9"

Update: So it upgraded finally but now I get the following when I type RfRaw 255

00:29:00 MQT: stat/RF_Bridge/RESULT = {"RfRaw":"ON"}
00:29:00 MQT: tele/RF_Bridge/RESULT = {"RfRaw":{"Data":"AA0355"}}
00:29:00 MQT: tele/RF_Bridge/RESULT = {"RfRaw":{"Data":"AAA055"}}

Also how do I send commands? I type this:

RfRaw 0
then I get
`00:31:28 MQT: stat/RF_Bridge/RESULT = {"RfRaw":"OFF"}`

Then I type:
`RfRaw AAB023040401FE04CE016834B20B091A0918091A0918091A1A1818181818181809090909090955`

The code was derived using **bitbuckedconverter.py -f console.txt**

Am I missing something??

[LucReynders]

"After the portisch upgrade I was able to sniff remote codes from Chacon and my Novy cooker hood with the Rfraw 177 command. The sniffed B1 commands need to be converted to B0 first as explained in github before sending these over the bridge (with bitbucketconverter tool)."

• Use cmd rfraw 177
• send codes with the remote
• the bridge will "sniff" the B1 codes send, the sniffed may be different
• select the best matching code
• use the bitbuckedconv for this code
• send the B0 code to the bridge as a payload

[Freestila]

Hello, i hope it is ok that i post in this "closed" issue. I have flashed my rf bridge v2 successfull. Tried with an rf remote, and it did show some data in the console. Since i wanted to send data, i flashed portisch firmware (with cutted traces), and according to the messages everything was fine. After that, it seems i can no longer receive any data. Tried multiple 433 mhz remotes and sensors, nothing gives an output in the console. reflashed original rf firmware, again nothing to see. reflashed polisch, tried the rfraw 177 / rfraw AAB155 command, this gives the "Data":"AAA055" result but nothing more. Any suggestions? is it possible that i cut too deep and damaged something below? Or that the flash was not correct (i used breadboard wires, did not solder anything)?

[ascillato]

Please, address this to the Tasmota Support Chat. The chat is a better and more dynamic channel for helping you. Github issues are meant for Tasmota Software Bug Reporting.

Please check the Contributing Guideline and Policy and the Support Guide.

Thanks.

---

Support Information

See Wiki for more information. See FAQ for common questions/answers and links if none of your question is in the list See Chat for more user experience. See Community for forum. See Code of Conduct

[syepes]

Just wanted to thank all the hard work on this one. I just flashed Tasmota + Portisch on my R2 v1.0 and its working as expected.

[LucReynders]

Hmmm. I tried to flash several times another rf bridge with esptool on a linux laptop. The flashing looked ok but no wifi ap connection visible. When I finally flashed with nodemcuflasher on my Imac everything went smooth from flashing up to installing portisch sw. I assume that esptool does not fully erase the esp before flashing and nodemcuflash does. So if you may have a similar problem try nodemcuflash.

[Jason2866]

Esptool.py does what told. So it does no erase before flashing. Recommended flash tool for Tasmota is Tasmotizer

[docsparks]

does anyone know which pin is GPIO2 on the r2v1 board? i blew out my lead for gpio4 and gpio5 i'm using. looking to add 315mhz sensors thank youuu

[cwttdb70]

Hey everyone, there's a new board layout (R2 v2.2). I was able to flash Tasmota, but can not figure out which pins to connect to flash Portisch, and whether or not I need to score any lines on the board. Any help would be greatly appreciated.

https://github.com/arendst/Tasmota/issues/13282

[barbudor]

Don't cross post

[bjwo]

Don't cross post

Well, currently the official documentation refers to this thread, and it does not make clear that it is currently not possible to flash the Portisch firmware to the RF sensor. This gets discussed in issue #13282 and it is very valid that this gets mentioned here.

It would be even better to update the Tasmota project pages with this information.

[barbudor]

It would be even better to update the Tasmota project pages with this information.

Absolutely and as you are suggesting it, please click on the pencil on the top right of the doc page to update it. Thanks a lot for your participation

[dbuezas]

Direct hack for R2.2 https://community.home-assistant.io/t/new-sonoff-rf-bridge-board-need-flashing-help/344326/17

[ascillato]

Direct hack for R2.2

This is under discussion at https://github.com/arendst/Tasmota/discussions/13283