DennisC

Not necessarily, UD Mobile could be using the remote portal connection and not your local connection. You should sign in to your router and verify you are using the correct IP address.

Check your router to verify eisy is connected and you have the correct IP address.

Sorry, had a long day yesterday......

Well, above you wrote: "My program was activated by this data, but it is written to activate only if daily precipitation is >0.45", but the program you posted says "<= 0.750 Inches"?

That is exactly my point. By doing this, you are not using the built in Elk smoke detection input, notifications, & quick action buttons. Also, by code, there are other requirements that need to be met when using a relay for smoke detection (supervised monitoring of relay). According to the Kidde documentation, these devices are meant to be for auxiliary warning devices, not primary notification and alarming. Would they work, probably, but......

How would they tie in to the Elk dedicated smoke detector terminals, which requires a 4 wire smoke detector?

This is what I am currently using: https://www.jmac.com/UTC_Formerly_GE_SecurityESL_541NCSXT_p/UTC-GE-ESL-541NCSXT.htm

Start with rebooting eisy.

You can start here: https://wiki.universal-devices.com/Eisy:User_Guide#eisy_(PG3)_Dashboard Once you decide on your first plugin, go to the store and select the plugin you are interested in. Most of the plugins have a more button, following that link will take you to specific instructions to configure the plugin.

If you are using eisy with a serial PLM, a special cable is needed. Are you using the correct cable and if so, could the cable be defective?

I use Yolink Power Failure device at two locations, along with Yolink Plugin. Works flawlessly.

I have to agree with @Geddy , strange file location. When you reboot, are you shutting down and restarting, or just restarting? I would suggest you shutdown, restart, and then follow these instructions: https://www.java.com/en/download/help/uninstall_java.html to run the Microsoft utility listed under troubleshooting. That will repair any corrupted files and stray registry entries. Afterwards, shutdown, reboot, and then try the offline installer.

Since you deleted that folder, have you tried rebooting, followed by using the instructions in the troubleshooting guide? That note about "investigating" this issue has been around for several years. I wouldn't wait on them finding an issue.

I have experienced the Java 1603 a couple of times over the years when updating. While this doesn't sound like it will help you, I was able to correct it by using the offline installer listed here: https://www.java.com/en/download/help/error_1603.html

That is not completely true. Even with Liftmaster coded system, you can use one of the below listed opener switches and then connect dry contacts to the terminal board. I did this a few years ago with a new Liftmfaster torsion bar garage door opener. https://www.amazon.com/883LMW-LiftMaster-Button-Control-Security/dp/B07W5RMN56/ref=asc_df_B07W5RMN56?tag=bngsmtphsnus-20&linkCode=df0&hvadid=80470717339467&hvnetw=s&hvqmt=e&hvbmt=be&hvdev=m&hvlocint=&hvlocphy=98524&hvtargid=pla-4584070199414765&psc=1&msclkid=382c3ea2718c12808f9857558fc91362