Everything posted by Michel Kohanim
-
Release 3.1.5 (Beta) Is Now Available
klundy/Candide, Thanks so very much for the update. Perhaps it would be best to have an intermediate release of 3.1.6 with spurious errors removed so that we can figure out what's causing the problem. I'll wait till tomorrow and then will decide (based on whatever else we can fix by then) whether or not we should have an intermediate release. With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello junkycosmos, As far as I remember, load sense simply sends an off when no load is connected. I am not aware of any multicast signals that would help ISY identify whether or not a load has been disconnected. With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello Brad, Sincere apologies for the inconvenience. This is a known issue with ELK and the only time we have been able to reproduce it is when ELK is in programming mode (through ELK RP or other methods). We should have the ELK module out shortly which should address this issue. In the meantime, if possible, remove ELK configuration from ISY and let me know if you still experience system hang. With kind regards, Michel Hi Michel, My ISY has also been freezing sporadically over the last few weeks. It's been driving me nuts. It wouldn't be that big a deal but I use it to control my EZRain and I live in Las Vegas, so the plants don't get watered and when it's over 100 degrees that can be really bad. I have two ISYs, one at my house and one at my parents'. The one at my house never crashes. It's the one at my parents' house that's been problematic. That one is connected to an Elk security system. I noticed you mentioned that in your diagnostic questions. Thanks for any help you can give. Brad
-
Release 3.1.5 (Beta) Is Now Available
Hello Brian, Apologies for the inconvenience. This is how ISY works: 1. If there's an error resolving a name to an IP (DNS erorr) then ISY increases the timeout for DNS resolution. If after 10 retries ISY can still not resolve a name (that used to work), then it concludes that DNS servers might have changed and therefore it tries to renew its DHCP lease (if it does not have a static IP address). From the errors below, it seems that ISY is trying to renew its lease but your router is refusing to renew ISY's lease. It would be a great help if you can look at router's logs and for the time period below cut/paste the entries. In 99.999% of the cases, the router must honor a lease renew request. With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
klundy, Thank you. Please try 750 ... you can ignore body errors (server, password, user timeouts should be fixed by increasing the timeout). ryarber, Sincere apologies. Would you please let me know: 1. Do you have ELK integrated with your ISY? 2. Are you now using 2048 SSL certificates? 3. Has anything at all changed in your LAN? With kind regards, Michel
-
XML parse error
Hi Tim, We have to factory reset your ISY (so it goes back to DHCP). Since you do not have a backup (and since we do not want you to have to redo everything), please do the following: 1. Take the SD Card out, put it in your computer and then copy its contents, zip it, and send it to support@universal-devices.com 2. Factory reset your ISY 3. Wait for us to send you an updated SD Card with networking configuration changed back to DHCP 4. Copy the contents of 3 back to your SD Card You should be good to go. With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello Candide/dennisric/RatRanch, Apologies for the inconvenience. Upon further testing it seems that our performance improvements to the SSL library has caused ISY to be faster than before so timeouts greater than 1000 ms causes ISY to wait for a response from the server after it has posted the Body but the server closes the connection before the timeout. In short, now, the longer the timeout, the more errors you are going to get. So, please try 500, 750, 1000, and 1500. The most important test is to not get Server not responding (that's what the timeout should be used for). Once you have the timeout set, you can ignore Body timeout errors since the email has already been sent. You will be pleasantly surprised by the improved performance with shorter timeouts. The extra errors are going to be fixed in the next release. Please note that this issue only affects TLS (which depends on SSL). With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello Candide/dennisric/RatRanch, Please do be kind enough to increase the timeout on SMTP settings and let me know if you see any improvements. Thanks and with kind regards, Michel
-
XML parse error
Hello remedy1234, Apologies for the inconvenience. XML Parse error means that the Admin Console cannot find your ISY on the network. Did you setup a static IP address for ISY? Do you have a good backup of your ISY? With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello Kevin, Please do be kind enough to look at Tools | Error Log and let me know the types of errors you are seeing. All SMTP errors are -50000 and the second column can tell us where the issue is in this list of error codes. With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello Candide, This is indeed quite odd. Are you using DHCP or static IP address? If so, has your router/modem recently changed? With kind regards, Michel
-
Network module slow when using hostname instead of IP addres
Hello j0dan, Thank you. Please try 3.1.5 and let me know if you feel any difference. With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Illusion, Was the Admin Console restarted? With kind regards, Michel
-
Nodes
Hello Greg, Your PLM is in Linking Mode. Are you linking any devices? Have you checked our Wiki / Userguide: http://www.universal-devices.com/mwiki With kind regards, Michel
-
Light bulbs
Hi Greg, Which menu are we talking about. Light bulbs in the Admin Console mean Responders. If you go to My Lighting, you will see them listed with their types. I am not sure what we are supposed to fix? With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hi io_guy, thank you. I shall give it a try. Candide, those errors (especially 503) means that the server is down or not available temporarily. Have you tried changing the station and see if there's any improvements. I know for a fact that WB servers sometimes go down for maintenance. But, it should not last so long. With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hi BrianH, Yes, of course! With kind regards, Michel
-
ISY stopped working - PWR, TX,RX steady ERROR blinks
Intellihome, You do not need to telnet to ISY nor would ISY allow you to telnet to it if the file system has not been initialized. So, simply replace the SD Card, and then power up ISY and see if you still have the same errors. With kind regards, Michel
-
What's in 3.1.17 (Official)
Hello all! Please follow us on Twitter for new firmware and other announcements. See you there! With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello all! Please follow us on Twitter for new firmware and other announcements. See you there! With kind regards, Michel
-
Insteon Message Not Decoded in Event Viewer
Hello sperok, Can you please take a look at the regular log (Tools | System Log) and check the activity on or around that time? With kind regards, Michel
-
Release 3.1.5 (Beta) Is Now Available
Hello tim2u, You need both modules. And, temperature variables come from WeatherBug and thus, YES, you can use them in your programs. With kind regards, Michel
-
ISY stopped working - PWR, TX,RX steady ERROR blinks
Hi wrj0, Not really. With kind regards, Michel
-
Brownout killed ISY99 and/or 2412s?
Hello ketchup318, It probably says "Not connected" which means that the PLM is dead. This is especially the case if your PLM is blinking instead of having a solid on LED. With kind regards, Michel
-
ISY stopped working - PWR, TX,RX steady ERROR blinks
Hi wrj0, Based on our experience, SanDisk is the most reliable followed by Lixar. With kind regards, Michel