slimypizza

Yes, exactly. Once the EISY was powered down the switches were snappy and functional unlike their behavior with the EISY on.

Thank you all for your suggestions. I believe its all sorted out now. Strange as it was, things seem to be working again. I ended up verifying the switches worked if my EISY was powered down. All switches responded as expected. Then I reset and restored every switch since the malfunctions seemed to be random. That took a bit of time. Then I resaved every program on my EISY. Extensive testing now indicates the system is working without issue once again. Don’t know how this started but glad it’s over and appreciative of all the help. I’ve got a medium sized automation network and can now resume my project to expand.

There are too many switches affected to think they individually all failed at once. Also, I mentioned some programs are not performing as they should. I suspect the EISY at this point and not necessarily the PLM (since HA and Alexa appear to work). Perhaps there is a programming or config glitch I can’t get rid of unless I start from scratch or go to a previous backup. As I outlined above I will disconnect my EISY from the network and see how the switches behave. After that I may need to go to a previous backup but I only have backups from older SW versions. As I said earlier, this problem was first noticed after installing two new 2477S switches. My only backup prior to the new switch installation was the one created when I advanced to 5.9.1. Again – Can I use older backups from previous OS versions in an updated system? Thanks all.

No power event at all and I did pull the tab on the bottom of a few switches, wait, and push back in. Unfortunately, no change. Thanks. I'm very open to further suggestions. Thanks all. Can I use older backups from previous OS versions in an updated system?

Although it seems random, about half of my switches seem to be unresponsive (and the LED light does not go to the top) but if I activate them through HA, they may become responsive again for a while. I admit this is very strange. Sometimes when I turn the switch on via HA, the switch may not be able to turn off. Some programs with timers (eg, landscape lights, fans, porch lights) may or may not work and the devices have to be turned on/off with HA. These programs worked perfectly in the past and have not been altered. A couple of things I am going to try: I should have thought of this before: Turn off my EISY and see if the 2477S switches work. They should operate as a standard switch. I have my old ISY994i and PLM. I will substitute it into the network temporarily in place of my EISY and see how it performs. Question: I have older backups from previous OS versions from my old ISY994 (I’m running 5.9.1 now on the EISY). Can older backups from previous OS’s (eg, 5.8.x) be used on my current system? Thanks for all your help.

Guy – Sounded impossible to me as well but yes, pushing the physical switch does not work on many switches but Alexa and Home Assistant work fine. I also noticed today that a programmed timer (for a bathroom fan switch) did not work. It was supposed to turn off after a few minutes and worked fine in the past but today it kept going for over an hour until I saw it through HA and turned it off. Brian – I’ll try power cycling a few switches and see if that makes a difference. Note: I first began seeing this behavior after installing new 2477S switches in a bedroom. I named them Bedroom 2 Light and Bedroom 2 Fan. I already had switches in other rooms named Bedroom Light/Fan and Bedroom 1 Light/Fan. Would the similarities in names cause confusion in the EISY and problems that would extend to the whole network? I did remove the new switches, checked wiring for poor connections, and reinstalled. I also flipped the circuit breaker for Bedroom 2 which would have removed any noise or interference caused by those switches if that was a problem but neither troubleshooting effort changed the outcome. I still don’t see how physically pushing the switch paddle could result in no on/off status change.

I have an interesting problem that has just begun. Many Insteon switches (eg, 2477S) are not responding. Manually pushing the switch does not turn on/off the load. The LED may flicker but the on/off state does not change. However, Alexa and Home Assistant have no problem working. I have rebooted my EISY 5.9.1 several times. No change in the issue. Thinking I might have a PLM problem I have ordered a new 2413U which I’m waiting on but if the PLM is at fault wouldn’t Alexa and Home Assistant have the same problem? Where else should I look?

EISY shows up as host name on my router (pfSense) but I can edit that field myself so I don’t remember if it came up on its own or if I added it.

Camping is fun though I haven’t done that in a while. No woodworking here (I see skilled work by some of you) but enjoy programming, gardening, hiking, gym time, want to get into pickleball. Heading north (from GA) to Michigan and Mackinac Island in June. Never been before and the wife has wanted to stay at the Grand Hotel for quite a while. Going to drive up and see a few things along the way. We like coastal towns as well, Savannah, St Simons Island, Bluffton, and Beaufort... More extensive travelling (abroad) is in our future.

