Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

DennisC

Members

Everything posted by DennisC

  1. Maybe I am forgetting something. When I first set up my ISY994, my lighting was imported in to my ELK M1. I don't remember if this was a manual operation, (some toggle button?) or done automatically. When I started using the Elk Node Server, all that lighting was imported back to the Node Server without user action. I don't see a way to delete these nodes, either in the Elk Node Server, or M1. In the M1, there is a column for "Show" and the description for this says " An X under "Show" means that device will be visible on the keypad and other user interfaces." I might be able to remove them from the Node Server by unchecking "Show", but never tried that, as I didn't want to break something.
  2. Are you on Polisy/eisy? On PG3, if you go in to the node server, where the command buttons for the node server are. There should be a button to Stop the node server and then there should be a button to Delete the node server. Just make sure you select the node server in the slot that is not working. If Delete button doesn't work, I think you will need to reach out to Bob.
  3. DennisC replied to mjrush's topic in IoX Support
    Make sure the battery devices are awake when you do the exclude/include procedure. Check the manual for the device, sometimes there are specific procedure for keeping the battery device awake for exclude/include.
  4. Are you on eisy? Which version of PG3 are you running? Some versions had trouble updating/update available message. The latest version 3.1.23 for eisy was suppose to correct the issue. I haven't seen this issue on Polisy's PG3 and I am on v 3.1.18, which I think is the latest. In some instances, to get the update, reinstalling in the same slot worked. In other instances, you had to remove the node server and then reinstall. Be carful, if you do this, you will need to setup the configuration page again.
  5. Are you able to just reinstall the node server in to the same slot? When you click on install there should be an option located about mid page to reinstall in same slot.
  6. At the least, may be you could add a toggle to the configuration page of the node server to disable adding the Elk lighting nodes? Programing in the admin console is so much easier.
  7. Jim, I for one would welcome the change. Have those extra lighting nodes listed under the alarm zones can be confusing, especially for my wife.
  8. You could try using UD Mobile instead. As a former Mobilinc user, UD Mobile is a much better app. It's eisy to customize and very quick to connect. As part the process of setting up a node, you get to choose what verbiage is displayed and can set colors for different states. It also interfaces to the portal seamlessly. I There is no charge and it requires a minimum firmware of v5.016. https://wiki.universal-devices.com/index.php?title=UD_Mobile
  9. I don't use a Mac & you may be required to update Java before the Launcher will work, depending on how old your version is. You can try opening Java Control Panel and going to the security tab. There should be a section called "Exception Site List". Add the IP address of your ISY to this list and click OK. This should skip the security block for this address. If this doesn't work, your Java might be outdated.
  10. Download and run this file and it will add the Launcher to your desktop. https://isy.universal-devices.com/start.jnlp
  11. I believe those are two separate errors. Resetting PLM should not trigger the message you received. I would suggest checking the error log. As an aside, sign in to portal and see if ISY is on line.
  12. I have experienced the same thing on v3.1.22, several times, that's why I repeated my comment. Yes, however, after running update packages from the admin console on eisy, you need to log in to PG3 and look for a message indicating PG3 needs to be restarted. Then you restart PG3 from the menu, upper left side. The current version of PG3 for eisy is v3.1.23, therefore, you should update. I have not experienced the login issue on the latest version of PG3.
  13. Thanks! I sent you an email with the links. You had most of what that site had available for weather, but I found a few more scattered around that might substitute for weather conditions.
  14. Did you try removing power from eisy, waiting a beat, and starting eisy back up?
  15. @Javi, When time permits, would you think about adding some additional weather related icons (wind, thunderstorm, various degrees of rain [light, heavy], ect)?
  16. If you really want to know which version you have: Identifying 300 Series Z-Wave™ By The Protruding LED The 300 series will have an LED protruding out of the rear of ISY and may have an antenna mount as well. Identifying 300 Series Z-Wave™ By Version From the Admin Console select the Z-Wave™ menu at the top of the screen. Select Z-Wave™ Version. If the version is 4.55.00 the ISY has a 300 Series Z-Wave™ dongle. If the version is 6.81.00 the ISY has a 500 Series Z-Wave™ dongle.
  17. It's not doing any harm in staying there. Providing you migrated your portal license, or if you find a new home for your ISY, you can delete it by clicking the red X in the first column on that line. Since it is at end of life and support is due to end soon, there is no real value to it, but it's possible someone here might be interested in it.
  18. What you are seeing is correct. The password to login after the portal login is your eisy login. If that doesn't work, make sure its not a browser cache issue by clearing your browser cache. If that doesn't work, I have found removing power from eisy, after a proper shutdown, helps.
  19. The only other suggest I can offer is have you looked in the node server log and PG3 log for errors? IF that doesn't help, I would suggest tagging the node server developer for help.
  20. After installing a node server, it needs to be configured in PG3. It is possible your previous configuration settings were lost in the upgrade. Check under the Configuration tab for the node server in question and compare what is required in the help text to what you have configured to insure all is correct. Did you have the admin console open during the upgrade, if so, you must close the admin console and restart it for the changes to be shown. While I don't use this node server, I found the following instructions in the readme file: Installation IMPORTANT: The latest harmony hub firmware broke access, you must manually enable xmpp for each hub in the Harmony App: https://community.logitech.com/s/question/0D55A00008D4bZ4SAJ/harmony-hub-firmware-update-fixes-vulnerabilities Connect to one of your Hubs in the Harmony App Select Menu -> Harmony Setup -> Add/Edit Devices & Activities Select Remote & Hub -> Enable XMPP Do this for every hub. Make sure your Harmony Hubs have a static IP assigned. The nodeserver can not re-find the hub if it changes IP addresses. This may be fixed in the future. Backup Your ISY in case of problems! Really, do the backup, please Go to the Polyglot Store in the UI and install. Add NodeServer in Polyglot Web Open the admin console (close and re-open if you had it open) and you should see a new node 'HarmonyController' The auto-discover should automatically run and find your hubs and add them. Verify by checking the nodeserver log. If it doesn't then Select the HarmonyController node and click the 'Discover'. While this is running you can view the nodeserver log in the Polyglot UI to see what it's doing This should find your Harmony Hubs and add them to the ISY with all devices and activities if your Harmony Hub and Polyglot are on the same subnet. If they are not, then you can manually add the hub address as described in the next section, Once all nodes are added you will need to close and re-open the admin console the new custom profile is loaded.
  21. Did you confirm the configuration for the node server is correct in PG3. Did you try selecting the Discover button on the page in your screenshot and then close and restart admin console?
  22. Try creating a program that queries the device in question and have it run at startup. Place a wait of several minutes before the query. That will give the Polisy a chance to complete start up.
  23. Glad you got it working.
  24. Not sure I fully understand what you are saying. Even a disabled device would show up in UD Mobile. Are you saying a disabled device was not showing up and when you enabled it, it still didn't show up? What kind of device, Insteon or Zwave? You could try rebooting Polisy and after the restart, syncing UD Mobile again.
  25. Assuming when you say ISY, you are referring to an ISY994 unit. What firmware did you upgrade to and did you download a new copy of stat.jnlp after clearing Java cache? ISY firmware has not been updated in some time, so know what you started with and what you upgraded to will help us help you.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.