Another Board Layout RF Bridge #1916

michaelmassee · 2018-02-14T22:21:04Z

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:

The Box is Screwed together.
To get to the Switch, just bend slightly the large Led on the Top
Then Flash it from Bottom Side

regards

emontnemery · 2018-02-15T07:12:30Z

Which RF bridge is this?

michaelmassee · 2018-02-15T12:36:14Z

The Sonoff 433 RF Bridge
https://www.itead.cc/sonoff-rf-bridge-433.html

mapsrof · 2018-02-16T11:31:38Z

Also got a new board design (2017-11-23) and it's working like Michael described!

arendst · 2018-02-18T14:20:39Z

Confirmed. Add this issue as link to Wiki > Sonoff RF Bridge 433.

claud9999 · 2018-02-27T17:53:34Z

I also received this board today.

Yes you have to pull out the rubber feet to get to the screws. I'm able to power the board but not flash the board using esptool.py, I've flashed a number of other Sonoff devices so it's not a computer config issue.

I've tried swapping RX/TX, pressing and holding the "peer" button, and changing S2 to "off", all to no avail.

More detailed instructions would be appreciated!

PeterEmbedded · 2018-03-06T21:03:29Z

@claud9999

Set the switch to OFF
Remove power from the device (3V3)
Press and HOLD the button
Power on the device
Wait +/- 1 second
Release the button
Device will now be in firmware download mode, use your IDE to upload the new firmware as usual
[if this doesn't work try swapping RX/TX]

newingit18 · 2018-04-19T12:00:14Z

like @claud9999 I have the same issue with this type of board - tried all hints from @PeterEmbedded - no way to flash - any idea? At this board works a ESP8285, not the ESP8266.

arendst · 2018-04-19T18:46:27Z

Again. This boards is fine. Just follow the wiki and this thread.

newingit18 · 2018-04-19T20:02:21Z

Sure - good board and wiki, but in the described issue this answer is no help...

newingit18 · 2018-04-20T12:28:39Z

Dear all, seems that is an issue with the COM-Port - I used an existing COM1-port, without an USB-adapter. Then I used a FT232RL USB-Adapter - this worked fine, thanks all.

Marty56 · 2018-04-28T17:10:49Z

I had to set the switch from OFF to ON after flashing was completed. Otherwise no RF commands was recognized.

Marty56 · 2018-04-28T17:12:57Z

I managed to get an Intertechno switch to work with the RF bridge.
The Intertechno remote control is not detected. Although it can operate the same switch that I can control via RF bridge. Strange.

mo8Zomo0 · 2018-05-01T12:11:04Z

The newer RF bridge itself works fine, what I wondered, which IO ports
are available and could be used for something else, like I would like to keep
the RF function and add a temperature/humidity sensor.

MikhaelGerbet · 2018-06-16T22:53:20Z

Hello everyone !
It's a good idea to flash from the bottom side but, we don't close the box after :/
I have try to flash by the top side and here how to do :)

Info : the opening is done with cruciform screws hidden by the non slip skids :

I lifted the LED of the logo, I removed part of the protective mouse and I welded behind slightly inclined pines

I flashed the module

Then I replaced the LED in its place

And now, I was able to close the box :)

Enjoy :)

angustyler · 2018-06-25T10:30:30Z

Flashing the RF Bridge with Tasmota 6.0.0a worked perfectly and is now accessible from the web page just fine. However, I'm now trying to install the Porticsh RF-Bridge-EFM8BB1 updated firmware by following the instructions:
https://github.com/arendst/Sonoff-Tasmota/wiki/Sonoff-RF-Bridge-433 . But am getting error:
"Upload Failed. Magic byte is not 0xE9"
I've using the RF_Bridge.hex found at:
https://github.com/Portisch/RF-Bridge-EFM8BB1/blob/master/Keil%208051%20v9.53%20-%20Release/RF_Bridge.hex
(Note: I guess this is the correct location as the folder "tools/fw_efm8bb1" does not appear to exist - unless of course I am looking in the wrong place!)
Any help greatly appreciated!

newingit18 · 2018-07-01T15:21:07Z

