Jump to content

Polyglot on new EISY


TVogl

Recommended Posts

Posted

I received my new EISY.   I have not yet migrated my isy994i config, nor moved the Insteon PLM so this is a very clean installation.   I was trying to play with PG3 and I tired to install the MagicHome Trial.  It throws an error message during the install and then never runs.   I see items like this in the general log.  There is nothing in the MagicHome log and the service wont start at all.

I am posting this problem here rather than in the Node Server site because I am having the same problem trying to install the ROKU polyserver also - so I suspect something with my EISY config rather than a Node Server specific issue. 

Any ideas what I am missing?

12/29/2022, 15:38:31 [pg3] info: [00:21:b9:02:5f:a5_2] :: Creating Node Server 'MagicHome'
12/29/2022, 15:38:31 [pg3] info: Adding customparams entries to custom database
12/29/2022, 15:38:31 [pg3] info: Adding nsdata, oauth entries to custom database
12/29/2022, 15:38:31 [pg3] info: [00:21:b9:02:5f:a5_2] Set nsdata
12/29/2022, 15:38:31 [pg3] info: [00:21:b9:02:5f:a5_2] Set oauth
12/29/2022, 15:38:31 [pg3] info: checkLicense:: Updaing MagicHome subscription expiration to 2023-01-29T19:22:03.000Z
12/29/2022, 15:38:31 [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/29/2022, 15:39:45 [pg3] info: [00:21:b9:02:5f:a5_2] Retrieved customparams
12/29/2022, 15:39:45 [pg3] info: [00:21:b9:02:5f:a5_2] Retrieved oauth
12/29/2022, 15:39:47 [pg3] info: startNs:: MagicHome
12/29/2022, 15:39:47 [pg3] info: startNs:: MagicHome is valid
12/29/2022, 15:39:47 [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 Object.startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20)

12/29/2022, 15:41:00 [pg3] info: [00:21:b9:02:5f:a5_1] Retrieved customparams
12/29/2022, 15:41:00 [pg3] info: [00:21:b9:02:5f:a5_1] Retrieved customtypeddata
12/29/2022, 15:41:00 [pg3] info: [00:21:b9:02:5f:a5_1] Retrieved oauth
12/29/2022, 15:41:01 [pg3] info: Starting log stream for pg3frontend_fOuoq :: /var/polyglot/pg3/ns/0021b9025fa5_1/logs/debug.log
12/29/2022, 15:41:01 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: Error: ENOENT: no such file or directory, access '/var/polyglot/pg3/ns/0021b9025fa5_1/logs/debug.log'
12/29/2022, 15:41:03 [pg3] error: downloadLog: Error: File not found: /var/polyglot/pg3/ns/0021b9025fa5_1/logs/debug.log
    at Object.addLocalFile (/var/polyglot/node_modules/adm-zip/adm-zip.js:258:23)
    at /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/log.js:133:16
    at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9

12/29/2022, 15:41:49 [pg3] warn: verifyNodeServers (00:21:b9:02:5f:a5) :: ISY has no node serv

Posted
1 hour ago, TVogl said:

I received my new EISY.   I have not yet migrated my isy994i config, nor moved the Insteon PLM so this is a very clean installation.   I was trying to play with PG3 and I tired to install the MagicHome Trial.  It throws an error message during the install and then never runs.   I see items like this in the general log.  There is nothing in the MagicHome log and the service wont start at all.

I am posting this problem here rather than in the Node Server site because I am having the same problem trying to install the ROKU polyserver also - so I suspect something with my EISY config rather than a Node Server specific issue. 

Any ideas what I am missing?

12/29/2022, 15:38:31 [pg3] info: [00:21:b9:02:5f:a5_2] :: Creating Node Server 'MagicHome'
12/29/2022, 15:38:31 [pg3] info: Adding customparams entries to custom database
12/29/2022, 15:38:31 [pg3] info: Adding nsdata, oauth entries to custom database
12/29/2022, 15:38:31 [pg3] info: [00:21:b9:02:5f:a5_2] Set nsdata
12/29/2022, 15:38:31 [pg3] info: [00:21:b9:02:5f:a5_2] Set oauth
12/29/2022, 15:38:31 [pg3] info: checkLicense:: Updaing MagicHome subscription expiration to 2023-01-29T19:22:03.000Z
12/29/2022, 15:38:31 [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/29/2022, 15:39:45 [pg3] info: [00:21:b9:02:5f:a5_2] Retrieved customparams
12/29/2022, 15:39:45 [pg3] info: [00:21:b9:02:5f:a5_2] Retrieved oauth
12/29/2022, 15:39:47 [pg3] info: startNs:: MagicHome
12/29/2022, 15:39:47 [pg3] info: startNs:: MagicHome is valid
12/29/2022, 15:39:47 [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 Object.startNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:915:20)

12/29/2022, 15:41:00 [pg3] info: [00:21:b9:02:5f:a5_1] Retrieved customparams
12/29/2022, 15:41:00 [pg3] info: [00:21:b9:02:5f:a5_1] Retrieved customtypeddata
12/29/2022, 15:41:00 [pg3] info: [00:21:b9:02:5f:a5_1] Retrieved oauth
12/29/2022, 15:41:01 [pg3] info: Starting log stream for pg3frontend_fOuoq :: /var/polyglot/pg3/ns/0021b9025fa5_1/logs/debug.log
12/29/2022, 15:41:01 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: Error: ENOENT: no such file or directory, access '/var/polyglot/pg3/ns/0021b9025fa5_1/logs/debug.log'
12/29/2022, 15:41:03 [pg3] error: downloadLog: Error: File not found: /var/polyglot/pg3/ns/0021b9025fa5_1/logs/debug.log
    at Object.addLocalFile (/var/polyglot/node_modules/adm-zip/adm-zip.js:258:23)
    at /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/log.js:133:16
    at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9

12/29/2022, 15:41:49 [pg3] warn: verifyNodeServers (00:21:b9:02:5f:a5) :: ISY has no node serv

There is an issue with PG3 that I was told will be corrected soon, after you install the node server you back and hit the (Re)Install putting it in the same slot and it should start after that.

Posted
2 hours ago, TVogl said:

12/29/2022, 15:38:31 [pg3] error: createNS: ReferenceError: status is not defined
    at checkLicense (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/node servers.js:710:95)

This is caused by a typo in a log message.  It doesn't effect anything else.

The log not being found is because the node server was unable to start.  After re-installing you may also have to manually issue a "STOP" to the node server and then a "START" to get it going.

Posted

Thanks but no dice. 

The "(re)install" for Roku says "Can't find puchase option for license record".  and does nothing.  And yes, "purchase" is spelled wrong in the message.


The "(re)install" for MagicHome offers to let me reinstall in the same slot, but when I select it, I get: "Node Server install of undefined failed with message: status is not defined"

 

Both are clearly in the purchased list (see attached screen shot) - even though they are the trial licenses.

 

Also tried deleting and re-adding.  Same results.

NodeServerPurchases.png

Posted

Before I got my PLM serial cable and restored, I had to play with Magic home ... 23 nodes and it worked!!!!!! I actually purchased it. I did have to go through a few reinstalls to get it to actually be online vs. disconnected, but I can attest to it worked at one point. Sent the developer mad props and praise for it too!

I'm working on a slew of other issues with Michel right now - after restoring my ISY994 backup I completely hosed the system - I'm one of the reasons for 5.5.0 now being 5.5.2 (and I suspect that number will tick up a few more times as we all do our install and some of the other bugs come up). 

My goal is to migrate 23 lights from Insteon to MagicHome but have it act like one system - app, voice, keypadlincs driving lights on/off regardless of what they are plugged into. Will see how well I can make it all work :)

Posted
10 minutes ago, MJsan said:

Before I got my PLM serial cable and restored, I had to play with Magic home ... 23 nodes and it worked!!!!!! I actually purchased it. I did have to go through a few reinstalls to get it to actually be online vs. disconnected, but I can attest to it worked at one point. Sent the developer mad props and praise for it too!

I'm working on a slew of other issues with Michel right now - after restoring my ISY994 backup I completely hosed the system - I'm one of the reasons for 5.5.0 now being 5.5.2 (and I suspect that number will tick up a few more times as we all do our install and some of the other bugs come up). 

My goal is to migrate 23 lights from Insteon to MagicHome but have it act like one system - app, voice, keypadlincs driving lights on/off regardless of what they are plugged into. Will see how well I can make it all work :)

Were you getting this error when installing/reinstalling:  "Node Server install of undefined failed with message: status is not defined"   - or was it just not starting?

Posted

So here is any update.   I was able to install a few other PolyServers: "holidays" and "Sun & Moon" both installed first time without issue, but "MagicHome", "roku" and "NOAA" weather all refuse to install with the same error: "Node Server install of undefined failed with message: status is not defined".

Posted

And with this update I am done for the evening.  The two node servers that did install, "holidays" and "Sun" look like they work about 75% of the way.   Meaning PG3 installed them cleanly.  They show as "connected", they generated nodes and populated them in PG3, but in the ISY the nodes appear, but there are no values.

image.thumb.png.a4586a84019cc205c5eff23b5f84b4ae.png

image.png.dd062997079a8a7fe33d2b2de7b1fe42.png

 

Let me close with this:  I love UD - I have been an avid fan of the isy since I bought it in 2014.  This eisy box is awesome (FAST!) and I understand it may take awhile to work thru early release issues.   Thank you all at UD - I look forward to working through these  bumps in the next few weeks and can't wait to retire my isy994i.    

 

 

 

Guest
This topic is now closed to further replies.

×
×
  • Create New...