Using Contact and Motion Sensors to Trigger Alexa Routines (DTH in post 97) (Official Amazon Feature)

Annd all of a sudden it stopped working yesterday. I have no idea why, I posted something over at the webcore forums but haven’t received a response yet.

9/24/2018, 4:06:40 PM +729ms
+1ms ╔Received event [Front Door].contact = closed with a delay of 926ms
+107ms ║RunTime Analysis CS > 17ms > PS > 44ms > PE > 46ms > CE
+110ms ║Runtime (38670 bytes) successfully initialized in 44ms (v0.3.108.20180906) (108ms)
+111ms ║╔Execution stage started
+121ms ║║Comparison (string) :544a9b992c238a89c379073fefaa7fe1: is_any_of (string) :544a9b992c238a89c379073fefaa7fe1:,:aa4b274e22d2f4c0001b65e07d3b32bd:,:2fce84ee632722b31122dc1a90d826c3: = true (2ms)
+122ms ║║Condition #1 evaluated true (6ms)
+124ms ║║Condition group #null evaluated true (state did not change) (8ms)
+134ms ║║Cancelling condition #8's schedules...
+135ms ║║Condition #8 evaluated false (8ms)
+137ms ║║Cancelling statement #2's schedules...
+138ms ║║Condition group #2 evaluated false (state did not change) (12ms)
+141ms ║╚Execution stage complete. (29ms)
+142ms ╚Event processed successfully (142ms)
9/24/2018, 4:06:38 PM +531ms
+1ms ╔Received event [Front Door].contact = open with a delay of 928ms
+127ms ║RunTime Analysis CS > 23ms > PS > 50ms > PE > 54ms > CE
+129ms ║Runtime (38680 bytes) successfully initialized in 50ms (v0.3.108.20180906) (127ms)
+131ms ║╔Execution stage started
+140ms ║║Comparison (string) :544a9b992c238a89c379073fefaa7fe1: is_any_of (string) :544a9b992c238a89c379073fefaa7fe1:,:aa4b274e22d2f4c0001b65e07d3b32bd:,:2fce84ee632722b31122dc1a90d826c3: = true (2ms)
+142ms ║║Condition #1 evaluated true (6ms)
+143ms ║║Condition group #null evaluated true (state did not change) (8ms)
+148ms ║║Conditional ladder step failed due to a timeout
+150ms ║║Cancelling statement #2's schedules...
+151ms ║║Condition group #2 evaluated false (state did not change) (5ms)
+153ms ║╚Execution stage complete. (23ms)
+155ms ╚Event processed successfully (155ms)
9/24/2018, 4:05:33 PM +107ms
+1ms ╔Received event [Home].time = 1537819534789 with a delay of -1682ms
+120ms ║RunTime Analysis CS > 17ms > PS > 51ms > PE > 51ms > CE
+122ms ║Runtime (38682 bytes) successfully initialized in 51ms (v0.3.108.20180906) (120ms)
+124ms ║╔Execution stage started
+136ms ║╚Execution stage complete. (13ms)
+138ms ╚Event processed successfully (137ms)
9/24/2018, 4:02:28 PM +601ms
+1ms ╔Received event [Front Door].contact = closed with a delay of 924ms
+169ms ║RunTime Analysis CS > 23ms > PS > 75ms > PE > 71ms > CE
+172ms ║Runtime (38680 bytes) successfully initialized in 75ms (v0.3.108.20180906) (170ms)
+174ms ║╔Execution stage started
+188ms ║║Comparison (string) :544a9b992c238a89c379073fefaa7fe1: is_any_of (string) :544a9b992c238a89c379073fefaa7fe1:,:aa4b274e22d2f4c0001b65e07d3b32bd:,:2fce84ee632722b31122dc1a90d826c3: = true (3ms)
+191ms ║║Condition #1 evaluated true (10ms)
+193ms ║║Condition group #null evaluated true (state did not change) (12ms)
+206ms ║║Comparison (enum) closed changes_to (string) open = false (1ms)
+209ms ║║Condition #3 evaluated false (9ms)
+213ms ║╚Execution stage complete. (40ms)
+216ms ║Setting up scheduled job for Mon, Sep 24 2018 @ 4:05:34 PM EDT (in 185.973s)
+229ms ╚Event processed successfully (228ms)
9/24/2018, 4:02:24 PM +840ms
+1ms ╔Received event [Front Door].contact = open with a delay of 917ms
+139ms ║RunTime Analysis CS > 25ms > PS > 65ms > PE > 49ms > CE
+141ms ║Runtime (38677 bytes) successfully initialized in 65ms (v0.3.108.20180906) (139ms)
+143ms ║╔Execution stage started
+152ms ║║Comparison (string) :544a9b992c238a89c379073fefaa7fe1: is_any_of (string) :544a9b992c238a89c379073fefaa7fe1:,:aa4b274e22d2f4c0001b65e07d3b32bd:,:2fce84ee632722b31122dc1a90d826c3: = true (2ms)
+154ms ║║Condition #1 evaluated true (6ms)
+155ms ║║Condition group #null evaluated true (state did not change) (8ms)
+164ms ║║Comparison (enum) open changes_to (string) open = false (1ms)
+166ms ║║Cancelling condition #3's schedules...
+167ms ║║Condition #3 evaluated false (7ms)
+170ms ║╚Execution stage complete. (28ms)
+172ms ║Setting up scheduled job for Mon, Sep 24 2018 @ 4:05:34 PM EDT (in 189.778s)
+212ms ╚Event processed successfully (211ms)
9/24/2018, 4:00:34 PM +626ms
+1ms ╔Received event [Mike's iPhone].presence = present with a delay of 85ms
+130ms ║RunTime Analysis CS > 21ms > PS > 63ms > PE > 46ms > CE
+132ms ║Runtime (38676 bytes) successfully initialized in 63ms (v0.3.108.20180906) (130ms)
+134ms ║╔Execution stage started
+145ms ║║Comparison (string) :2fce84ee632722b31122dc1a90d826c3: is_any_of (string) :544a9b992c238a89c379073fefaa7fe1:,:aa4b274e22d2f4c0001b65e07d3b32bd:,:2fce84ee632722b31122dc1a90d826c3: = true (3ms)
+146ms ║║Condition #1 evaluated true (8ms)
+148ms ║║Condition group #null evaluated true (state did not change) (9ms)
+155ms ║║Comparison (enum) present changes_to (string) present = true (1ms)
+157ms ║║Cancelling condition #8's schedules...
+159ms ║║Condition #8 evaluated true (7ms)
+160ms ║║Cancelling statement #2's schedules...
+161ms ║║Condition group #2 made progress up the ladder, currently at step 1 of 2
+167ms ║╚Execution stage complete. (34ms)
+169ms ║Setting up scheduled job for Mon, Sep 24 2018 @ 4:05:34 PM EDT (in 299.995s)
+178ms ╚Event processed successfully (178ms)

I just replied over in the other forum.

Cool, thanks!

Seems there is still no news of this being rolled out for UK customers. It’s so annoying that Amazon takes that long to roll things out for UK customers.

Has anyone tried this with zwave sensors yet? Or only zigbee ( which are also, perhaps coincidentally, echo plus compatible) ?

Works with 2 z-wave door sensors I have

1 Like

Agree, so much I want to do when it happens!

1 Like

I was successfully added a routine in Alexa, and it triggered correctly for the multisensor. Hower, the motion sensor detected event didn’t trigger the Alexa routine, I could see the device status changed to detected in Alexa, but action in the routine didn’t happen. I have the older motion sensor with hub v2

1 Like

Still no sign of this feature in the UK. This morning the App updated and there has been big UI changes. They’ve completely re-worked the UI and looks nice. But considering they’ve done all that I thought they might add this feature in by now. But still no sign of this feature for us.

It might look nice, however make sure your phone is fully charged

I’m hoping they roll this out in Australia too! (even though Smartthings isn’t officially supported here)

1 Like

Just checked, its now enabled for me in the UK

2 Likes

Awesome, i just checked mine too and it’s showing on mine too now. Finally :slight_smile:

Really awesome! Thank you for the information!

Regards

Jogi

Apologies if this has been answered already, if so maybe someone kind guide me to the correct post. I can’t seem to find any details on exactly how to add multiple virtual contact sensors

add them in smartthings or add to an Alexa routine?

I understand this Alexa Routine feature only works with Echo speakers. Anybody know if they will allow other audio speakers in the future? I have Alexa but it’s on a Sonos One and two Fire 10 tablets, no echos :frowning: So I cannot use routine to make Alexa speak :frowning:

What is easiest way to have the Alexa routine that I created for say like “Side gate is opened” to Echo Dot #1, Echo Dot #2, Echo #3, etc spread throughout the rooms in the house? Creating an Alexa group called Echos didn’t work.

Use the “messaging“ feature of the routines. See the examples in the following thread (this is a clickable link)

Awesome JDRoberts. Thanks for that tip. It is configured how I want it now.

1 Like