paulbates

Do you mean on the same power leg as opposed to 1 circuit? Most of them being on one leg is unusual, but it could explain what you are seeing. Insteon / dual band and electrical signalling is all concentrated on one leg, leaving the other leg "weaker". If there are phone chargers, low voltage lighting and/or motors on that other leg, it will definitely make it harder for insteon signals to get through. On possibility is to put a dual band device or a phase coupler on that opposite leg. You may have to move it around to several outlets to find the sweetspot.

The program appears ok. I'm not sure, can you try the scene manually from the ISY to make sure it functions as expected? There could be several things going on. An alternative suggestion to the programs, once you know the scene works: Add both switches as controllers to the scene with the lights. No program would be needed, the scene would do all of the work and the perceived performance will be a little better. Paul

The developer of the HomeSeer Insteon plugin had this set up. Its probably very similar to a serial over IP type of set up. The only down side that its interface is no more complex than that, and the hub must be polled by the controller (ISY) to get updates from the network. I ran it side by side on homeseer this way for a while and programs that respond to devices appear a little bit slower. You also have to decide if you want to hit your network once a '?' for updates. Its been brought up before but I do no think it is high on the list. Node servers on V5 is another way to access the plm from a network / programing perspective, through the ISY and regular PLM.

I would suggest submitting a ticket to UDI and have one of their experts talk it through with you on the phone. Paul

Hi Are all of the devices in a single scene, or are you sending 4 different "On" commands sequentially? I would suggest a single scene for 4 devices over the sequential commands. Having the ISY issue a number of individual device commands sequentially might give you inconsistent behavior like you are seeing Commands sent later in the sequence from the ISY program will be competing with the acknowledgement messages coming back from the initial devices reponse. Paul

Yes. I called insteon on this. In summary, a long conversation to find out that there does not appear to be a software method to defeat this feature as there is with beep, LED and Blink on Traffic Paul

You need to add both switches as controllers to the scene. Each controller sends a message to turn everything on, including the other switch's state. Paul

Were you using HAD? If your ISY is firmware 4.2.0 or greater, go to the default http webpage and select "Home Automation Dashboard" as the default UI. If the ISY firmware version is older than this, you will have to load it on yourself. I would really suggest updating to a 4.2.0 or newer ISY firmware if this is the issue. Also, I do not have iTouch.htm in my ISY's Web directory. Is this a custom page you wrote or installed on the old ISY? That page (and any other customized files) will need to be copied back onto the new 994i Paul

Thank you Benoit! That is helpful. I think I know what I am saving up for next..... Paul

Could that be 'wiresharked' if connected the local WLAN?

Jumper 5 means that external controllers like the ISY can set the options. What are the options set to when you look in the admin console? I have mine set to "On commands only" and have programs turn them off. Paul

Not a problem Brian. I had to search by LED, and then finally by Green. It was down in there a bit. No worries at all Its more that its a change and we find out by installing and turning on Paul

Found this in the the manual: LED Behavior Keypad has a dual-color green and red LED which momentarily indicates if a button press was successfully communicated to all scene members. LED State Meaning Blinks green once One or more scene members acknowledge the button press. Blinks red once One or more scene members did not acknowledge the button press (note: scene members may still have heard the scene command and adjusted their settings.) The statements seem contradictory. Either one scene member did or didn't respond. I've never seen both colors blink in response to the same button press.I believe my observations are supported by the statement about Red, if one of them doesn't respond, it blinks red. My circuit in question has one of my oldest inlinelincs, but it does come back green some of the time.

Sounds like it would be a separate option with its own message to the switch for defeating it. Probably not the news the OP is looking for Going to share this one with my wife

Hi Brian Let's say I reversed engineered what it does based on observations that are explainable. Another way to test it would be to control something like a single lamplinc that could be plugged / unplugged to see if its red when unplugged and green when plugged in. Its a 2334-2 v,43 Paul

