macjeff

I got it installed now but when I run it I get errors but I know the settings are correct. I can put them into the pg2 version and they work 2022-02-16 15:17:34 info: NS: Starting Node Server 2022-02-16 15:17:34 info: POLY: Interface starting 2022-02-16 15:17:34 info: POLY: Getting config from environment 2022-02-16 15:17:34 debug: POLY: Log file set to: logs/debug-2022-02-16.log 2022-02-16 15:17:35 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:36 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:37 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:38 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:39 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:40 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:41 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:42 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:43 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:44 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:45 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:46 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:47 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:49 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:50 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:51 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:52 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:53 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:54 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:55 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:56 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:57 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:58 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:17:59 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:00 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:01 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:02 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:03 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:04 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:05 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:06 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:08 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:09 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:10 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:11 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:12 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:13 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:14 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:15 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:16 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:17 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:18 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:19 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:20 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:21 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:22 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:23 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:24 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:26 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:27 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:28 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:29 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:30 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:31 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:32 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:33 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:34 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:35 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:41 info: NS: Starting Node Server 2022-02-16 15:18:41 info: POLY: Interface starting 2022-02-16 15:18:41 info: POLY: Getting config from environment 2022-02-16 15:18:41 debug: POLY: Log file set to: logs/debug-2022-02-16.log 2022-02-16 15:18:41 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:42 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:43 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:44 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:45 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:46 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:47 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:48 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:49 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:50 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:52 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:53 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:54 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:55 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:56 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:57 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:58 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:18:59 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:00 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:01 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:02 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:03 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:04 error: POLY: MQTT Error: Connection refused: Identifier rejected 2022-02-16 15:19:05 error: POLY: MQTT Error: Connection refused: Identifier rejected

Tried restore and it failed. Well some came over and some did not but the ones in pg2 never deleted and so I basically had two running in the same slot. I tried deleting the one on pg2 and then it deleted the stuff from the ISY so I had to set it up all again on pg3. My log is attached LOOK at 14:39 pg3_2-16-2022_24243_PM.zip

I know it’s not in this topic but I hope this is not the case with Climacell. I use the variables there in lots of weather related emails to show temperature today and tomorrow and things like that. I also used them in programs.

so will the nodes I have now convert when I do the upgrade?

About to upgrade to PG3. Can I add the nodeserver twice once for Tempest and once for Air/Sky Jeff

Ok better than nothing but I hope it will just ignore any that are not ported yet thanks for your help

BUG- Tried to purchase ST-Inventory. Says Node Server Info is Not Valid If you fix I will buy right away!!

So 12 of my nodeservers are ready and purchased and I do this tomorrow or later this week. Then a month from now 3 more show up. Can I restore from backup again to bring over settings and it will only do the new ones and ignore all the others? If so thats great. and yes I know its alpha but thought I might as well get this going.

BUG- Tried to purchase ST-Inventory. Says Node Server Info is Not Valid

#4 is awesome. So you would suggest trying the restore. I will try that tomorrow. I hope I dont lose the one I already did. if it does not work then the correct procedure is copy and paste settings from Pg2 into a text doc for now erase nodeserver on pg2 Resinstall to same slot on pg3 Put settings back in and it should pick it all up if the same names and same nodeserver right?

Feature request- Notification via email or text when a new nodeserver is added or a nodeserver is updated. Would be nice!!!

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.