Jump to content

Support thread: IoX 5.5.5 Release

Chris Jahn

By Chris Jahn
in IoX Support

Recommended Posts

tazman Advanced

tazman

Posted
Posted

I updated on eisy and PG3 will not start now

Feb  1 19:07:50 eisy daemon[4370]: 2/1/2023, 19:07:50 [pg3] ^[[32minfo^[[39m: PG3 shutdown complete with code: 1
Feb  1 19:08:06 eisy daemon[4370]: 2/1/2023, 19:08:06 [pg3] ^[[32minfo^[[39m: Starting PG3 version 3.1.21
Feb  1 19:08:06 eisy daemon[4370]: 2/1/2023, 19:08:06 [pg3] ^[[32minfo^[[39m: Using Workdir /var/polyglot/pg3/
Feb  1 19:08:06 eisy daemon[4370]: 2/1/2023, 19:08:06 [pg3] ^[[32minfo^[[39m: Starting sqlite database at /var/polyglot/pg3/pg3.db
Feb  1 19:08:06 eisy daemon[4370]: 2/1/2023, 19:08:06 [pg3] ^[[31merror^[[39m: Startup error. Shutting down: Error: The module '/var/polyglot/node_modules/better-sqlite3/build/Release/better_sqlite3.node'
Feb  1 19:08:06 eisy daemon[4370]: was compiled against a different Node.js version using
Feb  1 19:08:06 eisy daemon[4370]: NODE_MODULE_VERSION 108. This version of Node.js requires
Feb  1 19:08:06 eisy daemon[4370]: NODE_MODULE_VERSION 111. Please try re-compiling or re-installing
Feb  1 19:08:06 eisy daemon[4370]: the module (for instance, using `npm rebuild` or `npm install`).
Feb  1 19:08:06 eisy daemon[4370]:     at Module._extensions..node (node:internal/modules/cjs/loader:1332:18)
Feb  1 19:08:06 eisy daemon[4370]:     at Module.load (node:internal/modules/cjs/loader:1103:32)
Feb  1 19:08:06 eisy daemon[4370]:     at Module._load (node:internal/modules/cjs/loader:942:12)
Feb  1 19:08:06 eisy daemon[4370]:     at Module.require (node:internal/modules/cjs/loader:1127:19)
Feb  1 19:08:06 eisy daemon[4370]:     at require (node:internal/modules/helpers:112:18)
Feb  1 19:08:06 eisy daemon[4370]:     at bindings (/var/polyglot/node_modules/bindings/bindings.js:112:48)
Feb  1 19:08:06 eisy daemon[4370]:     at new Database (/var/polyglot/node_modules/better-sqlite3/lib/database.js:48:64)
Feb  1 19:08:06 eisy daemon[4370]:     at Database (/var/polyglot/node_modules/better-sqlite3/lib/database.js:11:10)
Feb  1 19:08:06 eisy daemon[4370]:     at Object.start (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/db.js:17:17)
Feb  1 19:08:06 eisy daemon[4370]:     at start (/var/polyglot/node_modules/@universaldevices/pg3x/bin/pg3.js:100:14)
Feb  1 19:08:06 eisy daemon[4370]:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Feb  1 19:08:06 eisy daemon[4370]: 2/1/2023, 19:08:06 [pg3] ^[[32minfo^[[39m: PG3 shutdown complete with code: 1
 

auger66 Advanced

auger66

Posted
Posted (edited)

Same PG3x problem on eisy.

I've had this pretty much every time after an IoX update. Usually an eisy systems settings reboot gets it back. Not this time. Repowering didn't work, either.

Edited by auger66
brians Advanced

brians

Posted
Posted

I tried at home on my MacBook and I can access AC at least on it. Both of my Windows 11 PCs cannot launch admin console though... something in this latest update makes not work with Windows 11 maybe? Can someone else check that is using Windows 11 please.

 

brians Advanced

brians

Posted
Posted (edited)

Ok I figured out that the Admin Console Cloud doesn't work and LAN connection works... must have selected differently by coincidence here... I confirm it works on Win 11 with LAN connection now.

PG3 still not working.

Maybe will try Zen17 seem if they actually fixed now.

Edit: I set parameter 2 and 3 to 10, did an update with interview, and even a replace with interview and I do not see separate sensor and relay nodes like there was before on Zooz 500 series dongle :( I did not exclude/include but the interview process should have done same and Zooz even says can do this eg. this is for a garage door, but parameter 2 and 3 values 4 and above should create extra sensor nodes.

Quote

If you're using a wired NC sensor on the S-C input side of the ZEN17, set parameters 2 and 3 to value 11 instead, then re-interview / re-configure the device. This will create 2 additional open/close entities for you to monitor the status of your garage door. Finally, set parameters 10 and 11 to value 0 to disable the input trigger so that the sensors changing state won't trigger the relays controlling the opener. 

 

Edited by brians
firstone Advanced

firstone

Posted
Posted
2 hours ago, tazman said:


Feb  1 19:08:06 eisy daemon[4370]: 2/1/2023, 19:08:06 [pg3] ^[[31merror^[[39m: Startup error. Shutting down: Error: The module '/var/polyglot/node_modules/better-sqlite3/build/Release/better_sqlite3.node'
Feb  1 19:08:06 eisy daemon[4370]: was compiled against a different Node.js version using
Feb  1 19:08:06 eisy daemon[4370]: NODE_MODULE_VERSION 108. This version of Node.js requires
Feb  1 19:08:06 eisy daemon[4370]: NODE_MODULE_VERSION 111. Please try re-compiling or re-installing
Feb  1 19:08:06 eisy daemon[4370]: the module (for instance, using `npm rebuild` or `npm install`).
 

I have the same thing. Node seems to be upgraded from 18 to 19 and upgrading this package fails as well.  This update definitely breaks both, pg3 and pg3x.

Chris Jahn Advanced

Chris Jahn

Posted
  • Author
Posted

Hello Everyone,

We had a glitch in the build process for the is build and based on your reports it seems to have affected PG3x.   We're looking at it and will hopefully have a fix very soon.

 

  • Like 1
  • Thanks 1
Chris Jahn Advanced

Chris Jahn

Posted
  • Author
Posted
9 hours ago, brians said:

Ok I figured out that the Admin Console Cloud doesn't work and LAN connection works... must have selected differently by coincidence here... I confirm it works on Win 11 with LAN connection now.

PG3 still not working.

Maybe will try Zen17 seem if they actually fixed now.

Edit: I set parameter 2 and 3 to 10, did an update with interview, and even a replace with interview and I do not see separate sensor and relay nodes like there was before on Zooz 500 series dongle :( I did not exclude/include but the interview process should have done same and Zooz even says can do this eg. this is for a garage door, but parameter 2 and 3 values 4 and above should create extra sensor nodes.

 

Hi Brian,

For the parameter values to take effect you have to either power cycle the ZEN17 and the do "Update with Interview", or, remove the ZEN17 and then add it back again.

I also noticed a bug introduced into our code that may affect interviewing a device for a second time if it was included using S2 security (i.e. it may be best to just remove / add it again).

After setting both parameter 2 and 3 to value 11 you should be seeing the additional nodes

brians Advanced

brians

Posted
Posted
1 hour ago, Chris Jahn said:

Hi Brian,

For the parameter values to take effect you have to either power cycle the ZEN17 and the do "Update with Interview", or, remove the ZEN17 and then add it back again.

I also noticed a bug introduced into our code that may affect interviewing a device for a second time if it was included using S2 security (i.e. it may be best to just remove / add it again).

After setting both parameter 2 and 3 to value 11 you should be seeing the additional nodes

Ok I’ll try that after work today. 

brians Advanced

brians

Posted
Posted (edited)

When I reboot Polisy, PG3 and AC do not sync and have to restart PG3 manually after a full Polisy restart. I have done this twice with same results.

Edited by brians
spelling
ronbo Experienced

ronbo

Posted
Posted (edited)

@Chris Jahn PG3 starts but does see IOX. Tried a reboot of Polisy... same problem

PG3 Version 3.1.17
Status: Connected
Frontend Version: 3.1.17
ISY Version: 5.5.5   Disconnected
Uptime: 15 Minute(s) 59 Second(s)

 

2/2/2023, 24:01:50 [pg3] error: No code in error response 2/2/2023, 24:01:50 [pg3] warn: ISY Response: [Try: 1] [00:0d:b9:5e:df:dc] :: [401 - OK] :: 6.113249ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 2/2/2023, 24:01:50 [pg3] error: No code in error response 2/2/2023, 24:01:50 [pg3] warn: ISY Response: [Try: 2] [00:0d:b9:5e:df:dc] :: [401 - OK] :: 10.221074ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 2/2/2023, 24:01:50 [pg3] error: No code in error response 2/2/2023, 24:01:50 [pg3] warn: ISY Response: [Try: 3] [00:0d:b9:5e:df:dc] :: [401 - OK] :: 4.950628ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 2/2/2023, 24:01:50 [pg3] error: No code in error response 2/2/2023, 24:01:50 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:0d:b9:5e:df:dc] :: [401 - OK] :: 4.781022ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 2/2/2023, 24:01:50 [pg3] error: Error: GET http://127.0.0.1:8080/rest/profiles/ns/0/connection Failed :: 401 - OK 2/2/2023, 24:01:50 [pg3] error: getExistingNodeServers :: Error: Received no response from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/isy/system.js:93:13) at async /var/polyglot/node_modules/@universaldevices/pg3/lib/services/isy.js:80:21 at async Promise.allSettled (index 0)

Edited by ronbo
ronbo Experienced

ronbo

Posted
Posted

@brians I got mine to work. In my case the issue was that I changed my IOX password a few days ago.  I had to update by ISY info in PG3 and I am back up and running

brians Advanced

brians

Posted
Posted (edited)

@ronbo I went into PG3 and just entered the ISY password again and reboot everything and is working now. I don't use the default password so maybe was reset back to admin or whatever default is.

Either glitch or coincidence dunno :)

 

Edited by brians
  • Like 2
Guest
This topic is now closed to further replies.
Go to topic listing
×
×
  • Create New...