Michel Kohanim

Hi Xathros, I assume you are talking about Ubuntu, correct? Yes indeed we have color issues with Ubuntu ... we cannot even get the background for the tree to work properly nor can we get the image overlay to work. A10/X10 module does not have any new GUI elements except: 1. Your ability to add X10 nodes to the tree 2. Use named X10 nodes in your programs To ensure you have it installed, please go to Help | About and check whether or not it's listed. Also, in Link Management menu, instead of Add new INSTEON device, you will see Add New INSTEON/A10/X10 device. With kind regards, Michel

Hi ahbrown41, The main question I have is whether or not you receive events from any other INSTEON device in your network. If NOT, then is it possible that you have factory reset your PLM? If so, restoring the PLM might help From a pure theoretical perspective, you can receive events from devices if and only if they have a master link in the PLM (PLM is the slave to them). So, if you have good communications then the only possibility is an issue with the PLM. With kind regards, Michel

Hi tome, I should be happy that it worked but there's surely something amiss here for two reasons: 1. You should be able to add them to a scene one at a time 2. If I look at the logs you sent: Mon 12/07/2009 08:34:48 AM : [iNST-ACK ] 02 62 13.C1.7A 0F 28 0F 06 SET-MSB(0F) Mon 12/07/2009 08:34:56 AM : [iNST-ACK ] 02 62 13.C1.7A 0F 28 0F 06 SET-MSB(0F) Mon 12/07/2009 08:35:05 AM : [iNST-ACK ] 02 62 13.C1.7A 0F 28 0F 06 SET-MSB(0F) It seems that ISY tried reaching 13.C1.7A (is that your KPL) but had major difficulties. In INSTEON, for every ACK, you should see an SRX (a response from the device). So, unfortunately so, I would not rule out more problems with this device in the future. Do you have Access Points? What does this device control? Could it be that the load on this device was OFF when you attempted to move it to the scene the second time? With kind regards, Michel

Hi evarsanyi, May I humbly ask if you followed the ISY instructions on the screen? There's a pause between pressing the set button and then linking. This is the time and EZIO initializes itself. We use group 9 and above for all inputs in EZIO devices. Unfortunately I really cannot provide any more input above and beyond our testing with EZIO6I here which works absolutely fine. The reason for the error is that ISY cannot communicate with the device ( trying to write into a memory location). With kind regards, Michel

Hello wrique, The process I am going to outline below should only be used as test. In 2.7.7/2 release (to be out shortly) there are additional features that will help you with what you need to do but, to use them, you will have to remove IOLinc out of ISY and then link it back in. Ok, what you need to do is to create a scene with the Relay portion of the sensor as a responder. Then, you would need to make two of your KPL buttons to act as non-toggle (click on any of the KPL nodes and then click on Buttons Toggle button). Make one Toggle-On and the other Toggle-Off. Then, you would want to add these two buttons in the scene as controllers. With kind regards, Michel

Hi tome, Aha! The main issue is that the way you are pressing the On/Set buttons is causing the KPL to want to link as a controller (not a responder); that's why the LEDs are blinking (asking for a responder to be linked). With ISY, the KPL should be linked as a RESPONDER and here are the instructions: 1. ISY/Admin Console: Link Management/Start Linking 2. Press and HOLD the set button for 3 to 5 seconds or till the attached load turns on and then off OR a node shows up on the Admin Console. At no time should you see any of the LEDs blink continuously on any of these devices Please let me know how it goes. With kind regards, Michel

Hi tome, Please check your junk mail ... an email was sent to Tom L .. for privacy purposes, I cannot give the last name. Instead of pressing the on button, try pressing the Set button (the little button below all the other buttons). Also, please upgrade before you attempt again. You might have the newer version of KPLs which is not supported by 2.7.0. As far as notifications, please copy/paste your program here so that we can take a look. With kind regards, Michel

Hi again, This is very similar to the issues with IOLinc version below .31 ... the status of the sensor is not updated correctly and not reported correctly via the query. It would be best to request for replacement. Furthermore, we have added more debugging information in 2.7.7/2 which should be out by the end of the week. If you do not yet have 2.7.7, I strongly recommend sending an email to support@universal-devices.com to be included in our list. With kind regards, Michel

Hi wrique, We have added more functionality to IOLinc in 2.7.7. If you are interested, please send an email to support@universal-devices.com. Please note that IOLinc versions 31 and below cannot query the sensor properly. With kind regards, Michel

