thruster999

Since the outage my Alexa Routine triggers (motion sensor) no longer work. Anyone else having that issue? Thanks.

Thank you very much for your help @Geddy! I was able to check my license and I'm good. And thanks for making me aware of the current issue. Very much appreciated!

Hi, today woke up to ISY99 showing as registered but OFFLINE in my UD Portal. I've recently moved / updated credit cards etc. How do I check to see if my annual payment went through - or least to see why my ISY is offline? Thanks

Hello @larryllix and @dbwarner5. So last night, everthing started to work again (down for 2 weeks). I contacted Amazon (with ticket ID) to ask them what they chaged. They said nothing was done to resolve my issue specifically. So they didn't know why it started to work again. However, they asked me a few questions including the date and time everything started up again and said they would investigate if something had changed on their end (on the 1st and on the 14th - the beginning and end of the issue). They said they'd email me if they found anything. Not gonna hold my breath.

Hello @larryllix and @dbwarner5 and everone in this thread. Just wanted to say thanks for the help. Dealing with Amazon support was insane. I had 12 agents ask me to do the same troubleshooting steps (12 times!) ie uninstall and reinstall the app, deactivate, reactivate the skill, disable, reenable the routines. create new motion sensors, create new routines, change the name of my echo devices, deregister, register etc. All but the last one agent dropped me without explanation. Anyway, the last one finally escalated it (opened a ticket) and they are going to look at my account first - to see why these Routines (related to ISY) are not running despite the change of state in the device. Thanks again

Hello @larryllix, thanks for your help. Yeah the Routines are enabled. I even started a chat with Amazon Support to make sure. What's weird is that when I change the state of the variable in the ISY, the related device I setup in the Portal reports "Motion Detected" in the Alexa app under devices (and vis versa). Depite this trigger, the related routine does not run. As I mentioned earlier, these Routines have been running for years, same smart devices, never dormant. The Routines just stopped running a few days ago. Since this is still working for other UD members in this forum, I have changed my mind - this has to be an Amazon issue since the Device state is changing in the app. btw the goto advice from amazon support is to delete your app (and the routines - even if you have dozens) If I learn anything new from Amazon I'll post it Thanks again

@dbwarner5 Thanks!

Hi @dbwarner5, if it's not too much of a bother could you post a screenshot of your portal screen for this variable please? Thanks

@dbwarner5, just want to clarify ... did your first example work as a Alexa Routine "WHEN" trigger? ie did your state variable trigger an Alexa Routine? Thanks!

Actually @garybixler you're probably right. It appears to be that ANY Alexa Routine triggered by a state variable is no longer being triggered and run when the state variable changes.

Hi @dbuss! Yes I have. I've run the ISY programs manually (then, else) to make sure the related state variable has been changed correctly (key is changed because its not a trigger if the state hasn't changed). And I've even changed the state variable manually in the variables section to no joy. And lastly, when I play the routines from the Alexa App they work great. As of 3 days ago these routines are no longer triggered when the state variable changes. prior to that they had been working for years! btw I spoke to Amazon and of course they blamed the UD skill - but of course they would :-). But I do think it is UD because as I mentioned earlier, all my other Alexa routines work great including those triggered by a motion detector that is not setup in the UD Portal. It's only routines triggered by Motion Detectors and Contact Sensors setup in the UD Portal. Thanks!

Thank you @larryllix and @garybixler My Alexa routines are definitely enabled and working - at least those that are not triggered by a Motion or Contact sensor setup in the UD Portal. For instance, when I use Alexa to call to turn on an Insteon Switch or to run an ISY program that turns on Insteon Switches (voice commands setup in the UD Portal), it works great (as always). Also, Alexa Routines not related to or dependant on the UD Portal work fine as well. I've narrowed this down to only devices setup as a Motion Detectors or Contact Sensors in the UD Portal. I believe something in the UD Portal was changed a few days ago and broke this. iow this is not an Amazon or Alexa issue. For instance, I have a motion detector at my front door which is recognized by Alexa as a Smart Home device and is NOT setup in or related to the UD Portal. When this motion detector is triggered the related Alexa Routine runs and notifies me. So, I don't think it's Alexa. btw I tried unlinking and relinking the UD ISY Skill (and rediscovering all devices) to no joy. I even deleted all the Motion and Contact Sensors I setup in the UD Portal from my list of Alexa Smart Home Devices and then rediscovered them successfuly - also to no joy. Thanks again

For the last couple of days Alexa does not recognize the state change of "Motion Detectors" or "Contact Sensors" that I created in the portal. For instance, I've setup a number of state variables in the portal as either Motion Detectors (multiple states ie 0, 1, 2, 3 etc) or Contact Sensor (two states either 0 or 1). So if a ISY program changes the state of a state variable, this triggers an Alexa Routine. I've been doing this for years. Even created some new ones last week. However, Alexa has not recognized these state changes for the past 2 days. Did I miss something? btw All other portal related functions appear to be working fine. Thanks

Hello @Michel Kohanim Would that include DarkSky (is it removed?). It still shows up as active but I can't stop or start the service - and my ISY is not retrieving data from it. Other than that I can login fine and my dashboard loads fine as well. Thanks

