Jump to content

DennisC

Members
  • Posts

    2761
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

DennisC's Achievements

Advanced

Advanced (5/6)

736

Reputation

70

Community Answers

  1. Very unusual, suggest asking for status by replying to each ticket.
  2. I don't think so, I think these files are UD default files - similar to "cookies". They seem to remember the setup. They will recreate themselves the next time you run the admin console after being deleted.
  3. Whenever you move back and forth between two monitors and one monitor, there is a display issue. You need to delete some files in between the move between monitors. The directions are in the wiki: 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
  4. Did you download a new version?
  5. Here are some links for you: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification https://www.jimboautomates.com/pg3-node-servers#h.h1ph1aotljg6
  6. Suggest checking out Nodesserver plugin and Pushover. Changed over several years ago and haven't missed any delivery times yet.
  7. Have you tried rebooting?
  8. As @IndyMike told you, the PLM address is not correctly written to your devices, or if everything worked correctly after the PLM swap, then the existing PLM is probable on the way out. How many Insteon devices do you have? Go to Tools - Diagnostics - PLM Info/Status. Does it show the PLM connected? Try checking the PLM Links Table under Tools - Diagnostics. If the number doesn't equate to the number of devices you have, then you have confirmation of what we are telling you.
  9. When you replaced the plm did you follow the procedure outlined in UD's wiki? The instructions call out the order of putting up devices and running restore plm and must be followed.
  10. Have you registered and approved your device (easy/policy) in the portal? Follow directions in wiki to add your device in portal and then approve in admin console.
  11. Unmanaged means pg3x doesn't know anything about that item and therefore can not manage or display information about it. It was installed outside of Polyglot version 3. Make sure your ISY (which machine are you using?) is connected to pg3x by going to the system tab. Edit - you can also try a power reboot.
  12. As @Geddy indicated, all you need to do is follow the directions: Enable PG3x: https://polisy.local:8443/rest/pg3x.enable Reboot and wait for a beep, then a second beep. While nothing will appear to happen, after the reboots you should be able to login to Polyglot and verify you are on pg3x. Afterwards, run upgrade packages from admin console and reboot when told.
  13. If I recall correctly, 170001 messages are informational and can be ignored. ISY is still the base of UD's platform. eisy is the hardware that runs the ISY system. If some programs are not running correctly, try rebooting eisy and see if it makes a difference.
  14. Make a Polyglot back up from pg3x and after your migration, restore the back up. However, some program manipulation may be required to adjust any changes to node names/addresses. Each program may need to be resaved after migration.
×
×
  • Create New...