Michel Kohanim

Hi Joe, Apologies. Please give me couple of hours; let me see if I can figure out what's causing this issue. With kind regards, Michel Mike: I tried your sequence a few times but no joy! Will probably remove and add the thermostat unless I hear otherwise from Michel. Joe

Hello all, If you are interested in our REST interface, you will find it here: http://forum.universal-devices.com/view ... 6654#16654 With kind regards, Michel

Hi All, Here's the link to the long awaited 2.6.14: http://forum.universal-devices.com/viewtopic.php?t=2251 Please note that no more enhancements will be added to the next release (hopefully it will be the official one). So, please do be kind enough to test and make sure all functions work properly. Thanks so very much, With kind regards,

Release 2.6.14 beta is now available and may be downloaded immediately. For fixes and enhancements, please peruse our beta forum at http://forum.universal-devices.com/viewtopic.php?t=930. You may also post your comments/questions and issues relating to 2.6.14 to this forum. This release provides the following important features: 1. 99i Series Optional Modules (Help->Purchase Modules) --> Webserver Module: allows you to use your ISY as a mini webserver to serve up your own files, applications, etc. You need this module for the REST interface (see developers forum) 2. i2 Support Please make sure you go back to automatic mode (Link Management->Advanced Options->Automatic). In this mode, all database communications are in i1 mode (except for motion sensor) and all i2 applicable commands use i2. This is the best mode to use. Bugs - Climate settings do not get updated in the GUI (WeatherBug) ... fixed - REST does not support X10 ... fixed - The link database comparison feature causes ISY Link Table dialog to require clicking the stop button when reactivated ... fixed IMPORTANT 1. For those upgrading from release 2.6 --->Please note that releases 2.6.1 and above will use default HTTP/HTTPS ports of 80/443 respectively. As such, before upgrading Disable Internet Access --->You will have to upgrade to release 2.6.5 ( http://forum.universal-devices.com/viewtopic.php?t=1409 ) before upgrading to release 2.6.13 --->If you are upgrading from 2.6.1, please make sure you export all your programs and store them in a safe place 2. If you have used bookmarks, please update them accordingly. If you have problems finding ISY, try http://www.universal-devices.com/99i 3. As always, please take a backup of your ISY Due to massive [plumbing] changes in this release, please do be kind enough to thoroughly test i2 related issues such as not receiving status feedback from i2 devices. INSTRUCTIONS for ISY-26 - Userid = isy - Password = autoupdate -- Step 1 - This step is necessary if and only if you are upgrading from any release except 2.6.11 and above - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step -- Step 2 - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step INSTRUCTIONS for ISY 99i Series - Userid = isy - Password = autoupdate - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step - Important: After upgrading, please close Admin Console, close all web browser processes, clear your Java cache, and reopen Admin Console. If there are any web browser processes running, the Java cache will not be cleared.

HI CompKing, We are going to have 2.6.14 released in a few minutes. So, perhaps, it would be best if you tried your experiments with the latest release? With kind regards, Michel By moving the AP from 40ft to 4ft away from the thermostat module, I have not detected a zero value for the returned value since. It is unfortunate that noise would be interpreted as a zero instead of an invalid result (and thus ignored). I am assuming that noise caused the issue since it did resolve itself, but even 40 ft away shouldn't be a problem (same floor, neighboring room, mostly open space between) I haven't been ignoring your response, I have been on vacation. I do note that in the 4ft location that I still do occasionally get 0 thermostat values in my programs, though not as often (once ever 40 hours or so). I can try moving it back to the original location (when I have a sec), and see if the problem worsens. Regardless, even at 4 ft I still get the invalid/zero values. Regards

gregoryx, This is a cause for a lot of concern for [at least code wise] you either have scenes or don't. i.e. if anything fails, then you will have no scenes whatsoever. As such, is it possible that you tried restoring an older backup? If not, please do be kind enough to try and remember the events just prior to this situation. Any hint would be extremely appreciated. With kind regards, Michel

Hello Zellarman, Our records indicate that you have ISY-99i/IR PRO (DOP 01/13/2008) which comes with a null modem cable. However, you would need a USB to serial converter which, I assume you don't have. So, I can send you a replacement immediately (tomorrow). If so, please verify your shipping address to tech@universal-devices.com. With kind regards, Michel

Hi Zellarman, Do you have null modem cable? If so, you can connect to port B, using Hyperterminal using 115200, 8, 1, none. With kind regards, Michel

Hello upstatemike, Excellent idea. Let me do some digging in the code ... although possible, I think this code is at the heart of link management and thus changing it will require a complete regression testing. The outcome, even more delays on releasing 2.7. I shall keep you posted though. With kind regards, Michel

Hello gregoryx, What do you mean by missing scenes? They are no longer in the node tree (to your left)? With kind regards, Michel

Zellarman, Apologies for the inconvenience. It seems that you have a filesystem problem. This could be as bad as a defective SD Card or as simple as reinstalling your app and backup. Please do be kind enough to try the following: 1. telnet to ISY 2. issue FS (and answer Y not y) 3. after reboot, if you still get the blinking err light, then let me know and I shall send you a replacement 4. if not, please reinstall your application (2.6.13) 5. restore you backup Please do keep me posted. With kind regards, Michel

