Convert Sonoff RF Bridge to ESPHome

Time to change my firmware on my Sonoff RF Bridge to custom ESPHome firmware
Links:
Buy your Sonoff RF bridge from Amazon - amzn.to/2JZYsUX
(As an Amazon Associate I earn from qualifying purchases)
My ESPHome yaml - github.com/pin...
DrZzs RF Bridge flashing + tasmota - • Sonoff RF Bridge with ...
WildWiz Hardware Hack - github.com/xos...
ESPHome Remote Transmitter documentation - esphome.io/com...
ESPHome Remote Receiver documentation - esphome.io/com...
ESPHome Documentation - esphome.io/ind...
Patreon: / pinkywafer
Buy Me a Coffee: www.buymeacoff...
My Home Assistant config: github.com/pin...
Music: www.bensound.com

[@filipsvoboda7712]

Be careful revision 2 has the wrong pins marked. Instead of wire jumpers I would rather use 270 ohm resistors.

[@SteveMasonCanada]

Awesome video! I've been needing some cheap outdoor motion detectors, I have 1 Insteon (expensive) and a home-made esp-01 unit, but I wanted some cheap battery-powered units. Did some Googling and read about the Sonoff RF bridge. Sounded perfect. Oh, hardware mods required? No problem! So I ordered 1 and a cheap < $10.00 motion as a test. I'm also a huge fan of ESPHome (nothing wrong with Tasmota, but ESPHome works for me for some other things) then found your video. I went straight from the factory RF bridge to ESPhome so needed to connect to USB for the initial flash. Worked first try! Almost too small for my 60-year-old eyes, but I have magnification and some good soldering tools, so got it done. Thanks!

[@adrianbishop694]

Thanks for the Video and excellent instructions, The rf bridge was my last device on tasmota and now all devices over to esphome. Love Esphome native API over Mqtt

[@babyface3105]

Hi it's the same things for me. I have a sonoff RF Bridge and a Sonoff Ifan02 on tasmota, the all others sonoff device work now with esphome. My questio is do you have a sonoff ifan02 flash on Esphome firmware ?

[@adrianbishop694]

@@babyface3105 Sorry mate no

[@AnoNymous-lp5tb]

How do you set up the mqtt to be able to listen to the codes and be able to integrate with the node red. I did that in Tasmota and listen to the codes but I can't quite figure out in esphome. Thank you

[@Pinkywafer]

I don't use mqtt at all on esphome, and just use the api. You can use home assistant states in node red, but if you want to use mqtt, the place to find out about mqtt on esphome is esphome.io/components/mqtt.html

[@gumboot13]

