JCDinPGH

After some aggravation, I decided to dump my ISY994 and go with wifi appliance and light controllers instead. The cost of a new eisy was way too much and even though I could get a used ISY994 relatively cheap, I would still have to pay to migrate my features to it. All of this would have cost more than the wifi modules I bought to replace my Insteon devices. I can create the same schedules in Amazon Alexa with the wifi devices that I had in my Insteon. I returned the PLM I purchased also since the problem appears to be with my ISY994. I do want to thank all of you though for being so helpful in trying to diagnose the issue between my ISY and the PLM. You are a great community.

Well right now I do have a mix of Insteon devices which I started with many years ago, but also wifi devices, both indoor and outdoors. I have a mesh network across my property in the 2.4 band so all of the wifi de idea have been working well. All of them are integrated into Amazon Alexa which is mostly the only controller I use with the exception of daily schedules for turning on/off lights at dusk etc. The only insteon device that will be tricky to replace is the garage door opener as it took some clever programming with "if then else" calling the "then" parts of other programs. There are way more options for garage doors now then there was years ago. I know it sounds like I have made up my mind but I haven't yet.

To be clear, this is all good information but I don't care about the X10 module. I only have 1 X10 device and it was buggy at best. The only modules I need are Portal integration Openadr Networking I have a slew of Insteon modules but I'm honestly starting to think of just replacing them with wifi equivalents which don't need any sort of hub at all and I can put them on schedules via Amazon Alexa. Even the insteon garage opener can be replaced what appears to be fairly easy for roughly $30. Still researching though and haven't committed to any solution yet.

