The program/state variable solution works. Seems the hidden door sensor works opposite the iolink sensor on the garage door. Perhaps that could be and option in a future ISY update.

The only thing that I can see that would make all this better is an option to have multiple Echos respond.

1 hour ago, bmercier said:

This means the ISY device you are adding has already been added. Once an ISY device has been added, it cannot be re-added under another spoken.

Use the search at the top-right to search for your ISY device (Descrioption or address).

Benoit

Thank you for your quick reply.

So, if I want to control a light with Alexa, rather than controlling the light as a device - control it as a scene?  (Even though it's the only device in the scene.)  That should allow Alexa turn it on and off (as a scene).

Then, if I want Alexa to make an announcement associated with that device turning on, this should eliminate the error of me trying to add it again (after I delete it from the Portal first).

Going to try that now...

 

13 minutes ago, Athlon said:

Thank you for your quick reply.

So, if I want to control a light with Alexa, rather than controlling the light as a device - control it as a scene?  (Even though it's the only device in the scene.)  That should allow Alexa turn it on and off (as a scene).

Then, if I want Alexa to make an announcement associated with that device turning on, this should eliminate the error of me trying to add it again (after I delete it from the Portal first).

Going to try that now...

 

This will work. However, when using a scene, the state of the scene cannot be queried.

A better alternative is to leave the device as a light, then use a program to set a state variable exposed as an Alexa motion (or contact) sensor.

Benoit

6 hours ago, markv58 said:

The only thing that I can see that would make all this better is an option to have multiple Echos respond.

YES!!! I have several Echos in different rooms and it would be GREAT to allow more than one device to respond.

Edited October 7, 20187 yr by johnjces

On 9/25/2018 at 6:32 AM, bmercier said:

FYI, the only devices currently supported which can trigger a routine are motion sensors and contact sensors.

Yes, exposing a state variable as a motion sensor allows to trigger any routine.

I made it in such a way that a single variable can be used to trigger multiple routines based on the variable value.

Benoit

I'm a Canadian ISY/Portal/Echo owner - is this new functionality only available in US? 

In Alexa Routines I only see "When this happens (Voice or Schedule), Add actions"...

Thanks!

mike

12 minutes ago, mmb said:

I'm a Canadian ISY/Portal/Echo owner - is this new functionality only available in US? 

In Alexa Routines I only see "When this happens (Voice or Schedule), Add actions"...

Thanks!

mike

 

It works in Canada.

Make sure you have a sensor configured, and wait a few hours.

Ref: 

Benoit

 

 

47 minutes ago, johnjces said:

YES!!! I have several Echos in different rooms and it would be GREAT to allow more than one device to respond.

If you select messaging  instead of alexa says and then send announcement you can have all your devices respond at the same time. Only difference is they ding  first. 

I'm having difficulty's getting the Variables working.

v4.7.3

Live Updating is turned on in Portal

Disabled the skill and re-enabled the skill

Deleted and re-add the Motion Variable tied to variable #28 calling it Test.

I can see "Test" change in the Alexa App - under Devices - and it changes when I change the ISY variable #28 so that works as expected.

I can test the routine and performs as expected.

Ran a program to change the variable to "1".

 

Just not getting a variable change in ISY to trigger the routine.

Edited October 8, 20187 yr by memphis2k

9 hours ago, bmercier said:

Yes, if the device is a contact sensor.

It can be queried this way:

Alexa, is <contact sensor spoken> open?

Alexa, is <contact sensor spoken> close?

Some spokens are not easily recognized by Alexa. If you see she has trouble understanding that, try changing the spoken.

Benoit

 

I have tried numerous contact sensors and every spoken that I can think.  Every response is either “... doesn’t support that” or “I don’t know that”.

Can you tell me a spoken that you know to work?

I have tried numerous contact sensors and every spoken that I can think.  Every response is either “... doesn’t support that” or “I don’t know that”.
Can you tell me a spoken that you know to work?

Try ‘hallway’

I have not tried many, but this one did

Benoit


Sent from my iPhone using Tapatalk

Gen 2 Echos are on clearance now that Gen 3 is out, so I couldn't resist and now I have a Dot sitting next to my Google Home just so I can use this functionality. 1st implementation is have her yell at kids to lock the door after they come home. Yes, I know I can (and do) lock the z-wave lock with a program, but this is more fun.

14 hours ago, bmercier said:

 

It works in Canada.

Make sure you have a sensor configured, and wait a few hours.

Ref: 

Benoit

 

 

Thanks, I have the ISY Portal setup and I see the variable setup as a contact and it's visible in the echo.

I'm stuck on Alexa Routines as all I see is "When this happens (Voice or Schedule), Add actions" - ie. no other options. 

Am I missing something?

I am pretty certain that this is not currently working in Canada.

I have added motion sensors, contact sensors and a variables as motion sensors yesterday and still only "Voice" or "Schedule" after selecting "When this happens"

They are showing as sensor devices in my Alexa app.

I am pretty certain that this is not currently working in Canada.
I have added motion sensors, contact sensors and a variables as motion sensors yesterday and still only "Voice" or "Schedule" after selecting "When this happens"
They are showing as sensor devices in my Alexa app.

Some have it working in Canada, including myself.


Sent from my iPhone using Tapatalk

OK thanks.  I am not sure what I am doing wrong as everything else has been working fine for me.

 

Edited October 9, 20187 yr by Outlander

Benoit,

To get around the Amazon state change time limit, would it be a good idea to have 2 variables? Maybe one for critical, but infrequent alerts that you want to make sure they come through and another for less critical alerts that wouldn't be a big deal if missed due to too frequent timing?

What is your best practice for resetting the variable? Currently I'm setting back to 0 in else, but I worry that it might stomp on another program setting to a different number for another alert.

Thanks again, great new functionality.

Mike

18 minutes ago, TexMike said:

Benoit,

To get around the Amazon state change time limit, would it be a good idea to have 2 variables? Maybe one for critical, but infrequent alerts that you want to make sure they come through and another for less critical alerts that wouldn't be a big deal if missed due to too frequent timing?

What is your best practice for resetting the variable? Currently I'm setting back to 0 in else, but I worry that it might stomp on another program setting to a different number for another alert.

Thanks again, great new functionality.

Mike

I'm using another program to reset the variable.

9 minutes ago, TexMike said:

Benoit,

To get around the Amazon state change time limit, would it be a good idea to have 2 variables? Maybe one for critical, but infrequent alerts that you want to make sure they come through and another for less critical alerts that wouldn't be a big deal if missed due to too frequent timing?

What is your best practice for resetting the variable? Currently I'm setting back to 0 in else, but I worry that it might stomp on another program setting to a different number for another alert.

Thanks again, great new functionality.

Mike

The limit is per "sensor".

If you reuse the same state variable for multiple sensors, using a different motion detected value (or Contact closed value), then it's a different sensor for Alexa.

So, no need to have multiple variables.

I would "reset" the variable shortly after to a value such as 0, which would mean no alert (Provided that you don't have a sensor with motion detected value=0). 

If you have another program changing the value, it's the same as if it was changed to 0 for that original sensor. You can think of sensors as binary. They are active if the value is the specified one, or they are inactive for any other value.

But there is a cavest:

If your routine is only triggered by the motion or contact closed event, your good.

If your routine is triggered by the No motion, or Contact open, then I believe it will be triggered multiple times if the value changes to different "inactive" values.

Benoit

 

Benoit

Just tested and you're correct (of course), I can get different alerts almost immediately, just not the same alert. 

As far as reset, I was just worried that my motion would go to 0 (1 minute delay) and reset the variable at the same time a different program was setting it for a different alert (murphy's law). Seems any reset method could theoretically have the same potential problem. Maybe the process is fast enough that I shouldn't worry about it.

Thanks,

Mike

Edited October 8, 20187 yr by TexMike
clarify

5 hours ago, mmb said:

Thanks, I have the ISY Portal setup and I see the variable setup as a contact and it's visible in the echo.

I'm stuck on Alexa Routines as all I see is "When this happens (Voice or Schedule), Add actions" - ie. no other options. 

Am I missing something?

Tap the "+" next to "When this happens".

As noted all I see is Voice or Schedule..  I gather others see more options?

Thanks!

mike

Edited October 8, 20187 yr by mmb

I finally have my vocal notifications working. I had to remove the V3 Smarthome app and re link it. Then all started working.

So if you have tried all of the above then try this.

59 minutes ago, south said:

I finally have my vocal notifications working. I had to remove the V3 Smarthome app and re link it. Then all started working.

So if you have tried all of the above then try this.

Yes thanks

Tried signing out then in again - fail

Tried disabling Smarthome v3 then signing out then in again that re-enabling Smarthome in the app - fail

I do see all of the devices, just no way of referencing them in Routines...

This shouldn't be rocket science...

mike

From the beginning I could that all was working but the vocal notifications. The last thing that I did was just disable the skill and then reenable it. Then all was ok. Sorry if this does not help you. 

53 minutes ago, south said:

From the beginning I could that all was working but the vocal notifications. The last thing that I did was just disable the skill and then reenable it. Then all was ok. Sorry if this does not help you. 

Thanks! I really appreciate your input but unfortunately it doesn’t seem to work

mike