New sub here. Came from Dr ZZZ. Great work. I already had aa RF Bridge modified from espurna that I had installed on it ( have garage remotes that can't detect on any firmware even with the mod done - turns out it uses rolling code - had to pull the remote apart to check the IC it was using) Looking forward to further videos. Thumbs up given also

[@filipecoelho9855]

Hello! My remotes also have the codes always changing (only now I leared it's called rolling codes). Did you manage to integrate them with ESPurna?

[@MrPSummerfield]

Yay, thanks Jenny. Just modified a R1 V2. And it works brilliantly and super fast, I'm impressed. I would never have been able to do this without your video help explaining things. Thank you

[@rrrrrrrr290]

Thanks for a great setup video, looking forward to more content from you excellent to see some bright nail polish while following alone with instructions.

[@907cariboo]

I finally got my door sensors working consistently after following your video, Thank you very much.

[@eclecticlife]

Thank you so much for this great video. I have been looking for this information for months!! Thank you!

[@fred7flinstone]

Thanks for the video. Thanks to you I have ESP-home on my sonoff RF bridge.

[@gooseza]

Thank you so much, this worked perfectly!

[@lindsayreid8347]

Great stuff - very well explained and all the links too - couldn't be better - all much appreciated,

[@iainhay2823]

Excellent video just what I need, finding tasmota works but a little slow to react so I’ll be trying this.

[@asdkjh4370]

Great tutorial - Many thanks it helps a lot - best regards from Poland,

[@woollysoxx]

Great video, have been trying to configure a tasmotized version and could not get my head around it. this has solved my problems, with your help. Thanks. Allan

Great video, greetings from Mexico! Thank you.

[@matheokoning4456]

Tip ... buy a D1 mini and an mx-05v on aliexpress and you have your own Sonoff Bridge for less than 3 euros. is even easier to make and works just as well with the same esphome setup as in this video. just change the transmit and receive pin in the config file you use on the D1 mini.

[@Pinkywafer]

Great way to do it... I've been planning to do this as a way of adding a few extra receivers for places where RF signals get 'lost'!

[@matheokoning4456]

Pinkywafer correction. do not use the mx-v5 receivers. these are very bad. the transmitters that go with it are more than fine but the receivers a crap. I now use the rx480 receiver and I like it very much.

[@piero957]

Very interesting and well explained, thank you.

[@evertythingtechrelated9715]

Definately gonna do this when I get mine in a few days.

[@slayps]

Thanks, this guide helped me set up my esp32 with an RF receiver

[@stickyfinger999]

Thanks for the video very informative please do some more.

[@AndrewDanne]

That is cools. Nicely done. I will be doing this.

[@StePhanMckillen]

10 out 10 well done

[@Jmcinally94]

In case anyone's interested, the wildwiz hardware hack isn't compatible with Portisch. Different hack! I recently looked into different firmware options as I've not been able to figure out how to send RF codes from ESPHome very easily.

[@sebydocky5080]

This is fantastic video !!!!! I will be able to migrate my last tasmota device to ESPhome. Maybe another vidéo how to send a msg from HA to the gateway ? for exemple to ring an alarm ?

[@mindracing]

Well done. Excellent instruction and thank you for your time in doing this. If you were starting with a virgin RF Bridge, would you flash it with Tasmota first or can you flash it with ESPHome Flasher on Mac using USB?

[@Pinkywafer]

No need to flash tasmota first, you can flash your esphome binary using the ftdi adapter and any esp flashing tool on Mac or PC. I did one for someone else a while ago, and flashed straight with esphome.

[@dickdatbenik]

Woman Power‼️👍

[@TheHookUp]

Great informative video. Question: Is it just speed that you get as a benefit of this? I'm such an ESPHome skeptic still, If I have tasmota running on my RFBridge will I notice anything different by doing this mod?

[@Pinkywafer]

Thanks Rob. You should be able to receive and send codes for a wider range of devices, as all codes are now processed by the ESP. (although I believe there is a similar hardware mod for tasmota as well). Other than that, you are also opened up to the possibility to use ESPHome's automations and lambdas, which can allow you to have various automations happen independently of HA, directly on the ESP.

[@squalazzo]

Rob, take a look at Espurna Direct Hack, it's the same hack as far as i can see... if you don't want to go for esphome, and are more familiar with tasmota and with mqtt in general, try that, i flashed on both of my 2 devices (1 version1, and 1 version2), and now i can receive raw data from a lot more devices, plus it's faster in react...

[@squalazzo]

info here: github.com/xoseperez/espurna/wiki/Hardware-Itead-Sonoff-RF-Bridge---Direct-Hack

[@Pinkywafer]

@@squalazzo It is the same hardware hack - The link to the espurna page is already in the description

[@zoltar99]

Great video, I'm running my two RF Bridge devices on Tasmota and wondering what would be the advantage to migrate to ESPHome, especially since there is no going back to Tasmota once you have made the physical changes. To me the configuration seems more complicated than on Tasmota, it may be because I am more accustomed to it. I have only one device running ESPHome, that is a SonoffSV which I used to open the Garage Door, now changed to a Shelly1 and I found that after we had an occasional power outage, it would no longer work until I restarted Home Assistant. That was rather unpleasant and was the reason why I changed it for a Shelly1. Getting back to my question, in your opinion, what would be an advantage of ESPHome over Tasmota? Thanks

[@jerryaycock]

Got it working - Can't see some of the signals that I saw with Portish- Hope someone comes up with a fix for ESPhome.

[@joeking5211]

Very interesting, just got started with ESPHome in the last 2 days, so a total noobe. So maybe stupid a question but if you have say a D1 mini with your yaml code and it has a cheapo 433MHz Rx & TX module connected to it, does that operate the exact same way as a hacked Sonoff RF Bridge. or have i got totally confused, but if that is so, would it do everything the same or would the Sonoff do/have extras. I ask as i have had a Sonoff hacked RF Bridge using Tasmota for long while and for what i wanted it for was a nogo and wondered if the ESPHome remote_transmitter module features may have more features. Sorry if this is dumb, but as the hours pass getting more attracted to this ESPHome thing but now trying to take in too much info too fast. But whoever came up with that YAML format wants ........ Rgds.

[@keithc397]

Hi, thanks for the video, how do i turn off the internal beep it keeps on making.

[@matheokoning4456]

thanks !! this video helped me a lot. receiving signals really works a lot faster now. sending signals is unfortunately still not reliable. 1 out of 10 signals are not received and can therefore not be used for my heating. am I doing something wrong or is this standard with Rf?

[@Pinkywafer]

Usually if sending RF signals, they are repeated. I would use repeat: 10 RF can be interfered with so easily and cannot be guaranteed that repeatedly 'banging out' a code is the normal approach, (and sadly also compounds the problem)

[@matheokoning4456]

Pinkywafer Yes. have found out that rf signals are not 100% reliable. I changed the protocol for pulse length and made my own sonoff bridge with a D1 mini and a better transmitter than the one in the Sonoff. Works better now.

[@MPElectronique]

You have a beautiful accent. Are you from England ?

[@Pinkywafer]

Thanks. I'm from England, but living in Wales!

[@evertythingtechrelated9715]

Hi, I have a door sensor that sends a tamper, open and closed codes, how can I add tamper code to the same template as open and close?

[@jennygorton3412]

You have two options: a binary sensor can only be on or off (ie open/closed for a door), so you'd have to have a separate binary sensor for tamper. Or you could use a sensor (which can have any value and simply add another else if line to the lambda.

[@evertythingtechrelated9715]

@@jennygorton3412 thanks for the fast reply. I get it now, I'll just use a regular sensor and just have a icon/picture for each state in HA.

[@brucerawiri7170]

Hi Jenny. I have written the sketch and upload to Bridge. It did successfully upload to device and removed tasiota. unfortunately i ended up having to flash manually after this as it did not connect to wifi. Got that sorted and successfully flashed the esphome sketch to bridge, and the bridge is now online. The problem i am having is seeing the codes sent from my PIR sensors and Door Switch. They are now showing in the logs? the log is only showing Wifi signal and uptime in the logs, and not get raw code to use in esphome. Do you have any idea why the PIR and or Door switch codes are not showing in the logs? Thanks in advance. Bruce

[@sebydocky5080]

Great video :) New subscriber. I got a question about ESPhome. I would like to integrate the pressure sensor MS5803-14BA working with I2c or SPI interfaces. Unfortunatly no official yet support for this sensor. Maybe there is a way with the "custom I2c" conponent. There is a lib available for this sensor for arduino. Maybe the translation for ESPhome is not so complex ?

[@Pinkywafer]

It should be possible. I've not tried using custom devices, but there's a good guide in the ESPHome docs: esphome.io/components/sensor/custom.html which should help

[@jerryaycock]

Moved back to tasmota. I can see devices and get codes. reflashed ESPhome. Nothing received - I see this in startup remote_receiver.esp8266:063]: Remote Receiver Signal starts with a HIGH value. Usually this means you have to invert the signal using 'inverted: True' in the pin schema!

