paulbates

The 994i is an end-of-life product No more software updates / fixes for it. No growth. Newer node servers, integrations won't work. IIRC, the new Insteon i3 switch products don't work, or not all features work with the 994i. I moved last summer from my house that I had my 994i at. I had finished automation around 2016, so I probably would have replaced it with a 994i if it died as my automation wasn't going anywhere. Now I'm at that point with the house I moved to, I've pretty much finished other than a few Insteon n-ways which won't need the eisy once set up. But I plan to be here ~10 years. The point is I'm looking for this eisy to get me through that time and not go through another system rebuild, supported and updated for most of it.

Relatively. You'll need a backup to restore on the me isy. And then complete the move to the new plm. The cable is a likely culprit and needs to be proven out

It's best for scenes/groups to be created and managed by the isy.. You can do this after the fact by adding them to the isy, the default is for the isy to remove any existing links when adding. A couple of points: Make a spreadsheet of devices with their insteon addresses and locations. If you can, wait until you have the eisy to do any programming of n-way switches and insteon devices. Use the spreadsheet data then This approach applies to inline modules, you can add them to the isy by insteon address

I don't think you're screwed. Submit a ticket and udi will help you resuscitate it. You might have to pay something as the 994i end-of-life product wise. https://www.universal-devices.com/my-tickets/ The alternative is to consider moving to the eisy.... As you've had 8 years of use which is a very long time for most electronic things

+1 to @atmarosi's suggestion. The front deminsions are the size of a 1 gang decora, and with the optional wall mount you can attach it to the wall and add a switch plate. No one will know (except you).

Another root cause to unpredictable, flaky behavior in an older ISY is the SIM card going bad. This potentially is a cause. I didn't scroll back through this thread to see if this was covered or not... but *it is* something that will eventually happen. If you search the forum for SIM Card, or the wiki the procedure is covered. The problems you are having still seem systemic to me based on their random nature.. ed corrupt PLM or/and corrupt SIM, and not a program suddenly going bad

That's correct, you can not / should not add the plm as a device to the isy. Also the 2412n is out of production/support for a number of years and I believe some newer Insteon. devices will not be supported by it. It's not dual band and I don't believe it supports i2 or i2cs Insteon protocols

When you add an insteon device, you get an option pop-up, to "delete existing links" or (I forget the other terms) include include links, something like that. Like I tried to say above, that didn't usually work out for me and I rebuilt my insteon from scratch

There's a way to do it, you can ask the isy to look for links and include them, rather than delete links. It will "crawl" the insteon network for devices related to the device you're adding. My experience trying this across several home automation system migrations is that it's better to start from scratch, adding the devices to the isy and delete existing links. Then build scenes from the isy

Unusual symptoms, but a factory reset and restore is easy to do and should be eliminated as a possible cause

EDIT: My recollection is that it was one device per hub, but that was wrong, here is yolink supports page. Can I use multiple YoLink hubs within the same network? Yes, you can set up multiple hubs within the same network, and it is recommended doing so. Having two or more hubs increases system reliability. If hub A is offline, devices will automatically connect to hub B. Additionally, placing hubs in various locations throughout your home will expand their communication range Wrong: Yolink devices can only be associated with one hub, so the answer is no from a practical point of view. However, the range and reliability of yolink devices allows you a lot of flexibility in the hub's placement; like right next to your router. My announcement capable, Wi-Fi only hub 2 is near my router. It talks to all my yolink sensors, even fridge/freezer seniors across the house in the garage. I have no Wi-Fi connectivity issues either

