DennisC

A good starting point might be the error log.

Here are a couple of possibilities from the wiki: Admin Console is very slow or hangs If the admin console is slow to respond, it is likely you need to increase the amount of memory allocated to the Java runtime (JRE). Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: -Xmx512m Press Ok to close the window, then Press Apply to save the changes admin.jnlp does not start the Admin Console If Java is indeed installed, the reason is that .jnlp file association is broken (it has to point to javaws.exe). Search for javaws.exe in the computer. Right mouse click and select "Open with" and point to "javaws.exe" to fix the .jnlp file association. Userid/Password dialog keeps popping up This is usually related to firewall software on your computer. Two solutions: Use https (instead of http) to connect to your ISY Configure Your Firewall Software Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.* file patterns: udi_tree.state udi_frame.state udi_pgm.state udi_finder.state udi_launcher.state

If you can't move past "linking", you best open a ticket with UD. They will help you.

Did you confirm you have the upgraded v5 zwave dongle, the one without the blue light? Go to the Help menu, About and post your zwave version number. If you upgraded to v5, it should not be 4.55.

It would appear, v5 was made for what you would like to experiment with. Have you taken a look at the nodeserver store? Here is a link to the UD Nodeserver store. https://polyglot.universal-devices.com/ These Nodeserver will run locally on a Polisy. Currently, they can also run on a RPI, however, that ability will be retired in the near future. Also, while not local, you could also checkout the ISY Portal. Here is some information on the Portal: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions

Is there anything in the error log? Maybe messages are full orsomething else causing delays or high traffic?

To prove your theory set a variable when Open Weather temperature is less than 40 degrees and use the variable to trigger your program. This will allow you to troubleshoot the remaining program.

Are you clicking on the "Set Configuration" button?

Do you have a copy of the Elk program Elk-RP? If so, you can write a rule in the program to turn on a virtual output when the Elk is armed and turn off the virtual output when the Elk is disarmed. Then you can monitor the virtual output in a ISY program to receive your notification. I think you will find this more reliable.

Apologies, didn't mean to send you down the wrong path......

The 110022 error message means: -SET SESSION KEY UNSUPPORTED BULK ALGORITHM What is the contents of the notification you are trying to send? Maybe something is corrupt with the notification. Try deleting it and creating a new test notification with a different name.

First, when you think your notification was missed, go to the program and check the last run time for true or "then" portion of the program. If the run time indicates it ran true and you didn't receive the notification go to the error log and see if there was an error around that time. Look up the error code on the wiki page for ISY error messages. If the program did not run true at that time, you have a problem with the program running.

Update neighbors and synchronize nodes is all you should have for the update zwave dongle and the current firmware. Use update neighbors after adding zwave devices and synchronize nodes if you are having problems.

Have you determined if all of the notifications are being sent and you are not receiving them, or the notifications are not being sent? You can tell by looking at the last runtime for the program and by checking the log.

Great to hear you got it working.

Locks usually need to be within 2 - 3 feet of the ISY to be added. Once you are within range, you should be able to exclude the lock first.

I would suggest you open a help ticket with UD. However, I would try a new power supply first. Some strange things have occurred with power supplies starting to fail.

Have you ever backed up your zwave? It use to be a separate back was required. If so, you could try zwave - restore.

support@universal-devices.com or https://www.universal-devices.com/contact-us/#contact

From the wiki here: https://wiki.universal-devices.com/index.php?title=ISY_Users:V5:ZWave:Advanced_User_Guide:NodeMenu I think I would try this: Repair Links Rewrites all the associations and other related settings to the Z-Wave device Remove Failed Node If a Z-Wave device is no longer available for any reason then this command can be used to forcibly remove it from the Z-Wave network. The device will not be removed if it still responds to messages sent to it. Replace Failed Node If a Z-Wave device is no longer available for any reason then this command can be used to forcibly replace it from the Z-Wave network. The device will not be replaced if it still responds to messages sent to it.

Here are some specific troubleshooting steps: https://wiki.universal-devices.com/index.php?title=Main_Page#Java_applications_are_blocked_by_your_security_settings

Sorta sounds like you are not using a DHCP reservation. I would suggest you configure your set up to match this: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Network_Settings

As I said, text has been very quick for me. In addition, you still have all of the same delivery steps with Pushover as in direct from ISY, but you then add Network Resources and Pushover process before the delivery steps. If it works for you or you have too many notifications for ISY to text, then that's fine. For me it is quick and reliable.

eMail, not so much, but text messaging has worked very well for me. Although, I do use email for backup notifications or if I want more of a trail of the notification. Anyway, my point was, I feel going through network resources and then the Pushover process added extra points of failure to the ISY notification. Final delivery process is the same, so since it works very reliably for me, I don't see the need to add the extra points of failure.

As I stated above, I use email substitution for both text and email notifications. I have found it to be highly reliable with delivery in a matter of seconds. While I think it is a personal decision, my thought is for critical applications, or what I think are critical applications, the fewer devices involved means the fewer points of failure. If you are committed to Pushover, then @MrBillhas given you good examples to follow. In my opinion you are adding additional failure points (Network Resources, Pushover).