Please look at the howto to prepare hardware for updating the EFM8BB1. I used the cutting of PCB strip lines as suggested in the picture (see https://github.com/arendst/Sonoff-Tasmota/wiki/Sonoff-RF-Bridge-433 - the last topic). It worked for me -I got success at the web gui of the Bridge.

joecool99 · 2018-07-10T08:39:32Z

In the section "Rf chip firmware upgrade" in the description mentioned above it is said, that "two not used copper traces need to be cut if you want to use the current power connector during updating".

Why is it necessary to cut these copper traces if they are not used?

Thank you!

newingit18 · 2018-07-11T07:26:26Z

The idea behind - as shown at the picture - https://github.com/arendst/Sonoff-Tasmota/wiki/Sonoff-RF-Bridge-433 - the 2 new wires can be in that case a permanent connection (you have to solder 2 small cables permanently), so you are able to patch new firmware via the web interface every time very easy without any hardware activities.

joecool99 · 2018-07-11T07:53:16Z

Thank you, newingit18.

Maybe i'm blind, but i still do not see why it is necessary to cut these two traces because as far as i can see, the lower part of the cutted traces is not connected to anything and the endpoints of the cutted traces are not soldered, as far as i can see...

This can not be seen very good on this image because of the new cables but on my sonoff bridge i've tried to find a connection with a magnifier - but i didn't ...

Thank you.

newingit18 · 2018-07-11T08:11:52Z

If you are sure, that these strip lines are not connected to anything (I didn't check that electrically) - you can leave the lines uncutted. Keep in mind that this PCB can be a multi layer PCB, so you can not see all connections inside the multi layer PCB - you have to check this with a AC/DC multimeter to be sure.

joecool99 · 2018-07-11T08:19:14Z

I'm not sure - that's my problem ;-)

I want to avoid a permanent change to the board, if it's not necessary, and as you said, if the board is multi layer - cutting something might be especially harmfull ...

arendst · 2018-07-11T08:30:16Z

Guys, the issue I wanted to raise here is the fact that the lower part of the traces are connected to the USB connector. If you connect external power to the USB connector these traces might carry either power or a USB signal depending where you get your power from which will interfere with the MCU flash signals.

So either do not use the USB power while MCU flashing but connect power to other pins on the header or cut the traces and use the USB connector to power the thing.

joecool99 · 2018-07-11T08:33:24Z

OK, thank you very much.

newingit18 brought me to the right idea, i've just checked the other side of the board and i've found what you say:

Thank you very much :-)

PeterEmbedded · 2018-07-11T14:31:21Z

Just for some more information. These "endpoints" are actually vias.
https://en.wikipedia.org/wiki/Via_(electronics)

videobuff · 2018-07-15T23:13:42Z

I aso have the same problem, and not yet resorted to cutting the pcb traces.
The tasmota firmware update went without a glitch:
Programma Versie | 6.1.0
2018-07-16T00:42:10
2_3_0/1.5.3(aec24ac9)
0T00:09:24
And i can see the webpage.

Anything else to try before cutting the traces ?

nnhhuu · 2018-08-22T14:29:50Z

I have an issue, in setting i can't find the Flash: 1M (no SPIFFS), these are the option i have

can i use other option here.?

ascillato · 2018-08-22T14:45:08Z

Offtopic.

Please, read the wiki

https://github.com/arendst/Sonoff-Tasmota/wiki/Arduino-IDE

Geoff571 · 2018-10-09T15:14:28Z

OK, I'm confused.

I read the Wiki on the Sonoff Bridge and it implies it should be flashed as an ESP8266, however the chip is actually an ESP8285. I saw a YT video that specifically set Arduino IDE to flash for an ESP8285. Which method is correct?

tedsluis · 2019-01-27T14:47:47Z

I am having problems with the RF bridge R2 v1.0 marked "2017.11.23". It looks like flashing went okay, no errors, but after powering the RF bridge using the micro usb I can not connect to it.

To flash I use a Fedora linux system with a CH340G USB serial adapter. I use VSCode with the PlatformIO plugin. I tried the Sonoff-Tosmota 6.4.1 (release) and the 6.4.1.9 (development). I have quite some experience with successful flashing other Sonoff devices, like Basic, Pow R2, 1CH and S26.

Preparations

I did not used the micro usb power during flashing, so I did not cut the copper traces on the board, as mentioned in the wiki.

Like @ozet, I was confused by the instructions in the wiki on the flash process. The image was different then the wiki text?! So I first tried the wiring according the image in the wiki and later on, as mentioned by @ozet, I also tried the wiring as advised in the wiki text.