Hello gregoryx, Got your email ... thanks so very much. Perhaps this will be a great opportunity to figure out exactly what's causing all these problems. With kind regards, Michel

Hello gregoryx, Thanks so very much for the update. If you find those devices still having issues, please do send me an email (tech@universal-devices.com) as I would like to have them replaced for you (while I get my hands on them). With kind regards, Michel

Hi Brian, If you have release 2.6.13, click on any of the motion sensor nodes (in your left) and then click the Set Options button in the center/bottom of the screen to your right. With kind regards, Michel

Hello gregoryx, First of all, I would like to hear about your RL's weirdness for, using programs instead of scenes, is usually not very efficient. With kind regards, Michel

Hi Rich, Perhaps it would be a good idea for you to contact our tech support (if you have remote access enabled) and let them walk through it with you. With kind regards, Michel

to_lighter, Thanks so very much. I am going to contact you shortly for next steps. With kind regards, Michel Hi Michel, Your description of the communications issues exactly describes my issues. My installation: 4 access points PLM firmware E.DC.9 v72 PLM has 840 links. I have four Filterlinks for lamps/etc where I was worried about noise The Switchlinks are v.35, Keypad links are v.2D, lamplinks are v.33 I don't know the count of my devices, many dozen. All of the equipment was purchased recently. Cheers!

Hello gregoryx, Thanks so very much. Would you be kind enough to describe what you are experiencing and whether or not it's isolated to some devices only. With kind regards, Michel

Hi Steve, The programs will not run if they have been tagged with an "unknown device". So,what you are experiencing is accurate. To make this process seamless, please use the Find function and re-save all those devices that you have removed and readded. With kind regards, Michel

Illusion, Thanks so very much for the feedback and it is already on our list of todos. RLIKWARTZ and huddadudda, First of all, I'd like to apologize for the inconvenience. This endeavor must be quite frustrating and we are doing everything we can to find answers. Now, as far as answers: 1. Burak's issue is completely unrelated. That bug has to do with ISY becoming 100% unresponsive 2. We have found the following pattern of issues: a. Newer SWLs/KPLs do not work reliably in scenes. This is not i1/i2 related since restoring them in either mode has no noticeable impact b. Newer LampLincs/ApplianceLincs (v31+) have related scene issues where they turn on with a noticeable delay. Restoring has no impact c. RemoteLincs eat up the battery if programmed in i2 mode ... this has been identified by SH and fixed d. In large installations, it seems that links at higher addresses do not report device statuses. We have not been able to reproduce it since we do not have a very large installation For 2, we are working very closely with SH to identify the root cause. I can assure you that SH is working diligently on resolving all these issues. As we all want a reliable system, may I humbly suggest that, collectively, we help SH in resolving these issues? This exercise will entail the following activities: 1. Sending one or two of your troubled switches to a designated person at SH and getting replacement units 2. Describing at high level your topology ... the number of access point, signalincs, filterlincs, devices, and your PLM's firmware version Your continued feedback, help, and support is very much appreciated. If you are interested - please send me an email (tech@universal-devices.com) with your contact information. Thanks again for all the great feedback and information. With kind regards, Michel

Hello upstatemike, I tested the same PLM version and it's working fine here. Of course, I don't have as many devices as you do. What I did, though, was to add more tracing and debugging in the hope that we can find something. We should have a build soon. With kind regards, Michel No, there is nothing at all in the Event Viewer. I can see the traffic generated in the flashing LEDs of other Insteon devices repeating the signal but there is NO entry in the Event Viewer at all. It seems that the PLM simply does not pass anything on to the ISY.

Hi Steve, I would love to do that and thanks so very much. The only problem is that the motion sensors should be put in programming mode other wise we cannot communicate with them. If possible, would you just capture the Event Log for the ones that do support i1 and then the Device Link Table (not ISY Link Table) for each. I would sincerely appreciate it. With kind regards, Michel

Hello lloverin, Would you be kind enough to do the following: 1. Tools->Diagnostics->Event Viewer (Level 2) 2. Link Management->Link a ControLinc 3. Enter the address Please send event viewer log to support@universal-devices.com. Please put "http://forum.universal-devices.com/posting.php?mode=quote&p=16492" as the subject. Thanks and with kind regards, Michel

Hi reakhavok, We still do not have any TriggerLincs but, theoretically, the answer is Yes. Do you already have a TriggerLinc? With kind regards, Michel

Hi Steve, Wow. Please do NOT tell me this!!! You are saying that you have some motion sensors that actually let you program them in i1 and then read the database links in i1? This will be unprecedented and something that I had received assurances for its impossibility. Are any of these Beta units? With kind regards, Michel Michel, I tried as suggested. Some devices use engine i1 and do finish restoring. I check and found links in the device tables. I tried again 4 times with another Version 1.0 and it says using i2 but I always get writing links failed. I haven't checked all of them but I have version 1.0B on some. I'm wondering if the version difference have something to do with this.