Michel Kohanim

Hi Tome, Since all aspects of ISY require a PLM, putting ISY on a power supply really does not make sense especially since: 1. ISY can keep the time for 6 hours 2. At startup ISY checks an NTP server to synch the time 3. You can use Run at Startup to do a variety of things at start up The 3AM Query is still there. Currently, ISY will not know if the PLM is not powered. With kind regards, Michel

Hi Mike R., Please do let me know what firewall software you have. In most cases the issue is firewall. In some cases the issue might be bad wireless connection. If all fails, please contact our tech support and we'll try to upgrade it remotely for you. With kind regards, Michel

Hi jkraus, Since this is a new release, I tend to consider everything a but (unless a known feature). As such, would you be kind enough to try again and ensure that you are telneting to the correct IP address. If not, would you be kind enough to let me know the approximate procedures you took before this started happening? With kind regards, Michel

Hi jbwood1, Would you be kind enough to post to this topic for your EZSnSRF: http://forum.universal-devices.com/view ... ht=ezsnsrf I am hoping that the author of this topic can better help you since we do not know the behavior of the latest firmware for EZSnSRF. As far as your IRLinc, please note that you can set the IRLinc buttons as non-toggle which means that they will ALWAYS either send On or Off. If you want the buttons (single scene) to be toggle, then you will have to follow the instructions on their user guide when adding the node to ISY. I am so very sorry I cannot be of further assistance here. With kind regards, Michel

Hello sk8er02, Apologies for the inconvenience. Thanks to hart2hart, the system crash has been reproduced and we are now working on a fix. As far as the network module, please ensure that your Network Module is still installed (Help | About). If not, please send your uuid to tech@universal-devices.com so that we can resolve this issue immediately. With kind regards, Michel

Hi NewTech, MY SINCERE APOLOGIES ... it should be: RF /CONF/UDFLPL.XML And, ISY should let you know that the file was removed successfully. With kind regards, Michel

Hi jkraus, Please make sure you do not add any port after telnet. In short, all you need to do is: telnet 192.168.1.102 It seems your computer is trying to use a different port! With kind regards, Michel

hart2hart Thanks so very much! Would you be so kind as to send your backup to tech@universal-devices.com? all We are right on the MAC GUI issue. With kind regards, Michel

Hi again, That's excellent news. You do not have to get rid of all your CFLs. If your installation permits, you can simply put the loads on FilterLincs. No more tests are necessary ... when we address the CFL issues, I am certain all others will be solved as well. With kind regards, Michel

Hi rlebel, Do you have the same issue if you use http://www.universal-devices.com/99i/2.7.8/admin.jnlp? If not, I must suspect that: a. Either 2.7.8 was not installed correctly on your ISY OR b. Java cache has not been cleared With kind regards, Michel

CJVann, Known bug: if you click the cancel button on the email editor dialog, then you will have to close/reopen the admin console to be able to add again. With kind regards, Michel

Hi, My first question is this: Out of all these devices, which ones are connected to CFL. low voltage transformers, or Halogen lights? A similar test would be to make sure ALL these devices are off and try restoring then one at a time. In short, we want to make sure there are no sources of noise before we go to the next step. With kind regards, Michel

Hi All, another collective reply! elvisimprsntr and others I am in utter disbelief as to why tstat nodes should be considered bugs? Do we consider KPL secondary buttons bugs? How about motion sensor low bat and dusk/dawn nodes? How about IOLinc relay vs. sensor nodes? The concept is precisely and 100% the same, it is not a bug, and shall not be addressed nor discussed again unless there is a bug in the functionality. Thank you for understanding. wwat Hi wwat, thanks so very much. Which tooltip are you referring to? jason|99 This happens when the Admin Console cannot be reached by ISY. Please do ensure that you have cleared your Java cache, and you are using the 2.7.8 URLs (not 2.7.7). hart2hart Apologies for the inconvenience. Please note that 2.7.8 does a migration on all configuration files for all the INSTEON devices as such, at the first boot, it might take a long time for the boot to complete. So, would you be kind enough to: 1. Disable query on startup 2. Upgrade to 2.7.8 3. Look at the status of the LEDs ... if you see quick blinking MEM lights, this means that ISY is migrating and you should let the process continue 4. If you have a serial port on your computer, it would be great if you could connect via Hyperterminal and let us know what you see With kind regards, Michel