My board (with wiring according wiki image, this does not match with the wiki text):

Wiring according the wiki image:

Wiring according wiki text:

Both ways of wiring gave the same result: The flashing process finished successful, but I was not able to connect to RF bridge.

Steps I took to flash:

connected the RF bridge board to a CH340G USB serial adapter: RX-TX, TX-RX, GND to GND.
set switch to off.
pressed and hold the button.
Inserted the CH340G USB serial adapter into my laptop.
connected RF bridge board 3v3 pin to CH340G USB serial adapter pin 3v3.
waited a few seconds and released the button on the board.
waited a few seconds and start flashing.

The Flash logging is the same for both ways of wiring:

> Executing task: platformio run --target upload <

Processing sonoff (framework: arduino; platform: espressif8266@1.8.0; board: esp01_1m)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif8266/esp01_1m.html
PLATFORM: Espressif 8266 > Espressif Generic ESP8266 ESP-01 1M
HARDWARE: ESP8266 80MHz 80KB RAM (1MB Flash)
Converting sonoff.ino
Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF MODES: FINDER(chain) COMPATIBILITY(soft)
Collected 53 compatible libraries
Scanning dependencies...
Dependency Graph
|-- <OneWire> 2.3.2
|-- <ArduinoJson> 5.11.2
|-- <LiquidCrystal_I2C>
|   |-- <Wire> 1.0
|-- <TasmotaMqtt> 1.0.0
|-- <Adafruit ILI9341> 1.2.0
|   |-- <Adafruit GFX Library> 1.2.9
|   |   |-- <SPI> 1.0
|   |-- <SPI> 1.0
|-- <PubSubClient> 2.6
|-- <ESP8266WebServer> 1.0
|   |-- <ESP8266WiFi> 1.0
|-- <DNSServer> 1.1.0
|   |-- <ESP8266WiFi> 1.0
|-- <ESP8266mDNS>
|   |-- <ESP8266WiFi> 1.0
|-- <I2Cdevlib-MPU6050>
|   |-- <I2Cdevlib-Core>
|   |   |-- <Wire> 1.0
|-- <NeoPixelBus> 2.2.9
|   |-- <SPI> 1.0
|-- <ESP KNX IP Library> 0.5.1
|   |-- <ESP8266WiFi> 1.0
|   |-- <EEPROM> 1.0
|   |-- <ESP8266WebServer> 1.0
|   |   |-- <ESP8266WiFi> 1.0
|-- <ArduinoOTA> 1.0
|   |-- <ESP8266WiFi> 1.0
|   |-- <ESP8266mDNS>
|   |   |-- <ESP8266WiFi> 1.0
|-- <Ticker> 1.0
|-- <Adafruit SSD1306> 1.1.2
|   |-- <Adafruit GFX Library> 1.2.9
|   |   |-- <SPI> 1.0
|   |-- <Wire> 1.0
|   |-- <SPI> 1.0
|-- <I2Cdevlib-Core>
|   |-- <Wire> 1.0
|-- <ESP8266HTTPClient> 1.1
|   |-- <ESP8266WiFi> 1.0
|-- <ESP8266httpUpdate> 1.2
|   |-- <ESP8266HTTPClient> 1.1
|   |   |-- <ESP8266WiFi> 1.0
|   |-- <ESP8266WiFi> 1.0
|-- <TasmotaSerial> 2.2.0
|-- <Adafruit CCS811 Library> 1.0.0
|   |-- <Wire> 1.0
|-- <Waveshare esp 2.9 inch e-paper display driver> 1.0
|   |-- <SPI> 1.0
|-- <C2Programmer> 1.0.0
|-- <IRremoteESP8266> 2.5.2
|-- <Adafruit SGP30 Sensor> 1.0.2
|   |-- <Wire> 1.0
|-- <SPI> 1.0
|-- <Joba_Tsl2561> 2.0.7
|   |-- <Wire> 1.0
|-- <BME680_driver-bme680_v3.5.9>
|-- <Wire> 1.0
|-- <I2Cdevlib-ADS1115>
|   |-- <I2Cdevlib-Core>
|   |   |-- <Wire> 1.0
|-- <MQTT> 2.4.0
|-- <TasmotaModbus> 1.1.0
|   |-- <TasmotaSerial> 2.2.0
|-- <Mutichannel_Gas_Sensor> 0.0.1
|   |-- <Wire> 1.0
|-- <Adafruit LED Backpack Library> 1.1.6
|   |-- <Adafruit GFX Library> 1.2.9
|   |   |-- <SPI> 1.0
|   |-- <Wire> 1.0
|-- <ESP8266WiFi> 1.0
|-- <NewPing> 1.9.1
|-- <Adafruit GFX Library> 1.2.9
|   |-- <SPI> 1.0
|-- <rc-switch> 2.6.2
Compiling .pioenvs/sonoff/src/sonoff.ino.cpp.o
Linking .pioenvs/sonoff/firmware.elf
Retrieving maximum program size .pioenvs/sonoff/firmware.elf
Building .pioenvs/sonoff/firmware.bin
Checking size .pioenvs/sonoff/firmware.elf
Memory Usage -> http://bit.ly/pio-memory-usage
DATA:    [======    ]  58.9% (used 48240 bytes from 81920 bytes)
PROGRAM: [=====     ]  51.4% (used 526764 bytes from 1023984 bytes)
Configuring upload protocol...
Looking for upload port...
Use manually specified: /dev/ttyUSB0
Uploading .pioenvs/sonoff/firmware.bin
Uploading 530912 bytes from .pioenvs/sonoff/firmware.bin to flash at 0x00000000
................................................................................ [ 15% ]
................................................................................ [ 30% ]
................................................................................ [ 46% ]
................................................................................ [ 61% ]
................................................................................ [ 77% ]
................................................................................ [ 92% ]
.......................................                                          [ 100% ]
============================================================================== [SUCCESS] Took 62.11 seconds ==============================================================================

