abrayshaw

Yep, my first was a Model 1, tape recorder for program storage. Then moved up to a Model II, then Model III (I still have one of those in my basement), then a Model IV and even a Model 12! Shortly after, I think, the IBM PC's hit the market. Dating ourselves, aren't we!

Geddy - Thanks for your response. I am runnning an ISY944 on Windows 11 with firmware 5.3.0, and have made sure I have the latest Java direct from Oracle's website. I was quite sure I had already done all that you suggested, but to no avail. However, I just followed your lead in your post to be sure (cleared the Java catch, downloaded a new copy of the Start app, etc.) and this time it worked. This reminds me of an article written by Jerry Pournelle years ago in Byte magazine, where he was explaining how to get a file transfer to work between 2 TRS-80 computers: "if you have everything connected properly, hold your mouth right and have the favor of angels, it just might work". I guess I just wasn't holding my mouth right before. Thanks again for your help.

I've run into the same problem as posted above. All of the sudden, the IoX launcher will not open the ISY interface. The launcher opens, finds the ISY, but when I click on the entry, then on AdminConsole (LAN), nothing happens. I've cleared the Java cache, deleted and reinstalled Java, re-downloaded the start.jnlp file. I've power-cycled the ISY. Nothing works. I can ping the ISY's ip address, and the ISY is functioning. I just can't load its interface. I've had this happen before, but was able to get things working again, but not this time. Any suggestions would be appreciated.

In my attempts to troubleshoot my loss of Alexa control, I opened the UD app on my phone, which reported that Izzy was not connected to the internet! So, I dug into the troubleshooting on the Wiki, and found a tip suggesting I take it off a static IP (which had worked for years), and set it back to DHCP. So, I did that, and that resulted in being unable to access it at all. So, I manually rebooted it (ie, power cycled it), redownloaded a new Iox launcher (as suggested in the Wiki), and that finally got me back into the admin console. So far, so good. I then looked at the UD app on my phone, and the "no connection" message was gone, and I could control lights via the app. And, voice control via Alexa was again working. Yippee! I have no idea which of my steps resulted in getting things back to normal, but I won't argue with sucess. However..... I have a new question. When I go back into the Admin Console, click on Help / About, the About screen shows "Internet access: Disabled". I frankly don't know if it used to show this in the past, although I'm pretty sure that would have set of alarm bells in my head if I had seen "disabled". Also, clicking on File / Enable internet access results in an error message "Failed Enabling Internet Access". So, is this referring to some other aspect of internet access, and if so, what the heck is it? Thanks

I just discovered that I'm having the same problem. When I log into the portal, and click on Select Tool / Connectivity / Amazon Echo, I get a message saying "ISY is not online". The ISY is working fine with all other functions (lighting control), bu not through Alexa. I suspect this is a portal issue, and hope UD gets that straightened out ASAP.

Thanks for the input. The "debouncing" at least explains the behaviour I was seeing. Thanks much again.

I've sucessfully interfaced my ISY to Alexa for numerous lighting controls, etc. But I'm having a weird problem with the ISY's communication with Alexa via my portal for one particular purpose. I've connected my hard-wired doorbell button to an X10 Powerflash Interface and set its X10 code. When the doorbell is pressed, the X10 Powerflash sends an "On" signal to the ISY. (I can see this is working by viewing the ISY Event Viewer.) I've set up a state variable named $Doorbell. I created a program that sets $Doorbell to 1 when the X10 code is received, waits 1 second, and resets the $Doorbell variable back to 0. When I press the doorbell button, I can see the variable change to a 1, and then change back to zero. So, I know the ISY is correctly reacting to the doorbell button press. I've exposed the state variable to Alexa via my portal, and have created an Alexa routine to announce "Someone's at the door" when the doorbell is pressed. Here's where it gets weird. When I press the doorbell button, I hear all 4 of my Alexa devices announce "Someone's at the door". BUT, if, a few seconds later, I press the button again, I do NOT hear the announcement. If I then wait several minutes, the doorbell again triggers the announcement. It's as if there's a unexplained "waiting period" before the sequence sucessfully repeats as it should. So, does anyone have any ideas as to why there's such a delay between Alexa's reaction to subsequent button presses? Basically, my doorbell setup works, but not as I'm expecting it to. I think the problem is with Alexa, not the ISY. The delay may be attributed to the action of the portal, but I can't find any reason there. Any ideas would be appreciated.

Thanks, oberkc. Tried that to no avail, but was worth a shot. Thanks

Thanks for all the chatter regarding my question. In response to asbril's post, these Leviton switches were just recently purchased, and are labeled "ZWave Plus". Interesting to hear even older switches that once did respond to manual operation no longer do. That does seem to me like it could be a UD issue, and not the switches. I'm very new to the ISY, so have a recently purchased ISY994i with firmware v.5.3.0 and UI of Insteon_UD994 v.5.3.0. I did find a tip regarding writing a program to detect a Hail and then doing a query. That causes the ISY to now detect the status correctly (i.e. when the light is on by manual operation the ISY no longer shows "Off") but there still seems to be no way to determine if the switch was turned manually or by a program. Guess I'll need to wait to see if a firmware update from UD addresses this.

A question from an ISY994i newbie: I have successfully added 2 Leviton DZ6HD dimmers to the ISY, and have renamed them ("Foyer lights" and "Hall lights"). When I select the switch (Foyer lights) on the Main tab of the Admin Console tab, the status is shown as Off. I can control the lights using the buttons along the bottom of the device's status screen, so I know the ISY can control the switch, and when I do the Status reflects the switch's status (no longer shows Off). BUT, if I manually turn the light on by pressing the switch button, the Status display doesn't change. If the switch is turned on via a program (then statement: "Set 'Z-wave devices/Switches/First floor/Foyer lights' On) the light turns on AND the Status display shows the light is now on. To put it another way, manual switch button presses don't seem to be reported to the ISY. The ISY doesn't "know" if the light is on or off. I'd like to be able to have a program detect if the light has been turned on manually (i.e. not by another program) but see no way to do that if the ISY can't tell what the status is. Hope this makes sense, and hope someone can shed some light on this for me. Thanks