paulbates

You press the button next to whatever feature your are tweaking after you change it. You should not need to write updates to devices, unless the little green 0101 icon is next to the device

@bmercier did not say it was your network, rather he offered to help investigate and resolve. When there's a portal wide issue, you'll see a thread with many users commenting. Many users were not commenting,

Are you sure about the communication? the IOlinc that the garage door kit is based on is power line only, and garages can be in the further away on the powerline in the house. Also, the garage door opener motor can make powerline noise. What I've done is: Buy an Insteon filter and plug that into the wall and the garage door opener into that Time the actual amount of travel time of the door so you know how long the motor is running and making noise Use Control instead of status to run the program when the iolinc is activated Have your program wait the amount of time from the second bullet above, then run the query to make sure the door didn't stop for some reason .. hit something, reverse, etc This may help too Up the amount of Insteon retries the iolinc has: Right click on the iolinc in iox/admin console Pick Advanced > PLM Communications Up it to something like 3 or 4 This is not a good general practice for all devices, but I use in my the iolincs monitoring my sump pump.

Did you download start.jnlp from here? https://isy.universal-devices.com/start.jnlp

Question for anyone testing... did your testing include disabling the internet on your router, or pulling the internet cable out of the router and seeing if things continue to work?

I would try to get the cable and terminal software (putty, or Telnet on windows) working using the simple command (above) for the ISY to reset networking. Get it back on its feet, confirm everything's working, especially Insteon, and then back it up. For upgrading to eisy, that will be a larger project and I would do it when you have time to deal with whatever things come up. When you do, I'd consider moving your existing PLM and then consider replacing it, depending how old it is.

That means that the ISY has woken up and is trying to access the network.... and not successful in getting network information. It looks like you didn't actually factory reset which is necessary.. a soft reset won't resolve it Do you have a recent backup covering your current state? If you can't do the terminal method (1. above), then you'll need to do a full reset and restore your ISY from that backup. You'll eventually need to upgrade. I would go to the eisy, as the new web based access that replaces the admin console / iox requires eisy. However, you will still need a good backup, so lets start with that question

Do you know how you configured Networking, specifically TCP/IP addressing in the ISY? This sounds like the problem of a static locally administered address was configured in the ISY, and the new router has a different subnet. Can you get to the interface of the new router in LAN settings and see if you can see the ISY trying to connect? If you can't get to it this way, there are 2 options I know of: Less drastic: Use a terminal to login to the ISY Get a USB to serial connector Connect via serial using a mini USB cable and terminal software (e.g., PuTTY. Pretty sure the cabling matters, maybe someone else knows the specifics) Use command CT to reset network settings to DHCP. More drastic: Factory reset the ISY and reload a current backup Power off the ISY. Use a non-conductive object to press and hold the reset button. Power it back on while holding the button for ~10 seconds. You should find it in the finder now, but will be in factory state Restore the ISY from a resent back up In either case, do not manually configure the networking in the ISY config, it sets up for this happening again. Also if you have older node servers that use hardcoded IP addresses, they may still be affected

@mbking is correct in that its not ready, today, to fully replace the the AC today as its exiting alpha and entering beta. What I appreciate is UDI giving customers the chance to test, respond and comment.

Yes. The "all on" is an Insteon feature... It's possible to send a message to all Insteon devices to go on instantaneously. It sometimes happens accidentally. there's actually an "all on" button at the bottom of iox. How old is your plm? If your don't know for sure, post the 4 digits from the sticker on the back

Agreed on it being an "all on". While there's little definitive data, battery devices like motion sensors can be involved... in my experience when the batteries are allowed to die. If you have a motion sensor where the battery died, or one that seems to be associated with the all on; factory reset it, right click on iox and pick "restore device"

Upgrade packages?

Is there a rough estimate for when eisy-us alpha/beta will be available as an update, not an SSH download? That's when I'll start joining the testing

To add to @Guy Lavoie's answer with a specific examples of products that integrate and work together with eisy: Yolink is a very good brand complement for Insteon on eISY using the well supported yolink plugin. It offers a number of sensors and devices. eIsy allows these work together with Insteon. Examples of how I use it: Battery operated temp/humidty sensors that can be placed about anywhere. I automate my bathroom fan with one of these that senses humidity rising when a shower has happened, eISY programs and an Insteon switch to operate the fan The same temp humidity sensors in the fridges / freezers tied to a notification program using the eISY notification plugin (also well supported). I use pushover as my notification app. Yolink Plug-in module that measures current draw of a device. I plug our second floor dryer into one and it lets an eISY program know the the power draw is up (dryer turned on) to turn on the room fan when the dryer is turned on and shut it back off after a set time after the dryer shuts off. (Without that automation, the fan doesn't always get turned on and it helps control heat and humidty on the second floor.) I use the yolink smoke CO sensors tied to virtualam for monitoring (eisy not needed for that part).. however I can get urgent notifications through the eisy's notification plugin if any of them go off. I also get eISY functionality out of an ecobee thermostat with the well supported eISY ecobee plugin. While the ecobee does a lot on its own, there some "halo" functions I get using it with plugin & eisy: I use an eisy program to follow up the 2 fan examples above to run the house fan afterwards to move heat/humidty out of those areas for a set time after the room fan turns off The ecobee thermostat provides reliable (for me) local weather data as part of the product, the eisy can see that via plugin can see that and I use that info to control my drip sprinkler system. The sprinkler system is $50 drip system controlled with a sprinkler control valve and a plugin 24vac transformer (both from the hardware store), and an i3 outlet... and eisy programs. There are days where it doesn't run based on forecast from the ecobee, or it adjusts the runtime based on how hot it's forecasted to be. Simple but effective I also use the "fast on" of the deck gazebo lights in the area to manually turn it on if I think its needed... with an eisy program Those are a examples to research.

What's interesting is that it looks like the backup is a V5 backup? Are both your ISY's on the same version? Maybe you're restoring a different back up the other ISY? The version difference is certainly one explanation for why it's choking on the restore.. especially when its at the major version ... 5.x vs 4.x