epete Posted July 18, 2021 Posted July 18, 2021 I have been having trouble getting Local Admin Console to launch on my Surface Pro7. I have loaded the latest version of JRE 8.0.7.0. I have cleared the Java Cache (several times). Since I have Admin Console FW 5.3.0 loaded on my ISY, I am using the https://isy.universal-devices.com/start.jnlp Console. The problem I am seeing is a version mismatch stating I have Admin Console v.5.0.16C and ISY Firmware v.5.3.0. What step have I missed? By the way, I have no problem accessing using the same link from my HP Desktop PC.
lilyoyo1 Posted July 18, 2021 Posted July 18, 2021 31 minutes ago, epete said: I have been having trouble getting Local Admin Console to launch on my Surface Pro7. I have loaded the latest version of JRE 8.0.7.0. I have cleared the Java Cache (several times). Since I have Admin Console FW 5.3.0 loaded on my ISY, I am using the https://isy.universal-devices.com/start.jnlp Console. The problem I am seeing is a version mismatch stating I have Admin Console v.5.0.16C and ISY Firmware v.5.3.0. What step have I missed? By the way, I have no problem accessing using the same link from my HP Desktop PC. Use the launcher from the 5.3 upgrade post
epete Posted July 18, 2021 Author Posted July 18, 2021 That is where I got the launcher in the link above 7. Launch the 5.3.0 Admin Console and/or Dashboard by going to the following link: - https://isy.universal-devices.com/start.jnlp
epete Posted July 18, 2021 Author Posted July 18, 2021 I even tried using the ISY's IP address 192.168.1.11/admin.jnlp and see the same, so I am wondering if java is launching something else that is in memory
asbril Posted July 18, 2021 Posted July 18, 2021 (edited) my suggestion is for you to exactly follow the steps in 5.3.0 including clearing Java. I have made mistakes in the past by not following all steps. BTW why no straight to 5.3.3 ? Edited July 18, 2021 by asbril
epete Posted July 18, 2021 Author Posted July 18, 2021 2 hours ago, asbril said: my suggestion is for you to exactly follow the steps in 5.3.0 including clearing Java. I have made mistakes in the past by not following all steps. BTW why no straight to 5.3.3 ? ok, will try again. I have been on 5.3.0 since the beginning of the year. I only learned there was a 5.3.3 today when trying to connect with my Surface. I was not upgrading from 5.0.16C no matter what the software thinks I am doing.
epete Posted July 18, 2021 Author Posted July 18, 2021 3 hours ago, asbril said: my suggestion is for you to exactly follow the steps in 5.3.0 including clearing Java. I have made mistakes in the past by not following all steps. BTW why no straight to 5.3.3 ? ok, will try again. I have been on 5.3.0 since the beginning of the year. I only learned there was a 5.3.3 today when trying to connect with my Surface. I was not upgrading from 5.0.16C no matter what the software thinks I am doing.
epete Posted July 18, 2021 Author Posted July 18, 2021 ok, I think it was working all along. When launching I now see an Admin Console (LAN), Admin Console (Cloud) and Dashboard. I used to only see Admin Console and Dashboard. I was now using Admin Console (LAN) as I am local and this was and is giving me the mismatch. When I select Admin Console (Cloud) I can access. Not sure if this is a problem or not but at least I can connect again. Now that I have connected I have also upgraded to 5.3.3 2
asbril Posted July 18, 2021 Posted July 18, 2021 1 hour ago, epete said: ok, I think it was working all along. When launching I now see an Admin Console (LAN), Admin Console (Cloud) and Dashboard. I used to only see Admin Console and Dashboard. I was now using Admin Console (LAN) as I am local and this was and is giving me the mismatch. When I select Admin Console (Cloud) I can access. Not sure if this is a problem or not but at least I can connect again. Now that I have connected I have also upgraded to 5.3.3 I have not figured out yet the difference between local and cloud and I can connect with both. I assume that cloud is related to ISY moving to Polisy, but am not sure. My issue is that at least 50% of the time I get an error message ( 'ISY was not able to load nodes' , or something similar) when launching the AC and then I have to re-launch till it fully opens. At other times, the AC opens with only 100's or 0's instead of On or OFF. I think (and hope) that this will be resolved when ISY moves to Polisy and/or when Java is getting rid of.
MrBill Posted July 18, 2021 Posted July 18, 2021 1 hour ago, asbril said: I have not figured out yet the difference between local and cloud and I can connect with both. I assume that cloud is related to ISY moving to Polisy, but am not sure. see Michel's post in the thread below where I asked that question. 1 hour ago, asbril said: My issue is that at least 50% of the time I get an error message ( 'ISY was not able to load nodes' , or something similar) when launching the AC and then I have to re-launch till it fully opens. At other times, the AC opens with only 100's or 0's instead of On or OFF. I think (and hope) that this will be resolved when ISY moves to Polisy and/or when Java is getting rid of. You should open a ticket with UDI concerning that, I suspect there might be a timeout that you're hitting based on the size of your z-wave network. (very similar to what happened with Home Assistant after you upgraded to 2021.6 --Since @Javi had a thought in that thread that lead to the solution he may here also.) 2
epete Posted July 18, 2021 Author Posted July 18, 2021 I am also seeing the 'ISY was not able to load nodes'
asbril Posted July 19, 2021 Posted July 19, 2021 18 hours ago, MrBill said: see Michel's post in the thread below where I asked that question. You should open a ticket with UDI concerning that, I suspect there might be a timeout that you're hitting based on the size of your z-wave network. (very similar to what happened with Home Assistant after you upgraded to 2021.6 --Since @Javi had a thought in that thread that lead to the solution he may here also.) @Javi Does @MrBillhave a point in that my extensive Zwave network may the issue of my AC launch fail at least 50% of the time ? 1
Javi Posted July 20, 2021 Posted July 20, 2021 Hi Guys, Do you get errors with UD Mobile as well? We can narrow the issue (client/server) if only one client (AC/udMobile) has the issue. Timeout issue from the other thread relates to requesting Definition files (NodeDef). However, I believe the Admin Console (from jnlp) includes these files, which is one of the reasons Firmware and UI must match. UD Mobile does not include these (large) files in distribution and requests them during synchronization. Have you tried rebooting ISY and Polyglot? This may be needed after Node Server Changes to publish human readable values and may be the cause of 0s and 100s.
epete Posted July 20, 2021 Author Posted July 20, 2021 On 7/18/2021 at 7:18 PM, epete said: I am also seeing the 'ISY was not able to load nodes' My problem is now resolved, while the SW was cautioning not to power down the unit, that was the ultimate solution. A power cycle fixed all of my issues.
asbril Posted July 20, 2021 Posted July 20, 2021 21 hours ago, Javi said: Hi Guys, Do you get errors with UD Mobile as well? We can narrow the issue (client/server) if only one client (AC/udMobile) has the issue. Timeout issue from the other thread relates to requesting Definition files (NodeDef). However, I believe the Admin Console (from jnlp) includes these files, which is one of the reasons Firmware and UI must match. UD Mobile does not include these (large) files in distribution and requests them during synchronization. Have you tried rebooting ISY and Polyglot? This may be needed after Node Server Changes to publish human readable values and may be the cause of 0s and 100s. I never (or maybe almost never) have an issue loading UD Mobile (which is a real cool App). On the other hand, The AC launcher fails at least half of the time, sometimes with the message that it could not load the nodes and at other times it loads everything but with 100% or 0% instead of ON and OFF. Today I experienced with increasing -Xmx512m to -Xmx1024m. It may be my imagination but I believe that ISY loaded faster and I will observe whether the failing launches still occur. 1
Recommended Posts