======================================================================================== [SUMMARY] ========================================================================================
Environment sonoff              [SUCCESS]
============================================================================== [SUCCESS] Took 62.11 seconds ==============================================================================

During flashing the LEDs on the CH340G USB serial adapter are flashing all the time, the big green LED of the RF bridge is green all the time. No other LEDs on the board flashes and I did not hear a beep.

There is one strange thing to mention about the flash process. Normally with all the other Sonoff devices I have flashed (using the same software and configuration), the upper and lower LED on the CH340G were "ON" when the flash process was fished. With the RF bridge only the upper LED was "ON".

Steps after flashing:

removed the serial connection.
set the switch to off.
powered the RF board using the micro usb connector.

Again the big green LED of the RF brigde is green. No other LEDs on the board flashes and I did not hear a beep.

I tried to connect to the RF bridge board, without success. It does not react on pressing the button.

Of course I have repeated the flash process several times. Many times I first erased the firmway using this command:

$ ./esptool.py --port /dev/ttyUSB0 erase_flash
esptool.py v2.6
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP8266
Chip is ESP8285
Features: WiFi, Embedded Flash
MAC: 60:01:94:be:7d:d1
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 0.0s
Hard resetting via RTS pin...

I am still puzzled about the correct way of wiring. Can any one confirm the correct wiring for my type of board?

Isn't strange that I am able to flash the the RF bridge, but that it does not work? What can be wrong?

I even tried a second RF bridge and I ended up with the same results.

How can I debug this?

TerryLansdown · 2019-01-28T10:23:23Z

How can I debug this?

Hi, See my earlier post for the wiring that works for me.

Sounds like you know what you're doing, but maybe you didn't try:

checking the serial monitor for device boot/network connect messages? I think I tested mine with the USB-serial cable powering it, first.
checking if the bridge is appearing on your network, ping'ing it?
flashing a different way? I used the Arduino SDK to flash mine.

What do you mean by 'I was not able to connect to RF bridge'? Is it dead? Can you ping it, but not connect to the web interface? On mine, powering by the micro-usb cable resulted in clicking reboots, until I fixed the wiring.

tedsluis · 2019-01-28T13:33:26Z

Hi, thnx for your extensive reply!

TerryLansdown said:

Hi, See my earlier post for the wiring that works for me.

Sure I have read your post, but it was/is not 100% clear to me whether your board has the "2017.11.23" mark, like my board. Can you confirm that?

TerryLansdown said:

checking the serial monitor for device boot/network connect messages? I think I tested mine with the USB-serial cable powering it, first.

I tried that, but without luck. I am not sure how to do it on a Sonoff RF Bridge.
I had my RF bridge connected using the TX, RX, 3v3 and GND to the CH340G serial adaptor. I did not connected it to a micro usb power. Is that correct?
I tried the cu command (Fedora command line, I have used this for other board successfully):

