Cannot get the Hue Emulator to run on PG3

[oberkc]

While updating software for IoP (in preparation for moving from ISY-994), the node servers from PG2 (on policy) all became disconnected.  Based on advise from submitting a ticket with UDI, I am now trying to move to PG3.  Unfortunately, I cannot get the Hue Emulator to run on PG3, neither while connected to the legacy ISY-994 nor to IoP.  When I load the Hue Emulator while connected to the legacy ISY-994 I get a big red error: 

Node Server install of undefined failed with message: status is not defined

When I load it while connected to the IoP, it appears to actually load, but shows current status as disconnected.  

More details upon request.

Thoughts?

 

 

[Jimbo.Automates]

For either issue "Download Log Package" and PM it to me.

 

[oberkc]

2 hours ago, JimboAutomates said:

For either issue "Download Log Package" and PM it to me.

 

Would love to do so.  To where does the log package download go (not to downloads, apparently, on a Mac)?  Do you want the "debug" package or one of the others?

While I suspect there is a problem with the "log PACKAGE", it appears that I can download a "log" file.  I will PM to you.

FYI, the error I get when trying to install the 

Node Server install of undefined failed with message: status is not defined

 

[Jimbo.Automates]

14 minutes ago, oberkc said:

Would love to do so.  To where does the log package download go (not to downloads, apparently, on a Mac)?  Do you want the "debug" package or one of the others?

It goes to where ever your browser is configured to place downloads.

15 minutes ago, oberkc said:

While I suspect there is a problem with the "log PACKAGE", it appears that I can download a "log" file.  I will PM to you.

FYI, the error I get when trying to install the 

Node Server install of undefined failed with message: status is not defined

 

Yes, I saw that error in your post, but that doesn't help, I need to see the PG3 log, not the NS log to see what happened before that error.

[oberkc]

I will try to send it, but the message system is not accepting the file for some reason.  

[bpwwer]

@oberkcmake sure you're running the latest version of PG3.  There have been a couple of bug fixes since the 3.1.6 version and symptom sounds like one of them.

[Jimbo.Automates]

There are tons of errors in the PG3 log about permissions communicating with the ISY:

9/20/2022, 20:14:30 [pg3] error: Error: GET http://192.168.0.48:8080/rest/profiles/ns/0/connection Failed :: 401 - OK
9/20/2022, 20:14:30 [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:91:13)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:533:9)
    at process.processTimers (node:internal/timers:507:7)
    at async /var/polyglot/node_modules/@universaldevices/pg3/lib/services/isy.js:80:21
    at async Promise.allSettled (index 0)
9/20/2022, 20:14:30 [pg3] warn: verifyNodeServers (00:0d:b9:53:2b:bc) :: ISY has no node servers installed, skipping

 

[bpwwer]

A 401 error is authentication.   So it looks like communication is failing because it can't authenticate with the ISY/IoP. Double check the username and password in  PG3 -> ISYs -> Edit Current ISY

[oberkc]

Thanks for looking and finding the errors in the log.  I wish I knew what do to about such a revelation.

I can get the hue node server to run on PG3>IOP, so the connection seems to be working.  Unlike the Hue node server, the hue emulator, I notice, has fields for the ISY, which I have populated multiple times, and match the global PG3 settings for the ISY.

In the hue emulator, I notice that the port for ISY (8080) is the same as the port for the emulated hue (also 8080).  I assume that this is not a problem.

I also observer that I can install the hue emulator, I get the big red error message during installation, but the hue emulator still shows up on the dashboard (disconnected).  I can then populate the ISY fields under the configuration page, but after a few minutes, the dashboard no longer has the hue emulator.

FWIW, I also have a second ISY (the legacy ISY-994) running and recognized by PG3.  The results with the hue emulator are nearly identical.  Furthermore, the hue node server (as opposed to the emulator) will not connect (it DOES connect to the IoP).

Edited September 21, 2022 by oberkc

[Jimbo.Automates]

42 minutes ago, oberkc said:

Thanks for looking and finding the errors in the log.  I wish I knew what do to about such a revelation.

That's odd because those errors are from PG3 itself, not the Node server so unsure how any could be working.

 Near the very end of the PG3 log it shows errors contacting the ISY:

