BOden

Short answer.... I did not have a chance to check the hold (wait) time before the factory reset. I'd update firmware and check the hold.

@tmorse305, @grtaylor, I'm on version 5.3.0. I think I read you need 5.?.? something to connect to Alexa but TRULY..... I'm not solid on that and probably shouldn't start rumors lol. An admin tech would probably set us right on that. I've read so many different version things lately on so many projects I could be overlapping info! If someone could let us know that would rock!! But before I muddy those waters more than I think I might have already.... Let me explain what happened to me and why I don't want to jump into telling anyone to factory the PLM or ISY, *After joining this thread I tried again to fire routines and failed. Prayed over it like a .... and it didn't work. * @larryllix suggested I set a var state hold time of 30+ seconds. But.... I had just started an updated from "5.0.somthing" *updated to 5.3.0 *When I did the update, I wanted to check to make sure I was running the latest admin console software. so I googled "universal devices admin" and selected the link. *the link was a direct download of an "admin" console at the universal site. That was a different console look and had sliders, so I figured it was an updated version!? This is where my nightmare started! hahaha *I developed some kind of overlap in java and started getting failures in the admin load screens. it was like I had two competing versions. My bad!! I didn't clear the java, but the sliders version gave me problems even after I did. *In my frustration, and I kinda like to wipe the slate when I have major problems and narrow the possibility's. *I got up and running again with the original admin console (without the "sliders" ) and new firmware and set the time on the "device hold time to 31 sec" as @larryllix suggested. * it worked! Unfortunately, I can't say what worked definitively. One the other or both, I just don't know. I'd update the firmware for sure though! I'm sorry I didn't have time to test the "hold" time before the update and factory reset. I know this is frustrating, trust me ... I'll attach the two different admin screen shots I had just for.... I don't know, I guess things to avoid. Please don't factory without an admin tech chiming in but if you do I understand where you are at!! I don't want to steer people in the direction of unnecessary work. I only have a couple of devices so it wasn't really a big deal.

@larryllix, thanks for the "how to" on the tag and wait time! Yeah saw your comment. Sounds like some tinkering going on in the background. That's really crazy that suddenly your variables trigger off false! I wonder if something they did finally connected mine? Now I've gone cross eyed.... ?

Sorry, guys I'm really not sure if taking to factory had anything to do it now working, it might just be coincidence as I never got to check the wait time Larry suggested before I had a bigger issue to deal with. Could have been one, the other or both, but my sensor II was initially set for a 15 or 20 sec hold time before I changed it to 31 sec. Unfortunately, I'm not comfortable suggesting factory reset to solve the issue. This is the first time I'm hearing of hold time. It sounds like you're sure the hold time is longer than 30 sec and to be honest I don't know why it would make a difference on the first routine firing as the Alexa response is reporting within a few seconds. I could understand the second request for a routine within 30 sec, but I don't know how those (magic) part works. I'm sorry, I wish I had more information. I'm seriously new to this form (love it) how do I tag someone?

Update.. First off; huge shout out to Michel for quickly responding to my ticket this morning (ISY is back up and running)! Here's what happened to me. My configuration had some issues so I took it all back to factory (I don't know if it was related to the issue here). I loaded the Sensor II, set the variable state but I decided to skip the "wait" in the program and went straight to the device and changed the hold time to 31 sec like Larry said. It works now. Thanks guys!

Ahhhh, I did not set a var state to a "wait" time before returning to initial state. I mean that seems legit because it could fire every few seconds in some conditions. I do believe the reset state in the sensor II is shorter than 30 sec. I'll set a wait time of 60 sec or more and report back.

Hi Michel, The "Variable State" is changing from 0 to 1 when motion is detected in the admin console as I configured in the program. *Both the device and "state variable" have been configured into the portal *New devices where found in Alexa app and added. *The var and device both indicate in the app and admin console when motion is detected and not detected properly. *The "Routines" are enabled. *Please note: I can control devices with voice commands. *Please note: I can play back Alexa routines with the app and though voice commands. *I kept the routines to "Anytime" for testing purposes (less to worry about). *Enabled and disabled the routines, deleted everything and put it back in the portal, every combination, even down to factory resetting the ISY and PLM. One of the last suggestions in the thread was to disable the routine from the app and re-enable it from a PC ?... I downloaded the Alexa app to my PC but, like the fire TV, I cant access the motion device or state variable from PC and it doesn't give me the option to get to my routines (unless I've overlooked it ?‍♀️).. UD told me 6 months ago it was an Amazon issue. And I think ultimately, if you are receiving both the state var change, in addition to the actual device state change in the Alexa app, then everything on the ISY side and portal is working, soooo.... it's really just a matter of finding the right combination of kicks and punches to the Amazon server to get it started... ? Sorry Michel, I'm new to the forum and don't know how to tag you back in the responses.

*I have disabled and re-enabled the skill *Disabled and enabled the routine *Deleted and Recreated the routine *deleted and re-created the Alexa portal links to the device *disabled and re-enabled the to the ISY portal Note: I haven't tried to disable the routine from the app and and re-enable it through the web interface yet. (I will try it) sounds clunky, but hey I'll sell my first born to get it to work. LOL JK I'll look into it again soon. Let us know if you have any luck, I'll do the same. .

I have the same problem. Sent emails to UD, they said it was Amazon problem, took the dive and called Amazon, they walked me through the same process on the phone several times and said they were stumped. They said they would have a tech call me, I didn't hold my breath. lol, they never called me back. But anyway, I can see the variable change in ISY and in Alexa app but the attached routine does not respond. I can control devices through the portal and I can play the routine from the app. ?‍♀️ I have read that some people have had luck starting a new Amazon account, but UGH... Good luck though!!