dbwarner5

@jimbo Moved my Kasa from pg2 to pg3. No problems. Did a delete on pg2, add on pg3. Key was to reboot ISY after the delete to free up the slot, per your directions. GREAT!! Glad I can throw it your way, again!

@satwar time/data node server is green. simple. works. I do something similar to what you are trying to do and I keep it pretty simple. Am sure it could be optimized, but its readable and easy. I am looking for three options for my sprinkler program #1. 1) 7 days a week, 2) three days a week 3) every other day. Three separate programs, plus some other very simple programs to change a variable to differentiate between which program is true. 1) Sprinkler 1 7 days - [ID 0158][Parent 02BD] If Time is 4:30:00AM And 'Non Alarm / Rain Sensor' Logical Status is Normal And $Sprinkler_1 is 1 And $I_Sp1_Days is 7 Then Run Program 'SP1 Lake 1' (If) 2) Sprinkler 1 3 Days - [ID 02D6][Parent 02BD] If On Mon, Wed, Fri Time is 4:30:00AM And 'Non Alarm / Rain Sensor' Logical Status is Normal And $Sprinkler_1 is 1 And $I_Sp1_Days is 3 Then Run Program 'SP1 Lake 1' (If) 3) Sprinkler 1 Odd Days - [ID 02D7][Parent 02BD] If Time is 4:30:00AM And 'Non Alarm / Rain Sensor' Logical Status is Normal And $Sprinkler_1 is 1 And $I_Sp1_Days is 2 And 'ISY Time Data' Odd or Even Day is ODD Then Run Program 'SP1 Lake 1' (If) Two enabler programs for the whole sprinkler system and controller program 1 to run or not: All Sprinkler - [ID 01BE][Parent 01A5] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $All_Sprinkler = 1 $All_Sprinkler Init To $All_Sprinkler Else $All_Sprinkler = 0 $All_Sprinkler Init To $All_Sprinkler Sprinkler 1 - [ID 0044][Parent 01A5] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $Sprinkler_1 = 1 $Sprinkler_1 Init To $Sprinkler_1 Else $Sprinkler_1 = 0 $Sprinkler_1 Init To $Sprinkler_1 Using Mobil link under advanced options for these programs, I change these "enabling" programs to be: -Run then: Enable -Run Else: Disable -True: Enabled -False: Disabled. Delete everything else I have three more for each of the different #days / week that sets the last variable in the Then and a 0 in the Else. Running an else of any of these shuts down the sprinkler as well. Now it super easy to change between: -Turn all sprinkler on or off, -Turn sprkinler program 1 on or off -Select the three different Days a week I preset.

@someguy @apostolakisl Check this post out. I tried to capture all I did in my conversion to IoP (isy on polisy).

ok. thanks for the validation. I will open a ticket on this.

Have run into the same issue. The module appears to not be supported. My devices, while they still appear in My Lighting, they are all "dead links". Clicking on them doesn't even bring up anything at all. The screen stays on whatever it was last on. They have become invisible. Furthermore, I am finding that I cant get the ISY to recognize x10 command received. It will send them fine, using the X10 command line, but not receive them. I will wait and see who else comments here, then open a ticket if needed.

@Michel Kohanim Can you confirm that the X10 module is no longer working / available on ISY 5.3 on Polisy? All my X10 devices are still in the Tree, but when you click on them they are not recognized in any way. Thanks

@tmorse305 For my new ISY n Polisy, thge Query All program was there, but the THEN statement was missing. To add it, Use Devices and search your SCENES for My Lighting, and add it to the Then for Query as @Techman shows.

@Jimbo @einstein.42 @exking THANK YOU ALL FOR YOUR WORK ON THE ELK PG3 Nodeserver I bit the bullet and did the conversion from 994i to Polisy with Elk being my biggest worry. WOW.. I am blown away at what a great job you guys did with this node server. Not a single problem! Cant wait for you to add the voice capability as that is the only missing link from my Elk / ISY system that I rely on that is missing now. Cheers and glad I could now purchase the to recognize you.

