Michel Kohanim

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

Yes. Any chance it's still coming out today?

Hi, The PLM is NOT failing. The request failed is the inability of the PLM communicating with one or more of your devices. With Pro and 2.7.8, you will have indications of which devices are having comm errors. Nonetheless, having that list is the first step and I am sure we'll get to the bottom of it. With kind regards, Michel

Hi rlebel, Yes, you are correct. The next drop will be 2.7.8 ... we are at the final stages of testing so you should see it shortly. With kind regards, Michel

Hi pacificsloop, We are working with SHN to figure out what changed between their version 24 (which works perfectly) and their latest firmware. It's now evident that the latest version of EZFlora do not work with ISY. I do apologize for the inconvenience. With kind regards, Michel

Hi Al, in addition to the observations by oberkc, I really do think you have major communications issues. All these request failed messages are not normal and, in 99.9% of the cases, they only happen if the PLM cannot communicate with your devices. So, the first thing I would do is isolate which devices are having issues. Please make a list of those that you frequently get request failed for. Then, we are going to go through each one and figure out which one is causing the issues. With kind regards, Michel

Hi Rick, I just wanted to let you know that we spent hours trying to improve the performance of our email client. I am happy to say that we got some improvements (below 10 seconds) but we have reached the limits of SMTP specifications: authentication takes approximately 2 seconds. Every recipient takes an additional 2 seconds. TLS/SSL (gmail) takes 3 seconds for negotiating keys. The rest of the conversation is in sub seconds. We should have 2.7.8 out today so please do be kind enough to test. Make sure you change the timeout to the lowest possible number that consistently works (for me 400 ms works consistently with all my mail accounts). With kind regards, Michel

Hi Rick, Currently no, but it's surely on our todo list. With kind regards, Michel

Hi Joe, Thank you so very much! Now that you've opened the can of worms, the next firmware update is going to cost $1000.00. ... just kidding. Thanks again so very much for your patience and support. With kind regards, Michel

Hi Rick, Unfortunately you cannot install Apache and PHP on ISY ... I am going to work on our email client code and see what's causing such long delays. In software, everything is possible. Thanks so very much for your patience. With kind regards, Michel

Hi Rob, Welcome! If you want the events to be in that sequence then the program you have is the best way to do it. And, you are not using more processing power than spitting it into more programs. Waits are simply constructs that put the execution of a program (as a whole) in a queue to woken up after that period ends. With kind regards, Michel

Hi backinthelab, Thanks so very much for your kind words; I do appreciate it very much (and it felt great!). With kind regards, Michel

Hi RickL66, Thanks so very much for the detailed explanation. I am going to think about it a little. I just don't like the fact that there's another piece of hardware required just to make this scenario to work. With kind regards, Michel

Happy New Year to ALL! With kind regards, Michel

Hi mbrett, Apologies for a tardy reply. To support thermostats (which are a little unlike other INSTEON devices), we had to basically redo most of the device management/communication/synchronization code. While going through this surgery, we also included some enhancements such as: 1. Fail safe/Atomic device linking: you can turn off ISY, take out the device, and ISY knows exactly where to start from the next time 2. Batch mode (Pro only): allows you to do all your configurations/linking without having to wait for each to complete before starting the other. When you are done with everything and with a press of a button ISY goes out and does everything. Combine this with 1, and then you will have a worry free installation regardless of what happens 3. Now the UI lets you know which device is being worked on using different icons 4. You can send notifications to different groups of email recipients And more ... All this said, we do need a few more days just to make sure we are not going to crash anyone's system. I am hoping Thursday 12/31. Thanks so very much for your patience. With kind regards, Michel