DennisC

I believe 170001 is an informational code, not a specific error code and UD has indicated to ignore it.

Only the power led on indicates the ISY is idle. Do you have the solid network light on in the rear?

Does UD know that you are using a static IP? That is not the preferred method of maintaining a permanent fixed IP address, as it has been known to cause different issues. U D recommends establishing a DHCP reservation in your router. This will enable your ISY to have a fixed IP by always issuing the same IP address. In fact, the ability to establish a static IP address has been removed from eisy.

How long has it been since you rebooted your router? If it has been awhile,, maybe something hung up.

You need to go in to your ISY/Polisy/eisy admin console and approve the connection. I think it's under Portal tab on Configuration page.

You should be able to load the IP into the ISY Launcher manually. Double check that eisy is still using the same IP address. When changing cables you may have been issued a new IP address.

Glad you got it working.

Here are the instructions for setting up the Elk Node server on the configuration page. Note the port :2101 after the IP address. To Configure the ELK Node Server Set temperature_unit to F or C Set host to the host or ip address and port, e.g. 192.168.1.15:2101 Set user_code, suggested to create a unique usercode for this Node Server Set areas to the range of areas you would like to include Set outputs to the range of outputs to include Set change_node_names to true makes ELK the source of node names so if they are changed then ISY names will be changed to match. A range can be comma seperated to include just those numbers, or seperated with a dash to include numbers in between. For example 1-3,5,7-8 will be 1,2,3,5,7,8 All ranges start at one just like the numbering the Elk uses. Note that if you remove an Area, it will not be removed from the ISY or Polyglot. This is intentional just in case it's an accident and your scenes or programs the reference the nodes. You can go to the Nodes Page in the Polyglot UI and delete them using the X to the right of the node. When any value is changed you must restart the Node Server for it to take affect.

I'm thinking the correct port is 2101, but double check, or just try it and see if it works. Don't forget to restart the admin console.

You need to use the non secure port to connect with the M1XEP. I am not home and don't remember which port is which, but I do remember it tells you in the M1XEP.

Here is the light troubleshooting section from the wiki: Front Panel LEDs/Lights Boot up sequence: Power, RX&TX, momentary blink of Memory/RX and TX, and then Power only Error light and Memory light blinking simultaneously: ISY is not able to get on the network.Please ensure: The Network jack on the back of ISY is connected to your router The lights on the Network jack have one steady on and the other one blinking. If not, check cable and connectivity to the router Your router provides DHCP There are no other devices on the network with the same IP address (IP Conflict) If you have configured your ISY to use DHCP, then you will have to search your network for devices that might be in the same DHCP range as your router is providing If you have configured your ISY with a static IP address, and as long as you have a good backup, you can Factory Reset your ISY and then restore a good backup (File | Restore ISY). Once prompted to change the network settings, choose No Only Error light blinking: ISY cannot communicate with the SD Card. Please ensure: The micro SD Card (on the front) is seated properly. Unplug ISY, remove the rubber cap, using a sharp object, push the micro SD Card in so that it pops out. Push it back in so it clicks in. Apply power to ISY If reseating the micro SD Card does not work, you probably have a defective SD Card. Please consult Replacing/Formatting SD Card You can have a family member unplug power, wait, and plug it in again, followed by checking the lights against the guide. You can also try a new power supply, weak ones do some strange things.

Since your test emails fail, are you following this when you send them: Testing the Settings "Go to Admin Console | Configuration tab | Emails/Notifications Under Groups click on the Name and highlight the desired row/group to be tested At the bottom, click on the Test button." How about creating a email notification with an email substitute. It can be anything: status, temp anything. You can find info here: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables Then write a program to send it maybe 5 minutes and see if that works.

I'm confused, you state update ISY994 and then you indicate "my Polisy" is dead. Are you attempting to migrate from ISY994 to Polisy and your Polisy failed when trying to update to latest version? If so, try power cycling. If that doesn't work, how long have you had it and if for a long time, have you kept it up to date? If not, check wiki for a reference to very early units? There is some language in there about intervention being required to update (possibly a chip replacement), I'm traveling now and can not look it up.

Thanks for the information, I'm always willing to learn something new. One follow up, after clicking on "Set Time" do you need to click on "Write Changes"?

I believe Bob has posted that 3.1.23 was in testing. When that happens it shows as available in PG3, but it is not ready for an upgrade command to install it. At this point, I think it is probably best to wait until Bob tells us an upgrade is ready.

Just to confirm, are you excluding before you try to include?

