marksidell

Thanks for the info. I've confirmed that using the ISY finder prevents the multiple login prompts. I was able to use the generic URL http://www.universal-devices.com/99i/. Very strange.

Roger that on the ports. I was guessing the ISY might use some other port for event notifications. I tried disabling the firewall on my computer, and I still get multiple login requests. (Since the ISY and my computer are on the same local network, I assume that my public-facing router/firewall settings don't apply.) FWIW, I get the multiple login requests on both my desktop and laptop. Both are running Windows XP, and I use the Chrome browser.

Thanks. Now it all makes sense!

Thanks for testing this. I set up the button as you suggested. And now it is sending an On command. Previously, when I set it up this way, I was puzzled that the button's default state ended up being On. I had assumed it would be Off and, when I pressed it, it would flash (on), send the On command, and then revert to off. But, it looks like putting a button into non-toggle On state causes the button to stay on all the time. Interestingly, I can push certain other buttons on the keypadlinc and cause the non-toggle button to turn off. I have no idea why that happens, since presumably none of the buttons are grouped. IAE, if I do cause the button to turn off, at that point and thereafter, pressing the button sends an Off command. Given all of this strange behaviour, I think I'll go with my plan of leaving the buttons in toggle mode, and use an ISY program to simulate non-toggle mode, by having the program turning off the button that triggers it.

Thanks for the info. Yes, the button is sending an Off, and when I configure the program's If statement to trigger on the button being turned off, it works.

Thanks for your help. The ISY reports the keypladlinc is v.29. (FWIW, my new keypadlincs are v.36.) As you suggested, I tried turning the button ON before using the ISY to set it to non-toggle mode. After doing that, here is what I see when I press the button: Tue 01/17/2012 09:31:07 AM : [ 7 DF 1 3] DOF 0 Tue 01/17/2012 09:31:07 AM : [ 7 DF 1 3] ST 0 Looks the same as before. I can try configuring the button locally at the keypadlinc. But, boy, the instructions for doing that are rather complex and ambiguous! Another idea I have is to give up on non-toggle mode for these older keypads. I could simulate a non-toggle by having the button's On command trigger an ISY program that runs my scene and then turns the button back off.

Thanks for the reply! What TCP port(s) does the ISY use to send events? Or, more generally, what TCP ports does the ISY use to communicate with the admin console (and other programs that use its restful API), aside from 80 and 443?

It's an old keypadlinc, one of the first they shipped, I think. When I try to set the toggle mode on a newer model, I do see the choose toggle-mode pop-up you describe below. So, the older keypadlinc must be programmed differently. It appears that the ISY tries to deal with the older keypadlinc, and instructs me to physically press the button to choose the state I want. I assume this means to choose whether the button sends an Off or an On command. So, here's what I tried this morning: 1. Use ISY to set the toggle mode. 2. Choose non-toggle for a button. 3. When the ISY tells me to physically press the button, press it so that it is ON. 4. Click Ok on the ISY pop-up. 5. At this point, the ISY says the button is in non-toggle mode. 6. The button is still on. The only way to turn it off is to press the bottom OFF button on the 6-button keypad. 7. Now the button is off (which I presume is its default state). 8. Press the button. It flashes twice, and presumable sends a command. Here is what I see in the event viewer: Tue 01/17/2012 08:46:40 AM : [ 7 DF 1 3] DOF 0 Tue 01/17/2012 08:46:40 AM : [ 7 DF 1 3] ST 0 Hmm. Is that an Off command? 9. Use the ISY to revert the button to toggle mode. 10. Repeat the process to set the button to non-toggle mode. Only this time, do not physically press the button, thereby leaving it in the OFF state. 11. Press the button again. As before, it flashes twice. Here is what I see in the event viewer: Tue 01/17/2012 08:50:22 AM : [ 7 DF 1 3] DOF 0 Hmm. Am I doing something wrong, or should I conclude that this old rev of the keypladinc simply doesn't do non-toggle mode correctly? I should add that when I set the button to toggle mode, it does send On and Off commands, which do trigger ISY programs. But, no matter how I configure the button in non-toggle mode, I cannot get it to trigger a program.

Sorry, I'm confused. There are no on or off buttons in the pop-up. The pop-up tells me to physically press the button I'm changing. If I (physically) press the button so as to turn it on, and then press Ok in the pop-up, what does that do? Does it configure the button to send an On command when I press it? More to the point, what is the procedure to follow to configure the button to send an On command when it is pressed, and to be non-toggle? Also, even when I (think) I have set the button to non-toggle mode, pressing the button fails to trigger an ISY program. Without changing anything in the ISY, if I change the button back to toggle mode, pressing it DOES trigger the program. So, I'm puzzled why a button configured for non-toggle fails to works as a program trigger. Regarding, the 6-button on/off buttons, yes I understand. Only the 4 other buttons can be set to non-toggle mode.

Microsoft Security Essentials and the Windows Firewall.

I'm trying to configure a keypadlinc button to work in non-toggle mode, so that pressing it triggers an ISY program. But, I can't get it to work. 1. In the ISY console, I select the keypadlinc I want to configure, and press [buttons Toggle Mode]. 2. Then, I click the button I want to change, and press [Toggle On/Off]. 3. The program displays the somewhat confusing message "Physically click on , choose your desired state (on/off), and then click on Ok. What does this prompt mean? Am I supposed to get the button into the "default" state (on/off) I want it to be in before I press it? Or am I supposed to get it in the state (on/off) representing the signal I want it to send when I press it? Or something else? IAE, I've tried configuring the button both ways. Either way, it doesn't seem to work. After I have configured the button for non-toggle mode, I write a program where the If clause triggers on the button being switched on, and the then action turns on a scene. But, pressing the button causes nothing to happen. Using the Event Viewer, I can see that pressing the button causes various messages to occur. So, pressing the button does something. But I can't get it to trigger a program. If I change the button back to toggle mode, and leaving my program and everything else unchanged, pressing the button (from off to on) DOES trigger the program. So, things don't work only when I've configured the button for non-toggle mode. Any ideas?

When I click the admin console link on the ISY web page, the admin java program runs and prompts me for a login. Then, almost always, after I enter my credentials and the console finishes initializing the network display, it prompts me again for a login. Sometimes it prompts me multiple times before eventually stopping. Right now, after entering the login info several times, I can see my list of devices and scripts, but the program display says I have no programs. Looking at the web UI, I see that my programs are still there. But the admin console has decided not to display them. Anyone know what's going on? Am I some sort of ISY black hole?

Windows XP 32-bit. FWIW, in many cases I'd prefer to be able to type the levels in as numbers rather than fiddle with the sliders. OTOH, being able to use the slider to adjust the current levels of all of the devices to get a scene just right is pretty cool. Thanks for your help, and speedy replies!

Wow, that was it. Moving the slider to the middle and then to zero works, for both appliance and dimmer devices. I never would have figured that out! I was also able to copy the scene settings to the other two controllers. So, the zero level is finally getting saved correctly. I had to install java on my computer to run the ISY console, so I know I have the latest version. The ISY Help | About says ISY 99i Pro (1040).

A progress bar does NOT appear when I slide the level for an appliancelinc to 0. Yes, the scene has two other controllers: A keypadlinc and a controllinc. (FWIW, this is also the case for the HouseLinc "scene" that works correctly.)

Here are the devices I am trying to set to off/level 0 in a scene: switchlinc dimmer appliancelinc lamplinc In HouseLinc, I can create exactly the same scenes (aka Links) that I am trying to create with the ISY -- where the levels for various devices are set to "off", and it works fine. Why can't I do it with the ISY?

I know there are restrictions on how a keypad linc can be programmed. For example, as I understand it, a button on a keypad can not be a responder to a scene for which another button on the same keypad is a controller. But I am still confused about what is and is not possible to program. Is there definitive documentation somewhere? What I'd like to do is this: Have several buttons on a keypad each linked to a particular light, so that the button controls and reflects the state of the light. Also, have a non-toggle button on the same keypad trigger a scene that includes the lights linked to the other buttons. IOW, when I press the scene button, I want the lights to go to the scene levels, and also have the buttons linked to the lights to turn on. Then, after the scene is set, I can use the linked buttons to control the individual lights if I wish. Also, of course, when I turn the scene off, I'd like the buttons linked to the individual lights to turn off, too.

ISY 99 pro... I can't seem to create a scene with some devices levels set to zero. Here's what I'm doing: 1. Turn off automatic writes to devices. 2. In the scene, use the sliders to set the levels for several devices to zero, with a ramp rate of 2.0 seconds. Other devices are set to levels between 0 and 100. 3. Turn on automatic writes to devices. 4. The ISY spends some time updating all of the links. After it has finished, the scene editor still shows the device levels at zero. 5. View a different scene. 6. Return to the scene just edited. Now it is showing the levels for the devices that I had set to zero back at 100. Aargh! The devices with other levels are still correct. Also, when I trigger the scene, I see that the devices that should be zero are indeed going to 100. I've tried this multiple times, with several scenes, and have even deleted and recreated a scene to try to get it to work. No luck. What am I doing wrong?