DennisC

Post a screenshot of your configuration settings from pg3x.

Did you read my reply in your other post? All configuration is done in Polyglot, PH3x, not admin console. After changes in PH3x you need to close and then reopen admin console.

You don't install any plugin from the admin console. Plugins are installed and managed from PG3x. Is that what you did? The Elk plugin has extensive documentation and examples. If you installed the plugin correctly, go to PG3x, click on Dashboard from the top menu, followed by Configuration. Instructions for setting the plugin up are there on the Configuration tab. You can also go to Plugins Store from the main menu, select Elk Plugin, followed by "More Info". Here you will find details and examples. If you haven't installed the plugin in this manner, or can't access PG3x, go to UD's wiki eisy manual and there are instructions there.

Hold on a minute. Your using http, with port 8443, it should be https. Try: https://192.168.0.151:8443

Use the multi- function button the front of the unit. Check the user guide for # of presses.

You would be surprised, stranger things have happened. I would suggest rebooting your router and after it starts up, reboot eisy. If you still have trouble after that, go to Universal Devices wiki page and look at their troubleshooting page. There is a section there about troubleshooting when IoX can't find eisy/Polisy/ISY.

If adding the IP address manually in IoX finder doesn't work, you can also try adding: https://eisy.local:8443/desc

Go to my first response to you, I attached a link with the migration instructions. Static IP addresses are no longer supported because of heavy support load when problems appear. However, you can still fix the IP address by using DHCP reservation in your router, which is a better way of fixing the IP address over static IP's. When you say website, are you referring to PG3 (Polyglot)? Have you registered with the portal and approved it in eisy? Instructions are in the document I linked in my first post. All programs may need to be opened and saved after migrating, along with any network resources. Follow instructions in migration document above. I would suggest getting these issues cleared up before worrying about scenes. Also, changing from Elk module to Elk plugging, all Elk addresses will need to be updated.

Hundreds of us have managed to migrate without issues. Maybe it is you who are misunderstanding the instructions? As I said in my post above, if you don't provide details no one here can begin to assist you. You didn't answer my questions from above, are you following the migration instructions? What firmware on the 994 are you migrating from? What specific issues are you having?

Hard to help without you providing details about what difficulties you are having. For starters are you following the instructions here: https://wiki.universal-devices.com/Eisy:User_Guide#Migration Be aware, to migrate from ISY994 to eisy, there are some minimum firmware requirements for the 994 that you must meet. Also, Elk module has been depreciated, you will need to move to the Elk plugin.

Verify the easy IP address with your router. Then click on the add button in the Launcher and add the IP address manually.

I would still suggest trying another power supply, and not POE.

In the meantime, you might want to try a new power supply.

As far as we know, eisy is it for the time being. It's a matter of what you are comfortable with. But I would suggest that you obtain a new USB PLM, to have as a spare just in case. Download a copy of the migration procedure from the wiki and read through it several times. Be sure to ask questions about anything that is not clear before hand. You didn't mention what firmware you are currently running. There are minimum requirements for migrating to eisy, so you might need to do some firmware upgrades first.

This definitely sounds like a nose issue especially given the location you have described. It has nothing to do with communicating directly. Use an extension cord from PLM to another outlet outside the electric room. Also, make sure you have the cable from PLM to ISY connected correctly. If you have another cable, try replacing the cable with the correct type cable.

Try plugging the PLM in to a different power circuit in case there is something on that circuit causing interference.

Short answer is the Plugin can do everything you are currently doing with the Elk module. You will need to update the programed address to change from the module to the Plugin. So there will be some manual work involved. While I do something similar, I do most of my programing in ISY/eisy because it is easier. There are only a few things that need input from Elk that is not already available via the Plugin and for those I use outputs. If you use outputs in the Elk, there would be no changes needed on the Elk when upgrading to eisy. The Elk just turns the output on/off and eisy will run the program based on the change in output state.

Try using Yolink and the Plugin for eisy control. Yolink has a solid 1/4 mile range.

If you follow the link to the manual and look at page 3, there is an illustration that shows you where the set button is. Continue on to page 7 for the written instructions.

Follow the directions in the owners manual: CONTROLLING OUTLETLINC FROM AN INSTEON CONTROLLER Linking an INSTEON Controller to OutletLinc To use OutletLinc as an INSTEON Responder, follow these steps to Link OutletLinc and a Controller together. Refer to the Controller’s Owner’s Manual for detailed instructions on how to properly install and Link it to OutletLinc. The following will work for the most common INSTEON devices: 1) Set the Controller to Linking Mode. (For most Controllers, press & hold an On or Scene button for 10 seconds or the Set button for 3 seconds.) You will have 4 minutes to complete the next step before Linking Mode automatically times out. 2) Press & hold the Set button on OutletLinc for 3 seconds The OutletLinc Status LED will flash once and then turn on solid The load will flash once 3) Confirm that Linking was successful by tapping the button you just Linked to on the Controller OutletLinc will respond appropriately See pages 3 and 7 in the manual. https://support.insteon.com/support-knowledgebase/2014/10/1/outletlinc-2011-owners-manual?srsltid=AfmBOorCsHzrWJgzvSi8VAcC6Tek-Ob3LpW9P6daxthYCt1Bv2SiuDjF

By app, if you are referring to the Yolink app, yes you need to install the app. The Yolink app is the way to interface with Yolink devices. You will also need it if you add the Yolink plugin to eisy/Polisy. The codes required for authorization come from the Yolink app.

I have a Yolink sensor installed on my metal mail box: https://www.amazon.com/Universal-Contact-Closure-Assistant-Security-Required/dp/B08P1VQMCR/ref=asc_df_B08P1VQMCR?mcid=b0c7c452897c36e98dc5936b3338999c&hvocijid=1587467274128929744-B08P1VQMCR-&hvexpln=73&tag=hyprod-20&linkCode=df0&hvadid=721245378154&hvpos=&hvnetw=g&hvrand=1587467274128929744&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9004510&hvtargid=pla-2281435179058&th=1 Long range and long battery life. There is a plugin to bring it in to UD infrastructure.

You need to delete Java files (all three boxes) and download a new start.jnlp from UD.

Yes, the Rain Machine app continues to work, at least on Android. With the exception of Notifications. I reported this to them at the end of last year and they responded that because of changes to Android they needed to rewrite the Notification portion of the app. They also indicated they were working on it. However, so far there has not been an update and my inquiry last week has gone unresponded to. While I never used the plugin for Rain Machine, remote access still works (without a subscription), but you need to open a port in your router.

You need to open a support ticket with UD.