[@Pinkywafer]

Try adding: inverted: true In the pin: section of the remote receiver configuration. So you'd end up with: remote_receiver: pin: inverted: True number: 4 Etc I have seen this before, but usually have been able to receive signals both with inverted: True and without. It may also be worth checking that you have a good solder joint from the chip to gpio 4, as Tasmota does not use this to receive signals.

[@jerryaycock]

@@Pinkywafer Works like a champ.. Thanks

[@cristianomaiaBTC]

Fiz todo o procedimento, mas encontrei 2 problemas. Ele não está transmitindo, apenas recebendo. E quando ele reinicia, informa todos os sensores como [off] ao HOMEASSISTANT. Vc sabe como resolver isso?

[@cosseyadam]

Hi. Thanks for the video. I have a sonoff Rf bridge the same a you have. I have carried out the hardware modification but I am confused about how I need to update the firmware. Is it the same way as drzzs using an adapter to connect to a pc or is there another way over network by logging onto the device? (Looks like how you did it) Sorry if I’m being stupid. Thanks Adam.

[@Pinkywafer]

Once you have compiled the firmware, you have 2 choices: If you already have Tasmota on the device, you can just go to the web page for the device and press the "Firmware Upgrade" button (how I did it in the video) or you can connect it to the PC with the adapter (like DrZzs) but flash the compiled ESPHome sketch instead of tasmota

