bmercier Posted August 29, 2023 Share Posted August 29, 2023 Hello everyone, This is the support thread for PG3x v3.2.3. After updating to 3.2.3, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.2.0. If you were on PG3x 3.2.1+ and you already re-installed your node servers, there is no need to re-install them as there has been no changes to UDI Python interface with 3.2.2 or 3.2.3. Link to comment
gviliunas Posted August 30, 2023 Share Posted August 30, 2023 Upgraded from PG3x 3.2.2 to 3.2.3 with NO Problems. Everything working well. None of my "Disabled" programs were re-enabled this time during the upgrade. Yeah! Thanks for your hard work UDI Development Team!!! Link to comment
sumguy Posted August 30, 2023 Share Posted August 30, 2023 This update caused my Disabled programs to re-enable this time. But not last time. Didn't know this was a problem! My garage kept opening and closing repeatedly, my alarm wouldn't turn off, lights kept turning off. It was a mess for about 10+ minutes before I found all the re-enabled programs. WAF went down several notches tonight! Link to comment
Athlon Posted August 30, 2023 Share Posted August 30, 2023 Upgraded from 3.2.2 without issue. 😀 Link to comment
mbking Posted August 30, 2023 Share Posted August 30, 2023 @bmercier, Shortly after a successful upgrade of PG3 to 3.2.3, I noticed a change in IoX Launcher. It now shows 2 instances of my eisy and generates a Not Found error. The instances are the same except for the URL. The first one looks like this: https://eisy.local:8443/desc The second one replaces eisy.local with the actual IP address of eisy. Both instances launch eisy successfully via the cloud. I did some work within the Admin Console right after the upgrade and I did not see this behavior. But several hours later, I started seeing the 2 instances along with the error message. I'm not able to delete either instance. I'm curious what this might be and wondering if anyone else is seeing this. Maybe something changed on the back end. Mark Link to comment
Geddy Posted August 30, 2023 Share Posted August 30, 2023 5 hours ago, mbking said: https://eisy.local:8443/desc This is normal and expected. It's possible that you were using the IP address in the past and this time IoX Finder window actually found the local broadcast address for eisy.local and added it automatically. I've had "Not Found" display sometimes, but it usually goes away if you're local and on the same network. Unless your router is running some sort of VPN or VLAN setup it shouldn't be an issue. I've never let "Not Found" bother me if the addresses were there. It's more or less something goofed up in the cache. If you're worried about it you can clear the java cache, delete the UD*.state files (look for reference to these in the wiki) then download a fresh start.jnlp file and add the IoX Launcher to your desktop. More than likely you've got the IP address cached in the finder window and it automatically added the .local address when it found it today. Mine actually has 3 entries because I also have the UD Portal URL listed since I usually access from a laptop and have that address on hand so I can login when remote. As long as you're able to log in nothing you've seen is a concern. 1 Link to comment
mbking Posted August 31, 2023 Share Posted August 31, 2023 4 hours ago, Geddy said: This is normal and expected. It's possible that you were using the IP address in the past and this time IoX Finder window actually found the local broadcast address for eisy.local and added it automatically. I've had "Not Found" display sometimes, but it usually goes away if you're local and on the same network. Unless your router is running some sort of VPN or VLAN setup it shouldn't be an issue. I've never let "Not Found" bother me if the addresses were there. It's more or less something goofed up in the cache. If you're worried about it you can clear the java cache, delete the UD*.state files (look for reference to these in the wiki) then download a fresh start.jnlp file and add the IoX Launcher to your desktop. More than likely you've got the IP address cached in the finder window and it automatically added the .local address when it found it today. Mine actually has 3 entries because I also have the UD Portal URL listed since I usually access from a laptop and have that address on hand so I can login when remote. As long as you're able to log in nothing you've seen is a concern. @Geddy, Thanks for the reply. I cleared the Java cache, deleted the recommended files and downloaded the latest start file, but I still get the additional instance and the error message. As you said, as long as I can login, I'm good for now. I'm still hoping for a fix to clear it up. 1 Link to comment
DennisC Posted August 31, 2023 Share Posted August 31, 2023 9 hours ago, mbking said: I'm still hoping for a fix to clear it up. There is not going to be a fix for something that is normal and expected behavior. If eisy is discoverable on your network either as a local host or IP address, it will show up in the Launcher. Link to comment
4481hoods Posted August 31, 2023 Share Posted August 31, 2023 I am having problems accessing the isy dashboard. I receive a message "http failure response for https://192.168.2.60/auth: 503 Service unavailable" i think it happened when I tried to update node servers. I can Putty into Polisy with my normal passwords IOx seems to be working. UDI Mobile is working. Alexa is working. All the above work except for anything that uses the node servers. Can't restore because I can not get past this error message. Tried rebooting . Any suggestions? I need help!!!!!!! Link to comment
bmercier Posted August 31, 2023 Author Share Posted August 31, 2023 I am having problems accessing the isy dashboard. I receive a message "http failure response for https://192.168.2.60/auth: 503 Service unavailable" i think it happened when I tried to update node servers. I can Putty into Polisy with my normal passwords IOx seems to be working. UDI Mobile is working. Alexa is working. All the above work except for anything that uses the node servers. Can't restore because I can not get past this error message. Tried rebooting . Any suggestions? I need help!!!!!!! This means UDX is not responding. If no upgrades are underway, I would try to power cycle your eisy.Sent from my iPhone using Tapatalk 1 Link to comment
Geddy Posted August 31, 2023 Share Posted August 31, 2023 13 hours ago, mbking said: I still get the additional instance and the error message @mbking are you running any 3rd party anti-virus or firewall software? If so, disable anything running. If possible completely stop those systems (don't just snooze the anti-virus or firewall). Clear Java Cache (again) - make sure you select all 3 boxes (this removes the desktop icon for IoX Launcher) Delete UD*.state files (again - just to really clear stuff out!) Perform a full uninstall of Java (maybe using the Java removal tool on their site to remove any old versions of Java). Reinstall the current version of Java - if using Chrome to download it the best option is to perform an offline install (From here - https://www.java.com/en/download/manual.jsp) Run "start.jnlp" (make sure anti-virus and firewall programs are OFF) Run IoX Launcher Report back if this fixes it. Link to comment
EricBarish Posted August 31, 2023 Share Posted August 31, 2023 Only problem I had was it dropped my old Nodelink nodeserver that was in slot 2. Reinstalled and now working fine. Link to comment
mbking Posted September 1, 2023 Share Posted September 1, 2023 6 hours ago, Geddy said: @mbking are you running any 3rd party anti-virus or firewall software? If so, disable anything running. If possible completely stop those systems (don't just snooze the anti-virus or firewall). Clear Java Cache (again) - make sure you select all 3 boxes (this removes the desktop icon for IoX Launcher) Delete UD*.state files (again - just to really clear stuff out!) Perform a full uninstall of Java (maybe using the Java removal tool on their site to remove any old versions of Java). Reinstall the current version of Java - if using Chrome to download it the best option is to perform an offline install (From here - https://www.java.com/en/download/manual.jsp) Run "start.jnlp" (make sure anti-virus and firewall programs are OFF) Run IoX Launcher Report back if this fixes it. @Geddy, No luck. I followed all the steps and I'm still getting duplicates and the error message. Fortunately, I can still get to the Admin Console, but my engineering mind wants to solve the mystery. Link to comment
garybixler Posted September 2, 2023 Share Posted September 2, 2023 (edited) just updated to 3.2.3 and none of the node servers are connecting. Tried reloading packages, reloaded all server, rebooted several times but servers will not connect. All have these messages in the log. IoX version 5.6.4 023-09-02 14:04:47,331 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:48,633 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:50,318 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:52,331 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:54,262 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:56,512 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:58,824 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 Edited September 2, 2023 by garybixler Link to comment
garybixler Posted September 2, 2023 Share Posted September 2, 2023 Log from PGx 9/2/2023, 14:13:42 [pg3] info: Verifying node servers are installed on IoX correctly 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/1/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 21.203976ms - http://127.0.0.1:8080/rest/profiles/ns/1/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for WeatherLink::1 OK 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/2/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 9.988015ms - http://127.0.0.1:8080/rest/profiles/ns/2/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for VenstarCT::2 OK 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/3/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.175943ms - http://127.0.0.1:8080/rest/profiles/ns/3/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for WirelessTag::3 OK 9/2/2023, 14:13:42 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/4/connection 9/2/2023, 14:13:42 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 3.467582ms - http://127.0.0.1:8080/rest/profiles/ns/4/connection 9/2/2023, 14:13:42 [pg3] info: IoX entry for Notification::4 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/5/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.120451ms - http://127.0.0.1:8080/rest/profiles/ns/5/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for Wemo::5 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/6/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.248131ms - http://127.0.0.1:8080/rest/profiles/ns/6/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for WeatherBit::6 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/7/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.066712ms - http://127.0.0.1:8080/rest/profiles/ns/7/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for LiFX::7 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/8/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 6.318889ms - http://127.0.0.1:8080/rest/profiles/ns/8/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for iTach-IR::8 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/9/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.299228ms - http://127.0.0.1:8080/rest/profiles/ns/9/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for iTach-IR::9 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/10/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.103385ms - http://127.0.0.1:8080/rest/profiles/ns/10/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for Bond::10 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/11/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.026874ms - http://127.0.0.1:8080/rest/profiles/ns/11/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for Russound::11 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/12/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 3.36697ms - http://127.0.0.1:8080/rest/profiles/ns/12/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for TeslaEV::12 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/13/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.093063ms - http://127.0.0.1:8080/rest/profiles/ns/13/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for AVRemote::13 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/14/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.216399ms - http://127.0.0.1:8080/rest/profiles/ns/14/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for ELK::14 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/15/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.125973ms - http://127.0.0.1:8080/rest/profiles/ns/15/connection 9/2/2023, 14:13:43 [pg3] info: IoX entry for iTach-IR::15 OK 9/2/2023, 14:13:43 [pg3] info: IoX Request: [Try: 1] [00:21:b9:02:60:38] :: - http://127.0.0.1:8080/rest/profiles/ns/0/connection 9/2/2023, 14:13:43 [pg3] info: IoX Response: [Try: 1] [00:21:b9:02:60:38] :: [200] :: 2.447125ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection Link to comment
hart2hart Posted September 2, 2023 Share Posted September 2, 2023 just updated to 3.2.3 and none of the node servers are connecting. Tried reloading packages, reloaded all server, rebooted several times but servers will not connect. All have these messages in the log. IoX version 5.6.4 023-09-02 14:04:47,331 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:48,633 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:50,318 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:52,331 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:54,262 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:56,512 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-09-02 14:04:58,824 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30What version of pg3 did you upgrade from? If older than a couple ago, you need to reinstall all node servers per instructions. Link to comment
garybixler Posted September 2, 2023 Share Posted September 2, 2023 The previous version. I think it was 3.2.2 and 3.2.1 before that Link to comment
MBell Posted September 2, 2023 Share Posted September 2, 2023 I have ran into the same issue. None of my nodes will connect. They all show disconnected after updating from 3.2.2 to 3.2.3 I have confirmed PG3X is 3.2.3 IOX 5.6.4 If I go to UD mobile app/admin/configure portals, I get the following error message: "no LOCAL IP ADDRESS is set for the system. System name Eisy" I have confirmed the IOX is set to http://127.0.0.1:8080 Wonder what changed in 3.2.3 that was not an issue with 3.2.2? Anyone have any suggestions before I open a ticket? Link to comment
deholt Posted September 2, 2023 Share Posted September 2, 2023 1 hour ago, garybixler said: The previous version. I think it was 3.2.2 and 3.2.1 before that I am having the same difficulty. After upgrading 3.2.1 to 3.2.3 (complying with instructions to re-install and restart all NS), all of my previously functional NSs are reported disconnected. I have gone through the entire upgrade process 3 times (with soft reboot, hard reboot, and power down / remove power / reboot). What am I missing? Link to comment
Xathros Posted September 2, 2023 Share Posted September 2, 2023 Ditto. Just created a new thread on the subject before I discovered this thread. Sorry for muddying the waters. Here is the text of my other post: I saw the announcement for 3.2.3 and decided to upgrade packages. I waited 35 minutes then logged into PG3x to find all my node servers disconnected. I have tried restarting the node servers, reinstalling all node servers and finally a full system reboot but all remain disconnected. Any advice? Thanks in advance. -Xathros Link to comment
bmercier Posted September 3, 2023 Author Share Posted September 3, 2023 I'm not sure what the problem is with node servers not connecting. I can't see any change that would affect that. I suspect update package updated something else that may cause this problem. Until this is resolved, if you want to try a downgrade to 3.2.2: Download PG3x 3.2.2: https://universaldevices-my.sharepoint.com/:u:/g/personal/benoit_universal-devices_com/ETyQLncGwUdFkEvYT93duF0BTEwrHzMfoXQJjDyVvqYdhg?e=Y8Uuez Transfer this pkg to your eisy using a transfer tool such as winscp or mobaterm SSH to your eisy using a tool such as putty or mobaterm Go to the folder you transferred the pkg sudo pkg install -f pg3x-3.2.2.pkg sudo service udx restart If that does not work, you may want to power cycle. To troubleshoot this problem further, we need a ticket with a log showing a reboot followed by nodeservers not connecting. This needs to be at 3.2.3 (Before downgrading) Link to comment
MBell Posted September 3, 2023 Share Posted September 3, 2023 (edited) Quote Until this is resolved, if you want to try a downgrade to 3.2.2: Download PG3x 3.2.2: https://universaldevices-my.sharepoint.com/:u:/g/personal/benoit_universal-devices_com/ETyQLncGwUdFkEvYT93duF0BTEwrHzMfoXQJjDyVvqYdhg?e=Y8Uuez Transfer this pkg to your eisy using a transfer tool such as winscp or mobaterm SSH to your eisy using a tool such as putty or mobaterm Go to the folder you transferred the pkg sudo pkg install -f pg3x-3.2.2.pkg sudo service udx restart If that does not work, you may want to power cycle. Is there any chance you can be more detailed about how to perform this downgrade? I am familiar with ssh but have no idea how to add that pkg to my eisy? thank you, BTW, I opened a ticket with all of the logs you ask for. Edited September 3, 2023 by MBell P Link to comment
bmercier Posted September 3, 2023 Author Share Posted September 3, 2023 2 hours ago, MBell said: Is there any chance you can be more detailed about how to perform this downgrade? I am familiar with ssh but have no idea how to add that pkg to my eisy? thank you, BTW, I opened a ticket with all of the logs you ask for. I have reports that downgrading PG3x to 3.2.2 does not help. This means that during the upgrade packages process, something else gets updated and breaks. Willl need @Michel Kohanim's help to figure out what got updated and find a fix. Link to comment
bgrubb1 Posted September 3, 2023 Share Posted September 3, 2023 just a note I upgraded 3.2.2 to 3.2.3 no issues (on a Polisy) ...Barry Link to comment
Recommended Posts