Jimbo.Automates

It's not difficult, go to the PG3x UI, select the Elk node server -> Details -> Configuration page and enter the values as described in the help message. To Configure the ELK Nodeserver Custom Configuration Parameters Set temperature_unit to F or C Set host to the host or ip address and port, e.g. 192.168.1.15:2101 Set user_code, suggested to create a unique usercode for this NodeServer Set areas to the range of areas you would like to include Set outputs to the range of outputs to include Set change_node_names to true makes ELK the source of node names so if they are changed then ISY names will be changed to match. Set light_method to ELKID to check for ELKID=n on ISY Nodes, or ELKNAME to check if the Elk Light Name matches and ISY Node name or address. ELKALL This creates an ISY Light node for every definded Light node on the ELk ELKID This works by right-clicking on a node in the ISY and adding a note with "ELKID=n" where n is a unique integer After changing to ELKID method, you must wait until you see "Export Completed" warning message in the Log. Then click on the "export" like provided below If you change an ELKID on a node then you must restart the nodeserver for it to be seen. ELKNAME This attempts to match the name of an ISY Node with the Name of an ELK Light node to control. The table on this page will show the matches. NONE No need to control ISY lights from your Elk Note that if you remove an Area, it will not be removed from the ISY or Polyglot. This is intentional just in case it's an accident and your scenes or programs reference the nodes. If you change light_method from ELKALL to another method, the Light nodes will not be removed. You can go to the Nodes Page in the Polyglot UI and delete leftover nodes from changing ranges or light_method using the X to the right of the node. Ranges A range can be comma seperated to include just those numbers, or seperated with a dash to include numbers in between. For example 1-3,5,7-8 will be 1,2,3,5,7,8 All ranges start at one just like the numbering the Elk uses.

It's just the PIN, you can use your personal PIN but it's recommended to create a new user in ElkRP2 with it's own PIN. You will know it's actually working if you can arm/disarm the system in the Admin Console.

I reviewed the log package you sent and see no issues. When you said "ELK Log" I assumed you meant the ELK node server log. I'm not sure why the ELK would give an Invalid Credential because the node server doesn't send username/password, it connects to the non-secure port where that is not required. Again, the node server log looks fine, please let me know what issue you have with the node server.

Please download log package from the PG3 UI ELK node server page and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

This should not be the case, the response should be very quick. Every report of this has always turned out to be another issue. First what PG3x and IoX version are you using? Then watch the Admin Console Event log, and the node server log while triggering the action to see if the delay is on the IoX side or the PG3x side. You may need to submit a support ticket to have them view your system.

1. Will need @Javi to help with that issue. 2. This is not a user_code issue. Did use the non-secure port of the ELK when entire host?

That looks good, continue on with the instructions.

Those errors indicate the install is corrupt. This is a known issue that happens with PG3, please upgrade to PG3x.

Is 10.0.0.xxx the IP address of your ELK? These warnings are because you set it to ELKNAME and you have an ELK light name 'all bathrooms' which doesn't match a ISY node name. 2023-10-07 22:18:02,033 ELK-3286 udi_interface WARNING Controller:sync_complete: ELK Controller: No node address or name match for 'all bathrooms' Sent from my Pixel 6 Pro using Tapatalk

UDI is adding epoch time as a driver so it will be more useful soon. But yes I could add seconds or minutes since the last update as well. Sent from my Pixel 6 Pro using Tapatalk

I don't understand what this has to do with the Notification node server, it has nothing to do with location services. What location services method are you using? UD Mobile or ?

Do you have the Harmony Hub IP address reserved so it doesn't change? Please restart the nodeserver and it should find the correct one, and reserve it in your router so it doesn't change.

Please download log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

If it has shown disconnected or failed then please download log package and PM it to me. Not sure why it would not work in a scene it's very reliable for me. Put log in debug + modules mode activate the scene a couple times and download log package and PM it to me and mention what device is not working. Sent from my Pixel 6 Pro using Tapatalk

Please download log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

Ok, that is odd. Shouldn't be necessary but glad it's all good. Sent from my Pixel 6 Pro using Tapatalk

Oh that's good! A full reboot of eisy/polisy, PG3 or the node server?

Looks like it doesn't know what type of device that is, it should show the device type next to where it shows n006_xxx - Check the node server log for ERROR and WARNING. The next enhancement I'd like to work on is making errors show up as notices on the PG3 UI, just ran out of time to do that.

@Chris McKean, @mjrush, my bad. You actually have the 3.1.0 but it just displays the wrong version. Re-install in the same slot and it will now show the correct version.

Fixed in 3.1.0

The Polyglot Version 3 Node Server for Kasa TP-Link 3.1.4 is released. See the Release Notes for all information. IMPORTANT: You must have the latest updates released 12/03/2023 for this to install. If you are not sure, please 'Update Modules' and reboot when complete before installing. Thanks to @Michel Kohanim for the fixes.

I have 60 disabled programs so going thru and finding them all is very painful. I just upgraded to 5.7.0 last night and all programs were disabled, so I restored my previous backup.

Unless I'm remembering wrong, the problem was the version of PG3 didn't support it. But it should all be working now. I'll try to confirm this weekend. Sent from my Pixel 6 Pro using Tapatalk

There's a configuration param change_node_names set it to true and restart the node server. Sent from my Pixel 6 Pro using Tapatalk

Sorry, which node server? Sent from my Pixel 6 Pro using Tapatalk