Michel Kohanim

Hi tahoe, It's not available now but it's on the list of those requirements which we are hoping to have included in the next releases (2.8+). With kind regards, Michel

Hi Eric, Thanks so very much. I seriously doubt the problem to be signal related. It's how we program the EZIO to use different groups for input. We do this to make a distinction between the inputs and outputs and since EZIO does not let us change the group numbers for output, that's why we have to change the group numbers for input. If we use the same group numbers, then ISY would not know if a relay was turned on or if the input was shorted. So, we have to figure out a way to allow for different group numbers to be used. I am still awaiting a response from SH. Thanks again and with kind regards, Michel

Hi someguy, This could mean two things: 1. ISY could not communicate with the device 2. The device refuses to allow a memory location to be written The best test would be to factory reset the device. If that works, then the issue was the device itself. If not, then we have to figure out where the signal is getting blocked. With kind regards, Michel

Hi X, Thanks so very much. Fixed many of the Linux related issues including the missing background. Still could not figure out how to add background to the tree. Please send your uuid to support@universal-devices.com. With kind regards, Michel

Hi Eric, WOW ... this is amazing and I must say one of the most comprehensive set of diagnostic aids I have ever seen. First of all, I wanted to make sure you knew that you can disable Query at startup while you are testing. This feature is on the Configuration/System tab. Secondly, based on all the logs and your explanations, the problem is definitely not noise related. The problem is how we should program EZIO such that it would work. From what I gather, the problem is that we are using groups 9 and up for inputs where as EZIO (itself) uses groups 1 and up for input. This was not a problem in their previous firmware releases but apparently now has become a problem. I am going to contact them again and see if we can find a resolution or at least some help in programming the latest version of EZIO. I am truly sorry for all the trouble you've been going through ... With kind regards, Michel

Hello WD, Thanks so very much for the update. I am still waiting for a response from SH on the hold time. We are simply sending it what their documentation outlines. So, I would assume that the minimum amount of hold time is 2 seconds. With kind regards, Michel

Hi evarsanyi, This was reported once before but we could not reproduce it. Can you try one more thing: disable it and see if it still complains. Thanks so very much for the troubleshooting. With kind regards, Michel

Hi, Condition test for communications errors is on our list. I am not sure why we would need conditional for disabled: commands sent to disabled devices are ignored by ISY. With kind regards, Michel

Hi, Thanks so very much. Just added support for it ... since this device is responder only, the change is only on the UI. As such, till our next drop, simply ignore the "Unsupported Device" phrase ... all functions should work properly regardless. With kind regards, Michel

Hi tome, Excellent. There is INSTEON protocol specification available on code.insteon.net but you will have to register. I do not recommend it unless you have some free time and a lot of coffee readily available. ACK means that the PLM received ISY's message and sent it out to the network. SRX means that the device responded to the message. Some loads (such as CFL) could actually impact communications to the point that the device itself will become deaf and dumb. With kind regards, Michel

Hi tome, Unfortunately ISY does not know if your router has been rebooted. Also, UPnP entries do not last after a reboot. Frequent querying the router for changes in ISP IP address, in some routers, causes the router to crash and that's why we took it out. For best and most reliable performance, it's best to do the following: 1. Assign a static IP address for your ISY 2. Create port forwarding rules in your router manually to point to ISY's HTTPS port 3. [optional] add dynamic dns service so you would not have to remember your ISY's IP address (in case it changes) With kind regards, Michel

Hi evarsanyi, The step by step using the address is: 1. Link Management | Add New INSTEON Device 2. Enter the address of your EZIO Based on their documentation, the input group numbers can be set to different numbers and that's what we are doing. With kind regards, Michel

Hi, Would you be kind enough to send me the link on SmartHome website to this device. With kind regards, Michel

Hi davep, Please increase the timeout. Also, in the next release 2.7.7, we have added provisions to allow multiple emails to be sent. If you are not on our alpha 2.7.7 list, please send an email to support@universal-devices.com to be included. With kind regards, Michel

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