Hi Bill, Unfortunately no! With kind regards, Michel

Hi NewTech, Please do the following: 1. telnet to your ISY (http://www.universal-devices.com/mwiki/ ... o_Your_ISY) 2. login 3. type (case sensitive): RF /CONF/UDFLPL/.XML With kind regards, Michel

Hello all, Apologies for a collective response .... jason|99 No, you are not doing anything wrong. This issue was reported before as well and it must be a bug. Would you be kind enough to send your uuid (Help | About) to tech@universal-devices.com? I'll have it taken care of immediately. Zellarman It does not seem like you are using Mutually exclusive buttons anyway. You just have ONE button the state of which is used to enable a folder. If you have two or more buttons in a Mutual Exclusive relationship, it's best to put them in scenes so that ISY could keep track of the status correctly. sk8er02 Apologies for the inconvenience. Would you please let me know: Do you get the Mem/Error lights blinking? Can yo get to it via telnet? Can you access the HTML page? What URL are you using to get to ISY? hart2hart I'll take a look at the other post. dougos2 I will have to take a look at this. With kind regards, Michel

Hello Elvis, have not received it yet. Please send it to support@universal-devices.com. Thanks and with kind regards, Michel I sent UDI support an updated test results matrix that inlcudes log artifacts in case you need it. In short, FS is incorrect in ALL modes upon power up or manual query. SPs are incorrect in program modes upon power up or manual query. Elvis,

Hi James, Querying an EZRain is one command which takes less than a 1 second to complete. As such, you will not see any dialogs. To ensure this is the case: 1. Tools | Diagnostics | Event Viewer on level 3 2. Query the FIRST zone (ends with a 1 in the address) If you do not see any traffic on the event viewer then please do let me know. With kind regards, Michel Tried unplug and replug both EZrain devices. Still no luck. The ISY does not appear to even TRY to query the device. I tried manually querying each of the 16 zones, the 'system busy' popup never even comes up. Its not reporting a communications failure, it just does not seem to execute the command. Event viewer shows no activity when trying to query either EZrain. Thanks, James

Hi brad77, Finally got to reproduce it. The problem is this: - In the dialog where you enter email addresses, if you hit the Cancel button once then as long as your Admin Console is on, ISY considers that dialog canceled (incorrectly maintains its state). Already fixed but, as a work around for now, please try not to cancel that dialog! Thanks so very much and with kind regards, Michel

Hi jkraus, YES. You got it. Now, this way, everything is represented in scenes + the added bonus that ISY now keeps track of the state of these buttons for you (unlike before). Just to reiterate: 1. Put them both in the same scene make both controllers 2. For each one, make the other turn off With kind regards, Michel

Hi Elvis, Upon ISY reboot, ISY does not have any knowledge of what the state of a tstat is and all should be queried. If you do NOT see this behavior, then there's something wrong. As far as the program mode, we will have to check into it to see what's going on under the covers. With kind regards, Michel

Hi brad77, Thanks so very much for the update. I really do think this is a Java cache issue. Would you be kind enough to try any one of the following URLs: http://www.universal-devices.com/99i/2.7.8/admin.jnlp OR http://isy/admin.jnlp (you can now find ISY by simply typing http://isy in your browser) With kind regards, Michel

Hi jkraus, Sorry for the confusion. Groupings are basically how each button responds to another button. Mutual Exclusive buttons are a special case of Grouping where turning one button turns others Off AND vice versa (i.e. mutually exclusive state). If your buttons are NOT in any scenes, then you can use the same method as before. My question is what's the point of buttons not in scenes? Are they controlling anything? Are they responding to something? Again, if you want the correct status of your buttons to be reflected in ISY, you must include them in scenes and then ISY can figure out which button is on or off regardless of their grouping. With kind regards, Michel

Hello mvprj84, In some cases, they do to figure out the root cause of important issues. I am going to send an email to our contact and see if he would like to help. With kind regards, Michel

Hi Elvis, The main issue is that the thermostat is not queried when first added to ISY. All controls including CLIFS, CLISPH/C are queryable and you should be able to query them both in programs as well as manually. Fan Mode was not removed (please see previous posts). With kind regards, Michel