Michel Kohanim

drw, Is it 2 minutes behind even in your MAC/Firefox? We need to make sure whether or not this is a bug (regardless of its severity). With kind regards, Michel

drw, Great! This is good news ... 1. You might have to clear Java cache if and only if you've done a firmware update. Otherwise, there's no need whatsoever. 2. I have not used Windows in Parallel. Do you have Control Panel? If so, you should follow: 1. Control Panel->Java 2. Click on Settings (at the bottom) 3. Click on Delete Files (at the bottom) With kind regards, Michel

blatryo, Thanks so very much for your kind words. I do hope that we can provide the same level of service for the years to come and continue enjoying the company of our loyal friends and customers. I had to think about your question for a while .... it's really hard to answer. I guess the gist of it is: 1. Believe in what you do and make sure you have a genius by your side to make it happen! 2. Believe that your product and services are only as good as what your customers think of them 3. Believe that there's always room for improvement Thanks again so very much, With kind regards, Michel

drw, Thanks. It's very possible that we have a Java cache issue here. Would you be kind enough to clear your Java cache as well? With kind regards, Michel

drw, This is really odd! I just need to make sure that when you log back in the time is correct, right? With kind regards, Michel

Hi JAJ, Yes. For instance, you have used 228 nodes (170 byte blocks) and, as far as memory is concerned, you can support more programs. The rest are objects that are dynamically allocated and deallocated and are there only for debugging purposes. With kind regards, Michel

Hi JAJ, It would be very difficult to explain these numbers with the object using those memory blocks. In short, the first column is the size of memory block used (in bytes) and the rest is self explanatory. With kind regards, Michel

drw, What version of ISY firmware do you have (Help->About)? This used to be a bug which has been fixed. With kind regards, Michel

blartyo, Yes, this configuration should work fine. With kind regards, Michel

Mark, Thanks so very much. With kind regards, Michel

IndyMike, Thanks so very much for your post and most valuable information contained therein. Rod, ISY-26 and 99 share the same amount of flash=512K ISY-26 has 2MB RAM ISY-99 has 8MB RAM As IndyMike suggested, you can use SM to figure out how much memory is currently being utilized but we do not yet have any utilities to measure the processor's utilization. Since ISY is a multi-tasking/event driven environment, the efficiency of the programs depend on the amount of information on the reader task (X10/Insteon) and the amount of information needed to be processed. All tasks have priorities; if you are interested, I can share with you the tasks and their priorities. With kind regards, Michel

IndyMike, Thanks so very much for your post and most valuable information contained therein. Rod, ISY-26 and 99 share the same amount of flash=512K ISY-26 has 2MB RAM ISY-99 has 8MB RAM depending on the build As IndyMike suggested, you can use SM to figure out how much memory is currently being utilized but we do not yet have any utilities to measure the processor's utilization. Since ISY is a multi-tasking/event driven environment, the efficiency of the programs depend on the amount of information on the reader task (X10/Insteon) and the amount of information needed to be processed. All tasks have priorities; if you are interested, I can share with you the tasks and their priorities. With kind regards, Michel

aLf, Yours was an upgrade to 2.6 and thus the name might not be QueryAll ... please look for Shedule 1 and rename it. With kind regards, Michel

Hello royceconnerley, The temp range is between 32 - 158 F (0 to 70 C). With kind regards, Michel

feleven! You are 100% correct vis-a-vis the user guide. Since user guide is embedded in ISY thus it will not reflect all the changes/additions that our loyal forum members are contributing on a daily basis to our Wiki site. I think/hope you will find most of the information that you are looking for in our Wiki site (Help->UDI Wiki). With kind regards, Michel

Hello arjnur, Is this an open box/refurbished unit by any chance? You can always add back a program to query My Lighting at any given time. Please let me know if you'd like more instructions. With kind regards, Michel

Hi Frank, Got it ... thanks so very much for the answer! With kind regards, Michel

IndyMike, Thanks so very much ... as a matter of fact, I am quite happy that you failed first otherwise we would've never had this wonderful topic. Thanks again and with kind regards, Michel

Hi Frank, Yes, your approach should work without issue unless there's a program that's run in which case a non-operating PLM will cause status errors. And, may I know why you do not have the 3AM Query running? With kind regards, Michel Hello Michel: That's very possible. There may have been one or more programs trying to execute during the time that the PLM was off. Yes, I could have just performed a network query, and if it ever happens again, I will try that. But the problem is that if I had been gone, and the power had gone out, maybe the same problem would have occured. Since I don't use a "3am status query" for the ISY, then my status readbacks would be wrong. That is the reason that I took the ISY off the UPS and put it onto the same outlet as the PLM. At least that way, it should reboot properly. Should this approach work without issues? Thanks

