garybixler

@bpwwer I was able to delete and uninstall a NS from PG2 (Wemo) and Install it from PG3. I used the same slot but does it matter in which slot it is installed? Does the ISY just go by names and not in which slot it is installed for identification? All I needed to do after that was just resave any programs associated with that NS. Thanks much for you assistance. Gary

@bpwwer Hi, I have migrated from the 994 to the ISY on Polisy and installed PG3 and have a few questions. Can I point PG3 to the ISY on Polisy having both PG2 and PG3 connecting to the ISY? Will an update show up on the PG3 for a NS I have installed from PG2 or will the Node Server config on the ISY need to be changed to port 3000 first? Just wondering how the NSs can be updated to the latest versions but keep the same definition on the ISY. What will need to be changed on the NS configuration on the ISY? I have one that can be migrated at this time. Thanks for any insight. Gary

Check out this link. https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues

I had the ELK module on the ISY994 but after migration I needed to install the ELK Node Server to restore my ELK functionality. The node server version will have different node addresses and some slightly different naming. So those programs that used the ELK had to be reconfigured for the new ELK nodes. After rebooting the ISY post migration and the ELK NS install I saw that the programs that needed attention had the message out of memory show up on the programs/summery page. 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 addressed in version PG3. For now you can turn on global polling for voltages on the Elk Area node if needed. After you 'Set Poll Voltages True' you must restart the NS for the change to stay True. Overall I think the NS version is great. Just one more thing. Temperature values aren't present on the ELK PG2 version but will be on the PG3 version.

I do have one question that maybe someone could answer. After migration the node servers are pointing to Polisy Host Name. In my config it is the IP address of the Polisy. Would there be any advantage to using the loopback IP address (127.0.01) or not? Thanks Gary

All I had to do was make a backup from the ISY994 and do a restore to the ISY on the Polisy from that backup. I used the same PLM so no restore was need for that. After the restore I just configured Polyglot (PG2 only) to the ISY on Polisy. If you have Network Resources you may need to edit and resave each item and then do the global save. Portal can be migrated at the portal web site. If you didn't have the ELK module on the ISY994 every thing should be good. At least that is how it worked for me.

Just wondering if anyone has successfully set up a Zooz Zen 17 with the input trigger disabled from the relay allowing the monitoring of dry contact inputs and controlling the relay through Z-Wave only. The settings are Parameter 2 value 7 or 10 and Parameter 10 value 0. Resynchronizing should create a 'Custom Button Press node' according to the Zen manual. I never had Z-Wave on the ISY 994 so I don't know if this setup even works. Looking to replace the Insteon SimpleHomeNet EZIO8SA for garage door monitoring and control. Thanks for any info or insight. Gary UPDATE: After a ZEN17 firmware update and properly removing and adding the ZEN all seems to be working great now. Thanks Gary

Z-Wave question. I have added a couple of Z-Wave devices (ZooZ ZEN76 and ZEN 17) to the Polisy ISY. They can be controlled from the ISY fine but any local control doesn't seem to be recognized by the ISY. The device status isn't updated. I have tried multiple Z-WAVE settings and device configurations but nothing works. The following is what I see on the event log when a device is locally switched on or off. Thanks. Any insight appreciated. Gary

I just added my first Z-Wave device on the Polisy ISY being the ZooZ Multirelay ZEN16. I am trying to separate the relays from the switch inputs so they can be used to indicate weather the garage door is open or closed. I have done that with customized parameters. Also I believe that the Basic Control 2 node should be able to read the state of the switch. ON/OFF. The Z-Wave options shows a setting for button press detection which I added to the node. ISY does see the change but is not reflected in that node. Not sure if this can be done. Just looking for any info or suggestions. Just in experimental mode at this time. Thanks Gary Update: I found that the ZEN17 may be better suited for what I am trying to do. Will give that a shot.

Thanks Techman I'll put the extra nodes in a folder. Just wondering if they can just be deleted. Something to try. Just discovered that the config needs to be done from the main node only. So all works great. Thanks Gary

Hi, Just looking for some info. I just received my first Z-Wave device to experiment with on the Polisy ISY. The device is the ZooZ ZEN16. I have it linked to the ISY with no problem. Can't figure out what all the nodes are for. The ZW002.1 On-Off Power Switch node does in fact turn the relay 1 on and off but associated with that is ZW002.1 Basic Control 2 which has no status and seems to have no function. Also when trying to set configuration parameters for the ZEN16 I just get an error. Thanks for any insight. Gary

It does place a comma between automatically. Also tried a text separately. But I think I lost my Group name file in the process. Nothing can be saved. Not important at this point. Will probably need to open a ticket. Thanks Gary

Just realized that emails work with out any problem and no error message. It was a text message that I was sending along with the email that was causing the problem. Thanks Gary UPDATE: Just an observation. If a text Recipient is included in the groups name list I will get the errors and the email won't be sent.

Unfortunately I keep getting this error. All the latest updates and procedures have been done. Thanks for any suggestions.

I have 2 Chamberlin wall mounted openers with MyQ capability using the included ethernet hub. Even though they have a smart wall switch they will still operate using a momentary close/open relay across the smart wall switch wires just as the older openers.

All good. Thanks Michel

Same issue.

Try clicking on "Admin Console (Cloud)". I'm doing that for now to keep the launcher from locking up. It works for local.

I have the same issue where the PLM shows not connected. All updates and upgrades are up to date. The PLM that I have is a smartlabs dual band 2413u version 1.0. It can be seen by an app that runs on the PC. 'Simplehomenet Utility Suite' Thanks Gary

All good here. Just one small issue. I need to use Admin Console (Cloud) from the launcher even though it is using the local IP address. If I use Admin Console (Lan) the launcher just hangs and needs to be restarted. Using port 8080. I did reinstall the launcher but no difference. Also just ordered the 2413u. Thanks Gary

@MrBillThanks. The upgrade seemed to go well. I did have one causality however. The NS WEMO can't fine file splite3. I'll check with WEMO on that problem. Thansk Gary

I did the update and upgrade but it seems that the polisy stays at version 12.2. (FreeBSD polisy 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 r369564 POLISY amd64) Suggestions on how to get to 13 welcome. Thanks Gary

I am not only concerned about the lack of Instron support but also no Network module. Some network devices are not supported with a node sever and may never be. Also some NSs may not cover all the desired commands that can be supplemented with the Network module. Thanks Gary

Same problem as @gviliunas but also would add that the 'Settings Polisy Configuration' never loads. However all works fine after a Polisy power reset. Reboot from the menu doesn't seem to work either. Thanks Gary

Thought these may be of interest. ELK-912 or ELK-912B. They are passive and need no external power.