asbril Posted October 19, 2019 Share Posted October 19, 2019 2 hours ago, JoltDefries said: I finally decided to upgrade to 5.0.16 and am having a couple really annoying issues. Admin console is really slow but it is only for Z-wave devices. Even something simple like right clicking a device to pull up the menu to rename/etc. is super slow. This happens on any Z-wave device regardless of manufacturer. Insteon devices respond quickly in admin console though. I have tried the Java thing by clearing cache and increasing amount of memory it uses but it has not helped with this issue. Also I had programs for my ZooZ ZEN 21 switches that I used to mimic a 3-way switch even though both switches were wired as single pole to the same load source and those programs do not work any more after upgrading. I came from 4.7.3 if that matters at all. Everything else seems to work well other than these 2 things. Any ideas on what I might be doing wrong? I have the ISY994i Pro with Z-Wave and an Insteon PLM running the firmware "Insteon_UD994 v5.0.16". Thanks in advance! I am not the most technologically advanced and others are much smarter than I am, but I believe that when going from 4.X to 5.0.16, you may have to go first to 5.01, or another earlier version. As said, others may know better. Link to comment
larryllix Posted October 19, 2019 Share Posted October 19, 2019 I think one version of v5.x I just reinstalled the same version again, and it cleans things up. It could be worth try. Just a bad install? Link to comment
JoltDefries Posted October 19, 2019 Share Posted October 19, 2019 yah i tried a reinstall of 5.0.16 because i thought the same thing but no luck. wonder if i need to go down to some earlier version of 5.x before going back to 16 since I might have gone from 4.7.3 right to 5.0.16 Link to comment
hart2hart Posted October 19, 2019 Share Posted October 19, 2019 yah i tried a reinstall of 5.0.16 because i thought the same thing but no luck. wonder if i need to go down to some earlier version of 5.x before going back to 16 since I might have gone from 4.7.3 right to 5.0.16 I doubt that’s the issue. I and many others went direct from 4.7.3 to 5.015A. 1 Link to comment
smacbride Posted October 19, 2019 Share Posted October 19, 2019 So I just did the upgrade from 4.7.3 to 5.0.16 and it took a few minutes and was pretty seamless. All of my programs converted over without issue. I have noticed that right clicking on the Zwave nodes takes about 2 seconds for the menu to pop up vs. instantaneously for the Insteon nodes. I'm running the console on an Intel core i7 windows 10 box. Link to comment
CJVann Posted October 19, 2019 Share Posted October 19, 2019 Right clicking an Insteon device in the Admin Console, (Advanced / PLM Communication) always causes a 'TCP client request failed' error. FW & UI = V.5.0.16, 994i/IR PRO Link to comment
JoltDefries Posted October 19, 2019 Share Posted October 19, 2019 @smacbride I am having the same exact issue after the upgrade to 5.0.16. Any zwave device takes a bit to pop up after right clicking it but any insteon device is instant Link to comment
BoomerangThree Posted October 19, 2019 Share Posted October 19, 2019 (edited) CJVann, I have had a few of these with my devices, very few and after a couple retries by changing an attribute the communication is restored and the error goes away. I've been thinking that its just interference, or just a network error or the Insteon device finally establish a connection. So, what I guess I'm getting to is have you tried bringing the light inside and seeing if you can connect. Communication distance error that might be solved by bringing it closer, letting it establish a link and then taking it back outside. Just a thought trying to assist. Edited October 19, 2019 by BoomerangThree Link to comment
brians Posted October 20, 2019 Share Posted October 20, 2019 I have upgraded from 5.0.15A and Z-Wave devices also take a couple seconds right clicking. I don't have any issues with programs however and I have a couple z-wave outlets as responders from Insteon KeypadLinc buttons and works fine. Link to comment
simplextech Posted October 20, 2019 Share Posted October 20, 2019 Reporting in the same slow response with right-click on z-wave devices. Link to comment
CJVann Posted October 20, 2019 Share Posted October 20, 2019 23 hours ago, BoomerangThree said: CJVann, I have had a few of these with my devices, very few and after a couple retries by changing an attribute the communication is restored and the error goes away. I've been thinking that its just interference, or just a network error or the Insteon device finally establish a connection. So, what I guess I'm getting to is have you tried bringing the light inside and seeing if you can connect. Communication distance error that might be solved by bringing it closer, letting it establish a link and then taking it back outside. Just a thought trying to assist. Thanks for the reply, Boomerang. I can communicate with the device (turn it on/off) but I am not able to reprogram it (change the default number of communications retries). Every device I try that on gives the Client Request Failed error. Link to comment
JP Posted October 20, 2019 Share Posted October 20, 2019 I just upgraded to 5.0.16 from 4.7.3 and everything went as planned. I had to save my programs to correctly update the Program Statues page but that was nothing. JP Link to comment
TrojanHorse Posted October 21, 2019 Share Posted October 21, 2019 I believe I found a bug or at least something that needs to be checked manually when upgrading. I'm not sure if this happened with 5.0.16 or with an earlier version of the 5.x firmware. The programs ran fine in 4.x. I have a couple programs with Insteon thermostats (2441TH) that reference the current temperature in the "IF" section. These were not evaluating / triggering correctly. They were evaluating false when clearly they were true. To fix, I edited the program and changed the value for the temperature, saved it, and changed it back. They now are working correctly. Anyone else have this issue? If you are using Insteon thermostats for anything mission critical you may want to look closely at any programs that reference them. Seemed to be a problem for me when they were referencing the current temperature. I'm glad I don't use these for my main HVAC. I'm assuming this is related to the 5.x firmware, but I never saw it mentioned by anyone. This also makes me worried about what else may be lurking that I don't know about... Link to comment
Chris Jahn Posted October 21, 2019 Share Posted October 21, 2019 On 10/19/2019 at 11:28 PM, brians said: I have upgraded from 5.0.15A and Z-Wave devices also take a couple seconds right clicking. I don't have any issues with programs however and I have a couple z-wave outlets as responders from Insteon KeypadLinc buttons and works fine. The speed will depend on your network connection to the ISY. The Admin Console gets various current Z-Wave settings to properly populate and build the popup menu. I'll add this to the list to see if we can improve performance, not sure when it will be prioritized though. Link to comment
smacbride Posted October 21, 2019 Share Posted October 21, 2019 2 hours ago, TrojanHorse said: I believe I found a bug or at least something that needs to be checked manually when upgrading. I'm not sure if this happened with 5.0.16 or with an earlier version of the 5.x firmware. The programs ran fine in 4.x. I have a couple programs with Insteon thermostats (2441TH) that reference the current temperature in the "IF" section. These were not evaluating / triggering correctly. They were evaluating false when clearly they were true. To fix, I edited the program and changed the value for the temperature, saved it, and changed it back. They now are working correctly. Anyone else have this issue? If you are using Insteon thermostats for anything mission critical you may want to look closely at any programs that reference them. Seemed to be a problem for me when they were referencing the current temperature. I'm glad I don't use these for my main HVAC. I'm assuming this is related to the 5.x firmware, but I never saw it mentioned by anyone. This also makes me worried about what else may be lurking that I don't know about... Yep, I had the same issue, had to go in and update any programs that set thermostats or used temperatures, then re-save them. Link to comment
TrojanHorse Posted October 22, 2019 Share Posted October 22, 2019 1 hour ago, smacbride said: Yep, I had the same issue, had to go in and update any programs that set thermostats or used temperatures, then re-save them. Was this noted somewhere or did you discover it on your own? Link to comment
smacbride Posted October 22, 2019 Share Posted October 22, 2019 14 hours ago, TrojanHorse said: Was this noted somewhere or did you discover it on your own? I just tried it as a debugging option to see if I could get them to work again. I also noticed that the temperature values now have decimal points in them, which might have been the reason it didn't work without the change. Biggest problem with the decimal points is that Mobilinc in landscape mode doesn't show the current temperatures correctly. Link to comment
TrojanHorse Posted October 22, 2019 Share Posted October 22, 2019 1 minute ago, smacbride said: I just tried it as a debugging option to see if I could get them to work again. I also noticed that the temperature values now have decimal points in them, which might have been the reason it didn't work without the change. Biggest problem with the decimal points is that Mobilinc in landscape mode doesn't show the current temperatures correctly. I noticed the decimals too. Didn't see any other mention of it. Link to comment
TrojanHorse Posted October 22, 2019 Share Posted October 22, 2019 4 minutes ago, smacbride said: I just tried it as a debugging option to see if I could get them to work again. I also noticed that the temperature values now have decimal points in them, which might have been the reason it didn't work without the change. Biggest problem with the decimal points is that Mobilinc in landscape mode doesn't show the current temperatures correctly. THIS IS ME WAVING MY ARMS ON THE INTERNET TRYING TO DRAW ATTENTION TO THIS PROBLEM!! There could be some very cold customers soon as the weather changes... With respect, the biggest problem here is that the programs don't run, not how it looks on Mobilinc. What's the best way to note this for people that have already upgraded? Checking these types of programs should be added to the list of things to do (e.g. confirm "run at startup", etc.) when upgrading. Link to comment
smacbride Posted October 22, 2019 Share Posted October 22, 2019 1 hour ago, TrojanHorse said: THIS IS ME WAVING MY ARMS ON THE INTERNET TRYING TO DRAW ATTENTION TO THIS PROBLEM!! There could be some very cold customers soon as the weather changes... With respect, the biggest problem here is that the programs don't run, not how it looks on Mobilinc. What's the best way to note this for people that have already upgraded? Checking these types of programs should be added to the list of things to do (e.g. confirm "run at startup", etc.) when upgrading. Good Point! Link to comment
lilyoyo1 Posted October 22, 2019 Share Posted October 22, 2019 (edited) 1 hour ago, TrojanHorse said: THIS IS ME WAVING MY ARMS ON THE INTERNET TRYING TO DRAW ATTENTION TO THIS PROBLEM!! There could be some very cold customers soon as the weather changes... With respect, the biggest problem here is that the programs don't run, not how it looks on Mobilinc. What's the best way to note this for people that have already upgraded? Checking these types of programs should be added to the list of things to do (e.g. confirm "run at startup", etc.) when upgrading. People just have to read the instructions thoroughly. It says to verify your programs in the instructions: After upgrading: o Please ensure your device nodes and programs are correct; in some cases you may need to update them. Edited October 22, 2019 by lilyoyo1 1 Link to comment
TrojanHorse Posted October 22, 2019 Share Posted October 22, 2019 Another worthless response from the lil guy... Link to comment
TrojanHorse Posted October 22, 2019 Share Posted October 22, 2019 9 minutes ago, lilyoyo1 said: People just have to read the instructions thoroughly. It says to verify your programs in the instructions: After upgrading: o Please ensure your device nodes and programs are correct; in some cases you may need to update them. I will also note that it appears you went back and edited your post to add the snarky first sentence. Thank you for taking time out of your personal/professional/family time to "help" by going back to add sarcastic comments to an originally unhelpful post. We are all so appreciative of your help, insight, and generally pleasant demeanor. 2 Link to comment
lilyoyo1 Posted October 22, 2019 Share Posted October 22, 2019 (edited) 10 minutes ago, TrojanHorse said: I will also note that it appears you went back and edited your post to add the snarky first sentence. Thank you for taking time out of your personal/professional/family time to "help" by going back to add sarcastic comments to an originally unhelpful post. We are all so appreciative of your help, insight, and generally pleasant demeanor. Your welcome. I'm actually adding to my comment this time. While it may appear my post was unhelpful there is truth to it even if you don't like it. You claimed something that wasn't true. UDI generally does a great job of providing pertinent information when it comes to their upgrades Edited October 22, 2019 by lilyoyo1 3 Link to comment
TrojanHorse Posted October 22, 2019 Share Posted October 22, 2019 21 minutes ago, lilyoyo1 said: Your welcome. I'm actually adding to my comment this time. While it may appear my post was unhelpful there is truth to it even if you don't like it. You claimed something that wasn't true. UDI generally does a great job of providing pertinent information when it comes to their upgrades Um, you're hardly worth responding to, but help me understand what I claimed that isn't true? Link to comment
Recommended Posts