[@kevbite]

I'm curious why you use the remote_receiver component compared to the rf_bridge component? esphome.io/components/rf_bridge.html

[@Pinkywafer]

When i made the video, the RF bridge component did not exist. At the time, the only option in esphome was to do the hardware hack and use remote_receiver

[@kevbite]

@@Pinkywafer thanks that's awesome, I thought it might be something like that, going to have a try with the rf_bridge component.

[@hakanhallberg8570]

Awesome video! I planned to do this mod but my RF bridge is ver 2.2 and a different circuit board. Do you know if it is possible to install Esphome on this ?

[@Pinkywafer]

I'm not sure. If it is still an esp chip, I don't see why not, but there is now a sonoff RF bridge component on esphome, so you may not have to do any hardware mods

[@ilyesmhiri4683]

hi! am trying to do this for 3 days after soldering where i have to plug my bridge ? thank you

[@stickyfinger999]

Hi great video, can I ask a question about what the Automation would look like in HA or even better ESPHome for example, to turn on and off a wifi bulb using the PIR. Thanks.

[@Pinkywafer]

There's a good exercise of this sort of automation in the HA docs: www.home-assistant.io/cookbook/turn_on_light_for_10_minutes_when_motion_detected/ it is not yet possible to call services on separate nodes in ESPHome, unless you use mqtt and publish messages, but if the light was controlled by the same node, you could use the on_press or on_release automations to trigger something else

[@stickyfinger999]

@@Pinkywafer Thanks for that. Keep up the videos.

[@joeastor3221]

Great video, but i’m curious if HA will retain the open position after a restart?

[@Pinkywafer]

I've done some testing with this: If HA restarts and power stays on the rf bridge, the true status is returned at boot, as the state of the sensor is stored on the rf bridge: 1 Window open - stop HA - no change to window - start HA - window shows open. 2 Window open - stop HA - close window - start HA - window shows closed 3 Window closed - stop HA - open window - start HA - window shows open If the RF bridge looses power, HA shows the sensor as 'Unavailable' When the rf bridge regains power, it has lost the sensor's value (stored in rtc memory), BUT: from my testing, after 'Unavailable' HA restores the last known state, so: window open - power off rf bridge - HA shows Unavailable - power on rf bridge - HA shows open (even though rf bridge web interface shows it as closed!)

[@chalidschool]

Thanks for the video! I have a question. I have a doorsensor that sends out open and close with the same code. Can you share any workaround for this. So if the binary sensor notices a signal it should switch the state to open. And if the notices a signal again it should switch to close? Anybody?

[@Pinkywafer]

