Right now, I can connect the bridge to the Ewelink app, and I can connect my Ewelink account to IFTTT but the only options that show up are plugs and switches.
I'd love to be able to send an email that "pushes" a button my 4-button remote, or hourly check to see if someone left the garage door open, and send me an email if it is.
@Sean - how did you get the 'trigger' basic that was turned on by the scene to trigger ifttt. I have never been able to get a sonoff to trigger ifttt if it has been turned on by a scene. (apart from the bodge around via an android notification).
@Andy - you can get it to trigger lights (or a buzzer etc) no problem using an ewelink scene. This issue current is getting it to trigger ifttt to do something else like send send a notification if I am out.
My testing is as follows:
Update: This morning sometime it seems that something has changed. At 11:37 GMT i got a stringify notification from one of my tests flows. wtf, I phoned mrs.A, and she had just got home.
Checking the ifttt history it seems that from sometime earlier this morning my scene was triggering ifttt, which then ran Stringify. I will set up a more comprehensive series of tests this evening and report back.
@Sean seems you are seeing the same thing. eg. Sonoff PIR turns on sonoff basic (trigger device), this triggers ifttt applet and then you can do anything. Could someone else test please to confirm?
In all honesty if this works and is stable I'm ok with having a Sonoff basic as a intermediate trigger device for short term.
The only better things would be (in priority order)
I would like to know which genius in sonoff decided to, hey lets make a door alarm bridge but the only thing it can do at its best is to send a notification that doesn't even work half the time, depending on the phone and internet connectivity, specially if the app hasn't been opened in a while. it's like they think they are making children toys that should just makes some sound and have no interest in real world usability. so much for reliability. I realized after some of my sonoff slmaphers died spontaneously, there is no warranty, service or accountability. now I just have so much regret investing in sonoff rf bridge knowing even after a year+ no one has thought there are essential functions missing from this setup, lets think real life. so much disappointment, now I have to invest in a proper smart door alarm system.
I think this is the real issue: do you confirm that now the "scene triggered switch" is "felt" by IFTTT.
I had setup the eWelink-IFTTT-Sringify-IFTTT "chain" like 6 months ago to automatically time a switch off after the PIR had triggered it on, through the bridge and, at the time, it did NOT work because IFTTT would not detect the switch-ON trigger if induced by the bridge.
It was weird because the same IFTTT did detect the switch trigger under any other circumstance (like driven by the eWelink app or driven by Google Home or even when powering up the switch with its state set to ON).
Just the trigger through bridge did not work.
Has anything changed since?
Hi, I would like to ask all participants not to generate confusion while discussing their workarounds. If you use a switch as a proxy to tell IFTTT or Stringify that a PIR sensor or eWeLink scene has been triggered, then turning the same switch on by other means (button, eWeLink, RF remote, Google Home, Alexa…) would look the same to the IFTTT/Stringify and it would, therefore, turn it off after the timeout that you set. In order to differentiate, I guess you need to dedicate one switch/gang as a trigger and use the other one to control the light. The same applies to the sending of emails via IFTTT.
Another problem with this workaround is probably that only the event (e.g. movement) that turns the switch can be detected, so the timer would turn the light off even if you keep moving and the PIR sensor firing. In order to detect subsequent movements, you should turn the proxy switch off.
In the garage door scenario, the source opening the door is irrelevant, and a single IP switch (controlling the door) would do the job. However, the garage doors are typically controlled by RF remotes…
What we really need is to enable the RF bridge to pass the RF remote or sensor events it receives to IFTTT/Stringify or start/clear/stop eWeLink's device/scene timers. That is what I assume as a part of RF bridge IFTTT support that was announced for October 2018. The other part would be the ability to control RF switches from IFTTT via the RF bridge.
Only if we are precise enough we may know what is actually going on.
also a lot of votes in the first post could help
This would be the worst possible time to flood them with emails...most Chinese companies either close down or have a skeleton crew leading up to Chinese New Years. If you want to get a response, my suggestion is wait until later in the month.
What might work better is if we request the trigger and action on IFTTT - it would go directly to the people that are programming the IFTTT functionality. A bunch of requests might get some action.