1 hour ago, macjeff said:

Yep that pretty much sends it up but I think its the speed of the packets.  Either way the refresh does not seem to hold so for now if you have to restart your ISY there is one more step.  Good news is if you are away and there is a power outage you can go into Alexa app and disable and reenable from remote

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.

1 hour ago, macjeff said:

I read it as the last thing you did was install the _03 so I was wondering if that changed anything.

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.

On 3/5/2022 at 6:21 PM, tmorse305 said:

Is anyone else having trouble with routines that use a motion sensor/ISY variable?  The variable is changing, and I can see the motion sensor is triggered in the Alexa app but the routine does not fire.  If I manually trigger the routine it performs the trigger correctly.  There was some discussion in another thread regarding the ISY upgrade to 5.4.0, @Michel Kohanim thought it was Alexa throttling but this is days later and mine still doesn't work.  It looks like an Amazon problem but I'm curious if anyone else is seeing this?

Same issue here. I can see the value change in the Alexa app. But the routine will not trigger. I am manually changing the variable from 0 to 1 to manipulate the motion.  I am using 4.7 firmware.  I did disable and reenable the “skill”. Anyone find a solution?

5 hours ago, fastbird1 said:

Same issue here. I can see the value change in the Alexa app. But the routine will not trigger. I am manually changing the variable from 0 to 1 to manipulate the motion.  I am using 4.7 firmware.  I did disable and reenable the “skill”. Anyone find a solution?

If you disconnect and then reconnect your ISY skill the pseudo devices you have created will have disappeared from existence and you will have to edit each routine, reconnect each device as a trigger and re-enable each Routine.

Some have had success with disabling their ISY skill for a very short time before the updating process in the Alexa app wakes up and "ruins" the Routine triggers.

3 hours ago, larryllix said:

If you disconnect and then reconnect your ISY skill the pseudo devices you have created will have disappeared from existence and you will have to edit each routine, reconnect each device as a trigger and re-enable each Routine.

Some have had success with disabling their ISY skill for a very short time before the updating process in the Alexa app wakes up and "ruins" the Routine triggers.

Mine works fine to disconnect but I am just using IoP, Portal, and Alexa.  No IFTTT.

Very important-  DONT disconnect from Portal or you will lose your devices.

Go to alexa app, search for the ISY skill.  Disable it.  Immediately re-enable it.   You should be good to go.

BUT everytime your ISY reboots you have to do this again.  Thats even with the 5.4.1_2 version which is the latest as of this post.

Michel is working on why this is happening.  He said we are being blacklisted on startup for some reason and thats why the disconnect and reconnect fixes the issue.

Interesting discussion re: Alexa. I too have many "motion sensors" initiating voices and have found the following:

-After initial setup, nothing will work for about 12-24 hours (maybe less idk), but so trying to "test" one immediately after set up (and for the next subsequent 1-2 hours of frustration), it wont work. But the next day (because I usually quit after 1-2 hours), it works!

-Have not had a problem with ISY reboots as far as I know causing Alexa to stop working.

Used to use IFTTT for this and some KASA plugs.. not worth the hassle. Direct Alexa integration and node servers are much easier.

Mine works fine to disconnect but I am just using IoP, Portal, and Alexa.  No IFTTT.
Very important-  DONT disconnect from Portal or you will lose your devices.
Go to alexa app, search for the ISY skill.  Disable it.  Immediately re-enable it.   You should be good to go.
BUT everytime your ISY reboots you have to do this again.  Thats even with the 5.4.1_2 version which is the latest as of this post.
Michel is working on why this is happening.  He said we are being blacklisted on startup for some reason and thats why the disconnect and reconnect fixes the issue.

While that seems to work well, once his routines are all destroyed they won't heal automatically and the routines will need to be touched up.

Sent from my SM-G781W using Tapatalk

36 minutes ago, dbwarner5 said:

Interesting discussion re: Alexa. I too have many "motion sensors" initiating voices and have found the following:

-After initial setup, nothing will work for about 12-24 hours (maybe less idk), but so trying to "test" one immediately after set up (and for the next subsequent 1-2 hours of frustration), it wont work. But the next day (because I usually quit after 1-2 hours), it works!

-Have not had a problem with ISY reboots as far as I know causing Alexa to stop working.

Used to use IFTTT for this and some KASA plugs.. not worth the hassle. Direct Alexa integration and node servers are much easier.

I am going to try and call Amazon today.  I have a master ticket in with them.  They say its on the Universal Devices side but the fact that someone posted they are seeing the same issue with 4.7 tells me its on their side since 4.7 is old firmware that worked fine for me for years and I have a huge setup.

 

I am about to scream.  Amazon OF COURSE said all other skills work.  They also said the skill has not been updated in several years and yes it may be blocked but its not due to a problem on Amazons side. It may be the skill is not following current protocols.

So I asked for it to be escalated and asked for someone to explain to me EXACTLY what needs to be done on our (speaking on behalf of Universal Devices) side. 

They said they will call me back within 3-5 days.

 

17 hours ago, macjeff said:

They also said the skill has not been updated in several years and yes it may be blocked but its not due to a problem on Amazons side.

That's an insult to UDI and specifically to @bmercier.   I'm certain if there was a need to update the skill it would occur.  Fan support was added at some point at least semi-recently, not sure about the time frame tho.  @bmercier has always responded in a timely manner to any issue with the skill.

