bmercier

Alexa does not know state variables. I however knows about motion and contact sensors. Have you configured an Alexa Motion or Contact sensor using the state variable, in ISY Portal? Have you then run a device discovery (Alexa, discover my devices)? Benoit

Excellent, thanks for the feedback! Benoit

Try to disable the skill, and re-enable it. It is likely to fix the problem. Benoit. Sent from my iPhone using Tapatalk

Did you turn on Live Update in ISY Portal?

Are you exposing state variables as an Alexa sensor? Are you perhaps exposing the same state variable as multiple Alexa sensors (using different values)? Benoit

About the delays, I can tell you that the detection is debounced with a delay of 30 seconds, as per Amazon specs. If the sensor changes come too rapidly, some will be skipped. In other words, the Alexa sensor will always stay in the open or closed state for at least 30 seconds. So let's take an example: Sensor is initially Closed (since at least 30 seconds). At t=0s, sensor is Open -> Alexa Sensor will change to open immediately At t=10s, sensor is Close -> Alexa Sensor will stay open (Up to t=30s) At t=12s, sensor is Open -> -> Alexa Sensor will stay open (Up to t=30s) --> This one is skipped At t=22s, sensor is Close -> Alexa Sensor will stay open (Up to t=30s) At t=30s, Alexa Sensor will change to closed At t=40s, sensor is Open -> Alexa Sensor will stay closed (Up to t=70s (40s + 30s)) --> This one is skipped At t=50s, sensor is Close -> Alexa Sensor will stay closed (Up to t=70s) At t=70s, Alexa sensor stays closed (The physical sensor is closed) Benoit

I'm not aware of native Google Home support for multiple homes. Can you share what you have seen? For now, the only method I know you could use is ISY to ISY communication using Rest commands & network resources, but it's rather tedious. This involves Alexa controlling a program, which runs a network resource which talks to the other ISY through ISY Portal.

When you have a device as a controller in a scene, it will only turn on/off the scene when physically activated, not remotely. This is how insteon works. Somehow, it looks like Mobilinc reads the scene, and activates the scene when it sees one of the member being controlled. Here's a way to do the same thing with Echo: Create a program like this: IF Device is not off Then Turn on Scene Else Turn off scene Expose that program as a Light. You will be able to control your scene using Alexa, and it will hold a status (The true/false status of the program). Obviously it can't be dimmed, but at least, you will have a status. One of the drawback to the above is the additional Insteon communication that will occur. Whenever the scene will be turned on, the member device will turn on, which will trigger the program, which will trigger the scene. The propram will be triggered only once, because once the device is on or off, it will stay in that state, and not trigger the program.

The original "ISY" skill has been sunset and no longer works. Please disable the "ISY" skill. Benoit

I would try a different room name. This message meands that the group name is similar to another group, or to one of the devices. Benoit

Possibly. I don't know why it would not appear.

Good point, I had forgotten to set init too. Benoit

Please look at ISY Portal, Connectivity | Amazon Echo. Is the "device" you are trying to control an ISY device, or an ISY Scene? You can't assume that because it's under lights, it's an ISY device. You can have an ISY scene appear as a light in the Alexa app. Benoit

1. In the admin console, create a state variable 2. Create a program If sensor=detected then variable=1 else variable=0 3. Create Alexa spoken using the state variable you created. Expose it as a sensor, with a motion detected value of 1. The idea is that your state variable will follow the state of your sensor, except that the state will be persistent. Benoit

An ISY scene can be exposed as a light, which would make it appear in the list of Alexa devices. Benoit

Instead of exposing the sensor directly, you can expose a variable that is set by a program that reacts to your sensor state change. Benoit

Could it be that the device is an ISY scene? Benoit

I have an Echo show, and an older echo similar to this one, but black. Benoit

I do not know the cause. All I know is there is a user who contacted Amazon support, and when they tried it, he found out it was now working. So I don't know if just waiting is sufficient, or not. If it does not appear within 1-2 days, I would try Amazon support. Benoit

ISY Portal has no direct support for ELK outputs. This needs to be controlled by an intermediate, such as controlling a program, or a state variable that triggers a program. Benoit

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

Some have it working in Canada, including myself. Sent from my iPhone using Tapatalk

Try ‘hallway’ I have not tried many, but this one did Benoit Sent from my iPhone using Tapatalk

Please try again. Now you should be able to turn off a scene in a routine, as long as the percentage is < 50%. (Recommended is 1%) Let me explain what is happening. Interestingly, when you have a scene in a routine, there are 2 commands sent in the sequence below: When turning On: Activate Scene, then Set Brightness. When turning Off: Set Brightness, then Deactivate Scene. So, when turning off, a Set Brightness was sent, and the minimum value you could choose was 1%. Because this is a scene, the brightness can't really be set, so any value >0 had the effect of turning on the scene. So, the whole process turned on the scene, then turned it off. When you turned on a scene in a routine, the above had the effect of turning on the scene twice, which was not noticeable. The Set Brightness for a scene has been changed such that any value>50 will turn on the scene, and <50 turn it off. Benoit

Thanks, I tried it and I'm able to reproduce the problem. Let me find a solution. Benoit