@bpwwer thanks very much for getting back to me. Anyway, the issue still persists. @Geddy described it far better than I did. Thanks

Hi Pretty much out of the blue (last night) I can no longer connect to Polyglot from the portal. The page sits there "Loading ...." forever. Most times it does this refusal to Load while authenticating. However, on the rare occasion the Dashboard loads (after serveral minutes of "Loading ...") it reports I have successfully logged in but the Dashboard does not recognize my ISY, it MAC Addr or any of the nodes I use. On the flip side my ISY cannot connect to any of the Node Servers such as DarkSky. So far I've tried several soft and hard reboots of my ISY, rebooted my router etc. Any other suggestions? Much appreciated

It appears the portal command (with alexa) for "set/lower/raise" syntax is broken. When you give a "set" command alexa will respond with "what setting?" And any response to that produces no reaction. Notably, if you change the Alexa Category to 'Light' the commands work correctly.

Thankyou very much @asbril, @lilyoyo and @Bumbershoot One other thing I like about Insteon was that I could also link the motion sensor to the light switch/dimmer which gave immediate results i.e. no delay in activating the light switch/dimmer. So, which motion sensor would you recommend to use with your Homeseer dimmers/switches? Could you link them or do you need an ISY program to turn on the scene? Thanks again!

Hi Well, I've been using Insteon switches, dimmers and motion sensors (controlled with my ISY) for 14 years now and have been happy with them. However, it appears they are starting to fail. In the last six months 2 of my dimmers, 1 on/off switch and 3 motion sensors (MS 1) have stopped working and have had to be replaced. Each device either just stopped working or the lights would flash on and off - eventually not coming on. Anyway, I'm thinking of replacing each future failed INSTEON device with a z-wave device. I only have a few z-wave devices now but they work very well with my ISY. Could anyone recommend z-wave switches, dimmers and motion sensors that work well with the ISY and are capable of being set to different scenes multiple times per day (i.e. brightness and ramp rate)? Thank you

Has anyone else run into any of these? When I installed 5.2.0(RC3) a number of problems arose making my ISY dead in the water: 1) Alexa can no longer communicate with my portal "The hub that device ... is connected to is not responding". 2) Polyglot no longer sees my ISY " Requested ISY not online" 3) Almost all of my Motion Controlled Responders (not the motion sensor but the device being controlled) are in a "1011" state. And its continuously writing to these devices and failing - putting my ISY into a constant busy state. 4) I receive several errors after a few hours "can't communicate with devices" BUT, As soon as I go back to 5.0.16 - everything is good again. I've installed 5.2.0 three times now - with the same results. Have had to back an reload 5.0.16 each time. Thanks

Just adding to Mr. Bill's comment: I have several Motion Sensors and update (adjust) the related scenes twice a day. As a result my experience with v5 is not good. My ISY is constantly in a busy state and bogged down. This slowness also interferes with other functions like voice commands - from delayed response to no response at all. It also appears that UD has no intention of fixing this bug anytime soon. So if you have a good number of motion sensors and use them as controllers in scenes and adjust these regularly I would NOT install v5.

@Michel Kohanim hi Michel, respectfully I think it is. I just wanted to point out (in my previous post) a potential reason why your team might not be able to replicate it. thanks

Hi @Michel Kohanim No. I believe these are MS 1's (I don't have any MS II's). See the pics below - this is the "bad" sensor I describe in my last post. Also, it is my understanding that when a scene is updated only the Responder should be written to. In both the "good" and "bad" examples I described in my last post the Controller is written to as well. Thank you

Hello @Michel Kohanim I use Adjust Scene programs on all of them. And as for the scenes they belong to they are all pretty standard i.e. Motion Sensor as the Controller and a light switch as a Responder. The only difference I see is the revision of the Motion Sensor. For example, one of my Motion Sensors is a #2420M 1810 Rev 2.0 and I don't experience any issues with it - the related scene updates fine and there are no subsequent unnecessary updates. Notably (however), when the scene is updated BOTH the Controller and the Responder get written to. Another example: I have a Motion Sensor 2842-222 1715 Rev 2.6. This is one of the Sensors where I experience the constant writes. The related scenes update fine (again both Controller and Responder get written to). However, subsequent to a successful scene update and then many times per day throughout the day, my ISY attempts to write to this Motion Sensor and fails causing subsequent attempts etc. I have no idea why these writing attempts are occurring i.e. there are no program triggering it. I've tried swapping "good" sensors with "bad" ones in an attempt to track down errant programs. Its not the programs - its always the same sensors that have the issue. Thanks

Hi @Michel Kohanim I continue to see these issues as well - I'm not sure about a queue of built up writes but my ISY appears to write to my motion sensor when there is a scene update. My understanding is that only the responder should be written to. And on top of that my ISY *repeatedly* tries to write (and fails) to some of my motion sensors (and not the controller) even after a successful scene update . As a result I have to turn off writes to battery devices because these continual write attempts bog my ISY down ("system busy"). Anyway, to add to this discussion, I don't see this happening to all my motion sensors (I have 22). It appears to happen to only a handful of the same sensors. I might buy a few new replacement motion sensors to see if this fixes this issue. However, I'm a bit worried about the investment because the effected sensors are newer. Thanks