Michel fixed it. It was embarrassingly simple... My Lighting is down in the Scenes part of the drop down! Was there all along, I just never went down that far in the list! Thanks @Michel Kohanim as usual for you quick and simple fixes!!

Have already looked through the whole list. Yes UI matches Orignial name was My Lighting..just as it now.. I will open a ticket. thanks.

@gzah sorry, should have already said that NO, it doesn't.

@gzahar. The top of the tree shows in the lights in MAIN.. but does NOT show as a pull down option in programing devices.

@MrBill Saw this post. Just migrated to isy on polisy. Lost this program. Cant recreate it as there is nothing available except the nodes below My Lighting. Also, nothing called ISY. Any suggestion? Thanks

I am not a daily user, nor developer of ISY and related items. However, I have been watching over the last few weeks with excitement of the migration of ISY to the Polisy (IoP). Unfortunately, while there are lots of excellent tips / guidance etc, many of them at first read are "over my head" and are very scattered throughout the forums. So after studying the many posts, I have collated and developed a Simple Person's Guide to making the migration. For those of you that are the experts / daily users, please feel to suggest edits /corrections to this page for others to benefit from. Disclaimer: I am still in the progress of this migration myself and will update with any corrections or new experiences. Lastly, many thanks to ALL the incredibly talented and smart people on these forums that I have "stolen" the information from. Here are a few: @Michel Kohanim @Javi @larryllix @bpwwer @tazman @lilyoyo1 @Jimbo @garybixler @kzboray ISY on 994i Preparation: Conduct a regular backup Export a text copy of all programs: Go to programs and right click My Programs and select Copy Folder to Clipboard. Open text editor and paste, save. All below are optional steps that are for protection and / or manual fix references: UnderTab Programs / Summary, copy all cells and past into a spreadsheet. Add column header names, and save. Under Main, click on My Lighting. On table, click on column header labeled Address to sort table by address. This will group all your Z-wave devices together, x10 devices together and your node servers together, etc. Take screen shots of all this information for reference if needed. ELK: If you have ELK module, click on Elk / Areas/ All Areas / Zones. Highlight all cells in table and paste into a spreadsheet, add column titles, save. Repeat for each area. Repeat for Keypads. Repeat for Outputs * NOTE : Elk module is not available for ISY on Polisy. The Nodeserver will replace that. Currently there is no migration tool for this and the Elk module data will not transfer to ISY on Polisy. Having the text copy of all programs in first step will be critical to restoring all the programs. Under Configuration / System tab, take a screenshot of all information Under Configurations / Emails/Notifications / Settings/Groups, take screen shot of all information Under Configurations / Emails/Notifications / Customizations, take screen shot of main screen. Labor intensive next step, do only if concerned: copy each name, past into text editor, open each Customized Content. Copy From, Subject and Body and paste into text editor. This will create a record of any system complex notifications you may have such as: -Front: ${sys.node.ZW015_1.ST} and ${elk.zone.1.status}. -Mud Room: ${sys.node.ZW020_1.ST} and ${elk.zone.15.status}. Under Configuration / Elk / Configuration, if applicable, take screen shot of Elk Config. Under Configuration / Networking / Network Resources, hit export and save At top level menu, select Tools / Generate Topography. Save. At top level menu, select Z-Wave / Backup Portal Preparation: If you use Alexa or Google or other voice systems, go to those tabs and Select Download (symbol) at the top and save a copy of the Spokens and their corresponding ISY programs / scenes etc. Polyglot Cloud Preparation (PGC): Log into above, and for any Nodeservers you have, go to Details / Configuration and save screenshots Polyglot on Polisy Preparation (PG2): Log into above, and for any Nodeservers you have, go to Details / Configuration and save screenshots Go to System / Check for Polisy Updates. Go to Settings / Polyglot Settings and select Download Backup, Save. Hardware Preparation, Polisy: Ensure latest version of ISY is on the Polisy. (IoP): Most recent versions of Polisy come with isy service already installed. So, the question is how old is your unit. If you have doubts, click the button behind the little hole on the front only once. This will download and upgrade your Polisy (if not very old). Once you hear the beeps, then isy on Polisy can be accessed through the ISY Launcher. If Polisy is old, you will need to SSH to the Polisy and update it manually. You will need the IP address of your Polisy. Instructions for a PC can be found here: https://forum.universal-devices.com/topic/34348-very-simple-instructions-requested-to-get-isy-on-polisy/?do=findComment&comment=324026 For a Mac, the built in application Terminal can be used to do the above. PLM Prep. The Polisy can use any of the PLMs available: If using a serial PLM, you will need the original cable that came with the PLM to attach to the serial output of the PLM. This is the cable. https://smartenit.com/shop/plm-serial-cable/ USB PLMs require a USB cord. Z-Wave: If you utilize Z-Wave, you will need a USB z-wave dongle to attach to the Polisy such as https://www.thesmartesthouse.com/collections/shop-by-brand/products/zooz-usb-700-series-z-wave-plus-s2-stick-zst10-700 . Attach this dongle to the back of the Polisy. Connect to ISY on Polisy (IoP): Ensure Polisy is running and updates above have been made. No need to connect to PLM at this point, still in preparation stage. Open the ISY Finder and see if it finds Polisy. If not, Add the following IP addresses, one at a time: http://myPolisy:8080/desc and https://myPolisy:8443/desc, where myPolisy is your IP address of you Polisy. Once the Polisy is found, open the Admin Console (Cloud or Lan): Sign in for the first time with User ID and password as admin Go to File / Set User ID/Password and change. For isy to support INSTEON and/or Z-Wave, go to the Admin Console / Configuration and check INSTEON/Z-Wave support checkboxes, click on save, and then click on the reboot button. Add Polyglot 3 (PG3) to Polisy. PG3 is the future development site for Nodeservers. Support for PG2 appears to be ending as developers look to move to PG3. To install PG3 on Polisy, create a SSH and enter the following: sudo pkg install pg3 sudo service pg3 enable sudo service pg3 start Once it is installed, you can access it at https://<your polisy's IP>:3000/ . It has the standard default login of 'admin' / ‘admin’. Change password by going to Settings / Profile. This will not affect your current PGC or PG2. Migration of ISY: Unplug 994i and Polisy from power Connect Polisy to PLM, and reboot Polisy. If PLM is new or has been reset to factory settings, you will need to restore it later the process Open ISY Finder, and then the Admin console for ISY on Polisy. Once opened, select File / Restore ISY. Select the ISY backup you prepared earlier from the 994i.. Everything is migrated except Z-wave at this time. Recommended approach is to be sure to print Tools / Topography. Then, using the topology, exclude then include your Z-Wave devices in ZW order ie ZW_01. This way, whatever programs you already have will continue to work and whatever Alexa spokens you have will point to the same devices (Network resources may need to be individually opened and re-saved, or can be deleted and reimported from file exported in prep stage if they are not working) NOTE: my ISY immediately disappeared. Upon reloading into it, the user id and passwords had reset to admin/admin, even though I changed them up above. Also Programs become randomly Disabled or Enabled. Need to check. I also lost my Query All Program details. If restoring or factory reseting or using a new PLM follow these directions Restore PLM Migration of PG2 to PG3: Both PG2 and PG3 can run at the same time and point to the same ISY. Since PG3 is still in development as is the nodeservers, it is unclear the best path forward, in this regards, but a migration / cleanup of duplicates between PG2 and PG3 may be best done prior to migrating either to the Polisy. User choice. On PG3, go to Settings / Polyglot Settings and select Restore Backup from Polyglot v2 to ISY on Polisy xxxxxxxxx, where xxxxxxxxx is the UUID of the ISY on Polisy. Select the file you backup up earlier from the Polisy, PG2. However, there are things to note about this process. The node server must exist in the PG3 store. It can't restore node servers that don't exist for PG3. Efforts are underway to create matches. The node server in PG3 must have the same name as the node server in PG2. If the name has changed, it won't be able to find it under the new name. If the node server in PG3 is not a free node server, you'll need a license for the PG3 version or it won't restore. Configuration parameters will only carry over if they are the same. If the PG3 configuration is different, it can't translate. Any node servers that exist in both can be deleted from PG2 at this time, prior to migration to ISY on Polisy. Note: Time for integration took 20-30 minutes. All, there was a big bug with migration which wiped out portal connectivity. A potential fix (which did not work for me. A ticket was required for UDI to restore): 1. sudo rm /var/isy/FILES/CONF/PORTALS.PSF 2. sudo service isy restart Migration of Polyglot PG2 to new ISY on Polyglot: Open Polyglot PG2 on Polisy and under Settings / Polyglot Settings, change ISY Settings to reflect the IP address of the ISY on Polisy. Should match the IP and port address used in the Admin Console to open ISY on Polisy, or host: localhost, port: 8080, uncheck HTTPS. Migration of Polyglot PG3 to new ISY on Polyglot: Open Polyglot PG2 on Polisy and under Settings / Polyglot Settings, change ISY Settings to reflect the IP address of the ISY on Polisy. Should match the IP and port address used in the Admin Console to open Isy on Polisy. Migration of Portal: Open your portal. Under ISY / Add ISY, add the UUID of the ISY on Polisy. This can be found either on the ISY Finder, or in the Admin Console / Help / About. Once entered, you will be asked about a license. Select Free Trial. Follow directions and back at ISY under Help / Manage Modules to add the Portal. ISY will reboot. Once rebooting, re-open admin console and go to Configurations / Portals and approve access for the portal. Go back to the Portal, refresh and you should see a green dot next to the UUID. Do NOT delete your old ISY as it is required to be there for the next step. To migrate Alexa or other commands, follow these directions while BOTH UUIDs are still in the portal. https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Portal_Migrate_configurations_to_a_new_ISY Migration of Elk: If you have the Elk module on the ISY994 you will need to install the ELK Node Server to restore ELK functionality. The node server version will have different node addresses and some slightly different naming. Programs that used the ELK have to be reconfigured for the new ELK nodes. After rebooting the ISY post migration and the ELK NS install, the programs that need attention will be highlighted in yellow as they show up on the programs/summary page. Refer to Program text file if backed up earlier for rebuilding. At that point it is just a matter of restoring the new ELK nodes back into the programs. Speak and query aren't available on version PG2 but will be added to PG3 in the future. Migration of Z-Wave: Currently there is no migration of z-wave, so the extra backup steps above will help you recreate your z-wave network. After all Z-wave devices were added, i notice many were in "different slots". Using the Find / Replace at the top My Programs worked like a charm for many of them. Saved me about an hour or two!. Reboot: Reboot your ISY and relaunch the Admin Console and begin any final work in the migration. WIki 994i to Polisy.pdf