Hello Doug, Please find my answers below. With kind regards, Michel This program is tested/evaluated every time there's a change in the status of that device. If the status of the device never changes then the "Then" clause will never ever again run! No, it only repeats the Actions within it See above

Hello dkaye, Here's what I'd suggest: Create a program such that the condition is 'when' you want your furnace to be on (say, winter nights). Save this program and then go to Program Summary tab, choose this program, then choose Run at Boot, and then click on Apply. This way, your program will run after reboot. With kind regards, Michel

Hi Frank, That is quite interesting and something that should not happen. It's possible that ISY tried some of the programs during the time your PLM was unplugged; that could explain some of the problems. Next time - if there's one - instead of rebooting ISY, may I humbly ask you to simply do Query on the Network node? With kind regards, Michel Hello Michel & Mike: For what it's worth, I found that approach actually caused me a problem. I had my ISY-26 on my UPS, and the PLM plugged directly into the wall. They were both on the same circuit, but the ISY was on the backup. I had to turn that ciruit off to do some work on my home wiring. That meant that the ISY stayed on (due to the UPS), but the PLM went off. The circuit was off for some time (20 minutes?). When the PLM came back on, the communication with the ISY was messed up. If I remember correctly, many of the status readbacks on "My Lighting" were missing. Due to this, some of my programs that depended on devices statuses were not functioning. I had to power cycle the ISY to get it to sync back up with the PLM. It then found the PLM, ran its reboot systemwide query, and everything was good again. Based on that experience, I took the ISY off of the UPS, plugged it directly into the same outlet as the PLM, and the next time I turned that circuit off, the PLM and ISY came up together with no problems. Best wishes,

Charlie911, Yes, it's normal especially if you have the run-at-reboot set on your programs. With kind regards, Michel

Hello Frank, Apologies for a tardy reply and thanks so very much for finding yet another bug! Yes, indeed we forgot to put a prompt in the replace function to warn the user when the replaced node is in any scene which also has an RL. This has already been rectified and is part of the next code drop ( http://forum.universal-devices.com/viewtopic.php?p=5399 ). My comments below. Thanks again and with kind regards, Michel Apologies ... this was an oversight on our part which has already been rectified Not normal and definitely and oversight on our part No Yes, absolutely correct!

The 2.6.1 beta release is now available. If interested, please send an email to support@universal-devices.com Fixes - Workaround for KPLs (1.5+) showing as LampLinc BIPHY - Power outage issue: ISY will use a new IP address if one is issued any time after the boot up. Previously, ISY would give up (slow routers) after 3 retries - Java Exception when removing a device the table was not updated correctly - Daylight Saving flag was always set to true when adjusting the time to the computers clock - The slider for a relay in a scene was not being updated back to its original state if the operation was canceled (neither on nor off) - Clicking to the left/right of the slider or using the left/right arrow keys were ignored - Enable Internet Access: null now shows a failure message instead - No replacement menu available for RemoteLincs - 'Program Run/Program Run Else' failed if a program tried to run itself - SocketTimeout exception when loading a large number of programs - Explicit Query no longer clears the status of non-load devices (such as KPL secondary buttons, RL buttons, IRLinc buttons, etc.) Enhancements UDMobile Support - HTTPS Support - HTTP and HTTPS ports can now be changed using the CWP Shell Command - HTTP default port is now 80 - HTTPS default port is now 443 - Simple HTML page both in HTTP/HTTPS which can be used by Mobile devices ... no more Java - Certificate issues remain to be resolved X10 - Added support for sending/testing for X10 unit code separate from X10 command code and vice-versa Programming - Added Fade Up/Down/Stop to programs (both conditions and actions) - Can use a program to set other programs to 'Run/Not Run At Reboot' (for power outage recovery) - Specify from 0-100% for dimmable devices (100% shows as 'On', 0% shows as 'Off') GUI - Changed Reset History to Clear Log - In case of non-Linux clients, one can now selectively decide to save the log (CSV) or view it in Excel - Applied Locally is now on the main view as well - AutoUpdate no longer pops up whenever the Admin Console is started. Rather - and as a compromise - there will be a reminder (in text) at the top right corder of the Status bar - Progress bar when programs are loading General - In the shell, configure default number of insteon command retries - Automatic increase in insteon command retries for long running commands (eg. restore devices) - Automatically reorganize links for KeypadLinc LED backlight (no need to add them to scenes in specific order) INSTEON - Added support for Companion 2 Wire devices (2474S/D) - Added support for KPL Countdown Timers (2484DWH8) - Added support for KPL (v2) sub-buttons controlling the on-level/ramp rate for the local load - Added support for IRLinc - Added programming features for thermostats - Add New INSTEON device now supports providing the type of device to be added SHN - Added support for EZSwitch30 (minimal testing) - Added support for EZIO4O (minimal testing) - Added support for EZIO6I (minimal testing) - Added support for EZSnSRF - Added support for EZX10RF (untested)