DennisC

Very unusual, suggest asking for status by replying to each ticket.

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.

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

Did you download a new version?

Here are some links for you: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification https://www.jimboautomates.com/pg3-node-servers#h.h1ph1aotljg6

Suggest checking out Nodesserver plugin and Pushover. Changed over several years ago and haven't missed any delivery times yet.

Definitely try @IndyMikesuggestion.

Have you tried rebooting?

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.

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.

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.

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.

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.

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.

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.

I would suggest asking UD this question via a support ticket.

It is great that you test your back up. One other thought, does your back up ISY also have the Elk Module installed? If I remember correctly, the Elk Module is no longer available for purchase.

Well, the 994 is no longer supported by UD. If UD assistance is required for a problem, you will need to pay for it. There will be no further development work done for it, so no firmware updates or new features. Currently, there are some new devices that will not work with the 994. If your existing unit fails and needs to be replaced, how inconvenient will it be to not have your automation working for a week or two? (I realize you said you have a spare ISY, but do you know it works?) From my perspective, I would rather plan a replacement/upgrade rather than have to do it on an emergency basis. Also, UD is offering a 15% discount right now. As for needing to update programs, including Elk, yes there will be some of that. However, if you copy all programs to clipboard and then paste to a document file, you will have a good reference to simplify the task. Are you still using the old Elk Module, or are you using the Elk plugin? At some point, UD might be shutting down the Elk Module since support has ended. If you are not using any plugins, a lot of new features have been added via plugins. Once again, I would prefer to do this as a planned activity. Only you can answer what is best for you.

What UD device are you running? Native notifications via email to text have been unreliable. Using the Notification plugin makes it more reliable. Add Pushover to the mix and you are rock solid. Check the wiki and UD plugin store for more information.

In the admin console, the Sensibo plugin allows for setting the target temperature in either Fahrenheit or Celsius. In UD Mobile, the Target Temperature displays in Fahrenheit, which is the setting utilized within the Sensibo app. However, the drop down for "Set" command in UD Mobile only allows for Celsius. A reboot of eisy does not make a difference. Is this an issue with the plugin or UD Mobile?

Not sure what you mean by matter dongle since UD doesn't offer Matter yet. If you are referring to UD's Zwave dongle, then yes, you make a Zwave backup, followed by an admin console backup. Save the file and you can then restore it to your eisy or a new one.

Sorry, I missed that. It's possible the PLM is failing.

For clarity, are you saying you can not change the armed status using the Elk plugin once the system is in an armed state, without disarming first? If so, that is correct. It is a behavior I reported sometimes ago and I believe it is listed in the open issues list.

Have you tried a new power supply? Just because the light is on doesn't mean it meets specs and failed power supplies are somewhat common.

The simplest solution would be to create a no cost Gmail address and use that just for sending messages from eisy. You will need to create an app password. There are instructions in the wiki. The best solution would be to use the Notification plugin along with Pushover. Check for more information in the Notification plugin write up.