try something like: - platform: remote_receiver id: door_sensor internal: true rc_switch_raw: code: 'your_code_here' protocol: 2 filters: delayed_off: 100ms - platform: template name: Example Door id: example_door device_class: door lambda: |- if (id(door_sensor).state) { // door sensor is triggered if (id(example_door).state){ return false; } else { return true; } } else { return {}; }

[@angelochimello7902]

my congratulations great video. would you have any curtain code? and can I get feedback if I use the curtain control?

[@Pinkywafer]

Thanks. I haven't actually done any curtains, but check out the ESPHome docs - look for the 'covers' section. You can get feedback, but how accurate it will be will depend on the equipment you use. Ie you could use an end stop cover if you have limit switches, and if you give it the time it takes to go from end to end, esphome will estimate position. This is also true of time based cover, but without limit switches, or you could use a template cover if you have some other method of sensing the position.

[@angelochimello7902]

Pinkywafer thank you

[@JohanBosman1]

I have the same issue as Bruce in the comments below, the PIR Codes does not show in the logs when I trigger it, just nothing appears? what might be wrong ?

[@JohanBosman1]

I opened it up and scraped the lines more and then it worked.

[@matthewbuschur6466]

Glad to hear about the increase in speed. I'm in the process of trying this out, basically followed all your steps. I did the hardware mod. Created an esphome sketch. Uploaded it to tasmota's ota update, and now it won't connect to the wifi. I checked my credentials and they are right. Not sure why it won't connect. I can't get it to connect to the computer through ftdi to reflash it either. Any ideas?

[@Pinkywafer]

I'm afraid I can't say for certain. If tasmota was still running fine after the hardware mod, there shouldn't be any issue with the mod, so that would suggest either a bad flash, or an issue in the ESPHome sketch you have uploaded, if your credentials are correct, I'd check the IP section. I have also had some devices that did not flash from tasmota on the first attempt, but after a failed flash, the device has always rebooted to tasmota after a power cycle. FTDI should still be available with the switch set to off.

[@dartfrogdk]

try to add a fixed IP

[@matthewbuschur6466]

Weird, yeah I tried flashing like 30 times lol. Switch set to off and everything. I also tried setting it to a fixed ip in unifi, but it's not even showing an ip. It pops up in the unifi client list but under up it shows "-". And it says it's connected to lan instead of my access point which it obviously isn't.

[@matthewbuschur6466]

@@dartfrogdk IP not up*

[@dartfrogdk]

@@matthewbuschur6466 did you change or set the ip in esphome yaml file? Remember to set it to your ip range. Try FTDI to flash it

[@frogeye22]

I'm currently using tasmota on my rf bridge, just how much better (reliable) would this mod make things. I'm planning on using an rf sensor to activate a sump pump connected to a wifi socket and am keen not to miss a signal from the float switch. Thanks

[@Pinkywafer]

I wouldn't want to guarantee that a signal would never be missed. Sadly using RF there is always the possibility. The reliability is going to depend a lot on the rf noise in the area, the range (which remains the same) and any obstructions, From my experience, there has been no noticable lag compared to tasmota, and the only signals I've missed have been when signals overlap, although it may be possible to improve the reliability by adjusting the tolerance, filter and idle values of the remote receiver component

[@anuadu]

This mod with ESPhome certainly made it a little faster and easier to manage automation within ESPhome, but at the expense of transmitting codes reliably. My YAML snippet as follows, none of the switches trigger the 433mhz device. I can see the code being transmitted is correct on my remote decoding device, but the pulse is all over the place. Tasmota with stock RF firmware used to send MQTT message "RfSync 9400; RfLow 320; RfHigh 880; RfCode 14384325"; I can see decimal 14384325 = to Binary '110110110111110011000101'. Do you know if there is a way to set the RfSync, RfLow and Rf High in ESPhome? remote_transmitter: pin: GPIO5 carrier_duty_percent: 100% switch: - platform: template name: "TestSw1" turn_on_action: remote_transmitter.transmit_rc_switch_raw: code: '110110110111110011000101' - platform: template name: "TestSw2" turn_on_action: remote_transmitter.transmit_rc_switch_raw: code: '110110110111110011000101' repeat: 10 - platform: template name: 'TestSw3' optimistic: true assumed_state: true turn_on_action: remote_transmitter.transmit_rc_switch_raw: code: '110110110111110011000101' protocol: 1 repeat: 6 turn_off_action: remote_transmitter.transmit_rc_switch_raw: code: '110110110111110011000101' protocol: 1 repeat: 6

[@Pinkywafer]

You could try setting your own protocol. instead of using protocol:1 you can adjust the pulse length, sync etc Have a look at esphome.io/components/remote_transmitter.html#remote-transmitter-rc-switch-protocol for all the options. I haven't tried it, but i'd try protocol: pulse_length: 9400 sync: [320, 880] As a starting point, but you might have to try various different values in the protocol section.

[@anuadu]

@@Pinkywafer Thankyou, after a lot of trial and error, I have got a few remotes now working. I have a frequency and code reader device that can detect the pulse width, however setting this did not initially work. Setting the pulse width and then adding a 100uS delay between repeat did the trick. I can confirm that that pulse width has to be adjusted for each type of remote. In my case, I have six RF fans from 4 different manufacturers. Another issue is the Sonoff RF ran out of memory after adding three fans (1fan=5 switches- on, off, high, medium & low). I quickly moved to ESP32 with an elCheapo 433mhz transmitter, works well now. ESPHome based RF works super fast, it was worth the effort.

[@Pinkywafer]

Excellent! Glad you managed to resolve this.

[@avant20full]

Hi ... how could that buzzer (on the Sonoff) make sound when the PIR sensor detects movement (just like that red LED that lights up) ... I want to use the system as it is ... sensor and sonoff without internet ... thanks!

[@Pinkywafer]

Hi. I'm not sure what you mean. There is not a buzzer on the rf bridge

[@avant20full]

it is definitely a buzzer on the board ... it makes a sound when you pair the PIR sensor ...

[@Pinkywafer]

@@avant20full My apologies! it was a good while since I've been "in" the rf bridge and I never used stock firmware, so had forgotton all about the buzzer on learning mode! I have looked into it, and it seems that the buzzer is controlled by a second microcontroller, so the only option would be to make a further hardware hack or add an additional buzzer to the last free GPIO (I think it's GPIO2 - labelled SDA on the header if I remember correctly)