Edited March 22, 20223 yr by MrBill

5 minutes ago, MrBill said:

That's an insult to UDI and specifically to @bmercier.   I'm certain if there was a need to update the skill it would occur.  Fan support was added at some point at least semi-recently, not sure about the time frame tho.  @bmercier has always responded in a timely manner to any issue with the skill.

I want to be clear this is what they said.  I am actually on a conf call now and the discussion is how amazon has gone down hill from their sales to alexa to the web services.

I will keep on this.  I cant argue I have other motion sensors and its only this skill.

I thought it was a IoP thing but someone posted they are having issue with old 4.7 firmware so that rules out IoP. 

They did tell me the more tickets the better and Michel gave me permission to scream at them  LOL   So feel free to overwhelm them with tickets.

But if there is something I should add to mine let me know.

3 minutes ago, macjeff said:

So feel free to overwhelm them with tickets.

so far I haven't seen the problem first hand.  I do believe there is something, perhaps with IoP firmware causing an issue, and that is obviously a UDI problem and not an Echo issue. Via v5.3.4 on an ISY944 I've not  had an issue... even rebooting ISY, which has happened many times in the last week as I've reconfigured and moved some things around to a new network closet I created.

5 minutes ago, MrBill said:

so far I haven't seen the problem first hand.  I do believe there is something, perhaps with IoP firmware causing an issue, and that is obviously a UDI problem and not an Echo issue. Via v5.3.4 on an ISY944 I've not  had an issue... even rebooting ISY, which has happened many times in the last week as I've reconfigured and moved some things around to a new network closet I created.

Here is a summary of my testing and reports----

I setup a test.  Created variable.  Exposed variable to Alexa as motion sensor in portal.  Set 1 as motion.  Discover devices on alexa and it shows up

Setup trigger that has Alexa announce TEST SUCCESSFUL when its device shows motion (variable is 1)

In ISY, I change variable to 1.  Instantly see it change in Alexa app and should fire routine.  I have had it work first try even after a reboot but sometimes it does not.

If it does not, I just disable and re-enable the skill in the Alexa app.  (NOT PORTAL) and everything works instantly.

Confirmed the same problem happens with real motion sensors in ISY as well as Locks in ISY.  You cant trigger routines from lights and switches as of now but they work fine in alexa even when motion and contact sensors are not.

I also confirmed Contact Sensors have the same issue.

This is what I reported.   I tried with Hue Motion sensors and one other brand motion sensor and it works every time so that is why Amazon wants to push off on the ISY skill.

 

10 minutes ago, MrBill said:

so far I haven't seen the problem first hand.  I do believe there is something, perhaps with IoP firmware causing an issue, and that is obviously a UDI problem and not an Echo issue. Via v5.3.4 on an ISY944 I've not  had an issue... even rebooting ISY, which has happened many times in the last week as I've reconfigured and moved some things around to a new network closet I created.

I'd have to agree with you on this one. I've had more issues with devices i run on polisy than ive ever had with the Isy (as well as devices still on my Isy). Things will get better over time though since the software is still alpha. 

12 minutes ago, lilyoyo1 said:

I'd have to agree with you on this one. I've had more issues with devices i run on polisy than ive ever had with the Isy (as well as devices still on my Isy). Things will get better over time though since the software is still alpha. 

Yea i'm sure it will get worked out... i was going to move my system over to IoP about now, but based on forum reports I think i'll give it at least another 30 days.... re-evaluate at the point...  I've got it running and it has a PLM for testing, but just not using it for 'production' yet.

45 minutes ago, MrBill said:

Yea i'm sure it will get worked out... i was going to move my system over to IoP about now, but based on forum reports I think i'll give it at least another 30 days.... re-evaluate at the point...  I've got it running and it has a PLM for testing, but just not using it for 'production' yet.

Smart move. It's not. I put half my stuff on my polisy. The things on the Isy work perfectly. Wrong devices get triggered on polisy, things turn on when they aren't supposed to, long delays etc. No such issues with Isy stuff. 

Edited March 22, 20223 yr by lilyoyo1

2 hours ago, MrBill said:

Yea i'm sure it will get worked out... i was going to move my system over to IoP about now, but based on forum reports I think i'll give it at least another 30 days.... re-evaluate at the point...  I've got it running and it has a PLM for testing, but just not using it for 'production' yet.

After bricking two polisys with the latest upgrade I have noticed a few different lighting devices turning on at random in the middle of the night. Now I have transferred back to my ISY994 and noticed some still happening. Unplugged the "not-quite functioning" polisy and the random events have stopped. Not 100% yet, and time will prove it, one way or another but, WoLs didn't work at all, still modulus function errors on fractional variable values (existing from ISY994), and internal time clocks are still offset by double the UTC offset. I have found work-arounds for most of it but the random stuff on WiFi bulbs and Insteon Switchlincs had me perturbed. Those I didn;t know about until switching back to ISY994 again (and another f%$ckin' days work and still finding upgrades that I have to recreate in my head ). Currently on hold for commitment point again, until better successes are heard consistently here. IIRC the original IoP was less buggy and no way to undo upgrades yet.

We cannot fix Echo issues. It's 100% related to throttling. It was also reported by someone with 4.7 firmware. 

WOL is low priority. We have no devices to test this feature.

Variables having incorrect time is a UI bug and will be fixed.

Random events being ascribed to Polisy being online is obviously a node server not a ghost.

With kind regards,

Michel