grtaylor

I'm on 4.7.3.

I didn't read it as that, or rather, I doubt that's my issue as my motion sensor variable already has a wait of 31 seconds. A factory reset of ISY to solve this sounds a bit ....

Mine looks just the same. I re-opened the device page, and it shows no motion since I was playing with this earlier today. It only reports that has detected motion when the app is running and ISY sets the variable. It was just triggered, it just updated. Makes me wonder though - If you don't have the Alexa app running, something triggers your variable, and then you re-open the Alex app - is the 'Inactive since' correct? When I open the app it only reports the last time there was motion zand when the Alexa app was open, not the last time there was motion, if you get what I mean?

I just checked, and I built a 31 second delay into mine in ISY. When the Elk motion sensor is violated set variable Alexa to 1. This is the variable that Alexa sees as a motion device. Then I have another program - if Alexa variable = 1 wait 31 seconds and then set back to 0.

I have followed that article to the best of my abilities and think I have done it correctly. I ultimately want to use an ISY variable, triggered by a program, not an Elk motion sensor, I'm just using that to test and make it easier so I don't have to keep triggering a program. So right now, an Elk motion triggers an ISY program, which sets the variable. That variable is set up as a motion sensor in Alexa. I have confirmed/done everything listed on the FAQ page under "I can create a routine, but it does not get triggered" So yes, I see the device change in the Alexa app, and the device has been both a motion sensor and a contact sensor. Both show as triggering when the variable changes. But neither cause the Alex routine to fire.

Sadly, I don't think either apply. I'm triggering the variable/motion no more than once a minute (it's an Elk motion sensor in this case actually tripping, and I think they have a built in 30-60 sec reset period). The routine is pretty darn simple - and if I hit 'Play Routine' it works perfectly. The action (turn on a light using ISY) works immediately.

Similar for me Michel. I see the variable change in ISY, Alexa sees the motion sensor device change when the Alexa app is viewing that device, but it does not trigger an Alexa routine.

I just used Alexa Test or something like that.

Sorry if my earlier reply wasn't clearer - I did all those things as you described. No change.

I checked the status of the routine, disabled and re-enabled the skill, and even tried using a contact versus a motion sensor. No changes.

Good to know it's not just me, but not that they seem to care so little. Is there any diff between creating the device as a motion or a contact sensor I wonder?

No change. It seems the only time Alexa recognizes the motion sensor as 'triggered' is when I have the app open at the device page. That shows as motion detected (it's actually an Elk motion, connected to ISY, setting a variable doing all this). This seems simple - but Alexa just isn't triggering. When motion is detected - turn on a light.

The routine is enabled. an ISY program sets a state variable which Alexa sees as a motion device. the Alexa routine is set to trigger when the motion device is activated. But it does not. But if I observe the motion device itself in Alexa, it gets set just fine.

Yup, state variable. I see the motion device in Alexa trigger when the variable is set to 1. Yet the routine doesn’t t fire.

Actually this is a test. The end flow will be HomeSeer to set a variable in ISY, slow I can trigger a routine to control a device that I can only control with Alexa. I haven’t found a way to create virtual devices in Alexa using HomeSeer. the ISY program works perfectly. If i am in the Alexa app and the program sets the variable Alexa sees the motion.