larryllix Posted November 19, 2020 Posted November 19, 2020 1 hour ago, tmorse305 said: @larryllix, that is bizarre. I created a test program on ISY today to play with this: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $sMS_Test_1 = 1 Wait 30 seconds $sMS_Test_1 = 0 Wait 30 seconds $sMS_Test_1 = 1 Wait 30 seconds $sMS_Test_1 = 0 I get two reports from Alexa repeatedly, when the variable is set to 1. I played around with the wait times to see if I could get it to ever trip on the variable setting to 0 but no luck. If I reduce the middle wait to 1 second then I can create the appearance of the trigger on the set to 0 but it's obviously just delayed from the previous set to 1. Hopefully Benoit can shed some light on this for you. I just talked to alexa support. Gotta love that one! The first one noted I was in Canada and then asked if my app URL was .ca or .com. I retorted it was an app and there was no URL.... "oh yeah but you need to call the Canadian support team". "How do I do that? I didn't even call you. I just clicked a link to call me in the alexa app" LOL!! Typical support for most companies! After being transferred to Canadian support the support front line took the information and is passing it on, with hopes of getting back today via email. BTW: You shouldn't need an additional Wait 30 seconds between trigger actions (var=0, Wait 0 seconds, nextVar = 1). Only needed for total between triggers. IOW: Only 30 seconds between speaking requests. 1
tmorse305 Posted November 19, 2020 Posted November 19, 2020 2 hours ago, larryllix said: BTW: You shouldn't need an additional Wait 30 seconds between trigger actions (var=0, Wait 0 seconds, nextVar = 1). Only needed for total between triggers. IOW: Only 30 seconds between speaking requests. I hope you hear back from them, I have made a few requests in the past and been promised follow up but alas still waiting... On the 2nd 30 sec wait, actually it is necessary. If I delete it, I never get the second voice response. If I shorten it to a couple of seconds the 2nd voice response comes about 30 second later. With it set to 2 seconds the voice response was nearly coincident with the variable resetting to 0. I thought I had duplicated your issue until I realized what was actually happening.
tmorse305 Posted November 19, 2020 Posted November 19, 2020 @larryllix, I played around some more with the delays to see if I could get a better understanding of what is happening. With this setup: $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 30 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt occurs 60 seconds after the first one. With this setup: $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 25 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt never happens. Here's my theory on what going on. It seems any change to the variable state triggers the 30 second exclusion period on Alexa. If another change comes along before the 30 second has expired, it's put in a queue and is acted on when the 30 second period has ended. Then another 30 second period begins. But the queue is only one deep, if another change comes along before the queue is cleared, it either ignores it or overwrites the queue with the updated value. Either way Alexa misses the next transition so there is no second voice prompt.
larryllix Posted November 19, 2020 Posted November 19, 2020 @larryllix, I played around some more with the delays to see if I could get a better understanding of what is happening. With this setup: $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 30 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt occurs 60 seconds after the first one. With this setup: $sMS_Test_1 = 1 Wait 5 seconds $sMS_Test_1 = 0 Wait 25 seconds $sMS_Test_1 = 1 Wait 2 minutes $sMS_Test_1 = 0 The second voice prompt never happens. Here's my theory on what going on. It seems any change to the variable state triggers the 30 second exclusion period on Alexa. If another change comes along before the 30 second has expired, it's put in a queue and is acted on when the 30 second period has ended. Then another 30 second period begins. But the queue is only one deep, if another change comes along before the queue is cleared, it either ignores it or overwrites the queue with the updated value. Either way Alexa misses the next transition so there is no second voice prompt.a new quirk has just popped up here.Any time I trigger a spoken using Motion Off it triggers twice. I have watched the pseudoMS in the Alexa app to verify it is not coming from my iSY.It triggers immediately on 1 and then about 60 seconds again, later.You may be getting that also and confusing things.I added that to my support ticket today as that is new. I know they are playing with the Routine software...no doubt.There is a delayed trigger with the off detection but that has been verified there is a 0 setting for all my routines.Sent using Tapatalk
tmorse305 Posted November 20, 2020 Posted November 20, 2020 3 hours ago, larryllix said: Any time I trigger a spoken using Motion Off it triggers twice. I have watched the pseudoMS in the Alexa app to verify it is not coming from my iSY. I've noticed that events shorter than 3 seconds on the ISY side don't show up in the Alexa app when I watch the device but do trigger the routines.
larryllix Posted November 20, 2020 Posted November 20, 2020 1 hour ago, tmorse305 said: I've noticed that events shorter than 3 seconds on the ISY side don't show up in the Alexa app when I watch the device but do trigger the routines. Good observation! That makes my device observation in the app weak then. I went through my programs and there is nothing else that set the variables and I was triggering it by hand tweaking the variables with my sequencing program resetting it at the 30 second mark. The second trigger comes about 60-90 seconds after the first trigger. Perhaps tomorrow I better disable my software and then hand manipulate the variables to prove it wasn't my ISY since the app indicator is lagging.
tmorse305 Posted November 20, 2020 Posted November 20, 2020 @larryllix, I created another test routine that triggers on 'not detected' just to make sure there was no difference in the way that Alexa responds. It seems to operate the same way as using detected. In the process I did discover one surprise. I can fire the 2 programs back to back and I get both voice prompts, one right after the other, no 30 second delay. It seems that Alexa is treating them as independent events with their own 30 second exclusion periods. 1
larryllix Posted November 20, 2020 Posted November 20, 2020 3 hours ago, tmorse305 said: @larryllix, I created another test routine that triggers on 'not detected' just to make sure there was no difference in the way that Alexa responds. It seems to operate the same way as using detected. In the process I did discover one surprise. I can fire the 2 programs back to back and I get both voice prompts, one right after the other, no 30 second delay. It seems that Alexa is treating them as independent events with their own 30 second exclusion periods. Please see my findings here
Recommended Posts