Jump to content

Problem issuing commands


TSinclair
Go to solution Solved by TSinclair,

Recommended Posts

I'm new to Node Servers but here is what I am experiencing.

I was able to connect the harmony hub node server to eisy.

I see all of my devices/automations

when I execute a command from the "main" tab for a device, I get "TCP client request failed [ISY:401]

when I execute a command from a program, nothing seems to happen

for either scenario I see the below on the PG3 log

What have I done wrong?

 
12/29/2022, 20:57:12 [pg3] error: ISY Inbound Status: UnauthorizedError: Unauthorized
at Object.throw (/var/polyglot/node_modules/koa/lib/context.js:97:11)
at checkAuth (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:29:56)
at getNodeserver (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:39:11)
at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:148:16
at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9

 

Link to comment

Unfortunately 3.1.18 did not resolve it.  Same behavior; TCP client request failed [ISY:401] and error below on PG3 log

 
1/5/2023, 20:51:48 [pg3] error: ISY Inbound Status: UnauthorizedError: Unauthorized
at Object.throw (/var/polyglot/node_modules/koa/lib/context.js:97:11)
at checkAuth (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:29:56)
at getNodeserver (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:39:11)
at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:148:16
at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9
Link to comment

Just for reference.  The error means that the configuration of the node server on the IoX (when you go to Node Servers -> Configure -> slot # -> <node server>) has an incorrect password.

When PG3 installs the node server on the IoX, it sets the password to an encrypted token, when the IoX sends a command to PG3/node server, PG3 checks that password to see if matches and if it doesn't, it throws that error.

Normally, this would mean that the node servers was installed on the IoX by a different PG3**.

 

** PG3 creates a unique identifier when it creates it's database for the first time.  Removing the database and restarting PG3 will create a new unique identifier and this will also cause the authentication to fail.

Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...