One thing I noticed when I made this video was that the scene got hidden when I opened the garage passage door. The whole process is a bit complicated, but it all works so well and is VERY reliable. A Raspberry Pi is monitoring a magnetic reed switch for a state change. When the state changes, a python program does a r =
requests.post to a Join URL that contains a the words garage, passage, and open. Tasker gets the "message" words and runs a task. One of the task steps is to do a "Join action" (Join action that sends a webhook with "GaragePassageOpen" to IFTTT and IFTTT sends a message to Wyze to turn on the lights on the stairs ). So what happens is that when you open the door at the bottom of the stairs, the stairs lights are turned on. This all happens before you even walk through the door. You'll notice in the video the Join toast that says "StairsLightOn performed on IFTTT" when I open the door. And then scene gets hidden/killed and something sends the device back to its home screen. All other steps of this "Garage passage open" task run to completion. (A few variables get set and a Google Sheet gets a new line).
I have thinned it all out and done some experiements. Whenever a "Join action" is run, any scene that is being shown at that moment gets hidden (or the device is forced back to the launcher's home screen). This does not happen when I do Join Send Push with the same "GaragePassageOpen" but the message is still received and the lights indeed turn on. I have proven this with multiple scenes.
Fun fact, I did a run log capture and nowhere in that did it have the words scene, kill, destroy, hide, home, page, launcher, or back.
Why does the "Join action" kill or hide an active scene?