Do licenses not transfer when doing a restore on a newer ISY994 with a backup from my old ISY? Essentially I am only controlling Insteon devices with the exception of one device with the Networking Model (a Yamaha receiver) which I have a workaround. The modules I have installed are: OpenADR Networking Module A10/X10 for Insteon (which i don't care about. I only have one X10 device) Portal Integration

Originally I didn't realize it wasn't a special cable but since finding that out, I have tried 3 different cat5e cables. No changes to the issues posted above. It is looking more and more like the problem is on the isy994 itself unfortunately. Very frustrating.

Support replied and suggested I make sure the connection from the ISY to the PLM was good. And if that doesn't fix it, it is probably the isy994 and they suggest I return the 2413s PLM and order the 2413u PLM if I plan on migrating to the eisy. I see lots of isy994s for sale on eBay for much less than a new eisy. Assuming they are fully functioning, is it easy to migrate all of my customizations on my isy994 to a different isy994 after upgrading the firmware to make the versions match?

I opened a ticket. Hopefully they have an idea. I will gladly pay for support if needed. It can't be as much as a new EISY, I hope. Thanks much.

It's looking more and more like I'm screwed. I followed the procedure to replace the sdcard and it seemed to work fine. Without doing a restore of my backup, I tried to see if the ISY could see either PLM and it can't. Unless there is some way to fix the ISY connection to the PLM, I am thinking that my ISY is now useless. It has been pretty rock solid since 02/2016 and I was really hoping that replacing the 2413s, since they seem to have had hardware issues in the early days, would solve my problem. There is the possibility that the new 2413s PLM I just purchased is also bad but that seems unlikely.

The actual error I am receiving is below. Couldn't post it before a I wasn't home.

I have had a working ISY994 with a PLM model 2413s for many years now. Recently, what I thought was due to a power outage, my PLM appears to be fried and not re ofnized by my ISY994 anymore. I ordered a new one and followed the following procedure to replace it Unplugged ISY994 Unplugged old PLM (2413s) Swapped old PLM with new one meaning power supply cable and serial cable (which looks like an Ethernet cable) Plugged in PLM Waited 15 seconds Plugged in ISY994. Logged into the ISY994 and clicked on restore PLM. The error I get says no PLM connected 0 0.0 0. And no config file found. Diagnoatics also doesn't see the new PLM. What am I missing? I'm kind of thinking the problem isn't with the PLM at all and wondering if my old PLM might still work but for now, I just want my system back up and working so leaving the new PLM connected. I doubt the serial cable went bad but I guess that is a possibility. I haven't been able to control any of my devices in over a week. Going slightly crazy. Ideas?

I deleted all of my programs and scenes involving the garage door opener and deleted the device and relinked it and then recreated all of my scenes and programs and it appears to be working correctly now. Thanks for your help.

It gets weirder. I disabled both "garage open real" and "garage close real" which is how they were before upgrading and then set the "garage door relay" to on when the garage door is open, which should simply toggle the current state of the garage door, in this case it should close it, it does close the door and then the door immediately reopens fully. I thought I would go back to basics, hence toggling the garage door relay. Only setting the garage door relay to on actually causes any actions, as both garage door open and garage door close use that but also check the status of the garage door sensor.

I tried restoring the Garage Door Relay and the Garage Door Sensor. Unfortunately it is behaving exactly the same. Garage Door Open only opens part way and Garage Door Close closes all of the way and then reopens part way. I tried rebooting the ISY and powering off the IOlinc in the garage. I can try recreating the programs from scratch but I would be very surprised if it makes any difference.

I am completely baffled. I was previously at 4.9.0 on my ISY994I and everything was functioning perfectly including he garage door controller. Now when I execute the "garage door close", it closes the door completely, and then about a second later, it opens the door but only part way. This used to work flawlessly in 4.9.0. I verified there is nothing blocking the door from closing like leaves etc. Also, if I execute "garage door open", the door now only opens part way. No idea why it would do this. Also, if I manually close the door using it's buttons, outside of the ISY, it also closes and then reopens partially a second later. This is definitely the garage door opener that is causing this because if I turn the power off for the IOlinc device, the regular garage door opener works without reopening the garage door part way. . Here are my programs if it helps. Garage open - [ID 0019][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'Garage open real' (If) Else - No Actions - (To add one, press 'Action') Garage open real - [ID 0017][Parent 0001] If 'Garage Door-Sensor' Status is On Then Set 'Garage Lights' On Set 'Garage Door-Relay' On Else - No Actions - (To add one, press 'Action') Garage Close - [ID 001A][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'Garage close real' (If) Else - No Actions - (To add one, press 'Action') Garage close real - [ID 0018][Parent 0001] If 'Garage Door-Sensor' Status is Off Then Set 'Garage Door-Relay' On Wait 10 minutes Set 'Garage Lights' Off Else - No Actions - (To add one, press 'Action') The garage door sensor is a (2450) IOlinc v.41 Any ideas?

Having the same problem and I did notice the cert expired. Glad it is an easy fix. I panicked at first and though my PLM went bad but was able to login via all other interfaces.

Setting up a program to call the GARAGE OPEN or GARAGE CLOSE programs was the way to go since that actually uses the logic of testing the sensor first since IF is actually executed.. Thanks for all of your help!

I will try the program calling program option as it appears you are correct, that Alexa bypasses IF.

I tried creating 2 programs. OPEN GARAGE looks like IF garage door-sensor is ON THEN set garage-door relay ON CLOSE GARAGE looks like IF garage door-sensor is OFF THEN set garage-door relay ON I disabled both programs and then logged into my ISY portal and choose connectivity AMAZON Alexa and PROGRAMS, choose GARAGE OPEN and set it as a SCENE. I did the same for PROGRAM GARAGE CLOSE. Then I went into the ALEXA app and discovered devices where it found GARAGE OPEN and GARAGE CLOSE. I then created a routine that when OPEN GARAGE DOOR was spoken would run scene OPEN GARAGE I also created a routine that when CLOSE GARAGE DOOR was spoken, it would run scene CLOSE GARAGE Unfortunately even though the logic in the OPEN GARAGE program should only open the garage if the garage door sensor is ON, both Alexa routines just toggle the current state of the door. Now I am even more confused. I'm thinking this is never going to work. I just don't know what else to try.

I tried changing the connection from using NO and COM and the door won't open or close, either from within the ISY994 or from the button on the 74551. I completely removed it and reset the 74551 by holding down it's button for 10 seconds while powering it on. I also tried every mode latching etc. It appears to only be able to trigger the door when connected via NC and COM.

Some things that may be relevant. My ISY994 is on firmware 4.7.3. I really am trying to avoid betas. I was never able to get the 74551 to be registered via linking mode. I tried multiple times. I have only been able to manually add it via link management -> New Insteon Device. I have tried changing modes including Latching, Momentary A,B,C. I saw someone else that is controlling their garage door via a scene instead of a program. If I can figure out how they did it, I might try that.

So I should try the NO and COM wiring instead? I will try that also. Nothing left to lose at this point.

Sorry. I forgot to mention that. I tried adding WAITs and set garage relay off also. No difference.

I am about ready to give up. Been at this for a few days now and it just gets weirder. I created a program called "Garage open" as you suggested that checks the status of the garage door sensor and if it is on (meaning magnets are seeing each other and door is closed), it sends as THEN "GARAGE DOOR RELAY ON". I also created a "Garage Close" that checks the status of the garage door sensor and if it is OFF (meaning the magnets are not seeing each other and the door is currently open), it sends as THEN "GARAGE DOOR RELAY ON". Remember only ON is working so everything must rely on the status of the garage door sensor. Once I did this, I thought I had it but now the door closes, and then opens 1/4 of the way and stops so it is left 3/4 closed. This is consistent and happens every time. I thought maybe something was mixed up in the ISY994 or in the garage relay so I removed the programs and the garage relay and rebooted the ISY994. I also performed a reset to defaults on the garage relay by holding in the button for 10 seconds while powering it on. Just for good measure, I also powered off the garage door via the subpanel in case it's sensors were screwed up. I did all of this a few times and no matter what, the garage closes and then immediately reopens 1/4 of the way and stops. If I disable the two programs (GARAGE OPEN and GARAGE STOP), toggling ON for the GARAGE RELAY works as expected. So the issue is definitely the programs. They aren't complicated at all. GARAGE OPEN - If GARAGE Sensor is ON, THEN set GARAGE RELAY ON GARAGE CLOSE: If Garage Sensor is OFF, THEN set GARAGE RELAY ON. No clue why it is acting even weirder.

That is a great idea and I can't believe I didn't think of it. Sometimes I forget that things that can be done with the ISY994. I will try that. I'm also wondering if I am using the wrong terminals on the garage module. I can try switching to NC and COM instead of NO and COM.