Jimbo.Automates

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.

I did this on my lake house Polisy, staying on Polisy for now and added internal Zmatter board. After starting the restore I brought up AC and saw all zwave devices were disabled, then it started popping up the "Performing -Wave Device Interview" for each device and they were coming back enabled. Some devices take a very long time and the display will say "[Device 11] Waiting on interview complete (timeout in 400)" then the timeout number will drop to 399, then go back to 400, and ever minute our so it will show a device message. But it's been stuck on this same device for over 20 minutes. I submitted a ticket. My question is, can I leave the internal ZMatter board installed, then plug back in the Zooz dongle, reboot and restore my previous backup? Or do I need to pull out the ZMatter board? I left for a while and when I can back it completed, but Z-Wave X-Ray All devices shows: Devices list: 1 Interview Not done 5 Interview done 6 Interview Not done 7 Interview done 8 Interview Not done 9 Interview done 10 Interview done 11 Interview Not done

I had a bad experience disabling WiFi. Michel has been trying to debug. I did the 4 button press as described on the wiki to fix it. Sorry I'm not sure I can change it and get it tested tonight. I'll try to take a look while at our lake house for the next couple weeks. Sent from my Pixel 6 Pro using Tapatalk

I suspect updates won't be pushed since the wireless tag hub needs to know the IP address of the node server machine and it probably used that weird WiFi one. Sent from my Pixel 6 Pro using Tapatalk

That bogus address is likely because WiFi is enabled, there are currently issues with using some node servers with WiFi enabled. I can fix this in the Node Server but not sure if I'll have time today before I head out of town tomorrow. Sent from my Pixel 6 Pro using Tapatalk

Should not be related to the apostrophe's. After setting change_node_names to true, set Log to Debug, restart the node server, download log package and send that to me.

Best to reserve the IP address in your router DHCP. I think you have to get the USB adapter from UDI store? Sent from my Pixel 6 Pro using Tapatalk

Not sure what would cause that error, maybe @bpwwer has a clue. The license issue may need @Michel Kohanim to look at the database, I had a similar issue. But first please try to reinstall in the same slot, don't delete and reinstall, use the reinstall option in the store. Sent from my Pixel 6 Pro using Tapatalk

This is taking a while to debug. It works fine outside of the node server, so I'll need to write some custom code that uses the library in the same was as the node server and see if that shows the issue. The 'write_msg' is displayed immediately before it tries to actually send the data to the ELK so I'm have no idea why it would take so long to print that message.

I had initially enabled WiFi, but switched to Ethernet and kept having problems. I just reset networking with the 4 button pushes described in the user guide and it seems better so far. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Reset_Networking

Yes that's the correct link, thanks for checking. If you order after clicking the link it will be credited. Sent from my Pixel 6 Pro using Tapatalk

What is your PG3 version? Should be .18 Sent from my Pixel 6 Pro using Tapatalk

It's not the password, it's a ELK user code like the one you use at the panel. I created a unique one specifically for PG3. Also, remember you are using eisy and a version of PG3 that's had many recent changes so there are bound to be issues. Also, the ELK NS has had very little testing on eisy. My eisy is having issues right now so I'm unable to test... Sent from my Pixel 6 Pro using Tapatalk

The doc: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#zone-node Shows Logical Status driver:ST If it's still showing the raw value try rebooting the ISY. It returns the correct for output because that uses a standard On/Off so a reboot is not required.