Jimbo.Automates

The disconnected is a bug in PG3, I'll release a workaround when I have time. All the false are System Trouble Status reported by ELK, so all false's are good they're documented in the readme. https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK Sent from my Pixel 8 Pro using Tapatalk

From @Michel Kohanim I just included rust in the dev packages (was not there before). So, for your existing customers please have them: Upgrade Packages Install Dev Packages

We are working on a solution.

Thanks, what does Content #4 look like?

New installs of kasa are failing. I've emailed @Michel Kohanim with logs. Hopefully an easy fix. Sent from my Pixel 8 Pro using Tapatalk

@Javi why is UDM showing numbers for things like content? @AnthemAVM can you show me what the program looks like in the admin console? Sent from my Pixel 8 Pro using Tapatalk

That looks like a bug. But please include how you are sending the notification. Did you review the Notifications For All and README ?

Sometimes the PG UI doesn't refresh the nodes, usu if you force refr the browser then they will show up. Hopefully that gets fixed someday. Sent from my Pixel 8 Pro using Tapatalk

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.16 is released. See the README and CHANGELOG 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