sjenkins Posted December 30, 2022 Posted December 30, 2022 8 hours ago, dbuss said: I installed two node servers and had to reinstall each one twice to get them to start. I also had to do the re-install with each of my ten node servers.
garybixler Posted December 30, 2022 Posted December 30, 2022 After reinstalling a node server more that once it still remains in disconnected state but is running. It was reinstalled from my purchases list. When I installed a node server not in the purchases list it does get installed. So how will I move the NSs presently in Polisy to eisy?
bigDvette Posted December 30, 2022 Author Posted December 30, 2022 I can't get my first 2 node servers to start. When I install one that has a license, I get what is in the picture below about undefined. When I install one that is free, i get an installed successfully message. I can't either of them to actually connect. I have this in the log for the MyQ (which is paid and throws the error in the picture). 12/30/2022, 09:40:18 [pg3] info: [00:21:b9:02:60:43_2] :: Creating Node Server 'MyQ' 12/30/2022, 09:40:18 [pg3] info: Adding customparams entries to custom database 12/30/2022, 09:40:18 [pg3] info: Adding nsdata, oauth entries to custom database 12/30/2022, 09:40:18 [pg3] info: [00:21:b9:02:60:43_2] Set nsdata 12/30/2022, 09:40:18 [pg3] info: [00:21:b9:02:60:43_2] Set oauth 12/30/2022, 09:40:18 [pg3] info: checkLicense:: Updaing MyQ subscription expiration to 2023-01-30T02:49:51.000Z 12/30/2022, 09:40:18 [pg3] error: createNS: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.createNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:433:5) 12/30/2022, 09:40:35 [pg3] info: [00:21:b9:02:60:43_2] Retrieved customparams 12/30/2022, 09:40:35 [pg3] info: [00:21:b9:02:60:43_2] Retrieved oauth 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Set customparams 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Set customtypeddata 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Retrieved customparams 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Retrieved customtypeddata 12/30/2022, 09:40:55 [pg3] info: [00:21:b9:02:60:43_2] Retrieved oauth 12/30/2022, 09:41:01 [pg3] info: [MyQ(2)]: Restarting Node Server 12/30/2022, 09:41:01 [pg3] warn: [MyQ(2)]: Was not running. Starting... 12/30/2022, 09:41:03 [pg3] info: Starting log stream for pg3frontend_9baEU :: /var/polyglot/pg3/logs/pg3-current.log 12/30/2022, 09:41:03 [pg3] info: Starting log stream for pg3frontend_9baEU :: /var/polyglot/pg3/logs/pg3-current.log 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ is valid 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ is valid 12/30/2022, 09:41:04 [pg3] info: startNs:: MyQ is valid 12/30/2022, 09:41:04 [pg3] error: MQTT on Inbound processFunction: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20) 12/30/2022, 09:41:04 [pg3] error: MQTT on Inbound processFunction: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20) 12/30/2022, 09:41:04 [pg3] error: MQTT on Inbound processFunction: ReferenceError: status is not defined at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20)
bpwwer Posted December 30, 2022 Posted December 30, 2022 17 hours ago, garybixler said: After delegating a couple of node servers from Polisy they show up in node server purchases. It looks like I can reinstall into the eisy from there. Will that also take care of the license issue? Thanks No, the license is tied to the hardware ID and that has to be changed in the portal based database that holds the license information. I don't know if it is part of the migration option in the portal or not at this point.
bpwwer Posted December 30, 2022 Posted December 30, 2022 17 hours ago, bpwwer said: These are the bugs I'm aware of: 1) First installation will leave some of the node server files with the wrong owner/permissions. This causes the node server to fail to start. Using the re-install option should correct this. 2) When it tries to start the node server after doing the installation it will fail. It actually tries to start the node server before the installation is finished. After installation, stopping and then starting the node server may get the node server working. 3)??? Since I can only test with my own node servers which don't use the Portal or a license, it's possible there are bugs here that I won't see. Based on some of the forums posts I suspect there is in which case, it may not be possible to install any node servers. 4) backup doesn't work. Well it actually does work but it hits the same bug as #2 and PG3 is told the backup is done before it's even started. The backup does happen (it's sitting in /tmp on the eisy) but PG3 doesn't see it and send it on through the browser. 5) start may not actually start the node server. 6) Migration is just not possible yet. There are three (four actually) things that need to happen to migrate node servers - First, PG3x needs to be able to read a PG3 backup. The backup file formats are different between the two. I have this bit already coded up. - Second PG3x needs to convert a PG3 node server to PG3x. How the node server is stored and controlled has changed. Again, this is coded. - Third, PG3x needs to move the node server to the local IoX. Restoring the PG3 backup in step 1 will keep the existing setup. So if the node server was installed to a Polisy IoP, then after the restore it will add the Polisy IoP to the database and expect the node server to be installed on that IoX device. I still have to write code. - Fourth the license needs to be migrated from Polisy to the eisy. This happens via the Portal and not something I control. A small update. #1 is fixed and will be in the next release of PG3x #2 is fixed and will be in the next release of PG3x #3 no progress #4 appears to be resolved and should be fixed with the next release of UDX (this should solve some other minor issues with the same root cause) #5 is being debugged now #6 the first 2 parts are complete.
garybixler Posted December 30, 2022 Posted December 30, 2022 Just one question. I am assuming that the eisy won't be able to load any NSs from PG2. Nothing pressing.
giomania Posted December 30, 2022 Posted December 30, 2022 3 minutes ago, garybixler said: Just one question. I am assuming that the eisy won't be able to load any NSs from PG2. Nothing pressing. Correct.
MJsan Posted December 30, 2022 Posted December 30, 2022 After some major work by @Michel Kohanim my system is 100% functional - PLM and Insteon side as well as MagicHome node servers on the PG3 side. Everything y'all have said about how awesome UD support is ... absolutely true. 2
Recommended Posts