WebCoRE asks a question, my voice response determines the action

text-to-speech
answer
query
voice
alexa

#102

Apologies. I got mixed up between the two Echo Routines and your one Yes/No piston. Of course you are right. You have only one yesd/no piston too. You are also right that I removed the Dashboard States - because I’m not currently using any piston dashboard states.

Update: I’ve noted my error in my earlier post above.

In any case, I’m pleased you shared with us your ideas regarding this functionality and I’m putting it to good (and fun) use.

Thanks again.


#103

@Mebejedi I know I am late to this discussion but I just found this piston. As for your question about which echo speaks to you…you can set that in the Alexa Routine.


#104

This is really great! Can be used in so many ways!


#105

Can someone help me get this going. I want it to ask me to play my playlist when I get home and come in the house. But it wasn’t working so in this piston I am just using a Test button to try to get it to trigger. However, I turn the Test button on and then I go and open the door and close it which makes it change to “Closed” but it doesn’t work. Seems to see that the Test Button changes to On but the Door sensors are closed at the time and it ends. It works if I just use the Test Button.

Here is the log:
4/5/2019, 5:18:50 PM +271ms
+1ms ╔Received event [Test switch].switch = off with a delay of 540ms
+109ms ║RunTime Analysis CS > 19ms > PS > 68ms > PE > 22ms > CE
+112ms ║Runtime (43688 bytes) successfully initialized in 68ms (v0.3.10a.20190223) (109ms)
+113ms ║╔Execution stage started
+124ms ║║Comparison (enum) off changes_to (string) on = false (0ms)
+126ms ║║Condition #2 evaluated false (6ms)
+127ms ║║Condition group #1 evaluated false (state did not change) (8ms)
+129ms ║╚Execution stage complete. (17ms)
+131ms ╚Event processed successfully (131ms)
4/5/2019, 5:18:44 PM +102ms
+2ms ╔Received event [Garage Door Sensor].contact = closed with a delay of 83ms
+117ms ║RunTime Analysis CS > 19ms > PS > 75ms > PE > 22ms > CE
+120ms ║Runtime (43698 bytes) successfully initialized in 75ms (v0.3.10a.20190223) (117ms)
+121ms ║╔Execution stage started
+137ms ║║Condition #2 evaluated false (9ms)
+138ms ║║Condition group #1 evaluated false (state did not change) (11ms)
+141ms ║╚Execution stage complete. (19ms)
+142ms ╚Event processed successfully (142ms)
4/5/2019, 5:18:41 PM +635ms
+1ms ╔Received event [Garage Door Sensor].contact = open with a delay of 62ms
+83ms ║RunTime Analysis CS > 14ms > PS > 49ms > PE > 19ms > CE
+85ms ║Runtime (43694 bytes) successfully initialized in 49ms (v0.3.10a.20190223) (83ms)
+86ms ║╔Execution stage started
+100ms ║║Cancelling condition #2’s schedules…
+101ms ║║Condition #2 evaluated false (9ms)
+102ms ║║Condition group #1 evaluated false (state did not change) (10ms)
+105ms ║╚Execution stage complete. (19ms)
+106ms ╚Event processed successfully (106ms)
4/5/2019, 5:18:33 PM +298ms
+2ms ╔Received event [Test switch].switch = on with a delay of 542ms
+113ms ║RunTime Analysis CS > 23ms > PS > 69ms > PE > 21ms > CE
+116ms ║Runtime (43688 bytes) successfully initialized in 69ms (v0.3.10a.20190223) (114ms)
+117ms ║╔Execution stage started
+128ms ║║Comparison (enum) on changes_to (string) on = true (0ms)
+130ms ║║Cancelling condition #2’s schedules…
+131ms ║║Condition #2 evaluated true (8ms)
+143ms ║║Condition #20 evaluated false (11ms)
+145ms ║║Condition group #1 evaluated false (state did not change) (21ms)
+147ms ║╚Execution stage complete. (31ms)
+149ms ╚Event processed successfully (148ms)


#106

The issue is that on lines 28-30, you have two triggers bound with “and”.

Triggers are only true for a brief moment, so tying two together with “and” will rarely work. (how can the door close at the exact moment as the switch changing to on?)

Normally, you only want a single trigger to activate a piston (with optional conditions following), or two triggers tied together with “or”. (meaning one or the other)


#107

So can have two conditions then? Or how can I do this?


#108

Unlimited conditions can be below the trigger.


#109

How would I do that? It says that these are Conditions.


#110

The top part of that drop down list are conditions… the bottom part are triggers.
(and the lightning bolts in the left margin also identify triggers)


#111

Oh, I actually didn’t realize that! Thanks!