Nice. I did exactly the same thing last year to interface my I/O Linc when I had to replace my old chamberlin opener. I was not happy to realize they’d changed their opener system. I have my hacked remote opener attached to the garage opener support bracket.

My update took only about 10 minutes. I only have Insteon devices as far as my EISY is concerned. I do have NEST, Blink, Kasa, and others but no plugins, HA handles those. Everything came up smoothly except the Admin Console was a version out of sync. Clearing Java cache fixed that. So far so good.

I’ve been using Netgear’s ORBI 6E mesh system. The RBK853 has a wifi router (router disabled, only AP active) and 2 satellites. House size 4200sqft. We have 1GBS Xfinity internet and all has worked well knock on wood for the past few years. I like Ubiquiti but the need for cabled connections to the WAPs drove me to the ORBI system which is all wireless.

I thought I was the only one who felt that way about my ultra-dependable ISY994i when I brought my EISY on board last year. I still have it along with its PLM as a back up should I ever need it. I haven't even moved it out of the equipment stack.

It was worth a try. I ran Update Packages but stayed on 13.2 RELEASE p11.

Thanks for the link. Here is what I got when I ran it. *** OS *** FreeBSD eisy 13.2-RELEASE-p11

Is that the whole program? You dont have a command to turn the lights off. Add that statement to the ELSE portion of your program. That will turn your lights off at 11pm.

There are a lot of entities but you might end up being glad they’re there. HA makes available plenty of sensors and items to control.

roblombardo what are you using to control your garage door? I'm using an Insteon I/O Linc 2450 that I've had for several years.

I would suggest using Home Assistant if something like this is what you need:

You might try restarting HA and your ISY as well.

I have used the Insteon 2450 along with geofencing to open my garage door for several years. I do not have it close the door when I leave. I do that myself from the car. The programs below work fine for me and/or my wife coming home. The garage door opens and the kitchen light turns on when pulling in the driveway. I use Home Assistant to handle the geofencing and it sends a rest command to my EISY to change state variable $s.J_ArrivedHome (or $s.T_ArrivedHome) to = 1 when the geofence zone is entered. I have another program that resets those ArrivedHome variables back to 0, 15 seconds after being triggered. My recommendation would be to cut out the part of your program that closes the door. ArriveOpenGarage - [ID 0020][Parent 0001] If $s.J_ArrivedHome is 1 Or $s.T_ArrivedHome is 1 Then Set 'Kitchen Light' On Run Program 'Garage_Open' (If) Else - No Actions - (To add one, press 'Action') Comment: Open the garage and turn on Kitchen light whenever someone arrives. Garage_Open - [ID 003A][Parent 0001][Not Enabled] If 'garage door-Sensor ON=Closed' Status is On Then Set 'garage door-Relay' On Else - No Actions - (To add one, press 'Action') Comment: Trigger relay only if garage door is closed.

I echo the sentiment of the Insteon hardware. Big fan. On the subject of the I3 however, I’m not so impressed. Indeed my attempt to replace a 2477D with an I3 this weekend did not turn out well. The switch kept getting stuck on the wall plate when turning on and off. I tried several times to make it fit better then gave up. Didn’t even get as far to realize the dimming range was not comparable to the 2477D. I wont be using the I3 unless there is a design change.

Im using the Insteon iolinc and have been for a few years now. When we moved a couple of years ago to a house that had MyQ, I took the iolinc from the old house, scrapped MyQ and installed the iolinc. Works very well with my KPL switches, geofence, Alexa, and Home Assistant. Haven't looked at the Yolink solution. Always wanting to learn more, I'll read up on that.

I’ll mention this just because its happened to me more than once. The device address can sometimes be misread. The letter O looks like a zero, etc. When I’ve keyed new devices in incorrectly like this I got the same error as you, “Cannot determine Insteon Engine”. Doesn’t hurt to double check the address. Good luck.

No I have not used the node. Looks like that may be the way to go though.