$ cu -l /dev/ttyUSB0 -s 19200

I didn't got any response. How should it react?
I also tried to put the RF bridge in flash mode, in order to get any response.
What steps should I take to start a console?
What tool did you use?

TerryLansdown said:

checking if the bridge is appearing on your network, ping'ing it?

The IP address of the bridge did not appear in my network. So I could not ping it or connect to the web interface.

TerryLansdown said:

flashing a different way? I used the Arduino SDK to flash mine.

I will try that, may be tonight (or in the coming days).

TerryLansdown said:

On mine, powering by the micro-usb cable resulted in clicking reboots, until I fixed the wiring.

My wiring is like yours now. When I power on the RF bridge using the micro usb, the big green LED turns "on". No other LED flashes, no beep and no reaction when I press the button.

I used the same Sonoff-Tasmota firmware + configuration as I used for other Sonoff devices (except for the IP address and topic name).

To flash the RF bridge I tried an upload speed of 115200 as well as 19200 (takes much longer to finish). Which is correct?

To test whether my current Vscode with PlatformIO setup still works, I have flashed a Sonoff Basic device yesterday. It still works.

TerryLansdown · 2019-01-28T14:02:08Z

Hi,

Don't know, it's now deep in a cupboard put back together. If I get a chance I'll have a look, from memory it was a 2017 version.
Again (from memory), I flashed with just the USB-Serial adapter. When uploaded, within the Arduino SDK there is a serial monitoring option. Using only the serial adapter (I think) I got status updates, connected to local network, connected to MQTT server, etc. You may have seen these with your Sonoff Basics? Only after a successful flash (using the Arduino SDK and the image from the main Tasmota Git pages; did I unplug the serial and power using just micro-usb cable.

I'm guessing your flash is a big fail if you can even see noise using 'cu'.
Think you did the right thing to zero out the board between each flash with esptool.

Smells like a big fail.
The Arduino SDK worked for me, good luck.

I don't think I needed to press any buttons to get the board up. Move onboard switch from flash to broadcast, then plug in and it connected to my network, and MQTT server. I could then access the webpages, much like (presumably) your other Sonoffs.

From memory, I think I tried flashing at both speeds, I think it flashed at 115200 and then it definitely communicates at 19200.

Other than trying a different flashing technique specifically for this board, sorry I'm out of ideas.

tedsluis · 2019-01-29T06:19:42Z

Hi, Thanx again for your detailed answer.

I think you are right, mine RF bridge is not flash successful.

I tried flashing using the esptool, several attempts with different baud rates, but they all ended like this:

[esptool-2.6]$  ./esptool.py --baud 19200  --port /dev/ttyUSB0 write_flash -fs 1MB -fm dout 0x0 /home/tedsluis/Downloads/sonoff.bin 
esptool.py v2.6
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... ESP8266
Chip is ESP8285
Features: WiFi, Embedded Flash
MAC: 60:01:94:be:7d:d1
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Compressed 561728 bytes to 383685...
Wrote 561728 bytes (383685 compressed) at 0x00000000 in 201.8 seconds (effective 22.3 kbit/s)...
File  md5: d4d8fc948a61ad6daba006cfb13ba547
Flash md5: 3a870a291785e4cc40d1af355e578b7c
MD5 of 0xFF is 9300bbcef90645be31241ea9ba92847b

A fatal error occurred: MD5 of file does not match data in flash!

I will try the Arduino IDE to night.

ozett · 2019-01-29T07:51:21Z

may you try the espeasy flashtools?
i had success with them: #1916 (comment)

LucReynders · 2019-01-29T11:05:56Z

Received my RFBridge yesterday.
Flashed it with Tasmota : (! no extra wires have been added, only the pins - no 5V supply during flash))

Dismantled the device (4 screws on the bottom)
lifted the "sonoff display" 90°
added 4 connector pins to the board (GND, RX, TX, 3.3V)
switched the on-board switch to "OFF"
connected the USB flash device to the pins
pushed the on-board button and connected the flash device to the USB port (Imac with PlatformIO)
released the button and flashed TASMOTA on the RFBridge.
found the IP address of the device
configured the sonoff device as usual (25 bridge)
put the on-board switch back to "ON"
shortened the connection pins and put the display back in place (you can remove the black seal partly)
assemble the unit.
(worked perfectly after teaching "Rfkeys 2" on the console and sending MQTT in Nodered)