While I use Insteon, I have never used an Insteon thermostat because of reported reliability issues. How is the time set when using with an ISY system? Is setting time available in programs or is there a configuration parameter that needs to be set? What nodes are displayed in the admin console? Is everything else Insteon working correctly, if not try rebooting. If everything is working correctly, try right clicking on the thermostat in the right hand window and select restore device. Also, make sure there are no write updates pending. If nothing else works, I would agree with @Geddy, you need to file a support ticket so UD is aware of it.

UD is aware of both these issue. The subscription issue will be fixed in the next release. I'm not sure if they have identified the upgrade packages issue, but appears that after several reboots it goes away, or at least doesn't appear as frequently. This last upgrade requires a second reboot after the update packages completes due to the files that are being updated.

No, you can not pick and choose during the migration, you either migrate or start over. Having said that & first, let me say I have not tested this but: According to the wiki migration instructions: "If you don't actually change your Z-Wave network by adding/removing Z-Wave devices after migration, you can back out the migration by connecting whatever Z-Wave dongle you were using before migration and restoring the backup you made prior to migration." When you migrate, none of the devices, programs, network resources, or variables are actual removed from your existing system. Theoretically, if you used a new PLM for Insteon and you had a different dongle for ZWave, you could just delete the devices in eisy after migrating and continue to use your existing system. However, you will have a lot of errors all over the system. I see at least several potential issues for doing this. 1. Part of the migration process is migrating your portal & node server license, & the node servers. From the wiki: Migrating Node Servers to PG3x Migration is only possible with version 3.1.17 or later of PG3x. The version of PG3x that ships with eisy is currently 3.1.16 which does not support migration. Please upgrade packages first and make sure you are running version 3.1.17 of PG3x before attempting to migrate. Backup PG3 on Polisy. Restore from PG3 backup on eisy using the "Migrate from PG3 Backup" option. Cautions: Node servers currently installed on eisy will be removed (and possibly replaced). Node servers migrated are left in the "stopped" state. You will need to manually start each one after migration. If the Polisy was configured to manage node servers on more than one IoX (say both Polisy IoP and i994) only one IoX will be migrated and you can't choose which one it will migrate. Node servers installed on the Polisy from the local node server store will likely fail to install on the eisy. Node server licenses should be migrated as part of the Portal migration step. I guess you could skip this step. 2. Once you delete Insteon devices from eisy, you will have communication errors unless you factory reset the PLM that stays on eisy. For ZWave it may or may not be an issue. In any event, you should not have two programs on two different systems controlling your devices, you probably should disable one set of programs. 3. When you are ready to make the final change over to eisy, you will have a lot of manual manipulation to complete and you might risk a strong possibility of a conflict or corruption of something(s). 4. Did I say you would have a lot of errors........... 5. You would be in uncharted territory here, and anything might happen. As for my opinion, this is not a path forward that I would want to undertake. If your system is that large, why put yourself through that much extra work? A safer cause of action would be to hold off from migrating a while longer until things settle down some more and managing Zwave device settles down a bit more.

UD Mobile was not designed to work with the EOL Elk Module. UD Mobile fully supports the Elk Node server and both developer's have worked together before to correct any issues. In UD Mobile using the Elk Node server, outputs appear as any other node.

As stated in my previous reply, the current crop of node servers run on a Polisy or eisy. The cloud based node server offering was shutdown due to security concerns. Depending on the specific node server, some cloud participation may be required for specific manufactures but Elk is not one of them.

Yes, I and many others are currently using this node server. I have been using it for over two years. Its functionality is at the least on par with the now end of live Elk Module and in some ways much better. The support from the developer is top notch. I am unaware of any of the approximately 100 current node servers developed mainly by individual developers with support from UD called "faux node server", but maybe it exists somewhere. The current list of Polyglot v3 node servers that can run on Polisy or eisy is here: https://polyglot.universal-devices.com/ If you follow that link and click on the name Elk, and then click through the next page, you will see information about the node server and its functionality. If you click the link at the top of the Elk node server github readme file called Issues, you will find current open issues the developer is tracking. You mention "ISY" in your last post. If you are referring to an ISY994, I use to, but I moved on to a Polisy and now an eisy. The current version of the node servers in the link to the list I posted will not run on a ISY994. These node servers require either a Polisy or eisy. The ISY994 is now end of life. Previously, with Polyglot v2, node servers could be run on a raspberry pi, however, while Polyglot v2 might still be available (?), it is also end of life and there will be o future development.

Prior to upgrading to v5.5.7, I had to manually query them to get them to populate since on eisy after a reboot of eisy. After upgrading to v5.5.7, yes, all nodes populated on their own, but it took about 7 minutes. Thanks for the explanation, I understand.

I suggest updating your support ticket to capture your testing. Sorry it didn't work.

Based on @Steve L comment, try triggering motion and immediately wright changes to device.