Right, the suggestion was to move that down a level.. set all but one of the program folders (assuming you have your programs in folders) methodically let each folder run for whatever time you think is right and have no problems, the uncheck another... rinse and repeat (after removing 1=0 from the top level) However, your other answer convinces me that the problem is not programs and barking up the wrong tree Can you get to all of the MS easily? You'll want to, one at a time, press and hold the set button and then check the options for each especially the timers... looking for 52 minutes or any value that looks suspicious. A factor reset and restore device is in order... but hold on to that thought.... +1 to what @IndyMike said. PLMs can suffer a long and agonizing death. Continuing to refresh the PLM's link table is a road to nowhere and likely explains the continued degreadation of ISY functioning. Here's my suggestion: Order/receive a new PLM Find an iox backup from before the most recent events happened Restore that backup Swap the old PLM with new, following the PLM replacement procedure Except... skip step 1, backup, that list, my guess is that the current state PLM/Links table is too far gone This will take a while and you have to individually do each wireless only device by placing it in set mode Look for any devices with the green "io" next to them and do a "restore device" until they're all clear. Test as best you can to address individual device problems. Factory resetting / restore device may be in order for some with corrupt data tables. Check all of the settings of each MS. My guess is the MS are ok, but have corrupt tables... hard to say

You're on the right track with this approach. To optimize it it, I would set that same 1=0 logic on all your top level program folders. Then step through turning them on from the top down, either Folders with many programs... or Folders with time based programs in it The PLM could be partially to blame, when flaky Insteon light activity happens out of the blue, it can be the sign of a failing PLM. How old is the PLM? However, the PLM and most Insteon devices do not have timers/clocks in them so it doesn't fit the 52 minute problem. The only Insteon device with a timer that I'm aware of is the timer key pad, where the buttons had different count down times on them... you don't have one of those do you? They're long out of production. EDIT. MS's have timers too, they are suspect as well

The network service that the finder uses to find the ISY is (initially) not part part of the TCP/IP protocol.. it's a discovery/magic frame. It's good because it doesn't care what the IP address of the ISY is... it will ask it to identify itself. What's not good is that because it's not TCP/IP packet, it won't pass through the router/gateway in the EERO. Many access points offer "Bridge Mode" where it uses the host (AT&T) as the router. If the EERO has "Bridge Mode" this gets around the problem. Yes. It's possible through your ISY portal account. It's a little tricky to setup, but once setup works really well.

It's best to make the IP settings in the ISY automatic... that will 'future proof' your ISY and computer if/when network changes are made again.

This is a good catch... if the ISY is physically plugged into the EERO, and the laptop connecting to the ATT... the NAT firewall in the EERO (assuming its on), would give these exact symptoms. If possible, plug the ISY into the ATT router instead of the EERO (laptop and EERO need to both be connected to one or the other)

The correct terminology should be: responder, or, controller/responder. It's always a responder. For example, if the button is responder only, it would light or "un-light" in response to another controller turning the scene on and off. If it's a controller/responder, it will do the above and be a switch that activates the scene for other responders.

There's 4 things on the list, I take it you recognize what .240 and .73 are and they are not the ISY? Do you know what the other 2 are? If no Click the add button on the finder, and one at a time try http://192.168.1.241/desc Try the same thing with .71

Have you tried unplugging, wait 10 seconds, replugging the ISY? Give that a few minutes and then try launching the finder.

No.... My suggestion was not to upgrade the ISY to eisy as a solution to what is likely a java or local network problem. I have an eisy, it's great, but the migration is a lot of work, for likely no immediate benefit to you. I bought an eisy because I sold my last house in Dearborn with the 994i and "things" last summer and started new here. The 994i is a solid device that should continue serving you as is; you'll still get help with it here on the forums.

Also, is the ISY functioning; your programs and lights etc are working, but you can't get to it?

If you're happy with your current home automation functionality, I would simply subscribe to another one or two years of the portal , and set a reminder in your calendar around the time of the next subscription renewal to avoid it happening again

Thank you. I don't have a lot of rules, but one of them is: No ports open on my router.

The typical way to fix this is to put the 'Then' statements in a second program with no 'If'. Have the first program (with the if) only have program 'run then' statement that calls the second program. That will solve the problem with the living kodi clean program.. The second program, with no 'if', will run uninterrupted to conclusion The office bath the program works because you physically double-tap the switch for fast off to trigger the program. The only thing that could change that during the wait is another fast-off.... which would restart the program.

Go to the summary tab and right-click on "Run at Startup"