DennisC

I didn't go back and read through how you have your programs set up, I did look to see what kind of sensor you are using, but didn't find it. Are these Insteon devices? Are you having any communication issues in the log? If this was me, I think I would start over. If these are battery devices, I would change all of the batteries. Then I would re-program the leak sensors using the example in the ISY Cookbook, pages 291 - 297. The Cookbook can be found here: https://www.universal-devices.com/docs/production/The+ISY994+Home+Automation+Cookbook.pdf

Node servers can add additional capabilities to your system. For example, weather, date/time, sun position, Kasa device, Elk alarm, Notifications, and many more.

For what it's worth - An occasional reboot should not be 4 times a week. I would be looking for a new router.

What version of PG3 are you running?

Did you stop the running programs before disabling them? Let us know how your new program works out.

Also wondering if the batteries maybe weak. Try changing them.

Glad you got it working.

Let us know how it works.

Not sure if you will have sufficient time to try this, but when you are connected, can you try restart PG3? If it still happens, check PG3 log.

In the past, I have found that sometimes when using run for 24 hours or longer, sometimes the program doesn't keep running past midnight. The exception to this is when using built in scheduling time and the "next day" box. That seem to be ok. So I add a line that either states "run if" or "run then" pluse program name ànd set the time to 12:01 am. Which one I use depends on the type of program I am writing. I am traveling and don't have access to my system to post an example. I hope that helps, if not, try adding it and ask a specific question.

Not sure if this helps, but when I have a program that runs over 24 hours, I add a run if or then shortly after midnight (12:01 am) within the program.

Sounds like you have communication issues. Isn't there a type of restore Zwave option or add/remove nodes? Don't remember exact language and I'm not in front of system. Last resort would be exclude/include, but if you are having communication issues that might make things worse.

If you read this section it contains information for restoring both ISY and PLM. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu

@wswartz Looking for something else, I found this in the wiki: Only Power Light Is On: Most probably power supply related. You can try any power supply that outputs anywhere between 5 volt and 30 volts,center positive, 2mm barrel connector

ISY is past end of life. Support for it ends soon, maybe end of year(?). There will be no further development for it. Time to start thinking about an upgrade.

Try rebooting Polisy.

Are they battery operated devices, if so try waking them up first.

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.