tedsluis · 2019-01-29T21:22:12Z

Thnx @TerryLansdown, @ozett and @LucReynders.

@TerryLansdown said:

The Arduino SDK worked for me, good luck.

It took me a while to get the Arduino IDE working on Fedora Linux. I guess most people use Windows. I followed the wiki instructions and I managed to build and upload the Sonoff-Tasmota firmware. Unfortunately still the same result: I can not connect to the bridge, but I keep positive. This is only my first attempt with the Arduino IDE :-)

Build options changed, rebuilding all
Archiving built core (caching) in: /tmp/arduino_cache_674523/core/core_esp8266_esp8266_generic_CpuFrequency_80,VTable_flash,ResetMethod_nodemcu,CrystalFreq_26,FlashFreq_40,FlashMode_dout,FlashSize_1M0,led_2,LwIPVariant_v2mss1460,Debug_Disabled,DebugLevel_None____,FlashErase_none,UploadSpeed_115200_c1df69fc8c56a963385ffb471ec2f0ff.a
Sketch uses 529928 bytes (51%) of program storage space. Maximum is 1023984 bytes.
Global variables use 51604 bytes (62%) of dynamic memory, leaving 30316 bytes for local variables. Maximum is 81920 bytes.
Uploading 534080 bytes from /tmp/arduino_build_804524/sonoff.ino.bin to flash at 0x00000000
................................................................................ [ 15% ]
................................................................................ [ 30% ]
................................................................................ [ 45% ]
................................................................................ [ 61% ]
................................................................................ [ 76% ]
................................................................................ [ 91% ]
..........................................                                       [ 100% ]

No output on the serial monitor yet, but I need some more time to get to know the Arduino IDE.

@ozett said:

may you try the espeasy flashtools?

Unfortunately I only have Linux systems. I think espeasy only runs on Windows.
Your previous post is very useful!

@LucReynders said:

Flashed it with Tasmota : (! no extra wires have been added, only the pins - no 5V supply during flash))

No extra wiring? Very interesting. Is your RF bridge marked "2017.11.23"?
Thnx for your detailed steps. Very useful!

I need some more time to carry out all the instructions and tips. I let you guys know in the coming days.

ozett · 2019-01-30T07:33:12Z

Unfortunately I only have Linux systems. I think espeasy only runs on Windows.
Your previous post is very useful!

Thanx,
Espeasy is a firmware for the ESP8266/Esp32 chips.
they have also firmware flash-tools.
i think there is a linux-variant of the good working windows tool.

may there some inspirations for your experiment:
https://www.letscontrolit.com/wiki/index.php/Flash_script_linux

---add:
as i looked your output of the arduino ide:
do you hard-reset (power-off!) your device after flashing? i think that is needed also...

LucReynders · 2019-01-30T07:43:00Z

For flashing the RFBridge, look at :
https://www.youtube.com/watch?v=XixXbg2T4Ns
https://no-ads-youtube.com/video-without-adverts/drzzs/sonoff-rf-bridge-with-tasmota?v=OfSbIFIJPuc

molexuse · 2019-02-01T09:58:38Z

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
Same problem. Flash without cut. It`s works, wifi connects. mqtt connects.
Rf received (red led flash) but in console serial and mqtt rf not send. I try diferent firmware with no success.
As i understand from schematic esp communicate with rf chip by uart, still analyze....

UPDATE!
It`s works!!! flash sonoff-classic.bin from git release and all ok

LucReynders · 2019-02-01T10:28:08Z

!!! Noot all remontes are detected by the bridge, only the 24 bit codes.
In my case only one out of 3.

Philips remote : Ok
chacon : nok
velleman : nok
Try different types of remotes.

tedsluis · 2019-02-03T19:39:36Z

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 · 2019-02-06T13:35:40Z

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 · 2019-03-03T16:32:29Z

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.

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.
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 · 2019-04-07T14:42:06Z

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 · 2019-06-12T22:04:15Z

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 · 2019-06-13T19:18:24Z

"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 · 2019-12-19T13:45:39Z

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 · 2019-12-19T14:03:22Z

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 · 2020-01-07T00:35:38Z

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 · 2020-03-14T09:24:17Z

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 · 2020-03-14T13:58:54Z

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

