DennisC

From the directions: "If you change a Elk object name it will not be automatically reflected on the ISY (currently). You will have to delete the node in the Polyglot UI Node's page for the node server, then restart the node server." You will also need to restart the admin console.

ouch

When I first migrated in early March, when the factory query ran some of my UD Mobile notifications were being triggered. This was corrected after the first upgrade. As it always done this since you migrated or is this something new? Have you rebooted recently?

Follow the instructions here exactly: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

Let us know if you experience any additional unexpected reboots and be sure to check logs.

Not sure what you have tried or what part of the instructions you have questions about? Here is the setup instructions: Setup User needs provide username and password used for the Blink App. A one time/2way authentication may also be needed. In the case of 2 way autenticantion. Obtain the code using the Blink app and enter the data under configuration The user must specify the sync unit(s) where the cameras are registered - A comman separated list is ok if more than 1 sync unit is being used. If no sync unit is used specify NONE Note, the API does not handle special characters in the camera and sync names - please remove/rename those before setting upthe node ShortPoll is heart beat from controller node, LongPoll updates data. Do not run update too often, as system may get throttled by Blink - Suggested to be more than 60sec between updates Still to be done I only have 3 camera types - Mini, doorbell and Outdoot (new) - I do not know the older camera's name. If you have those please enable debug and click update camera and provide log file and I can update this Plan is to add ability to send pictures of emails/videos taken.

You should be on the latest firmware. Upgrade to v5 6.0 and be sure to clear Java cache and download a new start jnlp to get a new Launcher to access the admin console. Try looking in the event viewer around the last time of your reboot to see if there is any info.

Great & thanks for updating us.

Do you know what firmware version you are running on your eisy? Have you rebooted eisy after the last upgrade? What version of PG3x are you on? It should tell you on the bottom of the initial PG3x screen. Your eisy should be on v5.6.0 and PG3x should be on v3.1.25. If your are on these versions, try rebooting eisy by 5 presses of the multi function button. If you are not on the most current versions listed above, try updating by 1 press of the multi function button. After eisy restarts you should clear your Java cache, including checking all 3 boxes when you delete files, and download a new version of start.jnlp. Run the downloaded file and you will get a new IoX Launcher on your desktop. After confirming you can get in, reboot eisy one more time by pressing the multi function button 5 times. Then check on PG3x again, if you were not on the latest before, you should see a note that PG3x needs to be restarted. You can do that from the System tab.

Try going to the tab in PG3x that says Node Server Store. When the list comes up, look for the node server in question in the left hand column. Click on the name of the node server, and if you have successfully purchased the node server, you should see a line that indicates version, price and under Purchase column there should be an Install button. When you click on install you should be able to select a slot. Also note, if the node server was already installed, half way done the page there should be a button that sats Reinstall here? next to the slot the node server is already installed in.

Before beginning the migration also make sure your eisy is up to date with the latest firmowhich is version 5.6.0. Make sure you follow the . migration instructions.

What firmware and UI are you on?

Glad you are up and running.

Are you using the IoX Launcher? Clear you Java cache being sure to check all 3 boxes to delete. Then download start.jnlp from here: https://isy.universal-devices.com/start.jnlp Click on the downloaded file to run it. The IoX Launcher should be added to your desktop. The IoX Launcher should automatically find your eisy, if it doesn't, click add and enter: https://eisy.local:8443/desc If that doesn't work, check your router for the eisy IP address and click add in the Launcher and enter: https://xxx.xxx.x.xxx:8443/desc Replace the x's with your eisy IP address. If you are still having a problem try the troubleshooting steps here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy

Read through the post here: Does this sound like a similar issue?

According to UD, they eliminated the ability to use static IP addresses in eisy because of the overwhelming support calls for issues that were traced back to the use of static IP addresses. It can work fine and then all of a sudden it causes issues. Can't think of any reason to continue with static IP when DHCP reservations in your router take care of the same function but without the potential for problems down the road.

When you use a static IP address with the ISY, strange things can happen. The preferred thing to do, and what UD recommends, is to enable DHCP in ISY and then make DHCP IP reservation in your router. That way, your router will assign the same IP address to your ISY. The wiki has the instructions for setting up the ISY in this manor.

Make sure your UI & firmware match. Did you clear your Java cache and download a new start.jnlp, which after running will install a new IoX Launcher on your desktop. After migration, you may need to go to each program, check it for errors or missing info and then save the program.

It was latter upgraded to 2A and if you decide later to use UD's ZMatter dongle, you would want the 2amp power supply. It won't hurt to use the 2 amp now, and you will be prepared. The load will only draw what it needs.

I know you indicted you followed all of the troubleshooting steps, but to double check, have you followed these steps from the wiki: 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. Cannot find Valid Java Home This issue usually happens on Windows and when you have had multiple versions of Java installed especially the older version. What you need to do: Clear your java cache Uninstall all versions of Java using the Control Panel | Add/Remove Programs Delete these directories (if they exist): C:\Program Files\Java C:\Program Files\Oracle C:\Program Files(x86)\Java C:\Program Files(x86)\Oracle C:\Program Files (x86)\Common Files\Java C:\Program Files (x86)\Common Files\Oracle Open Search or click "Windows/Start" button: In the search box, type Environment and choose Edit the System environment Variables Click Environment Variables Under User variables for <username> Click on the Path | Edit and then delete all occurrences of Java and Oracle If you see JAVA_PATH, click on it and then click the Delete button Under System variables Click on the Path | Edit and then delete all occurrences of Java and Oracle If you see JAVA_PATH, click on it and then click the Delete button Click the OK button (3 times to get out of "System Properties") Reboot your computer Reinstall Java 64bit version If you were running the 32bit (x86) version of Java you might need these additional steps after reinstalling Java 64bit version: Open Search or click "Windows/Start" button: In the search box, type Environment and choose Edit the System environment Variables Click Environment Variables Under "System variables" Click "New..." For "Variable name:" type JAVA_HOME (ALL CAPS) For "Variable value:" enter the directory for your new Java install Example: C:\Program Files\Java\jre-#.# [NOTE: #'s will be current version just installed] You can click "Browse Directory.." to find the directory or type or paste it in the entry field. Click OK Find "PATH" (still under System Variables) Click "Edit..." Click "New" Enter: %JAVA_HOME%\bin Pay attention to CAPS Click "OK" (total of 3 times to exit "System Properties" Reboot your computer To confirm Java is on the system start Command Prompt or PowerShell and type java -version. You should get a result similar to: java version "1.8.0_371" Java(TM) SE Runtime Environment (build 1.8.0_371-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.371-b11, mixed mode) IoX Launcher should be able to launch correctly every time now. If you still have issues please file a support ticket. Windows should update these entries as Java updates, but should you have issues you might need to update the JAVA_HOME directory above.

And the Polisy power supply is 12V 2A.

Do they show up directly in the wireless tag hub via cao tag website?

Then why do you have a run time in program A? You need to clearly list all of your requirements to get help. Right now we are guessing at what you want. It also helps to post both programs by right clicking on program and selecting copy to clipboard at the bottom of the list. Paste the results here.

To add to what was posted above, double check you have Configuration completed correctly.

Sounds more like a Java issue then a UD issue. Roll back to previous version of Java until it is squared away. If a restore point was created prior to upgrade it should be easy to go back.