Jimbo.Automates

After moving to the same subnet, run discover, then download log package and PM it to me. Instructions for manually adding should be on the node server configuration page.

Yes. You'll need to allow UDP discovery across the network if that's possible. There are also options to manually add devices or networks in the config, although those options have not been extensively tested. Sent from my Pixel 8 Pro using Tapatalk

If the name is changed to something besides the default, then updated in the Elk, and restart the node server then it should show up.

Not yet. The library I reference is working on support but not released yet. Sent from my Pixel 8 Pro using Tapatalk

Sorry for the delay in responding, I'm away from home. It doesn't make sense that the logical (ST) & physical (GV0 & DON) are 2 seconds apart. But, it's impossible to tell why. I would need to see the node server log in debug mode at the same time to see if it happens on the PG3 side or IoX side. Also, you didn't answer my other question, what IoX & PG3 version are you running.

By 2 way I mean does the sensibo or whatever option get confirmation back that the request was successful. Sent from my Pixel 8 Pro using Tapatalk

Is that 2-way communication or just one? Sent from my Pixel 8 Pro using Tapatalk

I'm having a mini split install in a garage, no choice on brand because I must use what the installer will support and there aren't many local reliable installers. So if that works with mine I'll be creating one ASAP. Sent from my Pixel 8 Pro using Tapatalk

Yes, it sends DON/DOF. Sent from my Pixel 8 Pro using Tapatalk

The Polyglot Version 3 Node server for ELK Security Version 3.10.3 is released. See the Release Notes

No, that's why I said to reinstall all node servers which is supposed to fix it Sent from my Pixel 6 Pro using Tapatalk

Topic Locked due to new version released

The Polyglot Version 3 Node server for ELK Security Version 3.10.15 is released. See the Release Notes Working on new documentation at ELK Node Server If you have issues or requests please check PG3 ELK Github issues to see it has already been listed. And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes. IMPORTANT: If using ELKID or ELKNAME you must enable the "Allow ISY Access by Plugin" on the configuration page. This will be required in PG3x Version 3.2.19 and beyond.

1. Is the "Arm Up State" = "Ready To Arm"? 2. Is the user_code set to a valid code entered in ElkRP2? 3. Is the ElkRP2 Disconnected from your ELK? If the answer is yes to all 3, then please download log package and PM to me again.

In the logs you just sent I see many: 10/18/2023, 09:10:32 [pg3] error: IoX Inbound Status: UnauthorizedError: Unauthorized This means that username/password was messed up. Please close the Admin Console, do a Re-install all node servers from the PG3x UI then open Admin Console when it completes and re-test Arming an area once they all finish.

Please do a Query on your Area node again, then download log package and PM it to me.

Password is entered when the node server is installed, if you edited that form and saved then it might have cleared the password. @bpwwer or @bmercier is that right? And is there a fix for the 401 error? Sent from my Pixel 6 Pro using Tapatalk

@bmercier or @bpwwer This means IoX is not communicating with PG3x, right? @JSchumann did you happen to open the Admin Console -> Node Servers for this node server and edit the username/password?

Where did you get that response? Please try from the Admin Console. Sent from my Pixel 6 Pro using Tapatalk

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?