ST Virtual Switches Via Alexa Not Firing Pistons

virtual
alexa

#1

1) Give a description of the problem
I am attempting to trigger ST and Lifx Scenes using virtual switches by linking them through WebCoRE. When I turn on the virtual switch using the ST app (or ActionTiles) both the ST Scene and WebCoRE piston fire. However, when I say “Alexa, turn on [virtual switch]”, the virtual switch responds and fires the ST Scene but not the WebCoRE piston.

2) What is the expected behaviour?
It seems that I would expect a virtual switch to behave in exactly the same way regardless of what triggers it.

3) What is happening/not happening?
This all works fine when I directly turn the virtual switch on using the ST app (or ActionTiles) both the ST Scene and WebCoRE piston fire. However, when I say “Alexa, turn on [virtual switch]”, the virtual switch responds and fires the ST Scene but not the WebCoRE piston.

4) Post a Green Snapshot of the pistonimage

5) Attach logs after turning logging level to Full
3/22/2021, 11:05:17 PM +354ms
+1ms ╔Received event [Goodnight].switch = off with a delay of 53ms
+58ms ║RunTime Analysis CS > 19ms > PS > 5ms > PE > 34ms > CE
+60ms ║Runtime (39784 bytes) successfully initialized in 5ms (v0.3.113.20210203) (58ms)
+61ms ║╔Execution stage started
+68ms ║║Comparison (enum) off changes_to (string) on = false (1ms)
+69ms ║║Condition #13 evaluated false (4ms)
+70ms ║║Condition group #1 evaluated false (state did not change) (5ms)
+72ms ║╚Execution stage complete. (11ms)
+73ms ╚Event processed successfully (73ms)
3/22/2021, 11:05:17 PM +130ms
+0ms ╔Received event [Goodnight].switch = off with a delay of 49ms
+49ms ║RunTime Analysis CS > 14ms > PS > 6ms > PE > 29ms > CE
+51ms ║Runtime (39778 bytes) successfully initialized in 6ms (v0.3.113.20210203) (50ms)
+52ms ║╔Execution stage started
+59ms ║║Comparison (enum) off changes_to (string) on = false (0ms)
+61ms ║║Cancelling condition #13’s schedules…
+62ms ║║Condition #13 evaluated false (5ms)
+63ms ║║Cancelling condition #1’s schedules…
+64ms ║║Condition group #1 evaluated false (state changed) (7ms)
+65ms ║╚Execution stage complete. (13ms)
+67ms ╚Event processed successfully (66ms)
3/22/2021, 11:05:11 PM +581ms
+1ms ╔Received event [Goodnight].switch = on with a delay of 46ms
+48ms ║RunTime Analysis CS > 16ms > PS > 5ms > PE > 27ms > CE
+51ms ║Runtime (39783 bytes) successfully initialized in 5ms (v0.3.113.20210203) (49ms)
+52ms ║╔Execution stage started
+59ms ║║Comparison (enum) on changes_to (string) on = true (1ms)
+61ms ║║Cancelling condition #13’s schedules…
+62ms ║║Condition #13 evaluated true (5ms)
+63ms ║║Cancelling condition #1’s schedules…
+64ms ║║Condition group #1 evaluated true (state changed) (7ms)
+66ms ║║Cancelling statement #16’s schedules…
+2256ms ║║Executed virtual command lifxScene (2187ms)
+2259ms ║║Executed virtual command wait (0ms)
+2260ms ║║Waiting for 3000ms
+5264ms ║║Cancelling statement #14’s schedules…
+5273ms ║║Executed physical command [Goodnight].off() (5ms)
+5274ms ║║Executed [Goodnight].off (7ms)
+5276ms ║╚Execution stage complete. (5225ms)
+5277ms ╚Event processed successfully (5277ms)


#2

Your logs show the piston being fired by a switch turning on, activating a LIFX scene, waiting three seconds, and turning the switch off again.

Curiously it shows two ‘off’ events.


#3

The log is correct as far as my piston is concerned: Due to the lack of a virtual button I’m using this technique to simulate a virtual button. It works great everywhere except with Alexa (the “Echo-system”)… speaking of echoes echoes…

Yea, that ‘off’ thing… I’ve discussed this at length with SmartThings. Their product is littered with duplicate commands. Dirty code I guess. Remember x10 did this too… and they’re so popular now, right?