dex

Looks like we posted at nearly the same moment. I'm having the same issue.

Sometime in the last hour, or so, Alexa control of ISY devices stopped working. (9:30 AM Pacific) I tried disabling the skill in the Alexa app, and re-enabling it. After entering sign-in credentials, it spins for a little bit then says "Unable to link ISY Optimized for Smart Home V3 with Alexa." I am able to log into the ISY portal (my.isy.iso) in a browser and it looks like the portal is up. But something either on the Amazon side or ISY side is not connecting. Anyone else seeing this? If not, what additional troubleshooting advice do you have? Thanks! [Posted here because it looks like the Alexa-specific forum thread is dormant.]

Thank you, Michael, for acknowledging you and your team are aware of and working on the problem.

Okay, I started from scratch -- uninstalling everything I can find, clearing out Java caches, deleted programs, uninstalled Java, etc. Reinstalled Java, reinstalled admin.jnlp, etc. Everything is back to normal, programs are showing up. Thank you all for the super fast responses and guidance!

Where is there a button to reload programs? In the Admin Console?

I did delete it and reinstalled from the link. I'm on Windows 10. What's the 'memory flag' and why/how/where do I add it? Thanks!

I have about 15-20 various programs for my ISY 994i with buttons and motion events that cause them to run and do things. They are behaving as expected. Meanwhile, when I log into the Admin Console and look in the My Programs folder, the sub-folders are there, along with the conditions (on select folders). But nothing inside the folders -- the programs have vanished. I've updated Java and completely flushed all forms of cached Java content (settings, applets, etc.), restarted the Admin Console numerous times, and still get this mysterious view of my program folders with no programs in them. I am running... Firmware v.5.0.16 UI v.4.7.3 Anyone seen this before? Should I update firmware? If so, to which recommended version? I see a 5.2 (RC) -- is it stable enough and recommended?

Thank you, all, for the thoughts. Knowing that the Scene Test restricts to Hops=1 is insightful and, I suspect, part of this issue. I do get occasional communication issues on those scenes, so when the Scene Test was very consistently calling out that one device, it becomes a target for deeper troubleshooting. Since I replaced with a brand new device and see the same test results, that [Failed] result is likely just a symptom of the communication issue, not a smoking gun. I examined/compared link tables and found no anomalies. I'll try recreating the scenes and see if I get similar results. Thanks again for the suggestions. It would be great if ISY could run a comprehensive system-wide test and spot patterns and enumerate possible problem areas, with links to troubleshooting best practices and processes. Any such thing exist?

I'd like to better understand what [Failed] really means in the results of a Scene Test. I had assumed it indicates a problem device or communication issue with that specific device. For example, if I see something like this... ----- Scene111 Test Results ----- [Succeeded] Device A [Succeeded] Device B [Failed] Device C [Succeeded] Device D … then I would assume Device C is having trouble. A scene test on this scene always produces the same results with that device marked as failed. However, that same device is in other scenes (with the same peers) and succeeds 100% of the time I run a scene test... ----- Scene222 Test Results ----- [Succeeded] Device A [Succeeded] Device B [Succeeded] Device C [Succeeded] Device D ----- Scene333 Test Results ----- [Succeeded] Device A [Succeeded] Device B [Succeeded] Device C [Succeeded] Device D I did a factory reset on Device C (a SwitchLink Dimmer) and did a Restore Device. Same results. I replaced the switch with a brand new one (using ISY's replace device process). Same results. I did a Restore Device on every other device in the scene. Same results. It may help me troubleshoot if I better understood the possible causes of a device being listed as [Failed] after a scene test. I suspect this sort of thing has been asked and answered before in this forum, but I was unable to locate anything closely related.

As I mentioned in the initial post, I started as "clean" as I could with a couple devices -- delete from ISY, factory reset, add as new device. That's when I started questioning my understanding of [Applied Locally] since it didn't do what I thought it should. With the help of you guys, I've confirmed that my mental model was correct, but the behavior I was seeing is unexpected (and still unexplained). Yes, I can set the On Level and Ramp Rate of these switches manually as described in the owner's info that came with each switch. If I do it manually and then query the device, the ISY settings for those two attributes (On Level and Ramp Rate) are not updated in ISY to match what I set manually in the device. The version numbers I mentioned above were the ones reported in the UI under the name. v.41 on the few new ones and v.27 on the older ones. I misunderstood the question as asking if I knew if that number was correct. In summary, here's what I've characterized in my configuration. With the goal of setting On Level and Ramp Rate [Applied Locally] from the ISY Admin Console... 2476D SwitchLinc Dimmers v.27 do not work 2477D SwitchLinc Dimmers v.41 work 2412S PLM version v.72 ISY 994i Pro firmware version 4.3.26 Having already spent way too much time on this, I'm thinking that I'll just have to stick with manually setting On & Ramp on each switch and not use ISY to manage these attributes. Thank you for the time/effort you've also invested helping me troubleshoot, folks!

