Thanks for sharing the piston!
First, I’m assuming I have something messed up, or maybe just don’t understand, but…
I didn’t fully understand it at first, but I imported it to give it a try anyway.
I thought maybe this was going to be something that I would add to a piston to help with directing Echo Speaks traffic. However, as I sit here and test speaking commands to different Alexa devices, I see that this thing is updating the variable automatically shortly after my voice interactions.
I am seeing an error in the logs when it runs, but it still appears to be working.
That is very cool!!
Regardless of the rest of my questions, I will probably leave this thing in place.
Now, with the delay I’m seeing, this would not be a viable solution for the thing I’m looking for.
Is there any way to sort of build this into a piston to have this info available mid-stream in an automation?
Is that just simply a matter of me understanding what’s happening here, and plugging the appropriate parts into my piston?
…and/or is that what @nathancu is talking about after your comment? lol
Oh wait…I see now that it is a local variable, and not global.
I guess that means I should be able to use it in a piston.
So, I will give it a try lol …
omg, it’s working! lol