Sonoff bridge

Did you try this one? I’ve had good luck with his stuff
https://github.com/BrettSheleski/SmartThingsPublic/tree/master/devicetypes/brettsheleski/sonoff-tasmota-rf-bridge-button.src

Nope, that didn’t work. It’s just a button of some sort. There is no explanation on how it works.

Found it!!
Do this:

2 Likes

Hello Steven

I also used Bretts device handlers for my Sonoff basic, shelly’s and it works perfect.

Did you get it to work? I have had a lot to do these last days so haven´t had any time to play with the Sonoff bridge.

Have a nice day.

Can you tell me the name and version of the tasmota firmware you are using on the bridge?

http://thehackbox.org/tasmota/release/
Lastest release is 6.5

Apparently this only sends messages to the bridge. If say RfKey 1 is activated on the bridge, nothing is sent to the ST app, but if button one is press on ST app, the bridge receives it and sends a mqtt message.

Weird cannot get i to create a child device.

In the ST ide, change the “type” to just Tasmota. Go into the app and add the IP address. The DTH will figure out what it is and create the child devices, all 16 lol

yeah i know, i got connection from IDE to app but no spawning. I had the same issue before with one of my Shellys’ but after trying changing the ip in the IDE to another online/working shelly and back again i worked… I will give it a go again later.

Now if we can get @BrettSheleski or someone to figure out how to capture “received” messages with WebCore, I may find a lot of use for this thing lol

I have several Sonoff RF bridge devices running my device handlers. I’m considering adding an additional device for every button of the bridge. Therefore there would be a button device used to transmit the associated RF code (existing functionality) and there would be an additional button device used to detect when the desired RF code is transmitted by something else.

I have a game plan for getting the communication back up to the device handlers, just need time to implement and test. I’m looking to refactor the device handlers code in order to do so. It wouldn’t be too crazy of a task, just need time.

1 Like

Sounds like exactly what I was wanting

Tasmota Rules + WebSend commands can send the RF code to DTH (or smartapp) to update the status…

1 Like

NICE! Thanks, took me awhile to get the coding right but I got it to work. Well I got it to turn on a switch on my 4CH Pro R2.
on RfReceived#Data=520DEE do websend [192.168.1.65] cm?cmnd/4CH/Power4 On endon

The only problem I have is, the DTH button doesn’t turn on unless I manually “refresh”

The DTH has to be able to handle the data (requires additional coding), otherwise it will not update/work…

Could anybody help me with my the child spawn issue? It seems if i change the bridge from (sonoff bridge 25) in Configure module it spawns right away but not when i am trying to use (sonoff bridge 25). When i first add the new device i get all info from the bridge into my App and IDE handler.

It looks like Brett Sheleski Sonoff handler stuff on GitHub is gone… any idea where I could find a device handler for the Sonoff 433 Bridge ?

How about https://github.com/BrettSheleski/SmartThingsPublic/tree/master/devicetypes/brettsheleski

If you flash to Tasmota firmware, then this would work for you -