paulbates

Stu, it was low voltage landscape lighting. A transformer that worked perfectly for years with an X10 supersocket would overwhelm a single outlet outletlinc in about 20 minutes. It would stop responding and needed a reset using a downstream GFIC. If I left the outletlinc on, and controlled the load with a appliance module it was fine. I tried and extension cord to give the noise room, no go. For a while I used a filterlinc as I described above, but that was not optimal because its an outside enclosed box, and adding the filterlinc caused the box's door to be popped open. Nothing bad happened, but didn't like an outside electrical box being open to the elements. Eventually I replaced the intermatic low voltage lighting system with an Patriot low voltage LED system; which had a transformer half the size. No filter and no problems since then Paul

You need to put the sensor in linking mode by opening the back and pressing the set button. The Led on the front will blink for a few minutes and then set mode will stop. While its in set mode: go to the admin console and click on the motion sensor. Towards the bottom of the screen there will be "options". Under options check the "on commands only" Press the set button again This assumes you set jumper 5 and restarted the MS as discussed in prior posts. You can link the switches and they should turn on fairly quickly. I have an MS covering my driveway and deck, and I'm very happy with how fast everything reacts. Paul

As a frame of reference, I have not upgraded form V2 to V3 yet and everything is working for me.

I think what you are clicking is a weblink to admin.jnlp and not the file itself. Assuming you're using windows, open file explorer and search for admin.jnlp. If java is loaded, it should have the white "cup of coffee" icon. Move that somewhere you want it. If there's more than one you'll need to make sure its the right version.. the only way I know is to execute the file Alternatively you can look here for your your current firmware version and follow step 4a in the first post to download admin.jnlp. That's what you want to use Paul

You don't add these devices to the ISY. They perform their signal bridging and repeating at the point that they are plugged in, and there is nothing to configure or manage Paul

There are a few threads around here discussing it. I have an established Insteon system around 50 devices. I'm happy with it. Downsides of a complete zwave conversion: Losing keypad functionality - This is a deal breaker for me for a 100% Zwave system All Insteon switches report their local status back to the the ISY.. some zwave switches do, some don't..you have to validate Effort and cost of conversion. What's functionally wrong with your insteon system now? Having said that, the ISY offers the advantages of integrating both. There are many sensor product choices onzwave. Many people use both insteon and zwave together successfully. Also, you can't have another one of the interfaces installed in your ISY.. the zigbee / zigbee AMI. Only one card can be plugged into the 994i. I would consider keeping your existing insteon hardware, and adding the zwave card to enhance it. Its more than the $1 software module, there is a zwave card that installs in the ISY was well. Write UDI to ask about that Paul

I found the the outletlincs to be "fussier" about noise from the load than other Insteon devices. I have 4 on the outside of my house and garage and they've had difficulty with the yard lights plugged in. I had to plug a filterlinc into the outletlinc and the yard lights into the filterlinc. Were the Christmas lights plugged in to the outletlinc when you attempted linking? If so, unplug everything and retry. If unplugging the lights work, then yes, plugging the Christmas lights into a filterlinc should do it Paul

especially if the temps dip down and the ms is outside

Hi 2 questions in there: Follow these directions for the "how to" of moving your setup from the 99 to the 994 Browse here and scroll down to "Upgrades" for getting a deal on a 994 as a current user. UDI makes it worth your while to upgrade! Paul

The ISY zigbee support is limited compared with zwave, you'll get more choices with zwave. Paul

The Hops Left=0 for 14.97.2A indicates that the sender and receivers are using up all of their 3 retries to get the message through, and that the insteon signal path is not good It suggests that the underlying Insteon isn't set up ideally... can you confirm one of: The power legs of your house are bridged via Insteon using Insteon dual band devices? (look at page 6, the steps will work for dual band devices including your PLM or do you have an Insteon signalinc bridge in your electrical panel? The other possibility is that the problem device is on an isolated part of your powerline as suggested earlier, and that Insteon RF isn't reaching, or that a dual band device in RF range like a range extender needs to be placed on the same circuit and nearby. If the above didn't solve it, can you describe where the problems devices are located on your powerline..eg futher away from the PLM compared to things that work Paul

This points to line noise (possibly in the vicinity of the CL2R and the load being controlled - LED).... potentially blocking the signal. A log of the communications is needed to further diagnose. In the admin console: Tools, Diagnostics, Event viewer Set to level three Operate the devices in a specific order that you can describe Press the clipboard icon Copy out just the events releated to the test Paste the results back here Paul

