Sonoff RF Bridge Easy Setup with Tasmota Rules and the trigBoard
ฝัง
- เผยแพร่เมื่อ 9 ก.ค. 2024
- Easy setup of wireless sensors utilizing the Sonoff 433mhz RF Bridge. Custom MQTT topics and automations with Tasmota rules all self contained in the bridge. We also check out the trigBoard from Kevin Darrah with deep sleep modes and custom sensors all from a battery powered ESP8266 based board.
Sonoff RF Bridge - amzn.to/2WF2XIM
TrigBoard - www.kevindarrah.com/wiki/inde...
Products I use and recommend - www.amazon.com/shop/digiblurdiy
Come chat with us!
-=-=-=-=-=-=-=-=-=
Discord - / discord
Patreon - / digiblurdiy
How to Flash the RF Bridge with Tasmota: • Sonoff RF Bridge with ...
Wireless Sensors
-=-=-=-=-=-=-=-=
Door - www.banggood.com/GS-WDS07-Wir...
Water - www.banggood.com/DY-SQ100B-Wa...
Sample Home Assistant Sensor Configuration
=-=-=-=-=-=-=-=-=
- platform: mqtt
name: "Freezer Door"
state_topic: "RFBridge/sensor1"
availability_topic: "tele/RFBridge1/LWT"
qos: 1
payload_on: "Open"
payload_off: "Closed"
payload_available: "Online"
payload_not_available: "Offline"
device_class: door Please note, the product links above could be affiliate links, using them could earn digiblurDIY a small commission of purchases potentially helping with future video projects. Thank you! As an Amazon Associate I earn from qualifying purchases. Please note, the product links above could be affiliate links, using them could earn digiblurDIY a small commission of most purchases and helps with future video projects. Thank you! As an Amazon Associate I earn from qualifying purchases. - แนวปฏิบัติและการใช้ชีวิต
Perfect timing on this video. I just received my Bridge this weekend! Many Thanks!
Exactly what I was looking for...
Thank you.
Subbed.
Welcome aboard!
Thanks for this video. I was unaware of being able to do the rules natively on the bridge. Spent days trying to work how to do it via node red.
Thanks for a very helpfull video !!!!! It helped me a lot!!!
Thank you for the tutorial this was super useful today :)
You're very welcome!
Great Job!!
Great work!
One of the reasons that I'm tinkering with a 433MHz bridge is that I'm limited to 10 device connections in one of my applications(remote property monitoring using mobile hotspot.)
I'm using Wyze cams and Sonoff switches (with their apps) for monitoring and I'm thinking that IF I can control at least 4 (and perhaps more) devices with the RF bridge then it would be very VERY useful.
......IF I can ever get HA working reliably enough....which is ALL on me.
If I were a real technician I might be able to cobble together something like an I2C solution for sensors and such, but that's a different squirrel to chase after on a different day.
Thanks again!
Great video. Thank you.
Wow, only $13, that's cheap! I bought a Hook Hub a while ago for like $45. This would work 100x better for not having to go out to the cloud. Thanks for the video.
Thanks!
Thanks for the video.
Do you know if the water sensor sends a battery low notification to the hub ?
If so what is the data payload and how would you make a rule to send that on to HA.
Thanks
Great video. Anyone measured the effective communication range of the bridge? Would one of those be enough for three floors?
Subscribed !
Thx for the nice video. Allow me a question. Do you have a hint why I got only a Data from the DW-Sensor when I separates the two parts, but not when I put them together? Thx in advance for your support
Thanks! Спасибо!
The part with Rules works great in OH3 with Door sensors that only have one code result i.e. sensor with only door open and no close code.
Travis, Thanks for this video. I was having problems with the way HA processes the codes from MQTT, assuming that a topic can only have a 2 states and it wants you to make more topics if you have more sensors. This method does that. I was picking the 'data' code directly off the tasmota MQTT output and it was spamming the error log with warnings from 8 other inputs any time one of them sent a code. Your rules worked great.
Oh, BTW, your comment on make sure you spell it right, well, I should have listened to that better I guess. I didn't know how to spell the word RfReceived either and didn't spot it until troubleshooting for an hour or 2....
I used your rules pretty much exactly.
This is what my binary sensors look like when I was done for dual code devices:
binary_sensor.yaml
- platform: mqtt
name: "Bathroom"
device_class: opening
state_topic: RF_Bridge2/BA
payload_on: 'OPEN'
payload_off: 'CLOSED'
force_update: false
availability_topic: RF_Bridge2/tele/LWT
payload_available: Online
payload_not_available: Offline
This is what I did for single code devices because my rule buffers were filling up:
I have an automation that watches for any code to come across the bridge. It then makes the data code a topic, and a binary sensor watches for the topic to go on and sends the momentary sensor to on, triggering whatever is watching that sensor.
automations.yaml
- id: bridge_2_breaker
initial_state: 'on'
alias: RF-Bridge 2 De-multiplexer
trigger:
platform: mqtt
topic: RF_Bridge2/tele/RESULT
action:
service: mqtt.publish
data_template:
topic: "RF_Bridge2/code/{{trigger.payload_json.RfReceived.Data|string }}"
payload: 'ON'
binary_sensor.yaml
- platform: mqtt
name: "Moms button1"
device_class: light
state_topic: RF_Bridge2/code/8D63A4
payload_on: 'ON'
payload_off: 'OFF'
off_delay: 1
availability_topic: RF_Bridge2/tele/LWT
payload_available: Online
payload_not_available: Offline
Wow.. Now that's a video comment! Amazing stuff. Going to have to dig through that this weekend and try it.
@@digiblurDIY The whole sonoff bridge thingie subject is both awesome and in need of love. You did an awesome job with the topic in this video and people will find this as they struggle. Thought I could add to it a bit.
The only problem now is 1500 characters space for rules. If you keep the names short thats like 10 2-code devices. I guess there's no reason I can't drop a few a bit longer rules (reading the data MQTT message directy) on another tasmota device and let that push the 2-code topics. Node-red could monitor for the data directly and deal with it I bet, but I'm not a node-red person. For whatever reason HA decided that MQTT topics can only output 2 states, and anything else it whines about...
So.. this worked fine until I tried to run some PIR sensors that need to react right NOW... If you analyze this here's what's happening with my automations...
- PIR gets triggered, it sends a 433 RF signal
- RF-Bridge sees the signal, converts it, sends out an MQTT to announce
- HA sees that topic with automation, sends out another MQTT on a new unique topic
- HA sees that new topic and triggers a binary sensor.
- HA sees that binary sensor in another automation and triggers the light.
Takes a couple seconds... Definitely have to fix this... I should be able to combine the middle 2 or last 3 HA actions into a one action.
I might just make a tasmota rule on my light look for the rf 433 MQTT message and react. I would have to add an MQTT topic from my dark/sun sensor because that is also in the logic so that the tasmota switch has that info.
@@digiblurDIY I just found this and implemented it. It works like the rule process you installed here, but puts the heavy lifting on to the HA computer and off the little bridge box. Also eliminates the limit like 4 or 5 devices per rule and 12 or 13 per bridge. community.home-assistant.io/t/sonoff-rf-bridge-strategies-for-receiving-data/108181
I've also done it with NodeRed in little easy method too without having to do any JSON stuff. I have a rule that pushes any RF commands to a topic and then NodeRed listens to the topic and has a switch after it. Pretty simple and easier to see as well to do various logic.
when i have 2 rf pir sensors how can i configure?
Hi this has been so helpful.
All fine until I try and transmit from the RFBridge.
Could you do a video on transmitting from the rfbridge.
Thanks B
Great video! Can you do a video where you have the sonoff bridge learn a remote such as a celing fan control?
I only had a few sensors and didn't have anything that I can control with 433mhz unfortunately.
Great tutorial , is there any chance to use 433mhz button (sends only one code) as toggle switch to control lamp.
Yes. Just have a rule push that event as a toggle.
Has anyone tried flashing the Sonoff RF Bridge O-T-A? Is it possible?
Great video, thank you. Is there a way to overcome the 512 bytes limitation of the rules buffer? It's too short for me...!
They added compression a few versions ago.
Hi,
I have just installed two sonoff sensors (motion detection, window sensor)
I can see a red led light on the (Tasmota) Sonoff bridge everytime one of the sensors is triggered,
But nothing on the tasmota console about these events.
Thanks for your help
You might have to turn on more logging to see them. Try weblog 4
Awesome video thanks for sharing! What are you thoughts on a trig board for motion detection? I want an indoor and out door motion detection. How much is the trig board? I didn’t find how to purchase it easily from the link. How is the Battey life? Obviously mileage will vary depending on how often it’s triggered.
He sells them on Tindie. I linked his wiki that has the Tindie link and more but here it is too. www.tindie.com/stores/kdcircuits
Battery life is going to be based on the battery size you get for it. Pretty cool board with some advanced features. He has a TH-cam channel as well and I believe he just did a PIR sensor one. Here is his channel. th-cam.com/users/kdarrah1234
Thanks Travis , you rock dude . Have 5 door sensors working and the best of all it keeps the state of the door. WE in SA often have power cuts and therefore my PI gets reset etc. Thanks again for your awesome videos and how you explain things. Another question, I bought a PI 4 and would like to move my HA from my PI 3B to my PI 4 ? Which is the best way ? Thanks
Take a snapshot from the 3B. Download it. Install the 4 with HA. Upload the snapshot and away you go. Make sure to assign it the same IP so you don't have to reconfigure any switches.
@@digiblurDIY Thanks , appreciate it. Meant to ask how many Rules can I place on the Bridge ? and if I have more sensors and want to add more is there a way around the limit of rule size etc
You can put 511 characters in each rule buffer. If you run out or find it hard to manage you can switch it to NodeRed.
Great video,
Can you publish a sample of the Hass yaml code for the Water sensor?
I'm trying to get the water sensor in Hass but I don't believe I have the yaml correct.
Thanks
I had it as a motion type and it is the same binary sensor setup except you can change the class to get the different icon.
Hi, sorry for the questions but new to OH3. I tried your way watching this video and it works, so simple, like you said dont have to worry about JSONPATH. I am getting the single code door sensor to Open and Close after 5secs. But would like to know how to do the following.
My door sensor has only one code for Open no code for close. When it comes on it stays on Open all the time. How do i get it to turn to Closed using OH3.
Do the same as I did for the water sensor, a timer to set the off again.
@@digiblurDIY Yes it works so easy but i would like to see how it works in OH3. Not many people are working on OH3 except one German guy.
I have 8 water sensors. How would i make one rule that acts on any RFReceived and sends the RFReceived#data to MQTT so i can run the logic in Node Red? Im a newbie.
Between this video and DrZZZs, I was able to get my bridge flashed and running. Thank you!
This is the way I do it.. rule1 on rfreceived#Data do publish rfBridge/all %value% endon
Great job on getting it going!
Great Video.
I noticed you have a card in HASS with what looks like all of the tasmotized device %topic% and firmware version... Question... How did you do that?
I want to create a dashboard where I can manage all my devices via MQTT on the tasmotized device. This will allow me to do away with http on the device.
First an Automation that fires at startup or manually triggering it: gist.github.com/digiblur/b8c28c07fae3859542a67a2e27646bc4
Then here's a sensor to pull the version out. gist.github.com/digiblur/6215bb4472dd156907225331b9900fdb
Great video. Are there any RF bridges which use 315 MHz, so I can control my ceiling fan?
I haven't run into any except for a DIY build of one.
@@digiblurDIY Thanks, I ordered 315Mhz RF transmitter and receiver link kit off ebay and planning to read the codes from the remote using arduino or esp8266.
Can you set the low battery in mqtt with this type of door sensor? I got the code but dont know how to make it show up in Hass. Same thing with the tamper code.
Can you send a snip of the log with it? TH-cam comments might eat the code up so feel free to email it or use the discord link in the channel to hit me up.
The water leak detector apparently only sends out one status message - which Travis covered. It looks like it sends out the same status message if the battery voltage drops to around 2.2V. So if you do get an alert from this device it could be that it detected water or the battery needs to be replaced. I would prefer some kind of "I'm alive" message but it is what it is - and it is cheap...
Zigbee is the way.
I'm liking these cheap water leak sensors more and more. They have excellent range. From my shop - about 80 feet from the house - and thru 2 walls back to my office - the sensor was able to communicate to the bridge. Set up a PM schedule once or 2X a year to just do a quick test of them and make sure I get the notification on my phone...I've only had one actual leak event in my life - knock on wood. The cloth washer cutoff valve stuck in the open position - I became aware of it when I saw a flow of water heading for the den...no major damage but if we had been in bed...
This is an excellent video. Can I ask if there is a technique or resource for editing Rules?
TDM is a great tool for editing rules as it makes them easier to read. github.com/jziolkowski/tdm
@@digiblurDIY Great Thanks
Do you know if these can pick up alarm contacts .. I have a 4 dsc alarm contacts
Not sure, are they 433mhz too? I know there's an extended firmware you can flash to the RF chip in the bridge to expand more to it. You can see more here: github.com/Portisch/RF-Bridge-EFM8BB1 and github.com/arendst/Sonoff-Tasmota/wiki/Sonoff-RF-Bridge-433
How did you get the trigboard to work with mqtt? I can't find any info on this (unless I'm just missing something obvious)
I modified his sketch to use mqtt instead of the notification service it had. I can send you the changes I made if you want. Email me at the channel name on the Gmail domain.
Email sent, thanks!
Hi Is there a new update to add these door sensors to Home assistant without writing rules. Also please can you point me to where you did a video using NodeRed to do these same door sensors with open & closed codes. I would appreciate it. The problem I have is I bought more sensors but don't how to add it to the original Rule. Unable to see my original rule in the console. Thanks
I haven't done a video on the new way I did it. Think I showed it on a live stream once but not going to make you dig for that. Shoot me an email at the channel name on the Gmail domain and I can send some screenshots of mine. Definitely the way to go when you have a ton of sensors.
@@digiblurDIY Thanks Travis appreciate it
Great video! Interesting concept, currently I'm using the "tele/RFbridge/RESULT in my HA configuration, but I get tons of these errors "Mon Feb 04 2019 08:05:56 GMT-0700 (Mountain Standard Time)
No matching payload found for entity: Garage Motion with state_topic: tele/RF_Bridge/RESULT" Will using rules stop this? Thanks Dale
Bingo! You nailed it. I had this same issue plus I was spending time to break it down in NodeRed along with retain issues, pushing to custom unique topics just seemed so much easier to me on the backend of managing things.
@@digiblurDIYGreat. I get a lot of the same msgs. Once I wake up, I will watch the video again and see what I need to change. I have numerous sensors as well as several 433mhz 4 button key fobs that I use to turn stuff on/off. Thanks @Dale Scott for bringing this up.
Michael Henderson
Search the home assistant community website for the error. It is known and there are ways of fixing it by commenting out some lines in a python file. You can run a custom version of the file if you create a custom_components folder in the folder your configuration.yaml resides and an MQTT folder in the custom_components copy the binary_sensor.py file there. Comment out the that output the warning message. They are in an ‘if else’ construct somewhere around line 145.
I’m writing on an iPad and don’t have access to my Pi so the above is from memory. Latest version home assistant.
@@ozriblit This works even better. No wierd custom component stuff, it uses about a dozen lines of python to do pretty much what Travis did in this video. community.home-assistant.io/t/sonoff-rf-bridge-strategies-for-receiving-data/108181 Works fantastic.
Great videos. How would i be able to cancel the rules that i have made? Thanks.
Just type rule1 then two quotes. Change the number of course if needed.
@@digiblurDIY Thank you.
If i use the Backup Configuration does it back up all the rules to?
Yes. I have done this to duplicate switches.
H, when i learn Tasmota console rfkey1 2 i get a result data 000000. Any ideas?
That might be a sensor that has a different type of code.
I was thinking of making several sensors with an ESP-01 + MQTT + HA. But seeing your video, it might be less work to buy a Sonoff Bridge.
Go with the Sonoff easy
Very Nice Video, being a newbie, where can you fine a list of rules for the Sonoff, and is there a video that shows how to setup the MQTT in HA and on the Sonoff device? Thank you.
Are you using HassOS?
@@digiblurDIY Yes I am.
I don't have one since I don't use HassOS. I just run a docker container of it. Juan does several great videos on HassOS and should just be a simple add on in the store.
th-cam.com/video/qnCRcGTznXs/w-d-xo.html
Hi man. Inspiring video. I was wondering if with tasmota rules you can set a command that when an rfraw command is a trigger you can repeat that command for 5 more times?
I'm asking because I have Dooya blind motors and I'm looking for a way to simulate a long press of the stop button.
Yes you could do a backlog command and put delays in between as well. How quick do you need the 5 messages?
@@digiblurDIY This is my payload_stop: payload_stop: "rfraw AA B0 35 05 04 12C0 05FA 015E 02E4 230A B481A3B2B2A3A3A3B2A3A3A3B2B2A3B2A3A3B2A3B2B2B2B2B2B2B2A3B2A3A3A3A3B2A3B2A3B2A3B2A3 55;rfraw 0"
I need to repeat the code 6 times to simulate the long button press.
@@digiblurDIY Could I set this backlog command as the payload_stop in hassio as well?
@@digiblurDIY So i tried the backlog command. It works in console for 3 consecutive commands... but if I try for a fourth it doesn't execute the backlog command :(
@@digiblurDIY Doesn't work for no more than 3 commands. I think it has to do with the line being so long in the console.
I had intended on making my own Wifi reed switches. But, after looking at the 433Mhz options I decided the RF bridge and 2-code sensors was the way to go. So my first place to look for advice was here and Dr. Zzzz. Once again your walkthrough awesome. Much appreciated - Thanks!
I do have a general question about the consol. Where would I find documention to learn how to use the consol?
Thanks again - great work!
Honestly just look at the commands section of the Tasmota Wiki. It has all of them and explanations right there.
@@digiblurDIY Okay thanks, a basic case of RTFM, haha..... I'll go back and look at it.
No worries. Let me know if you need help.
@@digiblurDIY Any idea why I get this error msg: "Connect failed to 192.168.254.100:1883, rc -2. Retry in 10 sec" After flashing and re-flashing. The bridge (board ver 1) cannot connect to the MQTT broker (mosquitto HASS.io Add-in). I do connect with WiFi as I can talk to it via the IP and of course the router shows connected , and MQTT is working fine I checked that with MQTTfx. I also flashed it Tasmota 6.6 and 6.5 .... same result. I researched the problem, but didn't find any answers. Don't expect you solve my problem, just wondering if you have run across this or heard of it happening.
Remove the HTTP part. For the host just put the IP and that's it.
I am just trying to get started with MQTT using an an RFBridge and followed the video, I set up the water sensor (single trigger) without a problem.
But the open/closed sensor does not work despite the fact the Tasmota console appears to give me back the correct results as below:
00:15:43 MQT: RFBridge/sensor1 = closed (retained)
00:15:50 MQT: tele/RFBridge/RESULT = {“Time”:“1970-01-01T00:15:50”,“RfReceived”:{“Sync”:13900,“Low”:460,“High”:1350,“Data”:“30190A”,“RfKey”:“None”}}
00:15:50 RUL: RFRECEIVED#DATA=30190A performs “publish2 RFBridge/Sensor1 Open”
00:15:50 MQT: RFBridge/Sensor1 = Open (retained)
I input the following into the console to create this:
rule1 on rfreceived#Data=30190A do publish2 RFBridge/Sensor1 Open endon on rfreceived#Data=30190E do publish2 RFBridge/sensor1 closed endon
My YAML entry is this:
- platform: mqtt
name: “Freezer Door”
state_topic: “RFBridge/sensor1”
availability_topic: “RFBridge/tele/LWT”
qos: 1
payload_on: “Open”
payload_off: “Closed”
payload_available: “Online”
payload_not_available: “Offline”
device_class: door*
The entity only shows a state of Closed.
Any advice appreciated
I'm a relative newbie but there is often a difference between upper and lower case. Your rule is sending "closed" but your YAML is set to "Closed" - If in doubt, always use be consistent
Hey, can you please help me? i want to set up multiple door sensors. they have only one code dor open so i set up rules for each one of them. When i got to rule4 it said command unknown, so i think you are only alowed to 3 rules. how can i group multiple sensors in one rule? what is the command line to put their codes and timers in one rule? i would realy appreciate your help, thanks!
There are 3 rule buffers. You put them together in each buffer. Rule1 on trigger do something endon on trigger do something endon and so forth.
@@digiblurDIY thank you! you saved the day :) it worked. i couldn't see the correct way to write them all together. Thanks
Great, but what if i get only one code? When i open it
You'd need to do a delay or something just on open. Or get a new sensor.
Isn’t it possible to monitor “tele/RFBridge1/RESULT” on your HA and just configure sensors using the data payloads? No need for explicit publish commands on the bridge because they’re already being published to the topic I wrote above?
And what is publishing the LWT message?
You can but then you get all the TELE messages unfortunately. Look at Dale Scott's comment as I ran into the same issue as him and this just seemed simple to me plus I could easily use it in NodeRed and other MQTT triggers.
@@digiblurDIY Ah, I see. He didn't specify where the errors are showing up - the HA log? Mosquitto? Sounds like something that can be fixed in a future HA release... unless for some reason I can't think of they want topics to be so restricted to only be for one purpose. Without doing what you are - we could just toss in all our sensors into our HA config with the general topic for that device itself (like the bridge) and just setup which payload goes with which sensor. If it doesn't match then discard or something. Having to setup rules for every single sensor data value doesn't seem sustainable.
He's getting errors in the HA log since the result topic is used for many things. Everyone's setup is different of course. Home Assistant is not at the center of mine, MQTT is. If I want to send a command to turn on a light, I don't want it to go from the RF Bridge to HA then to the light so I'd just have a rule to do that. Much like I do with long press actions on switches to toggle other lights. There's 10 different ways to do things in the HA world, I'm just showing how I do things in hopes of spawning various ideas for someone to find an even better way to solve a problem in their home.
Hi Great video - Can you help with this query. I have a bunch of single code device but it looks like im only allowed to add rule1/rule2/rule3 . When I add rule4 *** I get the following
22:50:16 MQT: stat/RFBridge1/RESULT = {"Command":"Error"} **
There are only 3 rule buffers. The latest version even has compression once you go over 511 characters.
digiblurDIY can you give me an example on how the add eg: single code sensors , 10 door contacts and let’s say 10 motion sensors.
How can I list the current rules ? (So I can see which should be my next avaliable rule number)
How can I backup the rules ? (Simply do a Tasmota full backup?)
How can I see how much more memory I have left for rules ? I would assume the memory is quiet limited, so I need to use as few characters as possible ?
It's not rule numbers, its a buffer of rules. There are three of them. Actually in the latest version of Tasmota they allow more by doing compression too
Backing up the config backs them all up.
If you type rule1, rule2, etc on the console it will show the rules and the amount of space you have left in each rule.
Question: I`m using the same door sensor with 2 codes, sonoff bridge etc.. The problem I have is speed of opening door and closing. If I open and close door too quickly ( 1-2s ) the sensor will not register closing sequence and the door remains open in HA. Have you experienced similar behavior on your end?
I haven't been able to reproduce it with the door sensors I have. Just tried opening and closing the door quickly but the state always went back correctly.
i have the same problem
Have you tried a different sleep setting in Tasmota possibly?
you mean the Tasmota in the Sonoff bridge? Never heard about sleeping state. I was more thinking that this delay is simply delay of the 433MHz + Tasmota on a Bridge. If the door sensor is further from the bridge it perhaps takes some milliseconds to transmit the signal. So as a side effect if you close door too quick the closing signal will get lost or ignored by the bridge
Yes. Type sleep at the console.
Seems there are only 3 rules available. How to extend this number ?
Did you fill all three buffers up? It's not just three rules. You have 511 per rule buffer.
@@digiblurDIY Ho I see thanks u... I will have a look how to add several rules into the same buffer
The basic premise is on trigger do something endon on trigger do something endon etc...
Great video digibluDIY. Quick question, I bought 5 sonoff wireless detectors for my home, and not sure how to configure the rules. Something like trhis didn´t work:
rule1 on RfReceived#Data=D3253E do backlog publish2 sonoff_rf_bridge_1/Sensor_entrance ON; ruletimer1 5 endon on rules#timer=1 do publish2 sonoff_rf_bridge_1/Sensor_entrance OFF endon
rule2 on RfReceived#Data=D3150D do backlog publish2 sonoff_rf_bridge_1/Sensor_kitchen ON; ruletimer2 5 endon on rules#timer=1 do publish2 sonoff_rf_bridge_1/Sensor_kitchen OFF endon
Can you help? Thank you very much in advance. Best reagards and thank you
I would need to see the log to see why it isn't running. Try the discord server link.
Do you know how many sensors one Sonoff RF Bridge can handle?
Really unlimited receive as long as the codes are unique.
Hello, I have a question and I need help. (sorry for my english, I am from Germany)
I have a Sonoff Bridge with Tasmota Firmware geflasht (6.4.1)
Now when I use my 433mhz Motion-Sensor, I see in the Tasmota Consol:
„RESULT = {"RfReceived":{"Sync":8890,"Low":290,"High":840,"Data":"2B56FA","RfKey":"None"}}“
I wish now, that a „Rule“ sending http Request to:
192.168.0.4:8083/fhem?cmd=set%20Anlagenschaltung%20on
(thats a switch in FHEM)
A example(its do not work) could be:
rule on rfreceived#Data=2B56FA do websend [192.168.0.4:8083] /fhem?cmd=set%20dummy%20on endon
If enyone is outside there in the World, who can help me, it would be very very good and you would do a big favor for me.
Have a nice Day,
Marco
It might not accept those characters. You could send a mqtt message to HA or NodeRed to have it send those different HTTP messages.
Hey mate.. as i said in my last comment i finaly buy one of these and flash it with Tasmota. But on console nothing happened when i active a 433Mhz Door Sensor.. Any ideas?
Make sure that the little switch below the big LED is turned ON. I had that issue, once I turned it on, it worked.
@@foxden5400 Hey man Thanks for the answer. But I checked that switch, it's okay with it. From what I've researched, the Sonoff RF Bridge can not learn all kinds of code. Unless I add such a 'Portisch' Firmware. github.com/Portisch/RF-Bridge-EFM8BB1.
I did not quite understand how to do it, so I'll let it go and buy another type of Sensor.
It would be nice if we can add IR control devices
My better 3/4 keeps getting after me to start posting about my 3D printing exploits. Never have been as comfortable speaking as you sound.
Why doesn't the following rule work: rule 1 on SerialReceived#data=Main.Power=On do command %On% endon ?
The following content appears in the console:
RSL: tele / tasmota_2FDFD1 / RESULT = {"SerialReceived": "Main.Power = On"}
I don't believe that is a valid command. Did you find that in the docs?
Very new to rules. This rule does not seem to publish the off command. Any help?
Rule1 on RFReceived#data=DF8911 do backlog publish2 RfBridge/WaterLeakKitchen ON: ruletimer1 5 endon on rules#timer=1 do publish2 RfBridge/WaterLeakKitchen OFF endon
Looks like you have a colon instead of a semicolon. For the backlog command you stack commands that are separated by semicolons.
github.com/arendst/Sonoff-Tasmota/wiki/Commands#using-backlog
digiblurDIY thanks a mil!
@@digiblurDIY could you retype the command rule for the timer
rule2 on RfReceived#Data=E754BE do backlog publish2 midtv_mqtt/Motion1 ON; ruletimer1 5 endon on rule#timer=1 do publish2 midtv_mqtt/Motion1 OFF endon
thanks I see the problem "rules#timer"
The Sonoff RF Bridge specifies "Control maximum 16PCS RF controlled devices on the App through network, make your home smarter." Is that due to the app? If you flash it with Tasmota, it should be able to listen to unlimited RF devices right?
Yes, you can listen to all the message codes you want that you can pile into these rules. If beyond that you would have to use something else to break down the TELE MQTT messages.
RF Bridge can CONTROL up to 16 RF devices (like power sockets) but can receive unlimited 433mhz signals from sensors, switches etc
Hello there, thanks a lot for the information, I just flash 8 sonoff basic and one rf bridge but now the rf brig is not sending or receiving anything, the rf led is not flashing at all, the switch is back to the on position, please help
Are you able to see the Tasmota GUI?
@@digiblurDIY yea I can acces the web ui no problem,
I really appreciate the help
It is set as RF bridge?
@@digiblurDIY yea rf bridge (25)
have same brigde for my switch button. but can not implement this on tasmota :-/ how cmd can use for this problem? i try >what can i do for solve hos problem .....????
Not sure I understand completely. Could you explain more on what you are trying to do?
i work with Hassio. bridge for run for sonoff type 86 433Mhz . I need the connand code for tasmota to assign the switches..
This i think is ok
on configuration.yaml file
One of 3 switches:
platform: mqtt
name: “Sonoff RF”
This isn't a switch. LWT is last will and testament. It let's you know if the device is on the network or not.
Hi, using Tasmota on Sonoff Bridge, can I register more than 16 devices?
Can I register the sensor scrolling code?
Can I register more alarm devices?
Thank you.
The 16 is for sending codes. Sensor scrolling code?
@@digiblurDIY Rolling code or Dynamic code.
Ahh... I haven't heard of any firmware on these to tackle the rolling codes.
Can you turn rules on and off over MQTT?
Yes, just publish cmnd//rule1 and then the payload is 0 or 1.
@@digiblurDIY wow. surprised I didn't figure this out last night...couldn't find anything in the docs. thanks!
You can send in just about any command like that. Check out my little live stream I did a while back on how I update switches over MQTT commands.
Is there a limit to how many rules?
There are three rule buffers and now with the compression you can fit quite a few in each one.
@@digiblurDIY Thanks! i've got like 30 of these contact sensors I need to install, gonna see if I can squeeze in 10 per rule!
rule 1 on rfreceived#Data=8E29EE do publish2 RF_Bridge/sensor1 Open endon on rfreceived#Data=8E29E7 publish2 RF_Bridge/sensor1 Closed endon
is this code right seem not to come up with what you have had to change RFBridge to my topic name still doesn't come up with retain open & closed
It appears you have copied Rene Sørensen's command above and likewise omitted a 'do' before the 'publish2' towards the end of your command.
Common rookie mistake ;-)
I get this bug, what am I doing wrong
20:03:33 CMD: rule1 on rfreceived#Data=2EC10A do publish2 RF_Bridge_1/baderumVindue Open endon on rfreceived#Data=2EC10E publish2 RF_Bridge_1/baderumVindue Closed endon
20:03:33 MQT: stat/RF_Bridge_1/RESULT = {"Command":"Unknown"}
20:05:23 CMD: rule1 1
20:05:23 MQT: stat/RF_Bridge_1/RESULT = {"Command":"Unknown"}
You are missing a 'do' before the publish2 towards the end of your command. Compare with this:
rule1 on rfreceived#Data=2EC10A do publish2 RF_Bridge_1/baderumVindue Open endon on rfreceived#Data=2EC10E do publish2 RF_Bridge_1/baderumVindue Closed endon
Hej René
Do mangler i hvertfald "do" før publish2 i closed delen...
rule1 on rfreceived#Data=2EC10A do publish2 RF_Bridge_1/baderumVindue Open endon on rfreceived#Data=2EC10E do publish2 RF_Bridge_1/baderumVindue Closed endon
haw many rules can you set?
You can set quite a bit now with the compression
How do you remove a rule?
Just type rule1 ""
@@digiblurDIY Thanks for your reply. Are they 2 Quotation marks?
yes... quote quote with nothing in between
Thank for the Video, but I can have only the first code working of the three in the rule:
Rule1 on RFReceived#data=E846AE do backlog publish2 Rf_Bridge/PSal 1; ruletimer1 5 endon on rules#timer=1 do publish2 Rf_Bridge/PSal 0 endon on RFReceived#data=E9E1DE do backlog publish2 Rf_Bridge/PIng 1; ruletimer2 5 endon on rules#timer=2 do publish2 Rf_Bridge/PIng 0 endon on RFReceived#data=E8329E do backlog publish2 Rf_Bridge/PCuc 1; ruletimer3 5 endon on rules#timer=3 do publish2 Rf_Bridge/PCuc 0 endon
Can't understand where is the mistake...
Only this: on RFReceived#data=E846AE do backlog publish2 Rf_Bridge/PSal 1; ruletimer1 5 endon on rules#timer=1 do publish2 Rf_Bridge/PSal 0 endon
great video, I noticed you are using Tasmota RULES a lot. I`m no expert but it seems to me that you can either put together rules in Tasmota or in HA. So here is my quest: Why do I want RULES in Tasmota instead of HA if all my automation goes through HA anyway? I like those rules but need some Business Case for them :-)
Yes, as MQTT is the center of a Smart Home with MQTT devices, not HA itself. Sometimes rules are easier to apply within the device itself and make a true smart switch/device. Plus I prefer for things to run if I have HA down for some reason. Not to mention it's quicker to skip the middle man. As I could publish a command right from the RF Bridge to another MQTT switch without Home Assistant running.
@@digiblurDIY it would be awesome if you highlight those special cases where rules for device to device communication will be beneficial. For Example I have the Dr.ZZzs 3 way switch installed with 2 SONOFF Basics where one which is not connected to the light talks with the other directly instead of going through HA. Chaning payload from '123456A" to "Open" is nice but not necessary. btw your rules for iMeh is awesome and nice example.
Will do. Did you see the rules on the Kuled switches I did? Probably like the ones you have done I assume.
I also use these MQTT topics on NodeRed so it would have been additonal work to have HA turn around and publish the packet back out or do additonal flows to break down the json template.
I did everything in the same way but in my Home Assistant after adding "entity" I se this entity with information "Unavailable". Where I did a mistake? I checked code milion times. RF Bridge see the sensor and status in the console.
My MQTT Topic is RFBridge. This is my code:
binary_sensor:
- platform: mqtt
name: "Balcony"
state_topic: "RFBridge/sensor1"
availability_topic: "tele/RFBridge/LWT"
payload_on: "Open"
payload_off: "Closed"
payload_available: "online"
payload_not_available: "offline"
qos: 1
device_class: door
Help:)
Can you check to make sure the LWT topic is correct on your device? In the console type restart 1
Then watch the console to see the LWT.
@@digiblurDIY RFBridge/tele/LWT
Looks like your topic is backwards from the one you have in the YAML. So flip one or the other to make them match.
@@digiblurDIY Something strange. This doesn't work:
- platform: mqtt
name: "Balcony"
state_topic: "RFBridge/sensor1"
availability_topic: "RFBridge/tele/RESULT"
payload_on: "Open"
payload_off: "Closed"
payload_available: "online"
payload_not_available: "offline"
qos: 1
device_class: door
but this work properly:
- platform: mqtt
name: "Drzwi balkonowe"
payload_on: "8F19EE"
payload_off: "8F19E7"
state_topic: "RFBridge/tele/RESULT"
device_class: door
value_template: "{{ value_json.RfReceived.Data }}"
6
7