I originally copied the text as is from the manual, but the server failed to load after restarting it. Only when I removed the content of the automation.yaml file I managed to start the service again.
I changed the way the code is presented in the message, if help looking at it.
Anyway, I will do it all again today to make sure nothing is missed.
You need to check you have the 2 recipes in IFTTT to work this.
You will be using ‘Receive a Web Request’ with the event ID of sonoff-2-off for one of them with a ‘that’ set to eWelink which will pick up the channel switch and you set the action to on or off.
This worked 100% for me and I documented how I did it in case I ever wanted to use that again. I flashed the switch with Tasmota so I’m using MQTT now but this works perfectly albeit with a slight delay using eWeLink and IFTTT. Make sure you have your IFTTT API key set up correctly in configuration.yaml as well.
Well, it worked!
The problem was there was as you wrote. once I created the second trigger, the server loaded.
Thanks guys!!
try https://shelly.cloud/ - they are esp8266 based, by their fw has option to use MQTT locally (with completely disabled cloud) and form factor is awesome. I use several of them (single and double relays) and very happy with it. no more tasmota )