Jump to content

DennisC

Members
  • Posts

    2742
  • Joined

  • Last visited

Community Answers

  1. DennisC's post in Getting started with Ployglot was marked as the answer   
    You can start here:
    https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Node_Servers
    and here:
    https://polyglot.universal-devices.com/
    The last link will list available node servers. If you click on the name of the node server, followed by more information on the next screen, you will get detailed information on most of the node servers. Sometimes the link doesn't work and you have to hunt around.
    As of now, you need to be on Polisy or eisy to use the current list of PG3x Polyglot and node servers. Previous versions are depreciated.
    Look in the wiki for information on how to access Polyglot for your platform.
  2. DennisC's post in ISY994 ELK program migration to EISY was marked as the answer   
    @Geddywas spot on with his advice. Document your programs before you start, including disabled programs.
    Be sure to follow the migration instructions completely. Make sure you are on the latest firmware for each system before you migrate and remember, there is a minimum firmware you must be on to migrate an ISY. You don't state what you are currently running.
    Makes no difference if you convert to the Elk node server before or after moving to eisy. However, there will be some manual intervention required once you migrate to eisy. So if you change over to the node server before migrating, you will need to complete manual work twice.
    Most importantly, read and follow the instructions and ask questions if you don't understand something before doing that step.
  3. DennisC's post in Z wave gone was marked as the answer   
    Did you back up Zwave and then make a migration back up in according to the following instructions:
    https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration
     
  4. DennisC's post in Third Reality Motion disconnects from IoX within a few hours was marked as the answer   
    I wonder if this could be related to the IoX slowdown bug that was recently discovered in 5.6.4.
    There was a patch, not a version upgrade released yesterday. Did you try installing that by running package update from admin console?
  5. DennisC's post in IoX disconnected was marked as the answer   
    You highlighted the error log that indicates to check your IoX IP address. Did you verify the IP address in PG3? 
  6. DennisC's post in Zwave no longer working...possibly after upgrade was marked as the answer   
    I would suggest you start by powering down, waiting a bit and power up again. After about 30 minutes, check your Zwave device. If there is no status, try a query.
    Also, make sure Zwave is enabled on the Configuration tab of admin console.
  7. DennisC's post in Finally ready (I think) to migrate to Polisy from5.0.16C was marked as the answer   
    Yes, the migration will only work using firmware 5.3.4 or above and only with the series 500 ZWave board.
    Your options are to find a used 500 series board, or start fresh on your Polisy.
    You might want to consider upgrading your ZWave dongle to UD's new ZMatter dongle. This way you would be up to date and prepared for ZMatter devices.
  8. DennisC's post in Upgrade Polisy from v.5.4.3 to 5.5.9... Taking forever? was marked as the answer   
    If it has been over 4 hours and you still can not access the admin console, then I would suggest using the multi function button.
    You could try upgrade packages or reboot. Upgrading packages will bring you to the latest version available, which would be v5.6.2.
    Update and Upgrade All the Packages
    Click the button once. Please consult support before updating this route. See link below for suggested update/upgrade process.
    Please see this important update (July 2022)
    Safely Reboot
    Click the button twice.
    Safely Shutdown
    Click the button three times.
    Be aware, after upgrading you will need to completely clear your Java cache and download a new start.jnlp, which when you run will place the IoX Launcher on your desktop.
    https://isy.universal-devices.com/start.jnlp
     
  9. DennisC's post in question - what is Install Dev Packages was marked as the answer   
    Install Dev Packages is used to install packages required to develop node servers.
  10. DennisC's post in "A Reboot of the system is required to complete the system upgrade." (how do I do that?) was marked as the answer   
    Go to the admin console of eisy/Polisy, configuration tab, reboot.
    It is no longer possible to just restart PG3(x).
  11. DennisC's post in Ok - so I'm an idiot was marked as the answer   
    Go to and log in:
    https://my.isy.io/index.htm
    Find your device in the list and click on Select tool - Information - ISY Information
    Copy the full URL address listed next to: Admin Console URL:
    Back on your desktop, start the IoX Launcher
    Select Add
    Paste the full URL address copied above from the portal and hit OK
    This should list your device with the portal access URL. To access, click on the portal access URL instead of the local address. Note: When you log in via the portal, you must use your portal credentials and not your device credentials.
    If you want, you can click on Save in the IoX Launcher to save the file of Launcher URL's in case it is returned to default during an upgrade.
  12. DennisC's post in Portal license renewal issue was marked as the answer   
    Are you renewing according to these directions:
    https://wiki.universal-devices.com/index.php?title=ISY_Portal_Renewal_Instructions
     
  13. DennisC's post in Admin Console not Responding - PC version was marked as the answer   
    What platform are you running on, Windows or Mac?
    Just as a guess, try clearing your state files:
    Admin Console Minimized/Invisible and Cannot be Restored
    This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.state or ud_*.state file patterns:
    ud_finder.state udi_finder.state udi_frame.state udi_launcher.state udi_pgm.state udi_tree.state There are some other causes for this, read about them here:
    https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Finder_does_not_find_ISY
  14. DennisC's post in ZMatter antenna assembly? was marked as the answer   
    I have attached the instructions for installing the USB ZMatter dongle.
    Here is the link for migration instructions:
    https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration
    Read through the instructions, it contains information for ISY994 & Polisy migration and for eisy.
    Let us know if you have any other questions.
     
    ZMatter-Assembly- Instructions.pdf
  15. DennisC's post in Upgrade Packages Went From 5.4.5 to 5.6.0 was marked as the answer   
    Tell us more about your system, what ZWave dongle are you using?
    Firmware version 5.4.5 had a bug that caused the upgrade packages function to get stuck in a loop. 
    If you know how to ssh in to Polisy you can verify this is what is happening. If you don't know, you best wait for UD support.
    To verify, ssh in to Polisy and type:
    sudo uname -a
    Post the output here, this will provide the package information.
    Next, type:
    sudo tail -f /var/udx/logs/log
    Then press the multifunction button one time and watch the ssh log you previously started. Check the output to see if the same entries keep repeating.
  16. DennisC's post in IPhone Apps for Eisy was marked as the answer   
    Yes, the best one is created by UD and it is called UD Mobile.
    https://wiki.universal-devices.com/index.php?title=UD_Mobile
     
  17. DennisC's post in ZW nodes remaining after migration from Zooz to Zmatter was marked as the answer   
    The node addresses should have updated to ZY, but the node names may need to be updated manually. All Zwave nodes on UD's ZMatter dongle should be ZY.
  18. DennisC's post in Cannot find Eisy in the IoX Picker to load the console was marked as the answer   
    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
  19. DennisC's post in Changes in Notification Variables was marked as the answer   
    I'm not clear why you are reporting on variables if the ZWave device reports status in the admin console? Why not just use that value in your notification?
    In either case, you can determine the values and property id of ZWave devices from the command listed below. Just type the command in your browser, replacing x's with your IP address & the main node address with the main node in the admin console (as shown in the example below):
    https://xxx.xxx.x.xxx:8443/rest/nodes/n001_81668
    You can also find all info by right clicking on the node in the left hand tree of the admin console and selecting Xray, in the next window select Node Info, and then Go.
     
  20. DennisC's post in Having trouble installing was marked as the answer   
    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.
  21. DennisC's post in Only 1 Node When Elk Node Server Added to PG3 Dashboard was marked as the answer   
    To add to what was posted above, double check you have Configuration completed correctly.
  22. DennisC's post in eisy send message to Elk Keypad cutoff on text was marked as the answer   
    Try showing your message on two lines in the body of your custom notification like this:
     

    The From and Subject should be empty.
  23. DennisC's post in Eisy connection to PLM was marked as the answer   
    If you have a USB PLM, just plug it in. If you have a serial PLM you need a cable like this:
    https://www.universal-devices.com/product/serial-plm-kit/
     
  24. DennisC's post in Migrated from ISY to Eisy. How do I make eisy program push F# button? was marked as the answer   
    There is an open issue regarding this. Currently, you can only trigger a program via function keys based on Status of Last Key.

    You can read more about it here:
    For now, a work around is to set an Elk output when a F key is pressed and then run the program when the output turns on/off. As described here:
    However, in your case, you are looking to press a F key to have Elk speak, but I would ask why do it that way?
    Why not just have the Elk node server tell Elk to speak the words?


  25. DennisC's post in 994 and PLM Status After Upgrade was marked as the answer   
    Factory Reset ISY
    Use a sharp object to push in the Reset Button till the RX, TX, Mem, Error lights start blinking (every second)
    Hold for at least 30 seconds until all of the the RX, TX, Mem, Error lights turn off and Mem light starts flashing quickly
    Release and wait for system reboot (reboot is complete when Mem light stops flashing)
    Factory Reset PLM 
    Remove PLM from power for at least 10 seconds. Press the black set button and continue to hold it while you insert it back into the 120 VAC power.
     
     
     
     
     
×
×
  • Create New...