Jimbo.Automates

Yes, good idea Bob. @SLiss please check the PG3 log, not the node server log. But it still baffles me that it works from UD Mobile. Sent from my Pixel 6 Pro using Tapatalk

Open the node server configuration in the AC and check the IP address. I think on eisy it should be 127.0.0.1 ? Sent from my Pixel 6 Pro using Tapatalk

Does changing the chime mode work from the AC? Sent from my Pixel 6 Pro using Tapatalk

If it's true and node server is restarted it should change the name. If your log was in debug mode you can download log package and PM that to me and mention what time a restart was done that didn't change a name, and what names were involved. Sent from my Pixel 6 Pro using Tapatalk

Is the change node names configuration option set to true? Sent from my SM-X808U using Tapatalk

It's been discussed but not implemented yet. Was actually pondering it this morning and have some ideas. It's a big effort... But also need to move my home from polisy to eisy. Discussion and link to issue here; /topic/38897-how-to-import-devices-into-elrp-using-a-node-server Sent from my Pixel 6 Pro using Tapatalk

@bpwwer any idea what could be wrong? Command works through UD Mobile but not the AC. Sent from my Pixel 6 Pro using Tapatalk

That would be nice. I'll look through the ELK API and see if I can find something. Their API is pretty limited and don't seem to want to update it unless necessary. Sent from my Pixel 6 Pro using Tapatalk

Well that is very odd because they do the same thing. But the slow response was fixed in 3.5.8 so that concerns me. Can you close and reopen the AC and try again to confirm? And when you do it, watch the node server log in Debug mode and see that it says something is happening?

Is your user code correct? Although it should throw and error if it's not valid.

Great, thanks Bob. But, also need confirmation that eisy was rebooted, or PG3 restarted after the upgrade.

>> Nothing populated That is normal behavior of the ISY on restart if you do not have the 'Query all on restart' option enabled in the ISY settings. But if that is enabled and the values were not populated, it means the node server crashed. I see you sent the logs, I will review.

Not sure what you mean by nothing was populated. Do you see any errors in the node server log? Download the log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

There are incompatible issues with the python elk library which caused a lot of issues and hopefully this one as well. The reason it required a reboot was likely because a subprocess didn't exit properly. Please test and let me know if it persists. Sent from my Pixel 6 Pro using Tapatalk

Sorry, not clear. Even after upgrading to 3.5.8? Sent from my Pixel 6 Pro using Tapatalk

Hopefully that is fixed in 3.5.8. I've never seen that happen before. Sent from my Pixel 6 Pro using Tapatalk

Check this post /topic/39896-357-upgrade-to-358-not-working-with-restart Sent from my Pixel 6 Pro using Tapatalk

That's a PG3 bug. Go to "Node Server Store" , Select ELK, Select "Install" of the Perpetual version. This will show in option "ELK is already installed in slot x, Reinstall here?". To be safe, I'd backup PG3 first, but I've not heard of this causing any issues.

Your steps are all good except, do not do #14. Sorry all the details of adding a node server are not part of the ELK node server instructions. That should be created for the new users. Sent from my Pixel 6 Pro using Tapatalk

Awesome! Thanks. Sent from my Pixel 6 Pro using Tapatalk

It's a PG3 bug. Please reinstall in the same slot. Don't delete and install, choose the reinstall option. Sorry, not at a computer to give the exact procedure... Sent from my Pixel 6 Pro using Tapatalk

Please update to 3.5.8 and let me know if that helps. I'm not home so I can't confirm.

Sorry, I found the issue with wrong version of elkm1_lib, I just sent ELK Node server 3.5.8 to the store, please update and that should fix the elkm1_lib version.

Yes, those ERRORS happen when node server is stopped or restarted, I need to figure out fix, but it shouldn't cause an issue. Interesting that you are seeing a delay on Polisy, we are seeing that on eisy but hadn't seen an issue on Polisy. You say library version 2.2.1, is it for this? [admin@polisy ~]$ sudo -u polyglot pip list | grep elk elkm1-lib 2.1.0 The node server doesn't support 2.2.0 or above, and specifically excludes that from the install so not sure how that happened? Edit: and besides that issue, I am running the same versions on both my Polisy's and see no delay.

Thanks missed that, guess I'll pull it back down tomorrow and pull it out if I don't hear back from support.