docsparks · 2021-10-06T00:04:43Z

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 · 2021-10-06T06:32:20Z

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.

#13282

barbudor · 2021-10-06T08:10:39Z

Don't cross post

bjwo · 2021-10-24T11:01:30Z

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 · 2021-10-24T11:18:08Z

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 · 2021-11-06T16:35:36Z

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

ascillato · 2021-11-06T16:49:28Z

Direct hack for R2.2

This is under discussion at #13283

arendst closed this as completed Feb 18, 2018

starkillerOG mentioned this issue Jun 27, 2018

Dooes this firmware support SONOFF RF Bridge R2? 1technophile/OpenMQTTGateway#200

Closed

Another Board Layout RF Bridge #1916

Another Board Layout RF Bridge #1916

Comments

michaelmassee commented Feb 14, 2018

emontnemery commented Feb 15, 2018

michaelmassee commented Feb 15, 2018

mapsrof commented Feb 16, 2018

arendst commented Feb 18, 2018

claud9999 commented Feb 27, 2018

PeterEmbedded commented Mar 6, 2018 • edited Loading

newingit18 commented Apr 19, 2018

arendst commented Apr 19, 2018

newingit18 commented Apr 19, 2018

newingit18 commented Apr 20, 2018

Marty56 commented Apr 28, 2018

Marty56 commented Apr 28, 2018

mo8Zomo0 commented May 1, 2018 • edited Loading

MikhaelGerbet commented Jun 16, 2018

angustyler commented Jun 25, 2018

newingit18 commented Jul 1, 2018

joecool99 commented Jul 10, 2018 • edited Loading

newingit18 commented Jul 11, 2018

joecool99 commented Jul 11, 2018 • edited Loading

newingit18 commented Jul 11, 2018

joecool99 commented Jul 11, 2018

arendst commented Jul 11, 2018

joecool99 commented Jul 11, 2018 • edited Loading

PeterEmbedded commented Jul 11, 2018

videobuff commented Jul 15, 2018

nnhhuu commented Aug 22, 2018

ascillato commented Aug 22, 2018

Geoff571 commented Oct 9, 2018

tedsluis commented Jan 27, 2019

Preparations

Steps I took to flash:

TerryLansdown commented Jan 28, 2019

tedsluis commented Jan 28, 2019

TerryLansdown commented Jan 28, 2019

tedsluis commented Jan 29, 2019

ozett commented Jan 29, 2019

LucReynders commented Jan 29, 2019

tedsluis commented Jan 29, 2019

ozett commented Jan 30, 2019 • edited Loading

LucReynders commented Jan 30, 2019

molexuse commented Feb 1, 2019 • edited Loading

LucReynders commented Feb 1, 2019

tedsluis commented Feb 3, 2019 • edited Loading

LucReynders commented Feb 6, 2019

antocorr commented Mar 3, 2019

sndipz commented Apr 7, 2019

TurboTronix commented Jun 12, 2019 • edited Loading

LucReynders commented Jun 13, 2019

Freestila commented Dec 19, 2019

ascillato commented Dec 19, 2019

Support Information

syepes commented Jan 7, 2020

LucReynders commented Mar 14, 2020 • edited Loading

Jason2866 commented Mar 14, 2020

docsparks commented Oct 6, 2021

cwttdb70 commented Oct 6, 2021 • edited Loading

barbudor commented Oct 6, 2021

bjwo commented Oct 24, 2021

barbudor commented Oct 24, 2021

dbuezas commented Nov 6, 2021

ascillato commented Nov 6, 2021 • edited Loading

PeterEmbedded commented Mar 6, 2018 •

edited

Loading

mo8Zomo0 commented May 1, 2018 •

edited

Loading

joecool99 commented Jul 10, 2018 •

edited

Loading

joecool99 commented Jul 11, 2018 •

edited

Loading

joecool99 commented Jul 11, 2018 •

edited

Loading

ozett commented Jan 30, 2019 •

edited

Loading

molexuse commented Feb 1, 2019 •

edited

Loading

tedsluis commented Feb 3, 2019 •

edited

Loading

TurboTronix commented Jun 12, 2019 •

edited

Loading

LucReynders commented Mar 14, 2020 •

edited

Loading

cwttdb70 commented Oct 6, 2021 •

edited

Loading

ascillato commented Nov 6, 2021 •

edited

Loading