@bpwwer I think I understnad the issue and goals of moving the configurations, but what happens to the nodes? For example when I move the NS Ecobee, from PG2 to PG3, will all of the nodes will become new nodes in the isy, meaning, that I will have to re-map any nodes I use in programs or scenes? If the ISY can have both reporting at the same time, then I suppose I can do Find/Replace in programs? Thanks

@Jimbo@Michel Kohanim Thanks Jim! As usual, I am sure you will do an awesome job with this! Voice is a critical part of my elk /isy /home set up. Am wondering two things: -should I wait until PG3 is completed before I convert from isy to isy on Polisy to avoid two conversions of the ELK systems --> ISY (with voice) to PG2 Isy on Polisy (w.o voice) to PG3 on Polisy (with voice) and -secondly, with over 160 programs that utilize an Elk based input or output, why is going to be the easiest way to "map" the two systems (current to new) together to minimize the work. ie what happens when I convert.. do all my current programs just show the ////error line and there wont be any reference point as to what needs to be replacded, Will the Programs/FIND/Replace command work, etc. Just trying to get my head around this upcoming HUGE task. thanks Doug

500 board but moving to the zoos 700 on polisy someday Sent from my iPhone using Tapatalk

Any idea if he would be abled to fix the Insteon connection part of a Dual Band Normally Closed 240V Load Controller (2477SA2) v.3A? ISY reports "cannot communicate with .." Slowly failed over the last month. Now cant write or connect to it but can sometimes turn it on and off from AC. Mine just died. Planning to replace with a z-wave. Knew these were prone to failure when I bought it a few years back, but didn't know of many options back then.

