sjenkins

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?)

My Brady labeller does.

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?

So sorry I didn’t get back to the post. Yes I did put in and get an answer to my ticket. Basically that the occupancy was part of the pg-online and therefore not working. I sort of knew this but was unsure if policy brought it back as it was in the menu system still online.

I’ve been using three of these for over a year now. Seem reliable. Been using for accent rgbw strips. Have programs to change for different seasons. (Christmas, Easter, Canada day, USA day, etc). Mostly use the white. Found timing of colour change to on/off can matter. Number of programs and outputs really grows as you add a few of these. As I say once through the growing pains they are very reliable.

Yup ; no issues or changes with mine.

Just did a "packages update" from ISY (or IoX) menu. Didn't come back on-line. Normally do a button push in this state but was in my comfy chair so did a sudo reboot from ssh; came back fine after that. Yes, had a 20sec pause for query, but nothing over the top. Backup of 5.4.4. before update was fine and the 5.4.5 backup after was also fine. Way back in time the last instance when my backup wouldn't work for me I had to revert then re-upgrade to make everything happy again. That was in the 994 and was early 5.0's.

Could you set up as a hybrid like some companies do with commercial hardware ; a software open source to develop the software; then back to the commercial side for support contracts. I'm sure you have thought of that, I am curious what you lose as owner in that scenario. It's a bit what you're doing now with pg3 just more of your bits in the OS side, wouldn't require a ton of restructuring. Again not telling just curious your thoughts (I'm one of those strange EE with an MBA types).

So since moving to Polisy, a few years ago now, I knew the occupancy was not working and was not too bothered. Had a few minutes and decided to resurrect it again... no joy. The configuration seems to be doing what its supposed to do, it finds my node and knows the id number. Even did the add node where it restarted the ISY and was out and login of both ISY and Portal a few times. Seems to look good in the configuration section. Cannot add or sync the nodes, get an 400 error with adding. Decided to do scorched earth and remove and restart (maybe didn't like the transfer from the 994 ?!?) but I get a 403 error if I do remove either in the configuration or occupancy. Any experience out there or is this a ticket item? Always hate to bother the UD team if its an easy fix.

I do think it is the power on cycle. Those power supplies are often not of the switching variety and don't forget the 24vac going back to the furnace. I bet the voltage comes up slow and non linear.

This would work.... GAEYAELE GRT8-S Asymmetric Cycle Timer SPDT Relay 220V 16A AC/DC12V-240V Electronic Repeat Relay(GRT8-S1,A230) https://a.co/j4A5gkG