paulbates

Bring a lamp/appliancelinc right to where the PLM is, plug it in, try linking mode and also "new insteon device" and type in its address Paul

I would probably try factory resetting the PLM, then restore the ISY, then restore PLM If that doesn't do it https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY Paul

I believe that the ISY links table gets corrupted by a PLM that's 'lost is marbles'. What's currently in the ISY reflects that. Given the PLMs notoriously bad track record, I back up just about every time I have a "change session", and turn the back up file's name into brief comments of what I did Paul

Mark After putting the new PLM in, I would restore from a recent, known & good backup. Then restore modem. Paul

Did you try it in an outlet near the plm? Iolincs remain powerline only afaik I have better luck when I plug the device in a known good outlet close to the plm when initially configuring. That eliminates undiscovered noise / other problems with the install location. Sent from my iPhone using Tapatalk

Karen One one more suggestion is to turn in a ticket to UDI. Things don't normally drive off the road this far. UDI is very responsive and is definitely the best at this. http://www.universal-devices.com/contact-support/ Post a very brief summary and a link to this thread in the support request, someone will call. Also, I'm pretty sure your uncle will get that "Insteon is Insteon", and this sort of thing happens from time to time... if not, there's a bunch of us here that can explain it Paul

Karen How many devices are !? I would start by addressing those. I wouldn't uninstall and reinstall each device from the ISY,,, Instead do the factory reset of the device, and then use Restore Device... one by one. That can go quickly if you have a laptop with the admin console to take around with you. (Typically a factory reset is unplug for 10 seconds, hold the set button while plugging back in and hold it until the beeping stops (or 10 seconds). For switches use the airgap by pulling the tab under the paddle out for 10 seconds, then push it all the way in until it beeps or ~10 seconds). Once ! devices are addressed, see how it runs before deciding to rebuild the entire network. This kind of thing can happen every once in a long while. Paul

Andrew I would try it out a number of times remotely with the ISY or other linked devices... can it reliably go on, dim and go back off.. many times in a row. Paul

Thanks Brian. I should have caught this before I came back down from the attic. I have 1.8 and 1.9 in the garage. I'm not sure about the one in the attic, other than its older than the other 2.

Hi Andrew It matters because whatever the load it (what you are controlling) is interfering with communications. Are you turning on low voltage lighting, a motor, LED lights? I would expect that you'll be able to reliably turn on whatever it is, but not be able to do anything with it once it is on Paul

Hi Andrew Did you install it by using New Insteon Device, or putting it in link mode and use Start Linking? What specific messages you are getting from the ISY? What type of load is connected? Was the switch turned on when you tried installing it to the ISY? If yes, turn it off and retry Paul

Hey Michel Checking in. Fortunately I got the same results from a couple of week old restore, so I don't think its the card. The PLM is pretty close to 3 years, but its link table is still what's expected I eventually had to factory reset the iolinc to get it working, but I've had that exact problem with it in the past and prior to having the ISY. We had a major power incident a few weeks before the backup, I guessing whatever happened is traceable to that Thanks! Paul

Karen Michel's advice would be next I would say though, first find another device that will blink on traffic and enable it and validate that.. A beaconing device, creating lots of traffic, would be a cause for of everything being slow. Paul

Hey Scott IFTTT delays are specific to channels that must be polled (like gmail), as opposed to true event driven channels like this case. Paul

Hi Michel 1. No, the contact. It doesn't show off in the ISY even though it was commanded off by a scene and definitely turns off. The ISY won't catch up until queried. A "restore device" should have addressed I think, but won't work. 2. This is one of my older devices. I've had similar problems with it over the years a few times, typically going up and putting in linking mode is required to get it talking again. Its controlling the output from a 24vac transformer that's plugged in all the time. I'm eventually putting an outletlinc there so I'm not powering the transformer when its not actually in use, which is a majority of the time Could this potentially be the symptom of a failing SD card? Thanks. Paul

Karen, sorry this is happening Here are a few things to try: Check your programs - are the icons next to any of them constantly blinking? if yes, disable, then retry restore modem Since the PLM is new, lets suspect it. Do a factory reset of it, and then restore modem again. Some devices have the ability to "blink on traffic" or "LED on TX" so you can see Insteon activity on the powerline- their led will flash. Do you have a switch that did restore that you can turn on "blink on traffic"? If its continually blinking, a device has potentially become confused in the process. If you have constant blinking, try shutting off breakers, one at a time until it stops.. that points to the circuity with the faulty device Paul

Hi Bumbershoot Thanks, I was pretty sure that was the answer. Its up in the attic which is why I was hoping to avoid the re-add. Its still reasonably cool out, I can head up there this weekend and do it Thanks! Paul

I have a device that doesn't report its status without being queried. Its an iolinc. I tried "restore" device, and I get Could not open file [CONF/######.REC] Could n ot open config file to read [CONF/######.REC] Is there some easy way to address this by getting the .rec file from a backup file, or should I delete and re-add the device and its scenes, program steps, etc? Paul

Karen Typically you should not have to restore an ISY backup. See how things go without. If a ISY backup proves to be needed, it should be pre PLM failure, as a backup after could back up a corrupted link table. Give the above a try and let's go from there. Paul

Hi Karen Give this a read Paul

Andy, its part of the skill. My Venstar Colortouches say that and they are not connected to the ISY via Portal for this function, but using the Venstar Smarthome Skill

Hi Put this statement in If door sensor is on then Repeat every x minutes (or seconds) chirp statements When the sensor detects door closed, the program will cancel

I noticed today that my dot began requesting and using ipv6 addresses. It feels a tad more responsive across the board , but hard to tell for certain. Can anybody else comment on this? Paul

Guessing that its a router bug that most would not run in to.. .don't know for sure, but it won't take long to prove. I would try individual rules opening 6667 and 80. Most routers allow individual port forwarding (LAN to WAN) firewall rules to be set. Usually its an "advanced" feature. If you can set an outbound firewall rule for the Tag manager, set rules for: 6667 for TCP/UDP - tftp binds to UDP & TCP 80 for TCP - HTTP(S) binds to TCP A search came up with these directions Paul

You can use a keypadlinc to trigger isy programs that count down and then turn it off