Am not that familiar with zwave but do have about 10 devices (locks, thermostats, outlets and plug-warts) in my ISY, but with Insteon's potential demise, I have been looking at some replacement / new z-wave devices. If my zwave mesh operates at the lowest common denominator in terms of speed, is there a way to tell what speed / series, each device is via the ISY? Or another way? Both out of curiosity but also to potential replace older. slower ones if they are the bottleneck. thanks.

@geddy Software update.. updated last night. .here is a screen shot. Not beta

@maxnorth Hmm.. ok. I will have to think through that a bit. Currently I use Voice-in-a-Can on my apple watch to access Alexa for things like shut the garage door etc. using voice. So from an initiation standpoint I have a way albeit its not completely handsfree when I am out and about. Is hands free only when near an Alexa-dot type of device. ( I have to touch the Voice in a can complication on my watch to initiate) Primarily I am looking for ways to get data verbally out of my ISY, from a verbal command in via Alexa. I need to go find other posts on this as well. ie: ask Alexa what is the wind doing and have it respond with my ISY data. Thanks for the response!

This Elk issue is pretty huge for me and until I understand the NS and what it can and cant do and the work involved to convert from my current Elk / Isy integration to a ISY / Polisy/ ELK NS set up, my migration to isy/polisy is on hold indefinitely. Sad. ~160 programs with Elk address (Motion sensors, outputs for sprinklers, open/close modules etc) ~ Voice announcements through the Page out to a whole house sound system to alert of things like Driveway motion, garage doors open /shut, external heater on / off etc. @Michel Kohanim Currently a show-stopper. Hope the NS and migration can both become better. And yes, it is worth $ on PG3 to me, if it were to migrate seamlessly and continue to support Elk integration as the module did.