/20/2022, 20:14:30 [pg3] debug: [PUBLISH: udi/pg3/ns/clients/00:21:b9:00:ef:c2_2] {"shortPoll":{}}
9/20/2022, 20:14:30 [pg3] debug: [MESSAGE_PUBLISHED] Client pg3_client has published message on udi/pg3/ns/clients/00:21:b9:00:ef:c2_2 to broker pg3_broker
9/20/2022, 20:14:30 [pg3] error: No code in error response
9/20/2022, 20:14:30 [pg3] warn: ISY Response: [Try: 1] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 11.024519ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection
9/20/2022, 20:14:30 [pg3] error: No code in error response
9/20/2022, 20:14:30 [pg3] warn: ISY Response: [Try: 2] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 6.935924ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection
9/20/2022, 20:14:30 [pg3] error: No code in error response
9/20/2022, 20:14:30 [pg3] warn: ISY Response: [Try: 3] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 9.455622ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection
9/20/2022, 20:14:30 [pg3] debug: ISY Response: [Try: 1] [00:21:b9:00:ef:c2] :: [200] :: 56.488285ms - http://192.168.0.33:1026/rest/profiles/ns/0/connection
9/20/2022, 20:14:30 [pg3] error: No code in error response
9/20/2022, 20:14:30 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:0d:b9:53:2b:bc] :: [401 - OK] :: 18.126119ms - http://192.168.0.48:8080/rest/profiles/ns/0/connection
9/20/2022, 20:14:30 [pg3] info: ISY node server configuration update required
9/20/2022, 20:14:30 [pg3] debug: Scheduling http://192.168.0.33:1026/rest/profiles/ns/2/connection/set/network?ip=192.168.0.48&baseurl=%2Fns%2F00%3A21%3Ab9%3A00%3Aef%3Ac2_2&name=Hue&nsuser=00%3A21%3Ab9%3A00%3Aef%3Ac2&nspwd=Fx8VH%3FXivE05leIS&isyusernum=0&port=3000&timeout=0&ssl=true&enabled=true&sni=true to group system
9/20/2022, 20:14:30 [pg3] error: Error: GET http://192.168.0.48:8080/rest/profiles/ns/0/connection Failed :: 401 - OK
9/20/2022, 20:14:30 [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:91:13)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:533:9)
    at process.processTimers (node:internal/timers:507:7)
    at async /var/polyglot/node_modules/@universaldevices/pg3/lib/services/isy.js:80:21
    at async Promise.allSettled (index 0)
9/20/2022, 20:14:30 [pg3] warn: verifyNodeServers (00:0d:b9:53:2b:bc) :: ISY has no node servers installed, skipping
9/20/2022, 20:14:30 [pg3] debug: ISY Response: [Try: 1] [00:21:b9:00:ef:c2] :: [200] :: 114.915795ms - http://192.168.0.33:1026/rest/profiles/ns/2/connection/set/network?ip=192.168.0.48&baseurl=%2Fns%2F00%3A21%3Ab9%3A00%3Aef%3Ac2_2&name=Hue&nsuser=xxx&nspwd=xxx&isyusernum=0&port=3000&timeout=0&ssl=true&enabled=true&sni=true
9/20/2022, 20:14:30 [pg3] info: [00:21:b9:00:ef:c2_2] 'Hue' installed into ISY successfully...
9/20/2022, 20:14:30 [pg3] debug: >>>>>>>  Got isy ready event >>>>>>

 

45 minutes ago, oberkc said:

In the hue emulator, I notice that the port for ISY (8080) is the same as the port for the emulated hue (also 8080).  I assume that this is not a problem.

That is a problem, change the emulated hue to a different port when using IoP. It doesn't matter what as long as it's greater than 1000 but just use something like 8081.  I need to change the NS default since IoP decided to use the port that I was using as a default.

And you never answered @bpwwer

6 hours ago, bpwwer said:

@oberkcmake sure you're running the latest version of PG3.  There have been a couple of bug fixes since the 3.1.6 version and symptom sounds like one of them.

Make sure you are on the latest version of PG3 which is at 3.1.10 now.

[bpwwer]

Ah, I think I see part of the problem. It looks like you have two ISY's (or an ISY and an IoP) configured but one of them doesn't have a valid username/password set.  That's just making the log file a bit harder to read.

