DennisC

While possible to do in the Elk, I generally follow the rule that if it is possible to program in the ISY/eisy, then I program there. I find programming in the UD infrastructure simpler than in the Elk, but the primary reason is to have all of my programming in one location. As for sample programs, there are many options depending on what you want to accomplish. While the programing is simple, if you get stuck with an aspect of what you are trying to accomplish, ask a specific question. Also, if you need to open/close your GDO remotely, take advantage of UD Mobile Command class and create a favorite that toggles the GDO open/close.

When was the last time you cleared Java cache by checking all 3 boxes, then deleting files in Java configuration, and then downloaded a new start.jnlp from UD? Not too long ago, there was a change made that resulted in not found appearing. The correction for this was a new download of an updated start.jnlp.

The newest update listed in the release notes is for v3.10.6?

Looking at the data you posted, you can see the temperature dip and then within 2-3 minutes an increase in temperature. Adding a wait for 2-3 minutes, would prevent the program from triggering until the temperature dip stayed below your trigger temperature for the duration of the wait period. If the temperature increase during the wait period to a point above your trigger point, the If statement will re-evaluate as false, thereby, preventing a notification from being sent. After the wait period, if the temperature is still below your trigger temperature, the program continues to run and your notification will be sent. It's a way of minimizing the freeze warnings until the temperature is below your trigger point for x minutes. While in my example, I used 2-3 minutes, the wait can be any time period you choose. If you waited 5 - 10 minutes, or even 15 minutes, what would be impacted by having a temperature below freezing for a short period of time?

You could try adding a slight delay to your program, say wait 2 or 3 minutes?

No, the issue is with the phone vender throttling certain types of messages. It has been happening to a lot of us for several years. It is the reason we switched to Notification plugin and Pushover. You can not beat the speed and reliability.

I would suggest checking the plugin log to see why the restart. If nothing is obvious it might be time to open a support ticket.

I had this issue on my Polisy and again on eisy. I opened a support ticket and requested a scroll bar be added to admin console. I was told that it would be done but it would take awhile. That was about 10 months ago.

You can not migrate Zwave, instead will need to rebuild your Zwave network.

That would suggest that there is another programming (maybe forgotten?) that is changing the temperature, or is it possible there is a forgotten setpoint in the thermostat? Maybe you should double check the thermostat's just to be sure. Next, use the Find/Replace option in eisy programs (right click on one of your programs with the thermostat device in it) and search for all programs with the device. Finally, run one of the programs, let the setpoint change back, then check the program summary page for a program that just ran. You could also monitor that page while triggering the program to run. Let's see if you find something else triggering the change.

Since there is nothing obvious with what you posted, let's try something, change your If section so it reads as follows: Weekend Thermostat Morning ODT condition - [ID 001A][Parent 0001][Run At Startup] If ( From 8:00:00AM To 11:58:30PM (same day) ) And 'Automation / Outdoor Temp' Temperature < 40.5°F

Have you toggled the use Zwave switch in Configuration tab and then rebooted? Is Zwave menu at top of the admin console?

I think you meant @paulbates

It is not clear from what you wrote, which ZWave dongle did you buy, have you successfully added the dongle, and enabled ZWave in the Configuration tab?

For anyone to provide assistance, we would need to see the programs in question. Right click on the program(s) and select copy to clipboard, then paste the program here. To insure the migration directions were followed, did you confirm the Zwave addresses were correct? If you migrated using UD ZMatter dongle, the device address changes from ZW to ZY prefix. Verify the programs are correct and then resave each program, even if no changes were necessary.

You can keep as many controller's as you like. At GDO, the wires from pushbuttons and controller's are all spliced together. The pushbutton can be dedicated to the GDO, or it can be an actively used button. This method is not dedicated to ELK, the same solution can be used by any ISY ecosystem device by adding an Insteon or Zwave contact closure switch or relay.

Sounds like it might be time to open a UD support ticket.

As a stand alone, the Notification plugin is great for short messages, as is UD Mobile. For longer or customized messages, Pushover shines. Have you seen the instructions page here: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md and here: https://www.jimboautomates.com/pg3-node-servers#h.h1ph1aotljg6

Try factory resetting the device and then add back in.

That is an indication that either the configuration is not correct or the carrier is delaying or blocking the text. It is why a lot of us switched to the plugin. Add a service like Pushover with it and you will be very happy, there are a lot of options available.

On the screen you setup the phone number, doesn't the test button send a test notification?

A quick search shows that is the correct format for TMobile. eMail to text has been very unreliable at times for many carriers. Sometimes using a dedicated email account with Gmail has helped. Instructions are in the wiki. However, for fast reliable notifications, if you are setup to use plugins, try Notification plugin. It is fast and reliable. Combine it with Pushover and you will not miss your text capabilities.

At one time, I had 3 UD devices on one portal account with no issues. However, they were all located in one house. For my vacation home I elected to use a second account. It makes organization and management easier. Since your existing ISY is at end of life with no free support available, I would not suggest trying to reuse it. Upgrading to eisy and disposing on the 994 is your best option for less headaches.

Another approach would be to use the find and replace search capabilities and search for programs and seems that have that device in it. Check wiki for details. You can also right click on the program that turns device on and select status. That will take you to the detail page and look at the last time the program ran. If not at the time of turning off, then check for what might have run at that time.

Assuming you are on PG3, go to System Tab and select reinstall all plugins. This will upgrade Python Interface. You want to be on 3.2.6 or greater. You can check this after the reinstall by restarting any Plugin and checking the first few lines of the Plugin log for Python Interface log.