mykroft77

My computer is not the issue, it's a 4.2Ghz Quad Core processor, I have a very capable machine as I am a software developer and use it extensively for development purposes. And if it's taking you 5-6 minutes to load in even your CPU, which is still decent, then it's not a very efficient process. We're not loading up Photoshop or some video editing platform that uses gigabytes of resources here (and even THAT loads faster on my machine)... just a simple UI interface to a hardware device. I can certainly use the HTTP port, but I am trying to setup a single point of access for my ISY for both inside and outside my home network and this will be exposed to the internet so I want to use SSL all the time, if I can. Well no I'm not trying to download the Admin console every time, I just cleared out my Java apps/cache so that I would get a fresh copy against the new HTTPS URL since I had just setup my SSL cert in ISY Dashboard. The difference was staggering in the time it took to download, and then it took close to 20 minutes to get the UI to FULLY load and be usable. That pretty much makes it useless for me. And yes, as I replied above I can certainly use HTTP on my LAN since it's local anyway, but if it's going to take THIS long over my gigabit local LAN, it won't get any better over the internet from outside. I've worked with SSL certs before, it should never take a "long time" (in my case, it was minutes) to download a mere 15MB even with a 2048 bit SSL cert. What I am learning is that the hardware on the ISY has no accelerated encryption engine so it's doing it all on the main CPU, which is probably underpowered for performing this task. To me this suggests that having HTTPS\SSL as a feature on this product is not even a viable use case. One thing I did find out, was that Java wasn't completely trusting my SSL certificate for some reason. I have a Comodo multi-domain cert I setup with the ISY and I guess it didn't quite like the intermediate CA's in the chain, so I was able to install those intermediate certs in the Java settings as trusted and that made a big difference in the load times. It's still SLOW, but more usable... but not like it should be. Thank you all for your replies so far... has anyone gotten this to work efficiently or does everyone just give up and use HTTP? (Or bite the bullet and walk away from the console while it "loads"?)

I have setup an SSL certificate within my ISY to try and secure access to the admin console and API and what I am seeing is that accessing the admin console is painfully slow. It took several minutes to install the JNLP, downloading it over the local LAN. I'm at 5+ minutes waiting for the UI to finish loading so I can even use it and it appears to be hung but I suspect it's just taking a really long time for each request to the ISY as every now and then it shows some progressing in loading. In the bottom left corner in the status bar is says "System Busy". Surely this isn't working right... What would be causing it to be so slow over HTTPS? Connecting over HTTP works fine and loads instantly.

I have the wireless Insteon thermostat and have read and followed many of the forum posts here regarding the various issues and bugs within this device. I have setup my thermostat to monitor the water temperature in my hot tub. I have the external temperature sensor soldered directly to where the internal temperature probe was as outlined by others in this forum as a way to get temperature updates to be sent to my ISY. I also have it connected to an external power source to get continuous updates. While I do get updates pretty quickly now that it's connected to the 5V power source, I have noticed that I only get updates every 2 degrees of temperature change instead of each temperature change. I saw this mentioned as the behavior it follows when on battery, but mine is not and I still only get two degree updates. (See attached log) Is this just a built-in limitation of this thermostat or is there something I can tweak to get it to actually send more rapid updates? Thanks.