Everything posted by DennisC
-
Network/server error logging into MyQ service
You can keep as many controller's as you like. At GDO, the wires from pushbuttons and controller's are all spliced together. The pushbutton can be dedicated to the GDO, or it can be an actively used button. This method is not dedicated to ELK, the same solution can be used by any ISY ecosystem device by adding an Insteon or Zwave contact closure switch or relay.
-
Support Thread for: IoX 5.7.1 (Nov 12, 2023)
Sounds like it might be time to open a UD support ticket.
-
Using Notification Node Server & Pushover together?
As a stand alone, the Notification plugin is great for short messages, as is UD Mobile. For longer or customized messages, Pushover shines. Have you seen the instructions page here: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md and here: https://www.jimboautomates.com/pg3-node-servers#h.h1ph1aotljg6
-
Light Goes To 100% Even When On-Level Say 25%
Try factory resetting the device and then add back in.
-
T-Mobile texting from Eisy Program
That is an indication that either the configuration is not correct or the carrier is delaying or blocking the text. It is why a lot of us switched to the plugin. Add a service like Pushover with it and you will be very happy, there are a lot of options available.
-
T-Mobile texting from Eisy Program
On the screen you setup the phone number, doesn't the test button send a test notification?
-
T-Mobile texting from Eisy Program
A quick search shows that is the correct format for TMobile. eMail to text has been very unreliable at times for many carriers. Sometimes using a dedicated email account with Gmail has helped. Instructions are in the wiki. However, for fast reliable notifications, if you are setup to use plugins, try Notification plugin. It is fast and reliable. Combine it with Pushover and you will not miss your text capabilities.
-
Moving to a new house - what steps should I take with Portal?
At one time, I had 3 UD devices on one portal account with no issues. However, they were all located in one house. For my vacation home I elected to use a second account. It makes organization and management easier. Since your existing ISY is at end of life with no free support available, I would not suggest trying to reuse it. Upgrading to eisy and disposing on the 994 is your best option for less headaches.
-
Troubleshooting and logs
Another approach would be to use the find and replace search capabilities and search for programs and seems that have that device in it. Check wiki for details. You can also right click on the program that turns device on and select status. That will take you to the detail page and look at the last time the program ran. If not at the time of turning off, then check for what might have run at that time.
-
Totalconnect node frequently showing failed and immediately reconnecting
Assuming you are on PG3, go to System Tab and select reinstall all plugins. This will upgrade Python Interface. You want to be on 3.2.6 or greater. You can check this after the reinstall by restarting any Plugin and checking the first few lines of the Plugin log for Python Interface log.
-
PG2 still offered in Admin Console?
If I recall correctly, in a few days it will disappear. You might need to upgrade packages first. As long as you have access to PG3x, I wouldn't worry about it.
-
Failed Notification Followed by Connected at Midnight
If it is "stuck", sure looks like a network issue....
-
Failed Notification Followed by Connected at Midnight
This doesn't look like the private message window. At the top of the page, select the envelop icon, when you hover over it, it will say messages. Then select compose new and enter the recipients name.
-
Failed Notification Followed by Connected at Midnight
Could you be having network issues? If not, it might be a good idea to create a UD support ticket so they can identify what the issue is. You shouldn't have any issues sending a private message with the log zip files. What exactly is the issue?
-
Stuck migrating from ISY994 to eisy
Admin console is designed to work on Windows or Mac's running Java 8. anything other than that, is undocumented. You will need to ask UD if they know if it will work on what you are running, however, they might not know. As for what use to work, well there are a lot of things that fall in to that category. With changes and tighter security requirements, you can not assume what worked on a ISY994 will work on eisy.
-
Admin Console-No Z-Wave Backup
From the migration document: Requirements If you are migrating Insteon you must have a compatible PLM Eisy / Polisy supports these PLMs: 2412S, 2413S, 2413U, and 2448A7 If you have a 2413S (serial), you will need our Serial PLM Kit If you are migrating your Z-Wave Network, you must have our ZMatter Z-Wave USB Dongle If you are using Polisy, you can alternatively use our ZMatter Z-Wave Board for Polisy
-
Clearing old / phantom ZW devices from ZMatter dongle?
You would need to factory reset the dongle and start all over. Every time you attempt to add a device, successful or fail, the number increases by 1.
-
Zwave / Matter dongle and Kwikset ZW locks - some functions missing
Sounds like you need to generate a support ticket and request that functionality be added.
-
New EISY Can not set time
Have you cleared Java cache and download a new start.jnlp? You can also try power cycling eisy.
-
Stuck migrating from ISY994 to eisy
I'm a little confused as to your exact conditions, so let's start at the beginning. Assuming you are on a Windows machine with Java installed. Let's start by using the multi function button to check for updates - one button press of the button will upgrade packages. Wait at least 30 minutes and then press the multi function button 5 times to reboot. Before trying to access the admin console, wait at least 10 minutes for eisy to completely boot up. Access the admin console by using the IoX Launcher. Start by deleting your Java cache being sure to check all three buttons to delete all apps. Then download a fresh IoX launcher from here: https://isy.universal-devices.com/start.jnlp . Here are detailed instructions: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop Run the downloaded file and it will place an icon on your desktop that you will use to access the admin console. If IoX Launcher doesn't find your eisy, go through these steps: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy If you run into issues with any of the above try to describe what is happening and/or post screenshots, obscuring any sensitive information.
-
Migrate Polisy > Eisy
Everything you need is right here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration Should not be necessary, look in migration document above for migrating PG3. Should be able to submit a hellp ticket, explain what happened and request a refund.
-
UD mobile synchronization doesn't complete
Have you tried rebooting eisy? Might even try power cycling.
-
EISY Network Issue?
Have you done an update packages on the Configuration Tab, followed by a reboot? If that doesn't clear this up, try power cycling. The correct way to access eisy is from the IoX Launcher. Delete your Java files (all 3 boxes), and then download IoX Launcher from here: https://isy.universal-devices.com/start.jnlp After downloading, just click on it and it will put the IoX Launcher on your desktop. Do not unzip the file. According to your post, you have done all of this already. Have you cleared your browser cache? Or maybe try a different browser? You access Polyglot from the following: http://xxx.xxx.x.xxx:3000/ Replace the "x" with your eisy IP address. This is normal, don't worry about it.
-
Clear Queued Messages
That is what I am trying to understand. I just did a reboot, maybe that will clear it up.
-
Program Bug?
I would second trying what @Techman suggested above. Sometimes programs get confused and you just need to start over. I would suggest rebooting between deleting and recreating the program. Also, at least initially, use a slightly different program name.