DennisC

Have you tried rebooting ISY and after it has completely started up, re-syncing UD Mobile? If that doesn't work, then I would suggest opening a help ticket with UD or tagging Javi.

If you think login credentials changed somehow, try the default admin/admin.

What is the light sequence on front of ISY? Have you tried resetting power to ISY? 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

If you don't find a way, you may need to do a rest: Multi Function Button There's a little multi function button behind the very small hole on the front of the unit. This button has multiple purposes outlined below. Every click on the button will cause the unit to beep. If the button does not behave as described below, please update Polisy. Update and Upgrade All the Packages Click the button once. Safely Reboot Click the button twice. Safely Shutdown Click the button three times. Reset Credentials Press and hold the button till the first LED (from the left) starts blinking then release. This action resets Polyglot as well as SSH credentials back to the default admin/admin. Reset Networking Press and hold the button till the first and second LEDs (from the left) start blinking then release. This action resets all network configuration back to DHCP on the Ethernet jack next to the serial port. All other network interfaces shall be disabled. Factory Reset Press and hold the button till all LEDs start blinking then release. This action resets the credentials, removes all configurations from Polyglot/Polisy, and resets networking.

The Elk will show up using either the UD Elk Module (which is available for purchase on UD website) for the ISY or the currently in development Elk Nodeserver. I should add that to use a Nodeserver you will need a Polisy or, for now, an RPI running Polyglot. When Polyglot 3 is released it is not expected to run on a RPI.

That's good. To continue the thought, when you port forward 443 to 443 you then used your ISY IP address as the device IP to forward to? The next option for you might be a portal subscription. It is inexpensive and it takes port forwarding out of the process.

Just to be be sure, for remote access you are using your WAN or DDNS address, not your ISY address?

For the existing ISY, adding zwave involves installing a zwave board and the purchase of an inexpensive software module. When Polisy takes over for the ISY, the zwave board will be replaced by a dongle.

This morning, I found Nodelink not updating to today's date. When I looked, I found my ISY user name in Nodelink was set at admin. I corrected my login information and restarted Nodelink. No the ISY Data fields were blank. After checking the remainder of the settings, I tried a Query from the ISY and received: I enabled debug in Nodelink and besides the typical duplicate names found the following: 2021-04-04 12:55:17 - Auto-Update: Checking for program update... 2021-04-04 12:55:18 - Auto-Update: New version found, downloading... 2021-04-04 12:55:19 - Auto-Update: Download complete, moving and restarting... 2021-04-04 12:55:19 - Auto-Update: Error downloading new version 2021-04-04 12:55:56 - Web Request Invalid: /isylink/nodes/n001_data1/query 2021-04-04 12:55:56 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/report/request/5170/failed) 2021-04-04 13:00:08 - Web Request Invalid: /isylink/nodes/n001_data1/query 2021-04-04 13:00:08 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/report/request/5171/failed) I am currently running v0.11.0 and have been for sometime. Not sure how to get Nodelink loading data to ISY again.

How do you access your ISY? Are you using the Launcher? If not, try again after accessing your ISY by the Launcher. If it still fails, then make note of the errors, including the filename and open a support ticket with UD.

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.