[@avant20full]

@@Pinkywafer I would be very happy if you could help me, but thank you anyway!

[@andy_baam]

Thx you so much for this video. I have question: after migration to esphome can Sonoff RF read and send rolling codes?

[@Pinkywafer]

Rolling codes are not supported. It would not be easy, but may be possible to do it via lambda code, but even that would only be possible if the algorithm for the code change was known

[@andy_baam]

@@Pinkywafer thank you for the answer and is any simple solution for rolling codes? (need for my garage gate and fence gate) where I can find info about lambda codes

[@Pinkywafer]

The code algorithms are not usually available, as it would be a security risk. I would imagine that it would take a lot of effort and research to work out how they work. You can read about lambdas on the esphome website, but the code is essentially written in C

[@andy_baam]

@@Pinkywafer thx and have nice christmas

[@andy_baam]

i need help with some other thing in HA can i send you e-mail?

[@joseblanco981]

Thanks, Are RF nodes easy for cloning? I mean can I emulate the code they send and the bridge will think its the node we associated ?

[@Pinkywafer]

In theory, anything that can transmit the same rf code would be assumed to be the node associated. The rf receiver has no 'linking' with the node, it is only aware of the codes it needs to respond to. However, most devices (at least those I have) seem to sent a code which is 24 binary bits long (that's a total of 16,777,215 possible codes if my maths is right!). Certain devices (such as car door locks for example) use a system where the code changes with each use. The rf bridge would be unlikely to be suitable for use in this application without knowledge of the relevant algorithms for changing the code. What's your use case?

[@joseblanco981]

@@Pinkywafer I'm thinking if my neighbors are courious like us, can send orders to my system. Activating alarms or turn on/off lights... Just thinking... ;-) Thanks !!

[@Pinkywafer]

In theory, yes they could. If they could find the right code... this is however no different to a conventional wireless alarm system in that way!

[@KhaiNguyen-ty5fm]

Since I have 3 RF Bridges, All the sensors should be all 3 bridges?

[@Pinkywafer]

I'd just put each sensor on whichever bridge has the best signal... if you have 1 sensor 3 bridges, it'll show as a binary sensor 3 times in home assistant, which could get very confusing!

I hate tasmota on this rf bridge due to memory limitation for adding rules being limited to only 500 chars. Does anyone know how many sensors can be added to one rf bridge using esp home?

[@Pinkywafer]

I would guess that you can keep going until the available progmem is reached... as the way each sensor is defined could be different, it's not possible to say how many that would be, but for ota flash, the sketch needs to be just under half the available memory size, so you're looking at a compiled binary size of about 500k

[@homeautomationmadeeasy3276]

Some videos show that they flash even without soldering, just pushing and keeping pressed male jumper wire pins with fingers. Is it really possible?

[@Pinkywafer]

If you are able to make the connection for the length of the flash, then yes, it is possible. With through holes for TX, rx gnd and vcc it is often quite easy to flash without soldering. The hardware mod in this video is permanent, but the flash can be done without soldering

[@homeautomationmadeeasy3276]

@@Pinkywafer thanks for prompt reply. Unfortunately I have never been successfully to make the connection by pressing pins with fingers. As I can observe the holes itself don't have any connectivity, but, the upper and lower part of hole has connectivity metallic space. If it's possible how to go for flashing without soldering just by pressing with fingers

[@Pinkywafer]

It depends on the device, most boards I've done this way have connectivity through the hole. I find the easiest is to use jumper wires with male DuPont connector through the holes and apply gentle sideways pressure, so "tipping" them in the hole

[@MatthewSmithx]

@@Pinkywafer I'm sorry. I'm a big dummy. what does the hardware mod do? is it needed if I have already flashed with tasmota?

[@Pinkywafer]

It bypasses the microcontroller to allow the esp8266 to directly control the transmitter / receiver.

[@fred7flinstone]

I am trying to upload the esphome binary, but I'm getting "upload Failed Upload buffer miscompare". Any advice anyone?

[@fred7flinstone]

In case anyone else gets this error. I re-flashed with tasmota-minimal.bin issued the command "SetOption78 1" in the console and re-flashed with the esp binary.

[@Pinkywafer]

Nice find... Tasmota binary is now very large, so needs the minimal to be able to upload many other binaries OTA. I think setoption78 allows uploading other firmware (without it, tasmota checks that the firmware you're uploading is also a version of tasmota)

[@jerryaycock]

Just got it converted to ESPHome. Not seeing my devices. Can I flash Portisch on this build or do I need to go back to tasmota?

[@Pinkywafer]

The wire from the RF receiver to the gpio pin bypasses the chip so all decoding is done on the esp instead of the chip. Esphome cannot communicate with the chip, so to do this, you'd have to remove the wire and go back to tasmota

[@Pinkywafer]

Actually, thinking about it,. You shouldn't need to remove the wire as the original path is still there. Flash tasmota to try portisch.

[@ygreq]

I recently lost my last backup and I had to resort to an older version. In between those versions, I installed RF Bridge on ESPHome. Now RF Bridge does not show in ESPHome. It does show in Configuration->Integrations. But it gives me errors when I try to configure it. It does not let me access it via its IP. And it does not let me upload new code to it via ESPHome, of course. Do you know of any solutions for this? Thank you so much!

[@Pinkywafer]

I can't see why it gives errors connecting via integrations, it may be worth rebooting the rf bridge (or even the router as mDNS issues can cause connection problems) The code for esphome is only stored in the config/esphome folder though, so if you've lost that, it will never show in esphome. In that case, I'm afraid that the only solution I can think of is to create a new yaml for it and flash using ftdi.

[@ygreq]

@@Pinkywafer Thank you, Jenny, for looking into this. The router has been started many times since then. BTW, it gives me this error: "Can't connect to ESP. Please make sure your YAML file contains an 'api:' line." And it gives me the same error with a d1 mini I also setup in between the backups. One other quick question. What is the port it uses in Integrations? It is inputing by itself port 6053. Maybe I should change this to another port? Otherwise I was thinking of trying to reinstall Tasmota. That would mean remaking the old hardware connections. Hope it will work

[@ygreq]

Sorry to bother you,@@Pinkywafer I managed to reflash tasmota. But I cannot seem to get the esphome binary onto the rf bridge. BTW, the first time I installed it, it gave me errors a few times before finally it worked. Did you happen to have this problem?

[@jennygorton3412]

@@ygreq I have not had this problem, but it could be due to the file size... try flashing a minimal tasmota first. I can't think of anything else I'm afraid

[@ygreq]

@@jennygorton3412 I got the answer with the help of someone from the HA FB group. It seems this is a new feature or something. It worked!! Thank you so much for the lovely tutorials and for getting the time to reply!

[@eyak69]

could you upload the configuration.yaml thanks

[@Pinkywafer]

My esphome yaml is in on my github... link in the description. There is no configuration yaml entry for home assistant as it uses the esphome API, so it is automatically configured when you set the device up on the integrations page in Home Assistant

[@cristianomaiaBTC]

Não consigo fazer funcionar o Transmiter. Alguma dica?

[@Pinkywafer]

Try something like: switch: - platform: template name: send_code turn_on_action: remote_transmitter.transmit_rc_switch_raw: code: 'your binary code' protocol: 1 repeat: times: 10 wait_time: 10ms

[@cristianomaiaBTC]

@@Pinkywafer bom dia. Não funcionou, pois o esphome não valida este código

[@Pinkywafer]

Check the indentation and try with : - before remote_transmitter.transmit_rc_switch_raw:

[@kennethfribert6074]

Hi Pinkywafer, so I got a second RF Bridge, and I've modded it, and it's working great for my sensors. But I have a problem when the bridge is booted, all the sensors are 'undefined', and I have to activate them once to get a known state in them, is there a way I can make them go to a specific state when it reboots?

[@kennethfribert6074]

Ahaa, I actually just found an answer, I can do a id(id_binary_sensor).publish_state(false); in a lambda in the on_boot, so that's great, now they will react immediately.

[@Pinkywafer]

@@kennethfribert6074 I'm afraid doing a publish_state at boot may be the only way to do this at the moment. a recent change to ESPHome seems to have caused this

[@Pinkywafer]

I've opened an issue around this on esphome github: github.com/esphome/issues/issues/828

[@joeastor3221]

@@kennethfribert6074 can you put your lambda example in the description. Thx

[@kennethfribert6074]

@@joeastor3221 under the esphome: on_boot: then: lambda: |- { id(stairsswitch_above).publish_state(false); } And I've just repeated that line for each sensor.

[@NunoSoares22]

I got an "Upload Failed" after doing all the hw modifications. I have a R2 V1 board. Can you help ?

[@NunoSoares22]

I managed to upload the firmware directly onto the esp chip

[@Pinkywafer]

Excellent. The usb port is not connected for flashing, so ftdi is the only option

[@NunoSoares22]

@@Pinkywafer I have some issue ... All is working great but after an hour or so the bridge stops procesing the signals!? I no longer see the codes on the esphome logger. Any ideias ???

[@Pinkywafer]

I don't know if it's the same issue, but there is a strange rebooting issue which occurs randomly which only appeared after an esphome update (I'm not sure which version) and I'm still trying to figure out what has caused it. If it is that though, it normally comes straight back online and continues reporting.

[@NunoSoares22]

@@Pinkywafer it doesn't look like it's the same.. Mine has been on for a few hours and nothing

[@kxt3084]

i've followed the video, however I cannot get the bridge to connect to ESPHome. Firmware flashed from Tasmota 6.5.0 . Web server works but cannot get status to work, it just shows as offline and as such 'show logs' does not work neither does OTA. Any ideas?

[@jennygorton3412]

Try using a manual ip address in the esphome sketch. I have seen this happen before if using dhcp assigned

[@kxt3084]

Manual IP has already been assigned

[@jennygorton3412]

I can't think of any other possible causes. You could try just a very minimal esphome sketch with Wi-Fi and logger and maybe just the status sensor. You could try clearing your browser cache. Beyond that, I can't think of anything unless there is a networking problem

[@jennygorton3412]

Sudden thought, do you have the subnet set correctly?

[@kxt3084]

Subnet is correct, will try a basic sketch

[@pozekool]

Very good video, I remove tasmota from my Sonoff RF and now I wonder how is possible to send a code. Here is my code switch: - platform: template name: RF Power Button turn_on_action: - remote_transmitter.transmit_rc_switch_raw: code: '010101010101010100000011' protocol: 1 remote_receiver: pin: 4 dump: rc_switch tolerance: 50 filter: 4us idle: 4ms remote_transmitter: pin: 5 carrier_duty_percent: 100% but nothing's happen when I activate the switch in HA. Any ideas ?

[@Pinkywafer]

I have no devices for testing the transmit I'm afraid. I have recently done this mod for someone else, which allowed me to test the transmit (one rf bridge to the other). I used the code the same as yours, but added: repeat: times: 10 wait_time: 10ms The code was received by the other bridge (without the repeat the code is only sent once)

[@pozekool]

@@Pinkywafer thanx a lot, it works ! The correct code, since 1.13 is : switch: - platform: template name: Remote Front Gate Control turn_on_action: remote_transmitter.transmit_rc_switch_raw: code: '010101010101010111000000' protocol: 1 repeat: times: 10 wait_time: 10ms

[@gasxet]

Thank you very much very interesting, but in this hack github.com/xoseperez/espurna/wiki/Hardware-Itead-Sonoff-RF-Bridge---Direct-Hack they put resistor (seems 680ohm) in place of the wires, it is better with or without?

[@Pinkywafer]

Either should work fine. The resistor essentially acts as a fuse link, so that if there is any issue with your soldering, the magic smoke is not let out!