# Scenes/eWelink Keyboard vs IFTTT **URL:** \ **Category:** Ideas & Suggestion\ **Tags:** ifttt, scene\ **Created:** [April 17, 2022, 12:29pm UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438 "2022-04-17T12:29:29Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![hookdk](https://avatars.discourse-cdn.com/v4/letter/h/bc8723/32.png) [@hookdk](https://forum.ewelink.cc/u/hookdk)\ **Post date:** [April 17, 2022, 12:29pm UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/1 "2022-04-17T12:29:29Z")
When you turn on/off a device with a scene then the device you have setup in IFTTT is not registered as being turned on/off … Please make it such that at least the device is registered as being turned on/off when doing it from a scene… Else IFTTT is kinda worthless esepcially when you are doing it from eWelink Keyboard where you only can have scenes!!! OR just make it so that things can also be triggered with scenes (like IFTTT can act on scenes) … whatever is most simple but as long as it works which it doesnt currently!!! ---
**Author:** ![Alexie](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/alexie/32/1593_2.png) [@Alexie](https://forum.ewelink.cc/u/Alexie)\ **Post date:** [April 21, 2022, 7:22am UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/2 "2022-04-21T07:22:21Z")
Currently there is no active subscription to get device state changes for IFTTT , this is due to the current API of IFTTT - we will look again, how can IFTTT get the latest device state ---
**Author:** ![hookdk](https://avatars.discourse-cdn.com/v4/letter/h/bc8723/32.png) [@hookdk](https://forum.ewelink.cc/u/hookdk)\ **Post date:** [April 21, 2022, 9:00am UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/3 "2022-04-21T09:00:22Z")
Im not sure what is stated here is entirely correct… always easy to blame IFTTT but when as I said I turn on the light manually and directly myself (in the eWelink app) then it works … Then IFTTT registeres it… And that would count as a device change right? So it cannot be the reason… As I see it its rather because Scenes in eWelink they are not letting your backend system register device changes … so its all about eWelink Scenes! ---
**Author:** ![yitie](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/yitie/32/3613_2.png) [@yitie](https://forum.ewelink.cc/u/yitie)\ **Post date:** [April 22, 2022, 2:52am UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/5 "2022-04-22T02:52:29Z")
Let’s dive in to locate the issue, have some clue but not sure for now. ---
**Author:** ![yitie](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/yitie/32/3613_2.png) [@yitie](https://forum.ewelink.cc/u/yitie)\ **Post date:** [April 24, 2022, 2:46am UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/6 "2022-04-24T02:46:55Z")
Hi there, we have located the issue and find a way to improve it, planned to be available in early June, so you can trigger IFTTT applet by eWeLink scenes at that time, free let me know if you have further suggestion. ---
**Author:** ![yitie](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/yitie/32/3613_2.png) [@yitie](https://forum.ewelink.cc/u/yitie)\ **Post date:** [May 27, 2022, 4:19am UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/7 "2022-05-27T04:19:01Z")
Hi hookdk, happy let you know that we have make it happen, you can trigger IFTTT applet by eWeLink scenes now, just have a try and let me know how’s going, cheers. ---
**Author:** ![hookdk](https://avatars.discourse-cdn.com/v4/letter/h/bc8723/32.png) [@hookdk](https://forum.ewelink.cc/u/hookdk)\ **Post date:** [July 8, 2022, 10:36pm UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/8 "2022-07-08T22:36:54Z")
Think somebody at Sonoff/here in this forum blocked my possibility of having Google Assistant changing colors/dimming and so forth my bulbs… PLease open this again… This should never be how you run a business at all… (I feel a bit disguisted that you did this - whoever did this “behind the curtain/below radar” in the back… ---
**Author:** ![yitie](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/yitie/32/3613_2.png) [@yitie](https://forum.ewelink.cc/u/yitie)\ **Post date:** [July 10, 2022, 9:24am UTC](https://forum.ewelink.cc/t/scenes-ewelink-keyboard-vs-ifttt/438/9 "2022-07-10T09:24:00Z")
What is the issue? May I know the device ID that can not work? Will check it dor you. Nothing changed of our side, and we did never and will not to block user’s account for inexplicable reason.