For me it was critical (one of my lights change light mode after quick turn-off-turn-on). With ESPHome I have immediate reaction.
Okay, maybe my MQTT broker on HA was not configured properly, maybe there some settings which can speed up responses. But now I have no need in MQTT, as I use only ESPHome devices.
I found, that ESPHome RF protocol need to be adjusted to work with some of my RF keyfobs. When I did this, I got instant response, at least from the remotes I have.
If TASMOTA works for you and you have no problems - good, no need to change it while it works. I just was unhappy with slow response and with MQTT broker that was running only for one device in HA network.
FYI, I make heavy use of MQTT for other integrations with Home Assistant,and use mosquitto running in a Docker container, alongside of Home Assistant. I believe it has higher performance than the built-in MQTT broker. I also find it handy to use MQTT rather than the newer Home Assistant direct integration in ESPhome because I can easily monitor what’s going on with a simple MQTT client subscribing to a relevant topic.
Glad the ESPhome solution is working great for you! I’m really pleased with Home Assistant having so many options available to solve these problems as they come up, and based on your circumstances.
Wow! Eagle eye!
Naah, it just looks like soldered on the photo, there is no actually the connection (and should not be), wire end is floating above the hole.
But thanks for pointing on that, I removed it
Have you used this approach with sensors that send multiple codes? Like a door sensor that sends one code when open and one when closed? Can they be “merged” into one binary sensor at the esphome level, or do they have to be treated as two separate sensors and merged in HA?
I did not find a way how to merge several codes into one sensor, I don’t think that is it possible. So door sensor with two states, open/close, will require to binary sensors and automation in HA (and I don’t think that it is a big problem).
I have one remove, where each button (4 pairs) send 4 different codes, cycling them on each next button press. So to you this remote, as example, to control 4 sockets with separate buttons for ON and OFF, I will had to create… 32 binary sensors… for 4 sockets. And I have TWO such remotes
Done. NodeMCU is working now with RF receiver and ESPHome & HA. I did some test month ago but without luck.
First of all, I used 3.3V before for RF receiver. Looks like it need 5V, so I connected it VU pin on NodeMCU (it have 5V there). Next, in my early NodeMCU config there was error, pin: 4 is NOT the same as pin: D4. So as it connected to D4 on the board, it should be pin: D4. I got first signals after this, but only from one of the remotes. So I began to play with config and found, that signals can be read with this settings in device config:
Now I have the signals from all the remotes. In compare to Sonoff RF Bridge (I make all changes on it to see the difference in performance between Sonoff Bridge and NodeMCU + RF), cheap RF receiver get more errors in signal recognition and really poor distance. So I made simple antenna for RF receiver. It increased distance a little, maybe even reduce errors count, but it still works poor. At end I can say, that Sonoff RF Bridge much more precise in recognition and have really good receiver sensitivity than separate RF module. But both can work with ESPHome if needed, without almost any difference in configs. At least, from what I saw on practice.
Also, the same approach should work for non-RF Sonoff devices, it is possible to connect cheap RF receiver there and read the signals (maybe I day I will test this too).
Hi, I note that you said you had really poor range with your 433Mhz receiver.
I think by chance you picked one of the worst performing ones on the market
Have a look at the ones listed on this info page from RFlink below, it has the good info on what modules are best. Trust me there will be a significant improvement with the right quality RX module. Good RX module info
Please help me with the answer to the noob question - how can I first flash the RF bridge with ESPHome after the HW modification (cutting circuits and solder the transistors) ? I dont see the RF bridge connected to the USB port in Home Assistant - only OTA is availlable.
I have tried starting the device with RF button pressed, with the internal switch in both positions (ON or OFF) …nothing I read is working.
Do I need to use the serial adapter to flash it?
connect usb-ttl adapter to computer while keeping the rf button pressed
flashing worked well, but no success with the RF part despite careful mod, reversed the mod and tasmota still works. will need to debug more anothter day
edit: hmm, nexa transmitter had dead battery, oddly enough worked with fresh battery. the other transmitter seems to use a different protocol which isn’t supported by rc_switch, but was supported by RFControl lib.
So I’m going to have a crack at this too (Sonoff RF Bridge on the way), am new to this, and guess I need a usb-ttl adapter. Could someone point me to one please? Like maybe one of these? I don’t have a clue what I’m looking at. ta.