JimTurner

Found it - thanks. I have so many devices, it was buried.

My old ISY994i had a query program for the 3AM resync operation. The EISY doesn't expose the node to do that - or at least not that I have found. I get the Reboot clearing the issue reason. I'm going to install my new USB PLM tomorrow.

I have no sensors like this. Just switches, plug in controllers and dimmers - mostly switches.

I saw that - but never played with it. I am assuming that it only touches the one that I select...??? I haven't tried to control from Console. Good idea - cut the problem in half.

I have the original 2413S (Rev 2.9 4716) and had purchased a backup (cause of where I live) 2413S (Rev 2.5 1619). I installed the backup when I installed the EISY. I also have a 2413U that I bought but never put in service.

I picked one device for each issue - there are many. Device Issue1: Randomly coming on: 2477S (Front Porch) is a controller for 2663-22 (plug with porch art), and is in 3 scenes (AllOutsideLights; SunsetToBedtimelights, and GoodNight (the one I use to manually shut things off). The SunsetToBedtimelights scene is controlled by a program. (see below). Device Issue2: Losing sync with EISY: B2457D2 (plug in dimmer) is in 2 scenes: SunsetToBedtimelights and GoodNight

They are all in a scene. I turn the scene off... No motion sensors in my setup. Plus they come on with a program that is based on Sunset and 10:00 PM (on and off respectively). I turn the scene off if I retire early.

Yes, All Insteon dual band. Same issues in the ISY. It's about 8 ish (never counted) devices with the issue.

Edit2: I have installed and synced my USB PLM. Took awhile to get things squared away. There was lots of mismatches between Device Link tables and IOX Link tables. I have one old PowerLine device that won't accept updates through the new PLM, but that's minor and a not very often used device. Now to monitor and see if this cleared my issues. Thanks to all for the suggestions and assistance! Edit: I have 30-40 insteon devices in this setup. My ISY994 did the same thing. I've been running EISY since mid 2024. Randomly I will find my outside lights on in the middle of the day. The EISY or UDMobile app does not know they are on. A reboot clears this. Additionally, the EISY will lose connection with devices. Sometimes, when I turn a scene off, not all devices are turned off - even though the UDMobile app things they are. Again, a reboot clears this. I have not been able to find a correlating event or sequence that may be the cause. Thoughts?

I have a Harmony remote, and several devices that use the Harmony app to control my Home Entertainment setup. The core Harmony configuration is stored on the actual Harmony 'controller' not in the app on the phones or tablets. When I launch the app, it automatically pulls the latest config to the app and off I go. I can edit on any device and it stores the new config back to the Harmony. This would be a great addition to the UDMobile setup. Right now, I have 4 devices running UDMobile and have to go to each one to do a hand sync / hand add to favorites, etc. if I make a change to the setup. Suggestion is to store the Config on the Controller (EISY / Polisy), and pull down when UDMobile launches. I understand this is a significant architecture change but would be REALLY cool. My $0.02 after taxes.

Static IP assignments are usually controlled by your router, not the device. I can 'reserve' IP 192.169.1.xxx for a certain device on my network, then set that device to use DHCP. If you hard code an IP in the device and don't reserve it, the DHCP server won't know about it and you could end up with IP Address conflicts. How you reserve it is a function of the router, and the methods are as unique as the router population.

Got that - I know that much about zwave. My issue was adding the lock previously removed from the ISY to the EISY. No nodes were created - so no control.

I moved everything to the EISY. Had to reintroduce ZWave (now on both controllers), and cleaned out the ISY Completely EXCEPT as noted. 1 ZWave device (with 2 nodes), and the four programs.

UPDATE: I am now using both the ISY994 and the new EISY. I stripped all nodes/devices from the ISY EXCEPT for the offending ZWave device (the August Lock). I figured out how to make the 2 controllers talk after perusing this board. (Love the brains here). First of all, I've submitted a ticket for the ZWave issue on the EISY, and as of this writing have not heard. On the ISY I have 4 programs: 2 lock and unlock the door respectively (needed the granularity for the programs that now reside on the EISY), and 2 control trap programs that grab the lock event (open or closed - in case I open directly) and make URL calls from ISY to EISY programs using network events. The target programs on the EISY set a single state variable to 1 or 0 to indicate the door is locked or not. Then use that to control the rest of the logic. I trap the switch event on an outside light in my garage, call the ISY program to unlock my shop, turn the lights on and set the state variable. Used this for a LONG time and didn't realize how much I relied on it until it was gone. NOW IT WORKS! Thanks all.

Just upgraded from IS994i with the zwave dongle that controlled an August lock. I can add the lock to the eisy but it has no sense of what the device is or the status of the lock. The isy994 had it all, and I could lock and unlock with programs. I use this A LOT and I'd like to think I'm missing something in the setup. What do I look for? Where do I look? _____? Thanks! ~jim