Michel Kohanim

Hello John, No problem at all. I take these questions/comments as opportunities to make ISY better. With kind regards, Michel

Hi Steve, I am so very sorry for the trouble. Please: 1. Telnet to ISY (http://wiki.universal-devices.com/index ... o_Your_ISY ) 2. Login and at the prompt type: RF /CONF/HW.CFG With kind regards, Michel

Hi Russ, Thanks so very much for the update. Can you please go to Help | About and make sure that the firmware is actually on 3.3.8? With kind regards, Michel

Hi raydoc, What's your ISY's firmware version? Support for this device was only added in 3.3.5+ releases. With kind regards, Michel

Hello arw01, I do not know much about them except that we did implement support for them in 3.3.7. So, you should be able to use and program them. The only problem was that we could not do extensive testing on the properties (latching, etc.) since it required devices that we didn't have. With kind regards, Michel

Hi David, thanks so very much for the update and actually finding the bug. With kind regards, Michel

Hello thomastran, Sincere apologies for tardy reply. I think it would be much quicker if you called our tech support team (links below) so that you don't have to keep waiting for a post to this topic. At the moment, I am thinking that perhaps your programs are indeed gone. Did you ever restore an ISY backup from 2.7.0 release? With kind regards, Michel

Hi jmed999, Weather Underground OR WeatherBug? With kind regards, Michel

Hello Mr. Mesberg, Welcome to our world! No, this is NOT at all normal. Would you be kind enough to: 1. Open the Event Viewer, change the Level to 3 2. Try adding a device 3. Save/send me the contents of the Event Viewer Also, can you please let me know what firewall software you have? With kind regards, Michel

Hi thomastran, Thank you and NO. Please do not restore anything as it will cause other issues. Please do be kind enough to: 1. Clear your Java cache http://wiki.universal-devices.com/index ... Java_Cache 2. Go to http://isy.universal-devices.com/99i/3.3.8/admin.jnlp Let me know if your programs are back. With kind regards, Michel

Hello thomastran, It's quite possible that ISY is in safe mode (Tools | Diagnostics | PLM Status/Info). If so, in all likelihood, your PLM has died or the connection from ISY to PLM is bad. With kind regards, Michel

Hi Alan, My pleasure and all great ideas which have been added to our requirements list. With kind regards, Michel

Hi jmed999, Is the 0.01 value what was reported in the Admin Console? Also, can you verify last program runtime? It could be that the notification didn't go through even through the program ran. With kind regards, Michel

Hi Elvis, Three questions: 1. Are any of your network resources UDP? 2. Do any of your network resources require DNS lookup? 3. I know this is quite difficult, but can you disable all your Network Resources programs and see whether or not there are any improvements? With kind regards, Michel

Hi Xathros, Thank you. With kind regards, Michel

Hi Tom, That's amazing! Was this http or https? johncrab and MikeD, thanks so very much for your vote of confidence. It really does mean A LOT to a LOT of us here at UDI. With kind regards, Michel

Hi Tom, thank you so very much and very much looking forward to it. sanders2222, please open the Event Viewer, send ELK commands and then observe the events as they happen in the Event Viewer. What do you see? Do you see any ELK-ERR entries? Hi JMC, cannot produce. Can you please send a screenshot of the program you are using + your KPL version to support@universal-devices.com? Again, cannot reproduce. arw01, Unlike other devices, ISY firmware is not just a binary that's flashed into the flash. It has more than 50 different files each one of which are inspected for integrity before being installed. In all cases, unless something goes terribly bad, you will not be left with a device that does not work. With kind regards, Michel

Hi Tom, Not at the moment. The reasons are: 1. I have one of those here and I've yet to receive a 100% accurate heartbeat every 24 hours (ever) 2. Heartbeat need to become another property such as on level/ramp rate 3. We have to alter ISY processing to do things based on broadcasts and not multicasts So, obviously we can add support for these features but it will not be something quick since it requires major regression testing (see #3). With kind regards, Michel

Hi ryarber, Thanks so very much. We shall certainly take a look and see what's going on. With kind regards, Michel

Tom, ISY does hear the hearbeat but does not actively listen or do anything with them. Low battery should work. With kind regards, Michel

Hi Tom, I appreciate your input and your expertise and no doubt you are a master at what you do. As such you can certainly use your network management expertise and do a traffic capture (Wireshark?) between your computer and ISY during the upgrade process and then send it to us. We'll surely review and try to figure out what's causing your problems. From ISY's perspective, you should be able to upgrade remotely or locally via http or https. With kind regards, Michel

Hi Tom, ISY does not listen for daily hearbeats. With kind regards, Michel

Hi Tom, Thanks so very much for your $0.02 and I do agree generally with the concept - and that's precisely what we do - but I still strongly advise against upgrading your ISY remotely. As far as you not being able to upgrade remotely, please look at the following things: 1. Your firewall software 2. Router logs (to see if anything is being blocked) 3. If ISY is connected to a switch, try connecting it directly to the router and retry The best test (if and only if your hosting supports it) would be to try using the remote URL locally and see if you have the same problem. If you don't then the problem is latency and packets being dropped when you are remote. With kind regards, Michel

Hi raydoc, It's quite possible that ISY now has a different IP address and thus must be re-setup in your firewall. With kind regards, Michel

Hi ellesshoo, Here's the link to Energy Monitoring guide: http://www.universal-devices.com/docs/p ... 0Guide.pdf ... in short, Zigbee setup must be tied to the type of device (RCS, Brultech, EM3) that you are trying to link to ISY. If you have any questions, please do not hesitate to contact our support (links below). With kind regards, Michel