Michel Kohanim

HI accessha and apologies for a tardy reply. I was referring to port 80 but you don't have Internet Access enabled and thus a moot point. Please reboot your ISY and let me know if you are still receiving these errors. Thanks and with kind regards, Michel

Hi Rand, Ok, this is done! The main issues are: 1. It's very difficult to test these messages 2. I2 testing is going to take a little longer to make sure everything is OK Thanks again so very much, With kind regards, Michel

Hello jamesx0, Apologies for a tardy reply. Please do not use the default since, in all likelihood, we have already gone beyond our limit for this month. You might want to try a gmail account as follows: server - smtp.gmail.com port - 587 userid - your gmail address password - ... Use TLS - checked With kind regards, Michel

Hi Dodger, Yes, this is correct. What do you mean by "looses connection"? With kind regards, Michel

Hi Philip, I do apologize for the inconvenience. Usually, the problem is that the PLM is not making good contact with the cable (RJ45). Sometimes, swapping the RJ45 cables fixes this issue. But, the best solution is to request for a new PLM. With kind regards, Michel

Rand, thanks so very much and a great catch. We should have this implemented in the next drop. With kind regards, Michel

accessha, This usually happens if you have another device port forwarded to the same port as ISY. With kind regards, Michel

Hi eddyk, I think the original problem was due to the fact that you had signal issues and thus Restore Device actually restored those links that were not written correctly due to Signal issues. With kind regards, Michel

edfinely, Thanks so very much! There is a bug with the Test function (it always returns request failed). But, this should always work with gmail. What worries me is the issue where your settings are not saved. Would it be possible at all to change your password and send me the account information? This way, I will check to see if there's a bug (possibly with length of the uid/account) and will immediately report back to you. With kind regards, Michel

Hello Philip, Apologies for lack of documentation and inaccuracies: 1. Telnet is enabled by default (not disabled) 2. Default ISY port numbers (from factory) are 80 (for HTTP) and 443 (for HTTPS) What you would want to do is to forward to port 443 unless you have another device which uses the same port. If so, use CWP (through telnet) to change your HTTPS port to something other than 443. With kind regards, Michel

Hi Rand, By plan, do you mean that it will be implemented, it's already implemented, or it's on the wish list? With kind regards, Michel

Hello eddyk, Is this a problem with all your KPLs or just a few of them? Can you try doing a Restore Device on one and let me know if anything changes? With kind regards, Michel

Hi Joe, Thanks so very much. The easiest fix/stopgap would be to give the user the ability to ignore A1 ... then, when we have more time (and with the help of ELK), we'll decide what would be the best possible solution and where it should reside. Thanks for all your input and finding this issue, With kind regards, Michel

Hi keribi, Apologies for a tardy reply. There's actually a bug with the "Test" function in that it always returns "Request Failed". Did you actually receive an email? With kind regards, Michel

Hello AnthemAVM, Have you setup ISY using File->Enable Internet Access or have you done it manually? With kind regards, Michel

Hello madcodger, We could possibly include an option in ELK configuration to ignore A1. This should be a stop-gap till ELK adds facilities to filter what is being sent to ISY. With kind regards, Michel

Hi Dave, I think the problem was that your PLM was overwhelmed! (this does happen with PLM firm 52). Please keep a very close eye on this issue and, if it happens again, please replace your PLM before the warranty is over. With kind regards, Michel

Hi Bob, I do apologize for the inconvenience and a tardy reply. Yes, there is a way to update the firmware through the serial port. But, before doing so, please send us your URL and perhaps we could upgrade it remotely (support@universal-devices.com). With kind regards, Michel Hi Michel, This appeared to work for a short time, where it said "negotiating keys" or something along those lines, then the browser (Opera) died. I retried using Explorer and the browser immediately died after attempting to login. Is there anyway to login using the serial port and update/reset the software this way? I'd really like to change the time, because one of our lights comes on at 4am or so, and I think our baby sees the light under her door and thinks we're up. It's no fun getting up at 5am to put the baby back to sleep. Thanks, Bob

Hi Dave, Sincere apologies for a tardy reply. It could certainly be a bug which was introduced in 2.6.7: do you have a thermostat in your installation? But, to be honest, I think there's something much more serious going on. How old is your PLM? With kind regards, Michel

Hi AnthemAVM, You are not doing anything wrong: ISY is asking your router for the external IP address to which your router is responding with 0.0.0.0. Perhaps you should reboot your router one more time! With kind regards, Michel

SomeWhatLost, Unfortunately I have no more ideas. Umm, ok, one last question: When you first used your ISY with this computer, did you accept the certificate? If not, or if you do not remember, please go to your Java console, click on the Security tab, and delete all your certificates. With kind regards, Michel

Hello Keith, I do apologize for the inconvenience. This is a bug that has been eluding us ... in all likelihood, the reason the GUI shows you ISY, is because it defaults to that if it cannot retrieve the configuration. It would tremendously help us find this bug if you could enable internet access so that we can get to it remotely. With kind regards, Michel

Hi SomeWhatLost, We do know for a fact that 32 bit Java installation does NOT work well on a 64bit system (it runs in compatibility mode). I am not sure why it work on Friday ... we have had reports of intermittent behavior but we could not reproduce them. With kind regards, Michel

SomeWhatLost, Apologies for a tardy reply ( I am in a week long conference). Aha! If you are using 64 bit Windows, you must use 64 bit Java (look for the x64 link here): http://java.sun.com/javase/downloads/ea ... p#6u10JREs Please do let us know of the outcome. With kind regards, Michel

Hello eddyk, Yes, it is! (unfortunately, though, at a very low priority since there's a workaround). With kind regards, Michel