macjeff

Thanks for posting Let me send a better instructions since I was mistaken 5.4.0_2 and 5.4.0_3 fix the issue not 5.4.0 even. I mis-spoke earlier and apologize. sudo service isy stop sudo pkg upgrade isy sudo service isy start pkg version check ISY is now 5.4.0_3 NOW it may work right away or it may not. If not go to Alexa app, skills, search for ISY optimized for Smarthome v3, disable it. IMMEDIATELY reenable it. Now it should work. If you reboot your ISY or your Polisy reboots due to power failure (You should put your Polisy on a battery backup but not the PLM) then you will have to do the alexa step again most likely

I dont use it either. I think it used to be the only way. Now using real motion, contacts, or locks or a variable is the way I think is superior but thats my opinion and I dont want to be attacked for my opinion

No. ISY shows the current x.x.x version not the _version. You would have seen it in the log as it was installing with SSH It would say do you want to install with 5.4.0_3 at the end and you say Y and it installs Sudo and do PKG VERSION and it will show you all the versions. My ISY shows _03

I know that inside alexa the device is being changed but Michel has told me he is 100% sure the devices are being blacklisted when the ISY reboots. They have to write in some throttling so this does not happen. For many of us (and every time for me) all I have to do is disable and re-enable the skill after each ISY reboot. That is a band aid until the permanent fix comes out. If it does not solve IFTTT then I cant help. Maybe someone will find a fix for that. But I literally spent all day Thursday and Friday and even restored my ISY from backup trying to fix this. I can confirm it does not work although Amazon does see the motion sensor or locks change in their app so the data is getting there but at that point the routine wont trigger due to blacklist. btw...I do know how they work. I was on the prototype team for Alexa when all the Echo could do is tell you the weather and play music and tested for UD all the way including routines. I have a master ticket in with Amazon on this and upper level can see the issue but they said its the Skill. Universal Devices said they will work on it but it may not be right away. So I came up with the workaround. I am sorry if it does not work for you, but it has for many.

You are posting in the wrong topic then. The topic is "Routines using ISY variables as motion sensors have stopped working" We are talking about ISY Variables used as motion sensors (and actually real motion and contact sensors too as well as LOCKs) do not trigger routines The IFTTT should be in another topic about IFTTT. That may still be broken but for the topic of this forum the fix we have has worked on several installs. If its not on yours I will try to help but I cant support IFTTT as I dont know it.

I dont even have an IFTTT account and have about 50 different anoucements with routines. You use Variables. A lot faster than IFTTT. Set variable to 1 when an event you want to announce occurs in a program Expose the variable to alexa as a motion sensor with motion value of 1. Create routine (SEE SCREENSHOT) where when the motion sensor (fake variable sensor) detects motion announce. I chose all devices and also send a notification to the phone. IFTTT is slow. I tried it once and killed it.

what verson of the ISY There is a 5.4.0 and a 5.4.0_2 and 5.4.0_3. sudo service isy stop sudo pkg upgrade isy sudo service isy start should bring in 5.4.0_3 which I think is newest. Wonder if 5.4.0 even has issue. I actually just realized I only did this test on _2 and _3. But it worked for others including me several times.

Maybe the reason you lose devices is because of IFTTT. I dont use it. Can you not use fake motion sensor variables instead? Like when my garage door opens I sent GarageDoorOpen to 1 and GarageDoorRelay to 1. I have a routine that announces when grarage door relay is 1 as Jeff's Garage Door Opened and then when its zero Jeff Garage Door closed. Then the GarageDoorOpen variable is used at midnight. If its 1 that means the garage door was left open so alexa announces it. I know I could set a program to close it. We tried that and my wife left the van back hatch door open and the garage door hit it. close to 1000 in damage to the door. So I do the alert and close it manually after looking at camera.

Yes Amazon alexa support is pretty much saying dont use the browser. As I said my guess is a support nightmare with all the browsers- Edge, Explorer, Chrome, Firefox, Safari, and others like Opera.

No but you can easily create my test. And you can try discover devices. Create a variable named TEST In the portal expose the variable to alexa as a motion sensor called Test Variable with 1 being motion Discover devices on alexa. Set your variable to 1 while watching the device on the phone in your alexa app The device should show motion within a couple seconds. Change variable back to zero. Now it should show no motion;. Create a routine If Test Variable shows motion, then announce something like TEST SUCCESSFUL on your alexa. Now change variable to 1 again. Sometimes I had to do this twice but once it works it keeps working on all of them If it does not work disable the skill and immediately re-enable it. Try again. My tests works every time. 5.3.0 does not need this. Tested on 5.4.0_1, 5.4.0_2, and 5.4.0_3 and you may have found another bug with IFTTT. I know Michel said devices are basically being blacklisted because the Polisy sends stuff so fast compared to old ISY. So maybe IFTTT is not fast enough and comes in too late. I am just guessing. But try without IFTTT and if it works now we have a new issue to report with IFTTT

