macjeff

Finally installed pg3 and did one of my nodeservers (PurpleAir) I have a few questions 1. When I log out of PG3 and log back in before I can install any of my purchases I have to go to the Purchases screen, log in again to portal, and then go back to nodeservers. Any way to auto login? Did I miss something? 2. I have about 20 nodeservers installed. I did one of them- purpleair because the config was simple but I have some with lots and lots of data and some keys I may have issues finding. I see talk on here and the button to import pg2 config but I also see it had issues. Is it ready to go? Can I import settings for each nodeserver that was ported? If not I guess its all or nothing? Problem is only 12 of my 20 are ported so far. 3. Depends on your answer to #3 but one idea I had is to install the same nodeserver in a different slot and then copy and paste data from Pg2 to pg3. 4. I assume no way to get programs to recognize the same nodeserver. I have hundreds of programs. Guess my weekend is going to be busy!!! But overall its nice. THANKS TO EVERYONE for a job well done Jeff

this is direct from Michel at UDI but it was in December 1. I ordered that dongle 2.- I assume if I move things over and it does not work well that I could move back right? 3. - do you use Alexa? I assume you have to relink all the devices there 4. This is directly from Michel at UDI from December so maybe things changed You can import programs and network resources. The only issue is the scenes. With kind regards, ****************************** Michel Kohanim CEO

I dont have any ELK devices. I have as you can see in my previous post about 67 zwave. The rest are insteon and pg2 nodeservers. I guess I would need a zwave stick to transfer the zwave to polisy and second once I move over the ISY backup I was told I have to redo all the scenes. Thats a lot of work!!!

I have about 20 nodeservers now on pg2. After talking to Jimbo and a couple others I am interested in trying pg3 both to get the latest nodeserver updates (due to end of life of Pg2 nodeservers) and to support the developers. Below are some statements and questions on my plans. Please comment!!! 1. First I need to make sure my polisy is up to date (which it is) and Install Pg3 using commands in this thread. 2. Pg2 nodeservers will work as if nothing happened. 3. Right now my polisy is on port 8443 so that will be the same but I use port 3000 for pg3 dashboard. 4. To update Polisy (and freebsd) I use SSH commands (sudo pkg upgrade) and not the GUI version in PG2 under the system menu or can I continue doing that. And will this update everything (anything for pg2 and pg3 as well as freebsd) 5. So lets pick a nodeserver as example- Jimbo WirelessTag. I disable it in pg2 and install on pg3? If I have issues with pg3 one can I go back to pg2 version until I get the issue resolved. Everything is working well now (knock on wood) and I dont want to mess it up (fix what aint broke!!) 6. Question- My ISY is NOT on polisy and I dont plan on moving it any time soon because I have a VERY complex setup (see screenshot) and it would take a lot to upgrade. So assuming I stay with the hardware ISY, can I now have more than 25 nodeservers? The nodeserver limit is fine now but as this expands to more and more devices 25 is not going to be enough. Depending on your answer here, I may consider running a second ISY on polisy since pg3 supports it and move over some stuff. My issue is some of the programs run other programs and having 2 ISY instances seems like it will be hard to manage what devices are on each one assuming you cant call commands from one ISY to another (if so I would like to learn more) 7. When I back up Polisy do I have to run one backup from pg2 and one from Pg3? 8. Some nodeservers may never be ported to pg3 so I assume pg2 will be able to run for along time and its not going away anytime soon. 9. Anything I missed and should know. Jeff Thank you very much in advance for your help and suggestions.

I checked again after midnight last night (sorry I meant to check sooner) and it said WINTER now. It either changed 24 hours later (3:59 pm yesterday) or it waits a full day before changing and changed today (Dec 23) after midnight. Its ok if there is a reason. I can always adjust my programs for this. *** I did notice the same thing last season change and thought it was just a one time issue but every season seems to wait a day before changing.

Thanks for Tagging him Mr. Bill!!!

Winter Started at 3:59pm on Dec 21. Its now 1:48 pm on Dec 22. So it has not been 24 hours but actually its winter. My guess it will change for tomorrow but I would like today to be counted too as winter since it is winter since 4pm yesterday. See screenshot from just now. You can see the date in there. thanks

I just ended up leaving the notes ever in there since the updates fine and they haven’t tried deleting it since then. Jeff

I have things that run on the Third Wednesday of the month or others like the 2nd Friday of the month I have been using this program to calculate week of month WeekofTheMonth - [ID 0282][Parent 0219] $WeekofTheMonthTemp = [Current Day of Month] $WeekofTheMonthTemp -= 1 $WeekofTheMonthTemp /= 7 $WeekofTheMonthTemp += 1 $WeekofTheMonthTemp Init To $WeekofTheMonthTemp $WeekOfTheMonth = $WeekofTheMonthTemp and then I say day is (Monday, Tuesday, etc) using the ISY TimeData Nodeserver and the week number is (whatever I need) Is there a better way to do this? Jeff

I think I had this issue and it was the password. I cant remember but it was either it wanted the envisilink password or the passcode. Disarm has a different code and thats probably why it works. Also make sure you can do it all with the EV4 aopo. If you can there then you know you are good and its a config issue. If thats not the issue, sorry but I thought I would see if I can help since I have an EV4 and honeywell.

UPDATE- Rebooted polisy (which I had done many times before running the sudo pkg upgrade -f) and now my polisy magically came back to 2.2.13 but when I just run sudo pkg upgrade it now tells me 0 candidates) All seems fine. Not sure what the 1 candidate was but its not coming up anymore, Polisy is back to 2.2.13 and everything seems to be working.

