larryllix

I haven't done any testing since the _03 upgrade. I was busy trying to find proof it installed at all. My routines still appear to be functioning despite several ISY and polisy SSH reboots, trying to make the update version display somewhere.

I have never had to redo anything inside the alexa app after many reboots and power cycling polisy yet. But hey! as you pointed out, things change. I will watch for that, and thanks for the warning, and the fix, temporary or not. Fixing these routines takes me about 30 to 45 minutes, each glitch, so I try to avoid disabling my skill as much as possible.

It seems (by logic) in the end this was all caused by Amazon "blacklisting" some device packets from ISY Portal, so that no routines using them would function again until refreshed. That is a whole 'nuther kettle of fish. It doesn't sound like ISY was even involved since it doesn't talk to Amazon directly, but through the ISY Portal bridge system. Sounds like we still need fixes at the ISY Portal and Amazon end. "You send me bad packets and I will destroy ignore you"

Maybe you missed my previous posts. That is what I already reported before updating my IoP version. However, I have been using "Messaging" for years and it is listed under the IFTTT title with the other action techniques. Now, I think we have been reading this incorrectly! IFTTT was formerly in a solid grey band, as a title, above all the action methods listed below it. Now IFTTT appears as just another entry with a distinctly different font! grrrrrr.... I believe I have been trying to tell @oberkcthis (falsely) based on the old screen layout that has fooled many people. OK I take back all the IFTTT crap I have been spouting. Most of us are not likely using IFTTT at all. Just a bad app screen layout. Sorry for that confusion.

Thanks! I used pkg version | grep isy Yes, I am running v5.4.0_3

OK Thanks. They definitely have changed the app a fair bit and I have trouble finding these items again. I set most of my routines up a few years ago. I have some that use "Say" and IFTTT for multi-speakers but looking at them again didn't reveal where IFTTT was used. I did find the small IFTTT title at the top of the bottom grouping of outputs though. BTW: I did try your disable / enable skill with the shortest time period I could manage and it didn't disconnect my pseudo devices for the routines. Nice find! I wonder if the timing is related to the success of this. I am still running IoP v5.4.0. This has been a PITA for a long time with routines and I have placed several support complaints with amazon over the last few years only to achieve no response, yet....but things do seem to clear up after each complaint...so far. hmmmm...maybe that is not completely true. IIRC they responded a few months later once. Also. I have now tried the sudo service....etc to update my IoP but I cannot find any trace of any firmware updated version. Is there some place to find a clue what actual version is installed? My Help | About pulldown and ISY Finder always show "5.4.0" Thanks again!

Only one speaker can be involved with "Say". To announce on your selection of multiple speakers Alexa uses IFTTT. Check the title of the sections above your selections where it is revealed. Some of the menus have changed recently. I don;t even see "make an announcement" anymore???

I haven;t found any other way to make an announcement on more than one Alexa speaker without using their IFTTT connection. For just one speaker, it is a different data pathway, and doesn't require IFTTT. Note that IFTTT isn't something the user sets up. It is built in to the Alexa app software and the user may not even be aware of using it.

You don't seem to understand how many Routines function, and also haven't read the responses to this where people have told you they have tested all the ISY components as functioning right into the Alexa software.

Read the posts in this thread. ISY and ISY Portal are not involved.

Amazon Routine announcements require IFTTT. None of my 40 routines function right now, despite all just being rebuilt (replaced the skill devices that were removed by disabling the skill) again. All pathways have been tested and function perfectly from ISY to voice output. The Routines are not being trigger by tested and proven alexa devices.

MY guess it is the IFTTT connection is broken between amazon and IFTTT. Routines using devices that have been deleted cannot repair themselves to the correct device without human intervention. There seems to be some confusion between devices and routines here. Sure devices will reappear when you enable the skill to connect with them all again, but the routines will have had no trigger device and remain that way until human intervention. I have used three different browsers and the amazon webpages have never supported or even displayed Routines. They must be setup via the mobile app.

All my routines use IFTTT. That may be the difference keeping a routine's trigger with it's missing trigger device. When you remove devices (as in disabling the skill) routine triggers based on those devices become blank and the routine gets disabled. I may try this again later today but I just finished rebuilding all my routines yesterday from this same technique. It takes about 30 minutes of intense finger poking. Routines were never available on a Windows browser, only the mobile apps. I have Alexa vocals that send out test vocal responses as I have had to rebuild these routines dozens of times now, each time devices are deleted by disabling the skill.

Each time you disable the skill, all the devices are removed. When you re-enable the skill, an automatic discover is performed and they re-appear. However my routines are always destroyed and they must be rebuilt and re-enabled. I have done this many times and routines must always be rebuilt.

If you disable the ISY skill in the Alexa app, all your devices will disappear and all your routines will then need to be rebuilt, selecting the triggers again, and then re-enabled. I have done this many times in the past. Despite the trigger points in Alexa fully functioning they will still not trigger the routines. This happened a few years ago and Amazon support did something that fixed it back then.

This is not an ISY or ISY Portal problem. ISY programs change the variables and ISY Portal sends the update to the amazon app and it shows a change in status, ecah time within a few seconds. The routine works perfectly when manually tested and the routine is installed and enabled perfectly. The alexa triggers just do not trigger the routine actions to happen. Mine have been enabled, disabled, deleted, rebuilt, rediscovered and tested throughout every stage. The 30 second delay has been observed, even over the next day many times. The problem is 100% amazon.s software. I suspect it is amazon's interface with IFTTT has broken.

Exact same thing here including the testing getting down to amazon. I put in a support complaint a few days ago and got no response. I suggest other put in an amazon ticket about this also. Mine haven't triggered since Feb 27th.

I have a support ticket launched with UDI on this issue. My program varaible hits are all recorded at 5 hours previously to the real time. The system time clock functions are all off by 5 hours also. At 7:00 PM the [minutes since start of day] return 0 minutes. This is all despite the forefront clocks all indicating EST, my time zone. These time clock problems have always existed on every IoP version. Sunrise and sunset times are also off by 5 hours.

@Michel Kohanim I have the same problem with my polisy clock(s). Program changes to variable record them 5 hours too early (I am in EST) Manual vaiable value changes report the correct times. I also found the system [minutes since beginning of day] uses about 5 PM as a base time instead of 12:00 PM. Admin console shows current time and sunset/sunrise as correct. I have opened tickets for both these problems since I ported ISY9994 code over to polisy.

Good catch! Repeats usually need a terminator so that following lines don't repeat in a loop fashion also. In this case of an infinitely repeating time loop, there is "no out". UDI needs to implement a Break on xxxxxx condition construct yet.

You have a useless Repeat construct. The lines to be repeated are found indented under the repeat loop construct command. To terminate the repeat loop use Repeat 1 times after the lines you want repeated. Repeat every 30 minutes .....do something in a loop Repeat 1 times do the rest only once. If you want two condition you can use this construct Repeat 20 times ....do something 20 times ....Wait 20 minutes Repeat 1 times Do more lines only once Etc... Move your Repeat line up one.

Posting this concern in a thread about polisy, has caused some confusion here. The thread titles tend to get missed once you scroll down through them.

Much simpler and safer to access your ISY via the ISY Portal, using pulldown menus inside it. There have been many reports of hacking people using port forwarding. Not really recommended. Also while I was away on a cruise, my power went down long enough that my ISP issued me a new IP address (first time in 8 years), and I had no access until I got home.

I don't use nodeservers for time functions. I use the native time functions provided inside ISY in programs and notifications. There are various formats that ISY provides built-in.

When you say Alexa...turn off xxxxx The program runs the else section of the program nicknamed xxxxx.