Hi tome, I am so very sorry to hear about all the problems you are having. Let's start from the beginning: If you could add these devices to ISY before removing them (using Start Linking) there's no reason why they should not add again. My suggestions and recommendations: 1. Ensure that you have 2.7.7 installed 2. Ensure that you are using the Automatic Mode (Link Management | Advanced Options) 3. Remove the devices from ISY, do factory reset, and then try adding them back using Event Viewer Level 3 (Tools | Diagnostics). If it fails, please save the Event Viewer and send to support@universal-devices.com For notifications, please ensure that you do indeed get the Test Notification using System/Configuration tab. If programs are run but your devices are not on, try running them manually through Program Summary tab (Run If). If you are still having issues, please do give us a call and we'll try to figure out what's going on. With kind regards, Michel

Hello again, Thanks so very much for testing. Would you be kind enough to disable any programs that might impact this operation. The main point is to ensure that the status of the sensor is ALWAYS equal to the state of the door regardless of us querying it. With kind regards, Michel

Hello stevehoyt, Do you get any errors while trying to clear the logs? Or is it just returning without actually clearing the log? With kind regards, Michel

Hello again, There is something that bothers me: Even though your door is open, the status of the sensor does not reflect the correct status unless queried. May I recommend the following: 1. Make sure you have 2.7.7 alpha installed (Help | About) 2. Please remove IOLinc from ISY 3. Do a factory reset on it 4. Add it back to ISY 5. Simulate door open/close and make sure that the status of the Sensor is reflected correctly and that the query returns the correct status If we figure this out, then I would hope that other problems are also solved. With kind regards, Michel

Hi mpf541, Would you be kind enough to do the following test: 1. Change the status of the sensor to be the reverse of the relay 2. Do a query on the sensor If the query returns the correct status for your sensor, then you should be OK. But, I am still unsure why you would have that issue after power failure. With kind regards, Michel

Hi Paul, 1. Using X10 messages as flags would have delays associated with X10. You can easily do the same with a program. i.e. run the Then part to set the program to true or else part to set the program to false. Then you can use the status of that program 2. ISY does not keep previous state ... but, this requirement is part of the new triggers release With kind regards, Michel

Hi evarsanyi, Would you be kind enough to try the following: When you have the issue, do a query on the device, then Right mouse click on the node and choose rename. In the rename dialog, just click OK (you do not have to actually rename it). Please let me know if after reboot you still get the same error. If you do, it most probably has to do with communications error. If not, then we have a bug in ISY. With kind regards, Michel

Hi kcrossley, Please go to Tools | Diagnostics | Event Viewer level 3 and try removing a device. Does it time out (i.e. you get a series of INST-ACK without INST-SRX)? With kind regards, Michel

Hi evarsanyi, Does it only happen after each reboot? With kind regards, Michel

Hi Paul, As much as I would love you to buy an ISY, at the same time I do not want to disappoint you. At the moment, you can use the status of programs as flags (true/false). We are working on variable support but I cannot really give you an ETA. With kind regards, Michel

Hi Mike, At this point, it would make a lot more sense to actually request for the latest version of IOLinc which would solve most of the issues you are grappling with. With kind regards, Michel

Hello, Apologies for any confusion I may have caused by pointing some of you to use http://www.universal-devices.com/99i/2.7.7/admin.jnlp ... ISY has two pieces: firmware which runs on ISY and client which is a Java applet/application. One could be using 2.7.7 UI features without having 2.7.7 firmware installed. As such, if you go to Help | About and it shows 2.7.6, then you do NOT have 2.7.7 installed. smileyw, yes, I am certain I was told v39 ... With kind regards, Michel

Hi all, The firmware that supports thermostat updates is 2.7.7/2 which is not out yet. Those who are on our 2.7.7 list, shall be notified of the release of this firmware. With kind regards, Michel

Hi Heiko, I got it ... this seems to be a bug. I have opened a bug to investigate. Thanks SO very much and with kind regards, Michel

Hi Heiko, Repeating random (in your case) means that it would either repeat the block or not execute at all. I think what you need is to use the Random function on Wait instead of repeat. This way, the amount of time waited for the next statement will be random. With kind regards, Michel

Hi Heiko, Thanks so very much. We will get right on it. With kind regards, Michel Unfortunately this doesn't work either. If I select 'Raw Text', then there's no 'Replace with' available. There was no 'not specified' available when I chose the type 'Insteon'. In addition to that, simply selecting the correct device didn't help either. As soon as I change it (manually) from 'not specified' to the correct device, the action (i.e. setting heat setpoint to 72) is lost (in this case it defaulted back to 'query') and I had to set everything again. My ISY is already configured correctly again, but you may get a flood of complains once folks start replacing their thermostat adapter with the v2.0. Heiko