Unfortunately it doesn't work that way. When you send a command to a switch, it controls just the switch.. not linked devices The intermittent behavior of scene suggests that load being switched on by the scene is creating enough line noise to compete with the scene message trying to turn it back off What is being controlled by CL2R (LEDs, CFL, ect)? Try removing the load (remove lightbulbs), does the scene work 100% of the time? Test it 5 times with and without the load. If so, the bulbs (or whatever it is) is creating noise. If not, it might be that CL2R is very remotely located on your powerline from the ISY/PLM, as opposed to the keypads. You might need to add a dual band device close to CL2R. I had to do this in my garage. Paul

Hi, welcome to the UDI forums! What you want to do is: Download the java application direct to your computer. Put the icon on your desktop... use it to launch the admin console I keep mine on the desktop where its easy to get to Do not launch through the browser links If that gets the admin console working, be sure your ISY has the latest firmwareGot to help / automatically upgrade firmware to get your ISY to the latest Give that a try and let us know if that got you going Paul

You are describing a demarc: easy to integrate with the ISY vs a fully featured wifi thermostat. The Ecobee 3/4 and Venstar ColorTouch Series are "fancy" full featured color screen wifi thermostats, but they require Automation Shack software running on a 24x7 Network computer, which is a little more difficult to set up. Nodelink is for ISY V5 fw Ecolink or Venlink is for ISY V4 software The Ecobee requires a cloud account to control it The Venstars can use a cloud account for remote access (apps), but its not required. They use a local API to the ISY. FWIW I bit the bullet and went with the Colortouches 3 years ago and it was worth the effort. I started with Venlink on one of my windows desktops, and moved to a RPi. It is extremely reliable 2 way communication on Venlink and Nodelink. I know others have had great luck with ecobee too. Paul

Take a look at this wiki entry, it walks through how links need to be created https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scene This applies to the 994i as well as the others. To the comment above, if you've locally linked the devices you should factory reset them (no need to delete or re-add them to the ISY). Then follow the procedure from the wiki link to create scenes that add links that can interact with the ISY Paul

For the core logging functions, no , ISYLogger subscribes to the ISY remotely from the server you set up, and no network module or portal is needed. (Some advanced features, like having the ISY remotely restart the isylogger instance, do require network resources and therefore the network module)

There is a tool from Automation Shack / io_guy that shows when programs run (by program number): Its included in ISY Logger for ISY V4 firmwares (added in isylogger 6.5) ISY logger is a part of Nodelink and can be installed with it for ISY V5 firmwares Either of these methods require you to run a program on a 24x7 .NET capable computer.. desktop, RPi, etc. Here is a sample for program and variable updates from isylogger forwarded to a syslog db. Paul

Larry, mine don't take 30 seconds.. but the response performance is variable. I even put my Dot near the top of a short QOS priority list on my router so its not competing with all of my other devices. However, I notice similar delays on non ISY iot device skills too. Without some type of network traffic monitor to watch the requests and responses, its tough to pinpoint the actual performance culprit. I wonder if having multiple devices contributes to performance problems? Paul

Did you get this resolved? If not, submit a ticket to UDI. They will call and help you resolve. Provide a link back to this thread inj the ticket so you don't have to type it all in again Paul

Not sure about this one. If the Factory Reset ISY was connected to the PLM before it was factory reset, combined with restore modem... it may have pulled in prior linking information from the previous house back into the equation My best guess is to run through the steps in post 6, starting with factory resetting the ISY again Paul

You don't want to restore the PLM. Restore PLM is for restoring Insteon links from your previous house's insteon configuration. You won't want those, and also they were removed when the ISY was factory reset. Your new house will be different and switches and devices will have different jobs. My primary advice has been for a complete fresh install, removing all of the previous house's information, including the Insteon devices... everything as if it were out of the box I would: Factory Reset the ISY (I believe you did that) Factory reset the PLM (follow the steps for plugin devices above) Unplug the ISY and PLM. Attach the cable to the PLM and ISY Plug in the PLM, wait 10 seconds, plug in the ISY, wait for it to boot up Plug in a plugin module (lamp linc, etc) that you factory reset following the procedure above Try linking it to the ISY like a new device. If that works, continue on with all of the devices Paul

It will be like a new ISY. You'll want to follow the new, "out of the box" steps. Set up the password, internet, etc Then factory reset the devices and start adding them back in, For the PLM and plug in modules, follow the factory reset steps for each devices, typically: Unplug the device for 10 seconds Hold the set button and plug it back until it beeps For wired devices, I would attach a piece of wire to replacement plug Wire each device to the plug with wire nuts, one at a time Follow the factory reset steps for each device (look at their manuals), again usually hold the set button and plug it back in till it beeps I would factory reset and add the devices back in the ISY as a separate step at a desk before installing in their final home Paul

Hi Here you go... just don't restore the back up, ignore those steps I would factory reset all of the Insteon devices. Paul

Yep, it will be on the device on a sticker in this format ##.##.## Paul Sent from my iPhone using Tapatalk