Michel Kohanim

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

jkraus Please take a look at this post under KPL Button Groupings http://forum.universal-devices.com/viewtopic.php?t=3717 . In short, I do not recommend using this dialog at all and instead create those groups within scenes that they belong. This way, you will also get the correct status of the buttons in ISY without having to query them. rlebel If the other method worked, I can only think of two reasons: 1. Your computers were using the previous cached version of the applet/application (you have to close all your browsers for clearing the cache to work) 2. 2.7.8 was not installed properly. Did you have any interruptions while installing 2.7.8? Yes, those other nodes can be used as controllers in other scenes. With kind regards, Michel

rlebel, What URL are you using? Are you going directly to ISY's remote IP address? What happens if you use http://www.universal-devices.com/99i/2.7.8/admin.jnlp instead and then add the remote URL? Fan mode cannot be null ... we can probably rename it and have it to nothing. With kind regards, Michel

Hello again: rlebel We decided not to remove Fan Mode because many third party clients depend on the position of the properties. Only the main node should show up in the device page. Please note that the thermostat should be in the OFF mode before you link it to ISY. As far are remote connectivity/Admin Console/PC, what error do you get AND which URL are you using to access your ISY? wwat/brad77/tahoe On the Email/Notifications Panel, remove all rules and click on Save. Then retry. Unfortunately as much as I tried reproducing this behavior, I cannot ... tahoe If you would want to be notified of Tstat changes, then you have to remove and reinstall them using Start Linking when they are in OFF mode. Otherwise, you will still have to query them all the time. jkraus Thanks for the update. With kind regards, Michel

Hi Al, I am so very sorry ... I meant Restore Devices. If you do not have Pro, all you have to do is to open the Event Viewer on level 3. When the process is done, we just have to go through the log to see which devices did not restore. With kind regards, Michel

Hi Al, With 2.7.8 for PRO, all devices that have pending writes are identified in the tree with a little green arrow. These arrows do not go away until: 1. All writes are successful (eventually) 2. You remove the device All we need you to do is: 1. Go to File | Restore ISY 2. Take a break 3. When you come back, all failed devices will have those little arrows next to them With kind regards, Michel

Hello mvprj84, Thanks so very much! Did SH contact you? What you are experiencing with this unit is not normal. With kind regards, Michel

Hi Moshe/oberkc, Status is the state of the device. So, if the device was off before and you turn it off again, the status does NOT change and therefore programs using it as condition will not be re-evaluated. Control is "what happened" ... so, regardless of the status of your device, if you press the Off button 10 times, you are going to get 10 Off events. Programs with Control in their conditions will be re-evaluated every time there's one of these events. With kind regards, Michel

Hi all, Thanks so very much for the input. I would humbly ask you all to first checkout the instructions here: Instructions for 2.7.8 can be found here: http://forum.universal-devices.com/view ... hp?p=27368 . This post is going to address all previous posts: jcthorne Please do be kind enough to unplug and plug your EZRain back in and let me know. The issues as far as querying the EZrain have always been the same and have not changed. Try querying zone 1. mbrett Please ensure your firewall is not blocking ISY. TheGent Please clear your Java cache and ensure that ISY has connectivity to the Internet. You should not see Notify All. CJVann 1. Please clear your Java cache 2. You need to press the Enter button after changing the email address (from xx.vtext to yours). If you do not do that, the entry is not saved brad77 Did you see a "Migrated" entry? And, if so, was it populated with your previous list? smileyw Please peruse the instructions for 2.7.8 which can be found here: http://forum.universal-devices.com/view ... hp?p=27368 . In short, remove your TStat from ISY, make sure it's in OFF mode, and then add it back in elvisimprsntr Please do be kind enough to follow the instructions for 2.7.8 which can be found here: http://forum.universal-devices.com/view ... hp?p=27368. In short, remove your TStat from ISY, make sure it's in OFF mode, and then add it back in. Please let me know if you still have the same issues. With kind regards, Michel