The ISY with UUID 00:0d:b9:53:2b:bc and IP address 192.168.0.48:8080 doesn't appear to be configured correctly in PG3 so PG3 is unable to communicate with it.  This looks like an IoP UUID.  Since it doesn't appear to be able to communicate, it's unclear how any node servers would be working with it.

The other looks like an ISY 994 but at a non-standard port 1026. However, it does appear to be communicating with PG3 and it looks like it was able to install the 'Hue' node server per the log.

As @JimboAutomatessays, trying to use port 8080 for the hue emulator will cause conflicts with IoP so that to is contributing to the issues.

 

[oberkc]

2 hours ago, JimboAutomates said:

That's odd because those errors are from PG3 itself, not the Node server so unsure how any could be working.

My whole experience with the IoP and PG3 has been odd (putting it kindly).  I had a working ISY-994>PG2.  I was preparing to migrate to IoP by updating the software of the IoP.  The results included breaking my ISY-994>PG2 relationship.

 

2 hours ago, JimboAutomates said:

And you never answered @bpwwer

I thought I had, but I can see it was not obvious, or perhaps answering the wrong question.  I have checked multiple times and my settings are correct as best I can tell.  Both show "connected".

 

2 hours ago, JimboAutomates said:

Make sure you are on the latest version of PG3 which is at 3.1.10 now.

I was on 3.1.8, but am now on 3.1.10.  It took me a few minutes to recognize that the update reset the username and password to default.  This did seem to have an affect.  Hue node servers are now showing connected on ISY-994 and IoP.  I tried installing the Hue Emulator node server on IoP and ISY-994.  No more errors and both are showing "connected".  I am going to call this a small victory.  The hue nodes now show up in "my lighting" , as does the hue emulator.  I will call it a big victory when I can confirm or configure all the programs and scenes with the hue lights.

 

1 hour ago, bpwwer said:

Ah, I think I see part of the problem. It looks like you have two ISY's (or an ISY and an IoP) configured but one of them doesn't have a valid username/password set.  That's just making the log file a bit harder to read.

Usernames are correct as best I can tell.  Both have been showing, and continue to show connected.  Both had some node servers working but others not.  But...the point may now be moot given that moving from PG3 v3.1.8 to 3.1.10 may have fixed the problem.  I will know more soon, but it all seems to be coming together now

 

1 hour ago, bpwwer said:

The other looks like an ISY 994 but at a non-standard port 1026.

The non-standard port was driven many years ago.  I had another device that also used port 80, so when I tried to access the ISY on port 80 from a remote location, it found the other device.  I gave the ISY it's own port at that time and things have been working well, so I never changed it back.

I will continue to check out everything to see if it is working or, if not, update all the programs and scenes to their original configuration.

[bpwwer]

15 hours ago, oberkc said:

I thought I had, but I can see it was not obvious, or perhaps answering the wrong question.  I have checked multiple times and my settings are correct as best I can tell.  Both show "connected".

Just FYI, there isn't any place on the frontend that shows the connected status of the ISY/IoP.  The "connected" badge in the footer represents the frontend UI to backend server connection, not the backend server connection to the ISY.

Right now the only way to tell if it is communicating properly with the ISY is by checking the log file.  Although adding a connected badge for the ISY isn't a bad idea.

[oberkc]

1 hour ago, bpwwer said:

Just FYI, there isn't any place on the frontend that shows the connected status of the ISY/IoP.  The "connected" badge in the footer represents the frontend UI to backend server connection, not the backend server connection to the ISY.

Right now the only way to tell if it is communicating properly with the ISY is by checking the log file.  Although adding a connected badge for the ISY isn't a bad idea.

Thanks for that bit of knowledge.  In an attempt at full disclosure, there was a short time where I had changed the default login credentials on the IoP and had yet to make the change to the PG3 settings.  I don't doubt that this created some log errors until I updated PG3.

I had two "ISY"s connected to PG3.  During all this difficulty I was having, my belief that both the ISY/IoP were connected was because there was at least one node server (not the Hue Emulator) on each that was appearing to work, and reflected in the admin console (the nodes were in the device listing, as well as under the drop down node server dialog box.)

Thanks for your help