@maxnorth Hi, I just saw this post and am wondering how you do step 4? I am interested in taking this in. a few directions, similar to yours, but also, to be able to ask Alexa "what is the wind", which I have a local station that the isy, knows the answer and I would like to eventually have Alexa answer it. Thanks

I see 15.2.2 is now available. This isn't listed as a fix, but here is hoping. Anyone have luck with it yet? I have downloaded it, but unfortunately, quarantining with Covid, so cant test. lol

Wow.. each time I think I am ready to invest in the migration, something new pops up.. This alone will cause several hours of work of re-writting programs. Have ~160 program with Elk in them, some with lots and lots of lines / references. It sure would be nice for someone to truly and simply explain all the steps, processes and things that need to be done. yes ,I understand everyone is still learning themselves, but I hope we dont loose sight that there are a lot of people that would like to do this, but just need a bit more guidance. Just a few that I keep hearing that I haven't seen enough explicit directions on, but surely could figure out after trial and error include: -Elk -Nodserver migration -Portal migration: how, what happens to Alexa links, etc -Z-wave migration; what to expect? complete rebuild into scenes, programs etc? Others? This posting helped just to get ISY on the Polisy... w/o this I would not have had a clue where to start. Thanks.. (just venting as I am anxious to convert but cant afford to have my house go down for days on end while I try to recreate a very complex system because I didnt understand all the land mines.)