paulbates

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

I would also try using the other method, "New Insteon Device" near the bottom of the Linking Type in the Insteon address and other info. (you won't need to put the keypad in Link Management mode) Paul

Since its counting on insteon traffic, I'd be surprised if the blinks were on "a rhythm". The blinks will most likely be inconsistent, eg 1 second 1, 2 seconds off, 3 seconds on, 1 second off, etc. If you have an extra key, dedicate one for "Spa Ready" that lights up when the Spa is at temp, goes back off when its not. Paul

How did the restore modem go, what kind of messages. Sometimes the ISY "learns" the corrupted information from the PLM and means you could be putting back the bad info from the old PM into the new one. Do you have a backup from before the latest PLM failure? Restore an ISY backup from before the PLM failure Then restore the ISY again Remember wireless devices must be put manually in linking mode and restored one at at time Do you have a backup from before the latest PLM failure?

How far is the outbuilding from the house? Dual band insteon might be able to make it on its own, but you may have to put a range extender in the house, as close to the outbuilding as possible, and one in outbuilding, close to the house as possible. Line-of-site between the 2 and no metal inbetween (siding, wiring, etc) The pool pump may need to be filtered as well as a source of noise. Paul

Unfortunately, the magic ran out. You do have the edit them individually. I know from my thermostats its a pain, but a one time thing. Hitting the save button is important. Paul

The zip files of exported Network Resources are not meant to be opened by winzip. Import them straight back in as Network Resources to your ISY. Once imported you can edit, delete, etc Paul

Hi Drew Are other network related things working with the ISY? For instance, if you go the the configuration tab of the admin console, and click synchronize now next to NTP, what happens.. does that work, or error out? Any changes to your internet/network, like a new router? If the ISY can access the network, the I would suggest you submit a problem ticket to UDI Paul

Ok. I wasn't sure in the original post the problem was solely insteon hub related. I've had very good success with a Dot and my ISY for a year. I also have thermostats, tv remote and sprinkler controller.. all controlled well by the dot too. Has it been perfect.. no, but only a few misses.. none noticed for quite a few months now. Given your solid internet and wifi, and I assume solid Dot use outside of the hub, you will be happy. Paul

Right. I wasn't sure from the original post if the problems were solely hub related. Paul

Hi, welcome to the UDI Forums! Its unlikely that the ISY will change the existing comm problems. They ISY another Alexa controlled device.. the core communications and voice recognition will continue to travel through the AWS Cloud like they do for you already. If there's something wrong with those existing communications, it needs to be figured out first. Let's start with a basic ones: How healthy is your internet service for other things... any drops or problems? How good is your wifi overall? Tablets, laptops, etc have any problems like the echo Does your router have a place to look at your connected wifi clients and see their signal strength? If so, how does the echo compare to other wifi connected devices? Paul

Being able to turn off only is unusual. If you could turn them on only its a sign that the connected load is generating a lot of noise. Did you check the On levels of the new switches, either the switch itself or a scene if used. That could be the cause. Paul

Using program state as logic is more matter programming style. Like a state variable, a program state is just another event state. I don't look for ways to use it, but in some situations it saves variables and variable handling, and makes the programs more readable with less code. Paul

Don't be alarmed, this has happened to me in the past, they are test devices. See this thread, that basically says to forget all devices and re-discover Paul