dwengrovitz Posted January 6, 2023 Posted January 6, 2023 4 minutes ago, ISY4Me said: I am not sure what else to try... I have an active ticket on this issue and it has been updated with this issue. I can't remember the exact steps I went through, but I also had some issues that I think were caused because my connection to the portal wasn't active. Just out of curiosity, does your Portal Integration show as being online?
ISY4Me Posted January 6, 2023 Posted January 6, 2023 1 minute ago, dwengrovitz said: I can't remember the exact steps I went through, but I also had some issues that I think were caused because my connection to the portal wasn't active. Just out of curiosity, does your Portal Integration show as being online? Yes it is... and to be assured it was active I was logged into it in a separate window. Hopefully @Michel Kohanim has an easy solution or suggestion.
asbril Posted January 6, 2023 Posted January 6, 2023 50 minutes ago, ISY4Me said: @asbriland @dwengrovitzYes I did. I even removed the Portal UUID item that was there for the EISY, logged out and went back into the Portal and added it just as you showed. Even then the approval in AC -> Configuration -> Portal still failed. I am not sure what else to try... I have an active ticket on this issue and it has been updated with this issue. Funny thing just happened..... I clicked on the upgrade packages and I was no longer able to access the PG3. I first deleted thei from my Portal and added it again, and when I wanted to Approve, I got the same bad error message as you. I power cycled my eisy and then the Approve worked. Now I am on 3.1.18
ISY4Me Posted January 6, 2023 Posted January 6, 2023 7 minutes ago, asbril said: Funny thing just happened..... I clicked on the upgrade packages and I was no longer able to access the PG3. I first deleted thei from my Portal and added it again, and when I wanted to Approve, I got the same bad error message as you. I power cycled my eisy and then the Approve worked. Now I am on 3.1.18 I have tried rebooting from the local terminal, power cycling and a few other things and the approval continues to fail... but I have not given up.
asbril Posted January 6, 2023 Posted January 6, 2023 (edited) 6 minutes ago, ISY4Me said: I have tried rebooting from the local terminal, power cycling and a few other things and the approval continues to fail... but I have not given up. I like your optimism 😁 Edited January 6, 2023 by asbril
ISY4Me Posted January 6, 2023 Posted January 6, 2023 42 minutes ago, asbril said: I like your optimism 😁 Well, I was finally able to get it approved. @bpwwer had indicated earlier that a license was not required for PG3x to function, but the EISY required a license to get that communication to the Portal to approve. So, I installed the trial and activated it in the AC after a power cycle. Sadly, approving the communication did not impact the "IoX not found" and the "Not connected to the server" in PG3x and it also can not be manually added. Time to update my ticket.
asbril Posted January 6, 2023 Posted January 6, 2023 3 minutes ago, ISY4Me said: Well, I was finally able to get it approved. @bpwwer had indicated earlier that a license was not required for PG3x to function, but the EISY required a license to get that communication to the Portal to approve. So, I installed the trial and activated it in the AC after a power cycle. Sadly, approving the communication did not impact the "IoX not found" and the "Not connected to the server" in PG3x and it also can not be manually added. Time to update my ticket. A real saga. The double evolution of eisy and the ZMatter board, plus the PG3 update, comes with a lot of challenges and I am sure that the UD team is on top of it all. The issues that we are going through, or at least some of these, will help the UD team to identify and resolve problems. At times it can frustrate us but we need to be patient (like you) and I'm sure that it will all be resolved soon. 1
dbuss Posted January 6, 2023 Posted January 6, 2023 When I attempt to log into PG3 on my eisy, i get the attached error.
ISY4Me Posted January 6, 2023 Posted January 6, 2023 6 minutes ago, dbuss said: When I attempt to log into PG3 on my eisy, i get the attached error. I think I have seen that error once, but I can't comment on what was unique about that day. I can only recommend making sure you are using the right URL or start PG3x from the Launcher and see if the response is different. I have never had the error persist, so it is essentially I can't comment on exactly what I did to make it go away.
dbuss Posted January 6, 2023 Posted January 6, 2023 3 minutes ago, ISY4Me said: I think I have seen that error once, but I can't comment on what was unique about that day. I can only recommend making sure you are using the right URL or start PG3x from the Launcher and see if the response is different. I have never had the error persist, so it is essentially I can't comment on exactly what I did to make it go away. I appreciate your response. The URL is correct. I've attempted to connect to PG3 by entering the address in a browser, using the launcher, and directly from the AC.
asbril Posted January 6, 2023 Posted January 6, 2023 4 minutes ago, dbuss said: I appreciate your response. The URL is correct. I've attempted to connect to PG3 by entering the address in a browser, using the launcher, and directly from the AC. I just had exactly the same issue. From one moment to the other the eisy PG3 3.1.18 did not open and I got the same error message. I tried reboot and power cycle, but this time no luck until I went to another computer and connected to PG3 without a problem. And then on the first computer I was also able to connect. This has never happened with my Polisy PG3, so I wonder whether there is a bug in 3.1.17 and 3.1.18. If @bpwwer wants I can send him another log as yesterday my log did not show him the issue.
dbuss Posted January 6, 2023 Posted January 6, 2023 26 minutes ago, asbril said: I tried reboot and power cycle, but this time no luck until I went to another computer and connected to PG3 without a problem. And then on the first computer I was also able to connect. @asbrilI just tried another computer and logged into PG3 just fine. I went back to original computer and am unable to connect. I restarted the computer and still unable to connect.
asbril Posted January 6, 2023 Posted January 6, 2023 11 minutes ago, dbuss said: @asbrilI just tried another computer and logged into PG3 just fine. I went back to original computer and am unable to connect. I restarted the computer and still unable to connect. Something is definitely wrong somewhere and I hope that @bpwwer can find out. On the computer that works, try to restart PG3.
bpwwer Posted January 6, 2023 Author Posted January 6, 2023 4 hours ago, dbuss said: When I attempt to log into PG3 on my eisy, i get the attached error. Do you have the option to log out on the menu? If so, try that and then try to log in again.
dbuss Posted January 6, 2023 Posted January 6, 2023 30 minutes ago, bpwwer said: Do you have the option to log out on the menu? If so, try that and then try to log in again. I logged out and I get the same error when trying to log back in. I've cleared my browser cache and tried a different browser with the same result. I've also restarted the computer. PG3 on eisy works fine on another computer and it worked fine on this computer until today.
asbril Posted January 6, 2023 Posted January 6, 2023 35 minutes ago, bpwwer said: Do you have the option to log out on the menu? If so, try that and then try to log in again. That seems to work
bpwwer Posted January 6, 2023 Author Posted January 6, 2023 2 minutes ago, dbuss said: I logged out and I get the same error when trying to log back in. I've cleared my browser cache and tried a different browser with the same result. I've also restarted the computer. PG3 on eisy works fine on another computer and it worked fine on this computer until today. I wasn't sure if logging out/back in would solve this. Guess not. That's strange that it works from one computer but not another. If you open the javascript console (developer tools) on the one that's not working is there any more details on the error?
dbuss Posted January 6, 2023 Posted January 6, 2023 22 minutes ago, bpwwer said: I wasn't sure if logging out/back in would solve this. Guess not. That's strange that it works from one computer but not another. If you open the javascript console (developer tools) on the one that's not working is there any more details on the error? Does the attached screenshot tell you anything?
bpwwer Posted January 6, 2023 Author Posted January 6, 2023 15 minutes ago, dbuss said: Does the attached screenshot tell you anything? Unfortunately not. Did you attempt to log in after opening the javascript console? If not try logging in with the console open. You may have to scroll up to see all of it outputs. I'm looking for an error message related to "/auth". The errors in the screen shot are "normal", in that it is trying to use information it gets from PG3 to format the menus, but because it isn't logged in, it doesn't have that info from PG3 yet.
dbuss Posted January 6, 2023 Posted January 6, 2023 2 minutes ago, bpwwer said: If not try logging in with the console open. I will try this tomorrow. I have to go watch my granddaughters play basketball tonight. Thank you!
dbuss Posted January 7, 2023 Posted January 7, 2023 (edited) 16 hours ago, bpwwer said: If not try logging in with the console open Does the attached screenshot tell you anything? This morning I am unable to log into PG 3X on either computer using three different browsers. Update: After removing power from my eisy and then adding power, I can now log in to PG 3X on the eisy. Edited January 7, 2023 by dbuss
bpwwer Posted January 7, 2023 Author Posted January 7, 2023 4 hours ago, dbuss said: Does the attached screenshot tell you anything? This morning I am unable to log into PG 3X on either computer using three different browsers. Update: After removing power from my eisy and then adding power, I can now log in to PG 3X on the eisy. Maybe. I notice you're using https. With that the browser needs to be told to trust the certificate from PG3x. If it doesn't trust it, it will likely simply not actually make the request which may explain the "empty response" error. If PG3x responds, the response can't be empty. If it happens again, try changing to regular http to access PG3x and see if that works. Unless you have some reason to not trust communication on your local network, I don't believe using https is necessary. In the meantime I can try with https and see if I can reproduce the problem.
auger66 Posted January 19, 2023 Posted January 19, 2023 eISY .20 I get this popup about every 30 seconds. This didn't happen repeatedly with previous versions. Also, my ST-Sonos shows connected with one node for the first time ever on eisy. It still doesn't work, though.
glarsen Posted January 19, 2023 Posted January 19, 2023 (edited) 1 hour ago, auger66 said: eISY .20 I get this popup about every 30 seconds. This didn't happen repeatedly with previous versions. Also, my ST-Sonos shows connected with one node for the first time ever on eisy. It still doesn't work, though. Seeing the same thing with ST-Sonos (same for ST-NuHeat). PG3x 3.1.20 also. No node server log, not much in the pg3x log (attached): 1/19/2023, 14:46:51 [pg3] info: Installing ST-Sonos on IoX 1/19/2023, 14:46:51 [pg3] info: [00:21:b9:02:62:8f_24] 'ST-Sonos' installed into ISY successfully... 1/19/2023, 14:46:51 [pg3] info: Installing ST-Sonos's profile files on IoX 1/19/2023, 14:46:51 [pg3] info: installProfile: ST-Sonos :: read /var/polyglot/pg3/ns/0021b902628f_24/profile/nodedef 1/19/2023, 14:46:51 [pg3] info: Uploading nodedefs.xml 1/19/2023, 14:46:51 [pg3] info: installProfile: ST-Sonos :: read /var/polyglot/pg3/ns/0021b902628f_24/profile/editor 1/19/2023, 14:46:51 [pg3] info: Uploading editors.xml 1/19/2023, 14:46:51 [pg3] info: installProfile: ST-Sonos :: read /var/polyglot/pg3/ns/0021b902628f_24/profile/nls 1/19/2023, 14:46:51 [pg3] info: Uploading en_US.txt 1/19/2023, 14:46:51 [pg3] info: Installation complete. Starting ST-Sonos 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos is valid 1/19/2023, 14:46:51 [pg3] info: upload successful 1/19/2023, 14:46:51 [pg3] info: upload successful 1/19/2023, 14:46:51 [pg3] info: checkLicense:: ST-Sonos Valid subscription license found. Expires: 2023-01-25T18:22:45.000Z 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos finished update check 1/19/2023, 14:46:51 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos starting polls 1/19/2023, 14:46:51 [pg3] info: Checking if ${Node Server.name} has expired 1/19/2023, 14:46:51 [pg3] info: Starting Node Server Info timer 0 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos updating database (enabled, timestarted) 1/19/2023, 14:46:51 [pg3] info: upload successful 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set customparams 1/19/2023, 14:46:52 [pg3] error: No code in error response 1/19/2023, 14:46:52 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:62:8f] :: [404 - OK] :: 41.833657ms - http://127.0.0.1:8080/rest/nodes/n024_controller 1/19/2023, 14:46:52 [pg3] warn: node controller on profile 00:21:b9:02:62:8f/24 not in the database. Adding... 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] adding node controller to ISY 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] addnode sucessfully added node controller 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:46:56 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:46:56 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:01 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:01 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:05 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:05 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:09 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:09 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:14 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:14 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:18 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:18 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:22 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:22 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:23 [pg3] info: Starting log stream for pg3frontend_JX4GN :: /var/polyglot/pg3/ns/0021b902628f_24/logs/debug.log 1/19/2023, 14:47:27 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:27 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:29 [pg3] info: Verifying node servers are installed on IoX correctly 1/19/2023, 14:47:29 [pg3] info: IoX entry for ELK::3 OK 1/19/2023, 14:47:29 [pg3] info: IoX entry for ST-Sonos::24 OK 1/19/2023, 14:47:30 [pg3] warn: stopLogging: unwatch failed, TypeError: Cannot read properties of undefined (reading 'pg3frontend_JX4GN') 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparams 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparamsdoc 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved notices 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved oauth 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparams 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparamsdoc 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved notices 1/19/2023, 14:47:31 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:31 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:32 [pg3] info: Starting log stream for pg3frontend_1XRrL :: /var/polyglot/pg3/ns/0021b902628f_24/logs/debug.log 1/19/2023, 14:47:36 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:36 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:40 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:40 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:44 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:44 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:49 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:49 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:52 [pg3] warn: stopLogging: unwatch failed, TypeError: Cannot read properties of undefined (reading 'pg3frontend_1XRrL') 1/19/2023, 14:47:52 [pg3] info: set to expire on 2023-01-25T18:22:45.000Z Edited January 19, 2023 by glarsen
bpwwer Posted January 19, 2023 Author Posted January 19, 2023 1 hour ago, auger66 said: eISY .20 I get this popup about every 30 seconds. This didn't happen repeatedly with previous versions. It should be at 5 minute intervals, not 30 seconds. But I've seen it do something like this before where the timer doesn't wait for the specified time. I wasn't seeing it happen at 30 second intervals, but I'm going upgrade everything and check again.
Recommended Posts