Hello all, Please take a note of the following instructions: Known Bugs in 2.7.9 KPL issues: adding sub button and load to a scene does not work in 99i Series (it works in PRO) KPL/RL issues: adding a button to a scene removes the slave link in the PLM ELK issues: There seems to be a bug where adding the security code in the configuration causes a crash. Please do not use the security code in the configuration page since it really does not provide any function yet X10 issues: In some cases, the system may crash. In others, the A10/X10 module cannot readily process X10 commands/messages -------------------------------------------------------- Known Bugs in 2.7.8 1. System CRASH in case of larger (>75 nodes) installations. If you have a system crash, please downgrade to 2.7.7 and then restore your 2.7.7 backup (File | Restore ISY) 2. Email editor dialog does not always work and requires the Admin Console to be restarted 3. Upgrading to PRO removed all other installed modules General Most UI related anomalies are related to Java cache. Please ensure that you have cleared your Java cache. Please be patient at startup! ... 2.7.8 goes through a migration phase to migrate all the configuration files to 2.7.8 format. As such, upon the first startup, if you see rapidly blinking MEM lights then all is normal and please do let the process continue. Please note that this process might take up to a few minutes depending on the number of devices you have setup in your ISY. V2 Thermostats 1. If already installed, they have to be first removed from ISY 2. Please ensure they are in the OFF mode before linking them back to ISY 3. Try using Link Management | Start Linking 4. You can safely remove your thermostat queries Note Changing the Fan status (on the thermostat itself) too quickly causes the updates not be sent to ISY. This is NOT a bug but limitations on the thermostat adapter interface. The thermostats are represented by 4 nodes: The main node - this is the main thermostat node xxx - Cool Control - indicates when the thermostat is calling for Cool xxx - Heat Control- indicates when the thermostat is calling for Heat xxx - Fan Control - indicates when the fan is on/off The main node can be used as a responder in any scenes and thus you can impact changes to the thermostat settings based on other INSTEON devices/ISY scene. The other nodes can be used as controllers in any of your scenes. So, for instance, adding the Cool Control in a scene as controller would cause all responders in the scene to turn on when the thermostat is calling for Cool and turn off when the thermostat is calling for Heat. IRLinc TX 1. IRLinc TX does not follow batch processing. This is not a bug Notifications 1. Make sure you clear your Java cache 2. Your previous list of email addresses must have been migrated to an entry named Migrated 3. Each entry/rule could have as many email addresses as you would like and you can have as many entries/rules as you wish Known Bug: On the email address edit dialog, if you hit the Cancel button, you will have to close and reopen the Admin Console otherwise email entries will not be added to the rules list. KPL Button Groupings in Scenes In this release, you can create button groupings through scenes: 1. For each controller button, change the on level for those buttons that need to turn off to 0 2. For each controller button, change the on level for those buttons that need to turn on to 100% Note: This is the preferred method for button groupings since: a. We are going to make the manual method obsolete b. The correct status of buttons are reflected in ISY regardless of their grouping If you so choose to use the manual method, please note that if you have those buttons in any scenes, any changes might have an adverse impact on the relationship between those buttons as reflected in the scenes. Although not recommended, the new Button Grouping dialog now lets you create non-mutually exclusive groupings in the top panel (when A is on turn B off but not the other way around): 1. The first row identifies the controller of the button grouping 2. The other rows identify buttons that have to be turned off when corresponding button in the first row is checked 3. For mutually exclusive buttons use the bottom panel as it is identical to the previous releases Thanks and with kind regards, Michel

Happy New Year to all ... It was just sent out. With kind regards, Michel

Hello pacificsloop, ISY reads a byte in the KPLs firmware to determine the number of buttons. As such, I am almost certain that your KPL is currently in 6 button mode. What you need to do is: 1. Pull out the set button and wait 10 seconds 2. Push the set button back in and leave it in for 10 seconds 3. Press and hold buttons A and H before releasing the set button Remove the KPL from ISY and then add it again. With kind regards, Michel