
DennisC
Members-
Posts
2838 -
Joined
-
Last visited
Everything posted by DennisC
-
Error404 when trying to load any plugin from the PG3
DennisC replied to FarmerGeek's topic in Polyglot v3 (PG3x)
Here is one more on the Elk plugin: https://docs.google.com/document/d/19uqu-jYmgxrkhhxn9YYeALRhC8mVBK2F0L589g-YU28/mobilebasic -
Error404 when trying to load any plugin from the PG3
DennisC replied to FarmerGeek's topic in Polyglot v3 (PG3x)
You would need to create the programs on your eisy, using the names of your devices. It sounds like you are asking for basic information, like how to create a program? If so, I am providing links for various resources on how to get started with UD's systems. The documentation may be for the ISY994, however, the main principles are the same. https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cookbook https://wiki.universal-devices.com/index.php?title=Main_Page#Complete_and_Comprehensive_User_Guides https://wiki.universal-devices.com/Main_Page -
Error404 when trying to load any plugin from the PG3
DennisC replied to FarmerGeek's topic in Polyglot v3 (PG3x)
Glad you got in. Go back to PG3, Plugin Store, Elk, and then click on "more info" button. That will take you to GitHub and plenty of examples on how to use the Plugin. -
Error404 when trying to load any plugin from the PG3
DennisC replied to FarmerGeek's topic in Polyglot v3 (PG3x)
It sounds like to me you are not logged in to PG3. Let's try this: In your browser type the IP address of your eisy followed by :3000 (xxx.xxx.x.xxx:3000). This should open up PG3. Login to PG3 using your eisy login info. Go to top menu and select IoX Configuration. If eisy is registered with PG3, you should see your eisy uuid number with a check mark (might be greyed out or lighter color). If that all checks out, click tab for Plugins Store, followed by Elk Plugin. -
Error404 when trying to load any plugin from the PG3
DennisC replied to FarmerGeek's topic in Polyglot v3 (PG3x)
Tried to load from where? Are you saying you received this message when you navigate to PG3x? PG3x is available by entering your IP address and port 3000. -
One other thought - In PG3x, on the Configuration tab of the Elk plugin, there is a small check box that needs to be checked, right under longPoll settings. It's called: "Allow ISY Access by Plugin". Do you have that box checked?
-
In your first message you indicated you had outputs appearing in the plugin, so I thought you knew to add new ones in PG3x Elk plugin Configuration. Go to PG3x, Elk Plugin, Configuration tab and you will see the help notes: To Configure the ELK Nodeserver Set outputs to the range of outputs to include Example: You should be able to create a program similar to this test program: Test F Key - [ID 0067][Parent 00B1] If 'Area 1 / Keypad 01 MB' is switched F4 Then Set 'Garage Light' On Else - No Actions - (To add one, press 'Action') You should be able to access the Keypad F Keys as per the screen shot below: If not, provide a screenshot of the available selections under "Condition" as follows: Control - Area 1(if that is what you use) - Keypad-Name (if keypads don't show up under Area, what does?) - choices in drop down box.
-
Not sure I understand what you are trying to expand? There is nothing to expand. When you click on the keypad in the left hand tree, the right side populates with 3 or 4 nodes - no different than a zone or Insteon device. When selecting the keypad, does anything show up on the right side? Did you restart the Elk plugin after creating the two outputs and did you remember to add them on the configuration tab of the plugin prior to restarting the plugin?
-
You can start by looking here: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#keypad-node More info here with examples: https://www.jimboautomates.com/pg3-node-servers#h.xscdgxvkku1o If you still don't see your keypads, try restarting the Elk plugin. If that doesn't work, try rebooting eisy. At one time, the F keys were not directly useable in programs, I don't recall if that has been added yet. The work around is to utilize Elk RP2 to have the keypad presses also operate a virtual output and have the eisy program work on outputs. Hope that made sense.
-
The 994 should have been powered down when you started to restore your backup on eisy. You should be following these instructions: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration
-
Typically, this can be corrected by rebooting ISY/Polisy/eisy.
-
If none of the above works for you, try this: 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
-
After deleting all three check boxes while clearing the Java cache, did you download a new start.jnlp from UD website?
-
You can start here: https://wiki.universal-devices.com/INSTEON_Signal_/_Noise_Troubleshooting https://wiki.universal-devices.com/INSTEON:_Troubleshooting_Communications_Errors
-
You should open a support ticket with UD before doing anything else.
-
Sorta sounds like the old Insteon All on event. ISY shouldn't activate devices on it's own. Plenty of info in the forum and troubleshooting wiki to dig deeper. If you are looking to update, easy is the most current and only available option.
-
If I understand what you want to do, all you need to do is start the IoX finder two times. The first time you start it, select your ISY994 unit and open the admin console. Start another instance of IoX finder and this time select eisy and login to the admin console. I do this all the time and everything works fine. As for migrating your programs, they should have come over during the migration process if the procedure was followed correctly. One thing of note, the migration backup is different than a normal ISY backup, so be sure to follow the migration instructions for making a migration backup.
-
I'm really confused, your saying you don't have zones but they are showing in your screen shot of the admin console. There are two areas showing, Basement & First Floor and both have zones showing. For example, Basement Area indicates no active alarm, Basement Mtn Ex Rm indicates Normal, Basement Mtn to Strs indicates violated, ect. If you click on one of the zones in the left hand tree, you will see more details about each zone. What is the issue? Your log now shows an active user code so you must have corrected something. Not sure what the screenshot of the Network Resource is about, why would you have a Network Resource to what appears to be Elk M1XEP?
-
Before downloading the debug log, make sure to go to log page, change to debug, and restart plugin. Wait several minutes before downloading log.
-
You can not have 2 connections open at the same time and have eisy update or issue commands. Only 1 connection can be used at a time with eisy. There is nothing difficult about it. Your previous post said the user code was incorrect. Now you are saying it was correct? Until you get the configuration correct, you will continue to have difficulty. Your previous Elk plugin log showed there was no working user code set. To move forward, post an updated Elk plugin debug log, screenshot of your plugin configuration, screenshot of Elk plugin Nodes page, and a screenshot of your eisy admin console Main tab, Network tree.
-
I apologize but I am still not clear on what you can not access. Are you having difficulty with IoX Launcher or opening admin console? Sounds like you first need to factory reset your dad's ISY, then restore your back up.
-
I PG3x, Dashboard, Elk, Configuration tab. All those settings need to be correct for your installation. This includes an active working user code. After updating be sure to hit save. That should be all you need to do now to get connected. Regardless to what Elk has indicated, currently the plugin to Elk can only be 1 connection. Although, that might change with the new interface UD is working on. Remember, for the changes to take affect, the admin console must be closed and opened after PG3x is updated.
-
Could you provide some additional information and clarity? What equipment do you have and what is it you are trying to do?
-
Correct My comment was intended to make sure you didn't have another connection open while troubleshooting this one. With the plugin, only one connection can be established at a time. As for your log, previous attempts up to around 17:00's were not connecting. Whatever change you made after that, as of 23:02, the plugin made a connection with Elk M1XEP - that's good. While the nodes appear to be in the log, the values are empty. From the Elk Dashboard within pg3x, to the left of the Configuration tab, there is a "Nodes" tab. Is there a number next to "Nodes"? Click on the Nodes tab and you should be seeing some node names. Are there any there? Within the admin console Main tab, under Network, do you see "Area 1" and "Elk Controller"? I see this in the log: 2025-07-13 23:09:50.865 ELK-82381 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:None elkm1_version:5.3.18 xep_version:2.0.48 remote_programming_status:0 system_trouble_status: temperature_units:None user_code_length:None type=<class 'elkm1_lib.panel.Panel'> cs={'elkm1_version': '5.3.18', 'xep_version': '2.0.48'} Back on the Configuration tab for the Elk plugin, are you still showing a value for user_code? If so, is the user code you entered here programmed in the Elk and can you use it to arm/disarm at the keypad?
-
You can only be in one of these at a time. Elk doesn't support more than 1 connection. Elk has nothing to do with UD or their plugins. That's because you are in the wrong location. You need to be on the Elk Plugin page - Log - Debug - Restart. Take a look at the attached mark up. Elk.pdf We will not be able to move forward without the Elk Plugin Debug log. If there is not an obvious error, you will need to tag the Elk plugin developer for his input. But first, we need to see what is in the log. Did you confirm the IP address of Elk M1XEP is correct? Also, go in to the M1XEP and on the TCP/IP tab, make sure there is a check mark next to "Enable Non-Secure Port" and the port is set to 2101.