Definitely not relays; they are all dimmers. I can set the On Level and Ramp Rate manually. Not sure how to tell if the device version in the UI is correct or not. How would I know? I did try a simple test program (like the one Jon posted above) and it also is not effective at altering the settings on the older switches, but did work when tried with the newer ones.

I've tried within a scene and it doesn't seem to matter. It appears to be something that's different between the older SwitchLinc Dimmers and the new ones. The new ones behave as I expect. Perhaps it's something that couldn't be set by an external controller (e.g. ISY) in the early ones. Perhaps it's a bug in ISY that shows up only when trying to write the older ones. I'm running v 4.3.26 on my ISY.

Sounds like you are seeing the behavior I expect, but am not getting. I too can change those settings (e.g. On Level [Applied Locally]) and real-time see the light adjust as I make that change in ISY. If I walk over and turn the switch off and back on, it does not honor the ISY settings (On Level and Ramp Rate are still appear to be the factory defaults, not what's showing in ISY). My devices are 2476D v.27 SwitchLinc Dimmers. Are yours newer? UPDATE: I have a couple newer switches in my house. I tried the above with a newer one (2477D v.41) and it works as I expect! The switch honors the On Level and Ramp Rate settings. So, my mental model is correct, it just doesn't work on the older switches. Now the question is, is there a fix for the older switches? Is it ISY that's not properly writing updates to the older ones? Appreciate the troubleshooting help, guys ... the fact that someone was seeing what I expected helped me dig deeper.

Thanks, Jon. Makes sense why that would work. I'm still fuzzy on why a program can adjust those settings, but changing the device settings directly in ISY doesn't.

Thanks folks. I understand altering On Level and Ramp Rates in scenes and programs. I'm just trying to understand what those basic level settings do on a device, independent of scenes and programs. Consider this simple case... 1. SwithchLinc Dimmer installed for an overhead light. No 3-ways or anything extra. Just a switch and a light, so yes, this device is wired to the load. 2. Factory Reset the switch. 2. Add the switch to ISY. 3. Within ISY admin console, select the switch device and adjust... On Level [Applied Locally]: 60% Ramp Rate [Applied Locally]: 2.0 seconds changes are written to device 4. Go to the switch and turn it on (physically). The light comes on 100% bright with the default (fast) ramp rate, not 60% with a 2-second ramp as I expected or desired. If I control the device via ISY, the On Level and Ramp Rate are honored as set in ISY. My mental model is that "locally" means at the switch, which appears to be the wrong mental model for what those settings mean.

I've been looking for some very basic information. I'm sure it's out there somewhere, but must be searching for the wrong terms or making bogus assumptions. Can someone please point me to (or post) a definitive description of when, where, and how the "Applied Locally" attributes of an individual device are used? I expected setting On Level [Applied Locally] and Ramp Rate [Applied Locally] would control the behavior of the device when I physically turn it on/off at the switch (in this case a SwitchLinc Dimmer). But that doesn't seems to be the case. I know I can manually configure these switch behaviors through the various press-and-hold procedures on the device itself, but I want to do everything from ISY.

First of all, kudos to Benoit, Michael and the UDI team on the Connected Home Beta. It's magical! Apologies if this has been asked and answered... Pre-Echo Setup: I have a KeyPadLinc, where three of the buttons are used to toggle among three scenes -- Clean, Party and Movie -- where they each control the same set of devices, but to different levels. When pressing the physical buttons, I get the behavior I want. If I press a button that's not lit, that scene activates and the other two buttons go off. If I press a button that is lit (on), all the device in the scene go off, including the buttons. Works great. Echo addition: I've given each of those buttons a spoken name (visible and verified in the ISY portal). But if I say "Alexa, turn on Party" she says "That command doesn't work on device 'party.'" Other ordinary scenes (those not controlled with a KeyPadLinc button) operate perfectly in response to "Alexa, turn on <scene>." Should I be able to control a KeyPadLinc button via the Echo and should it respond just like touching the button when the button is off? If so, what might I be missing or doing wrong? If that's not the correct approach for controlling those buttons/scenes via Echo, what is? Thanks much! - Dex