GDavis01

Thanks for the replies. I went ahead and reset the EISY to factory. The system appears to now be working well and I am in the process of reprogramming.

Thanks for the replies. I had forgotten to select 'Follow Topic' so I didn't actually see them all until a little while ago! To close the loop on this thread and a couple of other related ones... I tried the migration from the backup of the dead ISY to the previously used EISY and I'm not sure why but I had a lot of issues with the result! (none of the 3 keypads worked, other than the Main button connected to the load; some programs worked, some didn't; scenes didn't work; some devices on the UD Mobile app would show a status that didn't correspond to the actual device...etc). I could have submitted a ticket but I only had a very limited amount of time at this location so I decided to do a clean install to get the devices connected to the EISY and then do the programming remotely. I factory reset both the EISY and PLM. Initially I could not get the PLM to connect and tried that it could take numerous PLM unplugging and EISY reboots, but it eventually turned out that after the factory reset of the EISY the system setting for Insteon Support was not checked! I then connected the key devices to the EISY (20 so far) and will connect the others (10 – 15) when I’m there next. We are building an additional housing area on the property and so I will also be adding more devices there (+12) that I had previously been used at our former main home. (Our new home has Control4 which is another issue!!) The programming will be fairly time consuming but I saved the programs from the admin console of the failed migration so I at least have something to work from. A good lesson learned is that I should do backups more often because the last backup was quite old and missed a lot of the programming tweaks I have done over time! On the other hand, it is also an opportunity to clean up the programming that I no longer use and perhaps rethink my logic in some areas. Now to deal with a few comments… - I used the PLM from the former main home and I did do a factory reset. The PLM is a 2413U which I bought with the EISY in 2023. - My system is all Insteon, there were no ZWave devices My system seems to be working well and now just needs some work on the programming and network resources.

I have posted a few topics recently because my old ISY completely dies and I tried to replace it with an EISY that I had previously used at another home. I went through the process but I ran into far too many problems and I now think the best way forward is to do a clean install of the EISY. So, I am looking for some guidance on how I get the EISY / PLM back to factory state so I don't have any lingering issues. .

Yesterday, I migrated my system from a dead ISY (at 5.0.16C) to an EISY which I had previously had in another home. I upgraded the EISY to 5.9.1 before restoring from an old backup of the ISY. It essentially worked (sadly I wasn't diligent with my backups so it was a much older backup than I would have liked!). However, what does not seem to be working are my 3 (8 button) keypads. The main keypad buttons which are connected to the loads do work, however the other buttons do not seem to be doing anything. I have been away from programming the ISY for some time but I think my programming is correct and I am wondering if there is something else I should be tweaking or was this a migration issue. I will post a few pics and include the programs I am using for one button on one of the keypads. This keypad button (B) controls a lamp module. I have also set up a scene for the button's LED. Here are the programs: ================================================================== Key.B - Master Lamp - [ID 0050][Parent 004A] Folder Conditions for 'Key.B - Master Lamp' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- DoubleClick FAST OFF Master Lamp - [ID 004F][Parent 0050] If 'Keypad Master - Main / Key Master - B' is switched Fast Off Then Set 'Master Lamp' Fast Off Else - No Actions - (To add one, press 'Action') If the keypad button is double-clicked, when the lamp is on, then Turn OFF the Master Lamp ----------------------------------------------------------------------------------- DoubleClick FAST ON Master Lamp - [ID 004E][Parent 0050] If 'Keypad Master - Main / Key Master - B' is switched Fast On Then Set 'Master Lamp' Fast On Else - No Actions - (To add one, press 'Action') If the keypad button is double-clicked, when the lamp is off, then Turn ON the Master Lamp ----------------------------------------------------------------------------------- Keypad.B Update LED - [ID 0051][Parent 0050] If 'Master Lamp' Status is not Off Then Wait 1 second Set 'Keypad Master - B' On Else Wait 1 second Set 'Keypad Master - B' Off This program updates the status of the LED on the keypad. Keypad Master – B is a scene to control the LED. ----------------------------------------------------------------------------------- Turn OFF Master Lamp - [ID 004D][Parent 0050] If 'Keypad Master - Main / Key Master - B' is switched Off Then Set 'Master Lamp' Off Else - No Actions - (To add one, press 'Action') When the keypad button B is pressed once, while the lamp is on, the Master Lamp is turned off following the ramp rate set up for the device. ----------------------------------------------------------------------------------- Turn ON Master Lamp - [ID 004C][Parent 0050] If 'Keypad Master - Main / Key Master - B' is switched On Then Set 'Master Lamp' On Else - No Actions - (To add one, press 'Action') When the keypad button B is pressed once, while the lamp is off, the Master Lamp is turned on following the ramp rate set up for the device. I am also attaching screenshots of the keypad's Main button's settings; of the 'B' button's settings; and the LED scene settings. Does anyone have any suggestions on what may be wrong here or why this isn't working?

Thanks for the reply. After I posted my note I was reading about some of the issues related to running the Update Packages command. Have these been resolved? You are right about the Restore PLM command... I have been away from the ISY for too long I forgot the terminology! So, as you say I probably should Delete PLM to get rid of the links before I do the migration and then afterwards Restore PLM to establish the proper links on the PLM.

I recently arrived at my vacation home to find that my trusty ISY (5.0.16) had died, which explained why I had lost any remote access. I want to migrate the system to an EISY (5.8.0) that I had been using at my main home until we moved last year. The EISY has an active portal license. I also have a backup config file for the ISY. I only have Insteon devices. I am curious about a few things before i proceed: - I see that the latest firmware is 5.9.1 whereas I am at 5.8. Is it always advisable to update the EISY beforehand? (Update Packages) - The fact that the EISY was used at another home with different devices should I restore the PLM before I start the migration? The WiKi seems to suggest that I should only do this after I Restore ISY. - I am also assuming that restoring from the back up to the ISY will delete any traces of the installation I previously had on the EISY... is that correct?

Thanks for the replies. I took the advice and didn't hook up my old ISY. It turn out that this was a false alarm! While I was away I started having issues with the system and eventually opened a support ticket to which Michel Kohanim replied. I had sent him my error log and he replied that my PLM was dead. When I returned on Saturday I just assumed it was dead and that I needed a new one. However, just before I clicked on the purchase of a new one I decided to go look at the existing PLM. I saw that the LED on the side of the PLM was not lit! The PLM wasn't dead after all, my problem was that the PLM was not properly plugged into the outlet!

I bought the EISY and the 2413U PLM in October and it recently (March) died. Of course, this had to happen when I was away for a few months! I just returned today and I am thinking of pulling out the old ISY994i and 2413S PLM to get the system up and running again while I order and receive a new PLM. Hopefully there is some sort of warranty. Will simply plugging in the old ISY cause any issues to my system?

Interesting... I had not considered that. By the way, I am running on an EISY. So, I tried to a few things: - simply pulled the power cord out of the EISY to simulate a power outage; and - rebooted the EISY from the Admin Console a few times. Each time when the system came back up, the 'Home' node and sub-nodes were still populated with True or False. So, for whatever reason, it appears that I still do not need to use the variables.

Your method definitely works as does the method I explained. What I like about having the nodes set up on the Admin Console, the way I explained, is that I do not have to create and update a variable for each phone. Nor do I have to update the init value. The UD Mobile geofence, using the command changes the status of the specific phone node which in turn affects the status of the 'Home' node. My program simply tests the status of 'Home' to determine what to do. I also found interesting that changing the status of the 'Home' node acts like a state variable in that it triggers a program without having to query the node. So this program works as soon as the status of the 'Home' node changes. I also have another use where this approach makes programming simpler... we have a vacation home and we have a lot of family members coming and going; by having each member setting up their phone this way (as a separate sub-node) a simple program like this example runs when any member triggers the entry geofence. So either method works but with slightly different approaches. Thanks again for your detailed explanation in the earlier post. That explanation helped me realize that I needed to use the geofence command, from the UD Mobile app, to change the value of the Occupancy node (True / False) in the Admin Console. I had thought that the node would be updated somehow using the Occupancy tool in the Portal, but that does not appear to be the case.

Thanks for the clear explanation. However, if I understand correctly, your explanation does not actually set up a node on the ISY / EISY, it only allows you to trigger actions when you enter or leave the geofence. What I like about having occupancy nodes on the Admin Console is that I can have a geofence called 'Home' and geofences nested under 'Home' for my phone and another for my wife's phone ('Home/myiPhone' and 'Home/heriPhone'). This way I can have programs testing if 'Home' is True (when one of us is home) or False (when we are both away from home). I don't believe that simply following your instructions I can do that. Using the Portal Occupancy tool only, I could not figure out how to do change the status of the nodes. So, I first set up the nodes on the Admin Console with the Portal Occupancy V2.0 tool; then, using UD Mobile (your steps above) I created a Geofence on each phone; then, using the Geofence Commands in the UD Mobile app I set the action to turn ON the myiPhone node when I enter the geofence or OFF when I leave and the same for my wife's phone. Perhaps this is what was contemplated when using UD Mobile to trigger the geofences but, if so, it wasn't very clear. Anyway, thanks for your help as I can now do what I want.

I recently upgraded from the ISDY to the Eisy and I am trying to setup some Geofencing for our mobile devices. I am confused by which Geofence I should be using, Occupancy or Occupancy v2.0? I chose Occupancy v2.0 because it looks like it should be the latest! However, in the online help link when setting up the Geofence I see that it refers to 'UDI Mobile' app which no longer exists! Despite this I tried to follow the instructions and did the following: - Added geofence 'Home'; - Added Mobile Device - myiPhone; (the node shows as 'Home/myiPhone') - Assigned Mobile Device to 'Home' and then Synchronized so that the nodes ('Home' and 'myiPhone') now show up on the Admin Console. Here is the part that I am struggling with... the help section states: In the Portal when I look at 'myiPhone' in Mobile Devices, I see that the Linked section shows as "No". So I click on the small icon and I am asked if I want to Generate a new 6-digit pin. However, reading the help text suggests to me that the pin is only to link the app UD Mobile to the Portal. But since I have been using the app for some time now I would assume that it is already linked to my Portal account. Furthermore, after I generate a pin I cannot see where in the UD Mobile app I can actually enter it! So, I would think that the Linked parameter for 'myiPhone' should say "Yes" but it doesn't. In the UD Mobile app, I also set up a Geofence 'Home' and set the location. I then added a command that sends me an email whenever I enter or leave the geofence. This geofence works in that I receive the emails. However, there does not seem to be any synchronization with the app and the EISY for the nodes I created in the Portal! Can someone point me in the right direction, because clearly I am doing something wrong.

What do you mean by 'state files'? Do you mean the temporary internet files? I could not find anything in the Wiki related to 'state files'!

Yes, that is the link I used. My laptop is new so this wasn't an update from Win 10. However, I will try deleting Java completely and start the process over again.

In anticipation of moving from my ISY to my new EISY, I fairly recently upgraded my ISY to 5.3.4 from 5.0.16. All seemed to go well. I have not yet done the migration because I have too many other things on the go. My access to the ISY has been my PC which was running Windows 10. Subsequent to upgrading the ISY, I am now moved to a Windows 11 laptop. Today, using the IoX Launcher, I tried to log into the Admin Console but clicking on the Launcher brought up the UD logo for a second and then did nothing. Looking at the Task Manager I can see that the process is running but nothing is happening! (I'm not sure, but I thought that I had accessed the Admin Console on this new laptop before today and it worked properly) After clicking on the IoX Launcher many times, I went into the Control Panel => Java and deleted the files (all 3 options). Then I downloaded the admin.jnlp file again and tried to run it. It properly sets up the icon on my desktop but still every time I click on it I only see the UD logo for a few seconds and then nothing! Any ideas on what is happening? I fired up my old PC and it still runs the Launcher properly.