I just replaced one too and have the same behavior. Its a diagnostic traffic indicator specific to the keypad: Green: The Keypad saw the acknowledgement from the insteon network for the command that the key/keypad sent Red: The keypad did not see the acknowledgement from the insteon network for the command that the key/keypad sent I've left it on because one of the keys controls several devices that are a long way off, control noisy loads and I want to observe it. I just looked at the settings on the admin console for the new keypad that shows the red / green. It did not have blink on traffic set. I queried it, no options set. I set it, tested and unset. No effect. I could turn Beep and No LED on and off with the appropriate effects. I am using V5 firmware, not sure if that matters. SL adds features to devices but doesn't always disclose them right away, or the messages needed to turn the features on and off. At this point I'm not sure how to defeat it programmatically. Paul

There is a procedure in the users manual for the conversion. There are some keys to press when you start it up. After that, you should be able to restore device from the ISY and get back to where you were. Paul

The choice comes down to integration. For the hub, Integrating insteon devices to both the hub and the isy will be tricky to do and maintain. It will be difficult to impossible to integrate with other isy functions and programs. Also I would expect the echo integration from udi to be richer and deeper. Fwiw, I'm waiting. Not sure how long.

Each time Java is updated, you'll have to rinse and repeat. You can use the directions, or upgrade Java

Here is an additional way. You can have specific applications run in 640x480 mode, which effectively increases the font size and touchpoints Here is how to do this: Find the admin console icon Press and hold it for a second, then release You'll see a popup with the ISY Amin console icon in it Press and hold that for a second then release On that pop-up, tap properties Make properties look like the attached picture: Run in Windows XP (Service Pack 3) compatibility mode Run in 640x480 screen resolution press Apply press ok Its not a perfect solution: There will be a little bit of screen flashing / flickering bringing the admin console up. Also, the "+" icons to expand Devices and Programs are still maddeningly small. Press a little left of where you think you should If you didn't get the surface pen for your surface, you may want to. However, I can flip back and forth to other apps and the admin console. This approach does help with editing programs and watching / adjusting variables, which is my main requirement

Lee The non responsive zone is a test for a fried ezflora that can be programmed. Turn the zone on, query the zone, wait 5 seconds then call a program that checks for it to be off. If it is, notify etc. Paul

I just got a surface 3 yesterday, partially for remote admin console access! Here are a couple ways 1) VPN. VPN software lets you access your LAN like you were there. The surface has a VPN client built in, or there are other clients like openvpn. On your house side, you need a VPN server. My router provides that. If your router has A VPN server, that would work. A VPN allows you to access other things on your LAN in addition to the ISY 2) Port forwarding. Use your router's features to redirect an SSL port to your ISY. Set an option up in ISY Finder with your house's IP address and the port number that redirects to your ISY. A little bit of technical knowledge is needed to do this, we can help with that here if needed 3) The new ISY portal. Its in beta, but once available, it is designed specifically to put your ISY on the internet securely, and for you to access it remotely. If you can wait, and don't need to access other devices on your LAN, probably #3 is best If you can't wait, its a toss up between the other two options... Does your router have VPN and do you need to work with other devices? Then #1. If not, probably #2 Paul

Contact UD @ http://www.universal-devices.com/contact-support/ Summarize the above and paste a link to this thread. They are very good about being responsive

There can be conditions where devices that are supposed to trigger a dry contact electronically don't do that to the satisfaction of the ioloinc, and it won't register the "close". This means that dry contact bench tests work, but real world connections to devices like the infrared beam sensor do not.. A symptom of this is that the green LED on the iolinc will glow when there is an attempt to activate it with a device like the infrared beam sensor, vs bright green when bench testing with physical contact. I have had this happen with a current sensor to see if an appliance is on. The current sensor didn't do enough to convince the iolinc it was contacted, but it would make the iolincs led glow a little, which makes it appear it was activated. Are you able to get the iolinc to read an "on" at all, observed at the admin console, without the scene, using the infrared beam sensor as the trigger?

Al Go to the 4.2.30 version forum post and find the link to download the admin console again. Run it, and the icon will come back. Paul