I use the app and lost no devices. Amazon is trying to push people out of the browser to the app so they dont have to support the browser. I like the browser still for some things but I think Routines is removed from browser. I know you dont need it for this task though. But thats for posting you did not lose devices. I remember years ago that did happen to me and I complained. The other day I deleted some devices and added new ones with similar names. When I asked alexa to do something she said there were multiple devices with that name. I went in and the old ones were still there. I manually deleted all of those and then discovered devices. And thats another point. Even if you delete every device you can just discover devices again and they come right back. There is a chance the program would be messed up. Its the portal thats the real brain here.

3 of us have done this and none of us lost devices. You have to immediately re-enable the skill and no devices are lost. No routines are changed. We are talking Skill called ISY optimized for Smart home v3. I just called Amazon support. They said it USED to be that way but now even if you delete a device you must go in and manually delete it. So I tried 3 times in a row. Just DONT discover devices until after you re-enable it. No devices lost on my end. So if you are losing devices you have another problem or you are deleting them off the portal and not the alexa account. The user below posted on this forum and I worked with him doing the same thing and it worked. This is what fixes it. If you are worried screenshot all your devices and routines first. Save your spokens out of the portal. I did all that before the first test but have not needed them once. garybixler

I helped a couple people off the forum and it worked for then. I just did the test again. Rebooted ISY. Routines would not trigger. Disabled the skill and then re-enabled it. Boom it worked. You DONT delete your devices. DONT disable the forum. Just open the alexa app. Go to skills. Search for ISY v3. then hit the disable button. Then hit the enable button. Then authorize it with your portal account. Then it will give you success. When you close that it will ask you to discover devices. Does not hurt to do that but I also tested without and it still works. As long as you DONT touch the portal your devices will be fine. During testing I must have done this 20 times.

I am working with Michel on this. I helped a couple of you so far in Private Messages. Go into Alexa Skills Disable Alexa Skill Immediately re-enable skill. You dont have to discover devices unless you just added a new device. Problem will be fixed UNTIL you restart ISY or Restart Polisy and then you have to do the same. This started in 5.4.0 and they now have 5.4.0_3 but the issue still exists. I created a test variable I can turn on and a routine in alexa that fires when that variable is 1. So I will be testing with tech support.

I am a beta tester for a living so I guess its part patience but I also dive into the bug to give a good report. Sorry if it came off wrong. Tested and working now. thanks

Deleted it totally Reinstalled same slot 3.0 (says 3.01 on install screen but 3.0 after install). Tried a different slot - still 3.0. It has to be a bad upload or something

No matter what I do I cant get it to update. I restarted nodeserver three times. Takes a while but still says 3.0 when you go to config,. Restarted Pg3. Still 3.0. There was a purple air update to 2.01 and that updated on restart of Pg3. Do I need to erase and reload the entire nodeserver?

Did you wait at least 15 min before rebooting. It has to reflash and I made the same mistake and rebooted too early. Just repeat procedure.

Talked to Michel at UD. He said do the 6 quick pushes of the reset button and then walk away for 15 min. Dont do what I did and get impatient. It will reflash and then reboot (you should hear a beep) but I did not. Wait a good 15 min before logging back in even though the light may go away sooner. Worked for me.

I have the flashing light also. But dont want to do this if it will clear anything else. Does Universal Devices agree to do this?

Amazon said they have over 100 tickets and created a master ticket so it looks like its on their end for this one!!!

I am calling Amazon. You should probably call too. I confirmed it is seeing motion on its side but not responding to it.

I use variables. If garage door is closed set variable to 1. When alexa sees variable one it announces the garage door was closed. Seems to be issue on Alexa side but strange it started almost the exact time of upgrade.

THANK YOU You saved me hours of testing. Thinking it was on my end. I have put a ticket in with UDI. I will mention you in the ticket in case they need other logs. Now there is a chance Amazon has the issue and it happened at the same time but if that was the case my controls would not work and they do.

Can someone please test this. Run a program that exposes a variable to alexa as a motion sensor and have alexa run a routing and say something. It was working just before 5.4 update. Not working now. I even created a new one. Variable setup in ISY and expose to alexa as motion sensor and 1 is activation Discover devices In alexa routing put if motion sensor is activated then say something or do something run program in ISY to set variable to 1 I watch the variable change to one but nothing happens in Alexa. **Controlling alexa devices does work Its just the variables