sjenkins

Paid node servers are connected to the unit you paid for them on. From what I am hearing you can either purchase again or through a manual process (a ticket I believe with the old UUID and the new UUID) you can transfer your nodes over. You will lose the ability to use them on the old unit. I am personally buying the nodes again for two reasons. One, I want to use my POLISY & EISY together. Two I want to support fellow developers for UD and UD.

I am not seeing SSH blocked at this point with 5.5.2 ; I really hope it will not be as I use it a fair bit. Static IP I handle with my router. Are others unable to SSH ?

I also had to do the re-install with each of my ten node servers.

Mine was "out for delivery" @6:30 this morning! woo-hoo early Christmas present! thanks to the UD team & especially @Michel Kohanim , You and your team have worked WAY too much the week before Christmas! PLEASE take some time off and enjoy your family and friends and recharge for the new year.

I am on 5.5 with a Zmatter installed but still using my zooz. No issues at all once upgraded. Upgrade process had the one glitch with the upgrade of the pkg package needed. All my z-waves are working as fine as they ever did, which is just OK. Z-wave still sucks compared to Insteon & YoLink.

I bet you are!! woohooo!!!! Very very exciting! (As long as one of the few was mine) Emacs forever! cheers, stephen

@Michel Kohanim Did you just start a VI/Emacs holy war on this Forum ?!!? I LOVE the key bindings & hate modal. We may need a new topic in the Coffee section....

Its likely locked up in the update process which has plagued many. Here is a link to the solution from @Michel Kohanim

don't forget Emacs for those of us hard core & over 50 ! (I installed it on the Polisy a while ago)

I would try to update pkg with sudo pkg update sudo pkg upgrade pkg sudo reboot -r then bring up the AC and hit the update package button

Amazing how you know something and then forget it. Thanks for the remind! I'll do that now.

often thought of that for my Insteon devices; never did; I'm impressed.

so in simplified form the only thing holding up the udi script is the update to pkg (caveat: In my case) so just doing a sudo pkg update , then a , sudo pkg upgrade pkg , then a, push of the Update Packages button in the AC will do the trick.

Tried to do the Update Packages method & watched the process with HTOP. No where did pkg update from 1.18.4 to 1.19.0 & the process slowed down to a lock another fun way to watch is to do a tail on the messages tail -f /var/log/messages | bzgrep pkg anyway I had to eventually do an update of pkg then hit the Update Packages again. NO WHERE did the POLISY lock up which is a testament to the choice to use BSD anyway I am hearing happy beeps right as I type this maybe the update script should do an update of pkg before it goes into the rest of the udi update?

@bpwwer I'm on 3.1.15 with ISY 5.4.5 as well. Have been holding a couple days on my POLISY update until the firmware stabilised with the new board. So sounds like from your description that will be the issue, appreciate the explanation. I will likely hit the button today once I get read up on the current Matter board procedure.

ok, so the reinstall will work from the store page but not from the purchase page ; not sure if that is particular to your NS or a PG3 issue. The auto update with a node reset would not work even after I did a PG3 reset (did NOT try a full POLISY reboot) anyway the YoLink NS is back up and running doing a re-install and I did check HTOP ; all is well. I will mark as solved and leave these other issues as they were not part of the high CPU usage issue. Thanks so much @Panda88!!

So just tried the (Re)Install button on the purchases page and it gave me a red box with.... "Can't find purchase option for licence record" ...not even sure what that means as its in my purchase list.

yes you can (I forgot the button and was just refreshing the page, duh) anyway it would not do an automatic update...see image from the log. Didn't want to do a reinstall until I showed you.

Great, I’ll test as soon as the master UD computer digests & updates. Looks like it takes a few minutes (hours?)

See similar behaviour with my battery z-wave from zooz. Agree, I don't like not seeing any sort of heartbeat from leak sensors ; its why I prefer to use my old Insteon or am using YoLink increasingly.

agree I have not looked at cpu usage much at all ; I pulled up HTOP as it seemed like my ISY was a bit laggy. Which is when I found this issue. I am not using the delay timers. Any thoughts on short poll long poll as a mitigation until you do your change to the message handling approach?

@GTench Can't remember if I installed it or it was there. sudo pkg update sudo pkg install htop (do NOT do a sudo pkg upgrade as that can cause issues with your Polisy system)

Appreciate that. I am assuming you are not seeing this kind of cpu usage though?

17 devices for 18 nodes total. don't think I'm seeing memory build over time as the Polisy is stable but it is slowing down the whole ISY.

First, I really love this node server, but I just did an HTOP on my Polisy and wow there seems to be something going on here in this node server that isn't right. Attached are two runs of HTOP with the YoLink Node server running and stopped ( I think you can figure out which is which). Anyone else having this issue?