I ran the Check For Polisy Updates. Been a few weeks since updated. I usually have at least 1. Had none. Checked with another member and he said he checked a few days ago and had none and checked yesterday and had 1. So I manually did the check I noticed I had this when doing the sudo pkg upgrade it says 1 candidate. I could not get the 1 candidate to go away. and noticed it did download and process..... [admin@polisy ~]$ sudo pkg update && sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. I finally fixed it by running this. Notice it says my Polygot was newer. So I let this run.... [admin@polisy ~]$ sudo pkg upgrade -f Password: Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (446 candidates): 100% Processing candidates (446 candidates): 100% The following 425 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: polyglot: 2.2.13 -> 2.2.11_3 [udi] Installed packages to be REINSTALLED: (DID NOT SEND LIST BECAUSE ITS HUGE) After it downgraded now I ran the same command and now zero candidates [admin@polisy ~]$ sudo pkg upgrade Password: Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy ~]$ So I should be good now? Anything else I should run or any idea why I had a newer version? I only do the updates it says to run. Jeff

I had someone else test with my system on their iOS device and had the same problem but I don’t have another ISY running that node server to test with. But I have access to an android device it will test that shortly so I can confirm it’s just an iOS issue.

Timedata Nodeserver looks fine on the ISY Admin Console. All nodeservers are fine in UD Mobile (new iOS release) except timedata (and I have about 20 nodeservers running) Here are some screenshots. Data is missing from timedata and no data in sun (part of timedata). BUT its all in the ISY admin console just fine and everything is working. SO...this is not a huge deal but would be willing to work with you if you want me to help test.

You need .net v5 installed first. It no longer works with 3.1. I ran it on a mac for a while and now on a pi. I would highly recommend fixing or replacing your Pi. But if you did not see it, you can download a short setup guide here http://automationshack.com/Files/NodeLink_Setup.pdf

KeenHome also works with Ecobee but they are having issues this week. Flair update for the same problem came out Dec 5. Still waiting for Keen update for the app. They totally changed some things on the Ecobee end. Surprised the UDI nodeserver is still working fine. I may end up going with Flair if that is not fixed.

sorry about that. I did a quick google and did not look. But yes its KeenHome

btw...forgot to say WHY i have keen vents. I live about 50 miles outside of DC and run servers for places in DC (mostly backup ones) for disaster recovery. I have a server room in my house that of course runs hot. Keen vents solved the problem. It cools every room to the same temp using their own (or Ecobee/nest) room sensors. It closes vents and opens them if needed.

I invested in KEEN SmartVents because they were first before Flair. I saw there is a flair nodeserver but not about to spend $2000 to replace all my vents with flair unless I have to. I would be willing to chip in for time and also beta test. Of course if its going to cost as much as the flair vents then I guess I will go that route. Not sure if UDI would assist at all. Here is their API https://keen.io/docs/api/?python# I h

I discovered something new. When the Check Updates and Install Updates wont give any feedback, it wont retrieve the configuration when asked under the settings menu. It just stays on retrieving configuration (as mentioned by another user in this post). The polisy reboot fixes this also but as with the check for updates I assume its a temporary fix,

yes but just did it again [admin@polisy ~]$ curl -s https://pkg.isy.io/script/update121.sh | sudo bash Password: Installing FreeBSD-base updates Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. All repositories are up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'FreeBSD-*' have been found in the repositories lookig for .pkgnew files... Preserving files that are unique to Polisy lookig for any left over .pkgnew files... Upgrade complete, please reboot using: sudo shutdown -r now

yes and he said on the chat he has the same behavior as me "Maybe I declared victory too early.... I am actually seeing the same behavior as @macjeff. After a Polyglot restart, you get the green "No updates available..." bar BUT, one day later, the bar no longer appears. Past history has been for updates to be released at least every week. I plan to wait a few weeks and see if any updates are received and successfully installed. " and I have spoken to him just recently and it is still happening. If you reboot everything is fine. You say check for updates under the system menu. and you get a response in a green box Update Check complete. No updates available!" or Update Polisy under the System Menu and you get a green box saying "Update success! Check polisy logs for details." BUT if you wait a while. Sometimes 12 hours but for sure the next day. You check for updates or Update Polisy and you get no response. Again I confirmed that @gviliunas still has the same issue. jeff

any update on this. Now been a month and if I reboot polisy I can check for updates and get no response. I used to get a banner that says Success- No Updates Available or maybe 1-5 minor updates available. I even did an UPDATE polisy and no response there either. I used to get a response there too. Once I reboot it works and I can try again later and it works but the next day every time it wont work. And I have confirmed I am not the only one seeing this problem. So the workaround is just to reboot polisy. I can confirm NodeServer updates are working as they should.

I reported this issue a week ago to Michel. I have done testing since. If I check for updates now it works but every morning when I get up I dont get the green bar. But if I reboot polisy then I get the green NO UPDATES AVAILABLE bar. Try again later in the day or at night its fine, but the next morning same thing. No bar. This started after the last Polisy updates I ran about 1-2 weeks ago.

Not only did I reboot several times but I restored both my polisy and ISY from backup up to a few days ago. I restored back after all the tests (again) to my latest backup. everything is working fine but I CANT delete the nodeserver so I will just leave it until UDI can come up with a solution Worse case I lose a slot in the ISY because as I said I can delete from Polisy, delete all nodes from ISY (but leave the server in the nodeserver menu which wont delete) and then install the same nodeserver in another slot. It works fine in the other slot and it deletes. Its just my one slot that wont delete.