mirror of https://github.com/arendst/Tasmota.git
Improved the flow of the document and made several clarifications.
parent
016922558d
commit
aa508d550b
|
@ -1,12 +1,26 @@
|
|||
|
||||
|
||||
* Itead Product Page: http://sonoff.itead.cc/en/products/appliances/sonoff-rf-bridge-433
|
||||
* Itead Shop: https://www.itead.cc/sonoff-rf-bridge-433.html
|
||||
* Itead Wiki: https://www.itead.cc/wiki/Sonoff_RF_Bridge_433
|
||||
* Flash Guide: [How to Flash the RF Bridge](https://github.com/arendst/Sonoff-Tasmota/wiki/How-to-Flash-the-RF-Bridge)
|
||||
* RF Bridge 433 R2 Information: https://github.com/arendst/Sonoff-Tasmota/issues/1916
|
||||
|
||||
## Attention ⚠️️⚠️️⚠️️ ##
|
||||
## Overview
|
||||
|
||||
On R2 V1.0 Boards, GPIO4 and GPIO5 are swapped!
|
||||
The bridge has the *ESP chip*, similar to all other Sonoff boards. This chip can be flashed with the Sonoff-Tasmota software. In addition the bridge has an *RF chip* (433MHz) for which there is a custom firmware commonly referred to as 'Portisch'. The original Sonoff RF firmware is limited. By updating the firmware of the RF chip (EFM8BB1 MCU), new features and types of devices become usable. Tasmota supports the Original Sonoff RF firmware and [Portisch firmware](https://github.com/Portisch/RF-Bridge-EFM8BB1).
|
||||
|
||||
The RF upgrade requires wiring the bridge and then flashing the firmware via Sonoff-Tasmota Web UI.
|
||||
|
||||
|
||||
The preparation process outline is as follows:
|
||||
|
||||
1. Make sure you read the [Prerequisite](https://github.com/arendst/Sonoff-Tasmota/wiki/Prerequisite) wiki.
|
||||
2. Connect to the bridge via the four flashing pins. Do not plug anything in the micro USB port.
|
||||
3. Flash the ESP with Sonoff-Tasmota software
|
||||
4. Make sure the bridge connects to your wifi.
|
||||
5. (Optional) Flash the RF firmware with Portisch via the Web UI.
|
||||
6. You're ready. Now go figure out how to communicate with your 433MHz devices.
|
||||
|
||||
## Serial Connection
|
||||
|
||||
|
@ -30,44 +44,48 @@ Tasmota provides default remote control commands to all 16 keys so you can start
|
|||
|
||||
See [Supported Commands](https://github.com/arendst/Sonoff-Tasmota/wiki/Commands#sonoff-rf-bridge-433) for available specific Sonoff RF Bridge 433 commands.
|
||||
|
||||
## Rf chip firmware upgrade
|
||||
|
||||
<img src="https://github.com/arendst/arendst.github.io/blob/master/media/sonoff_bridge_rffw_upgrade.png" width="300" align="right" />
|
||||
|
||||
By updating the firmware of the Rf chip a EFM8BB1 MCU new possibilities become available. Starting with Tasmota v6.0.0a the Rf chip firmware upgrade is easily done using Web Gui **Upgrade by File Upload**. Tasmota supports the Original and [Portisch firmware](https://github.com/Portisch/RF-Bridge-EFM8BB1). **For downloading the firmware press the green download button** on the main page. If you download the firmware via click on file it will be corrupted (error "Magic byte is not 0xE9").
|
||||
|
||||
## Flash-Process of Hardware R2 with Hardware preparation
|
||||
_This chapter applies only for R2 and only if you want to use USB for powering the device during EFM flash process._
|
||||
|
||||
Shown picture is the Bridge R2 version where two not used copper traces need to be cut if you want to use the current power connector during updating.
|
||||
|
||||
A hardware preparation is needed (only for R2!) if you want to use USB for powering the device during EFM flash process.
|
||||
Shown picture is the Bridge R2 version where two not used copper traces need to be cut if you want to use the current power connector during updating and connect two wires between GPIO4 and C2Ck and GPIO5 and C2D. These changes can be permanent as they do not interfere with the normal Bridge functionality and it also allows for easy changing of firmware in the future.
|
||||
|
||||
## Flash-Process of Hardware R2 without Hardware preparation
|
||||
**You dont have to cut wires to upgrade the firmware of R2!!!!**
|
||||
If you dont like the idea cutting something in your bridge there is no need for! In that case DONT use USB to power the bridge. Power the bridge over a pin in the bridge labeled 3.3V. Just the same way as flashing the ESP. However you still need to connect GPIO4 & GPIO5 as described above.
|
||||
After flash process is done the bridge can be powered over USB for normal use.
|
||||
|
||||
|
||||
## Flash process
|
||||
Connect two wires between GPIO4 and C2Ck and GPIO5 and C2D. These changes can be permanent as they do not interfere with the normal Bridge functionality and it also allows for easy changing of firmware in the future.
|
||||
After the correct Tasmota firmware has been uploaded select the desired RF_Bridge.hex firmware file from the tools/fw_efm8bb1 folder and Start upgrade. This will replace the current Rf chip firmware within 60 seconds.
|
||||
|
||||
**IMPORTANT:** In the Module configuration GPIO4 and GPIO5 must be left as **00 None**
|
||||
|
||||
## Learning of Commands with custom Firmware
|
||||
## RF Firmware Upgrade
|
||||
**Attention ⚠️️⚠️️⚠️️ Compared to R1 the R2 V1.0 GPIO4 and GPIO5 have been swapped** This impacts flashing of the RF chip only.
|
||||
|
||||
Wiring for R2 V1.0 RF firmware flashing shown on the right.
|
||||
<img src="https://github.com/arendst/arendst.github.io/raw/master/media/sonoff_bridge_rffw_upgrade.png" width="300" align="right">
|
||||
|
||||
1. Connect two wires between GPIO4 and C2Ck and GPIO5 and C2D. These changes can be permanent as they do not interfere with the normal Bridge functionality and it also allows for easy changing of firmware in the future.
|
||||
2. Switch the ON/OFF switch on the board to 'OFF' to switch off the RF.
|
||||
3. Hold the pairing button while powering up the bridge via the 3.3V & GND pins. (See below if you need the USB power)
|
||||
4. Go to the Web UI **Firmware Upgrade** > **Upgrade by File Upload**
|
||||
* Available since Tasmota v6.0.0a
|
||||
5. Select the .hex firmware file of your choosing.
|
||||
1. In Sonoff-Tasmota package under [tools/fw_efm8bb1](https://github.com/arendst/Sonoff-Tasmota/tree/master/tools/fw_efm8bb1) folder.
|
||||
* These are also Portisch firmware but may not be the latest.
|
||||
2. Latest [Portisch firmware](https://github.com/Portisch/RF-Bridge-EFM8BB1)
|
||||
* Download it by pressing the green 'Download ZIP' button** on the main page. If you download the hex file only, it will be corrupted (error "Magic byte is not 0xE9").
|
||||
6. Hit **Start Upgrade**. The flashing should complete within 60 seconds.
|
||||
7. Put the ON/OFF switch on the board back to 'ON' to enable the RF again.
|
||||
|
||||
### Optional: USB power while flashing the RF firmware (Hardware R2 only)
|
||||
_This chapter applies only for R2 and only if you want to use USB for powering the device during EFM flash process._
|
||||
|
||||
Hardware preparation is needed (only for R2!) if you want to use USB for powering the device during EFM flash process.
|
||||
Shown picture is the Bridge R2 version where two not used copper traces need to be cut if you want to use USB power during updating. These changes can be permanent as they do not interfere with the normal Bridge functionality.
|
||||
|
||||
## Portisch Firmware Specific Usage
|
||||
These chapters only apply to the custom Portisch firmware.
|
||||
|
||||
### Learning of Commands with custom Firmware
|
||||
In order to learn Buttons from your remote, go to the Console of your RFBridge.
|
||||
There, enter rfraw 177 and push the buttons on your remote. Repeat each button 2-3 times, as the signal may be different for each try.
|
||||
This will give you a so called B1 code of your button, which needs to be converted to a B0 code (see below).
|
||||
|
||||
## Sending of Commands with custom Firmware
|
||||
### Sending of Commands with custom Firmware
|
||||
The commands learned with the hacked (Portisch-)Firmware **cannot ** be stored in the webinterface. Instead, they must be sent via MQTT:
|
||||
`mqtt=">[broker:cmnd/sonoff-8E8329/Backlog:command:ON:RfRaw AAB0210314016703F924180101011001100110010101100110011001010110010101100255; RfRaw 0],`
|
||||
Refer to [this](https://github.com/arendst/Sonoff-Tasmota/issues/3973) issue for further information
|
||||
|
||||
|
||||
## Interactive B1 to B0 tool
|
||||
### Interactive B1 to B0 tool
|
||||
Here ([link](https://github.com/henfri/bitbuckedconverter/blob/master/BitBucketConverter)) an interactive tool was developed to learn Commands/Codes.
|
||||
Process:
|
||||
-Run rfraw 177 in your SonOff console -Push all your remote (each Button 2-3 times)
|
||||
|
@ -86,7 +104,7 @@ Then:
|
|||
* In the end you can test all of these codes
|
||||
|
||||
|
||||
## B1 to B0 helping tool
|
||||
### B1 to B0 helping tool
|
||||
(if you prefer the non interactive version)
|
||||
After learning how bit bucket works from here [#23](https://github.com/Portisch/RF-Bridge-EFM8BB1/issues/23) this is a python script to help calculate the right 'B0' message to send using 'RfRaw' command in Tasmota from the received 'B1' sniffing message (rename file from 'BitBucketConverter.txt' to 'BitBucketConverter.py'.
|
||||
|
||||
|
@ -98,7 +116,7 @@ i.e. BitBucketConverter.py "AA B1 04 07EB 0157 00FD 3EBC 01010101010110100101010
|
|||
Command Line : "AA B1 04 07EB 0157 00FD 3EBC 010101010101101001010101101010100103 55" 20
|
||||
Result: 'RfRaw AAB01C041407EB015700FD3EBC01010101010110100101010110101010010355'
|
||||
|
||||
## 'Raw sniffing' procedure.
|
||||
### 'Raw sniffing' procedure.
|
||||
With Portisch suggestions I did the following:
|
||||
In Tasmota console I sent
|
||||
***
|
||||
|
|
Loading…
Reference in New Issue