Michel Kohanim

Hi rlebel, I am not sure how HouseLinc is capable of doing such a feat since - to conserve battery - motion sensors are deaf to INSTEON while not activated. You might want to try activating the motion sensor (by moving in front of it) and then test and see if it responds to ISY settings. With kind regards, Michel

Hi Robert, What's your ISY's firmware version? You should be able to do that on firmware 2.7.6 and above: 1. Click on the Sensor node 2. In the main panel, click on the Set Options node With kind regards, Michel

Hello Xathros, My pleasure. I really wished I could give you better news especially in this economy. With kind regards, Michel

Hi chicharon, I totally understand what you mean and I can assure you that we are doing as much as we possibly can given our resources and constraints. Variables are not like modules or other INSTEON devices for which we can add support. Triggers are like the brain for ISY and, as such, what we have to do is like a brain surgery. We are completely aware how important this feature is and all I can say is that it will shall be done. We just have to schedule such that it will have the least amount of impact and ensure that migration is considered thoroughly. I am really sorry I cannot give you more information as far as timelines. With kind regards, Michel I would never suggest "100s" or even tens of beta releases (between official releases) nor am I implying criticism here (sorry you took it this way). We are privy to what is targeted for the next beta release and those changes are scheduled to take roughly 4 months from the last beta release. If the changes defined in 2.7.7 take this amount of time and variable support is considered a major change and there is no estimate on when variable support might be implemented then it is difficult to imaging when this feature might be delivered. That was my point IRT releases. I wish it wasn't left up to me to calculate when we might see such a feature but without a roadmap or a statement that includes a possible target date, there is nothing else to go on. This is an enhancement that is important enough that I cannot help but try to determine when it might become a reality.

Chicharon, I understand your disappointment. Sometimes we all lose the sight of the fact that as an organization, we have to first ensure that the company continues to run and operate otherwise we'll be letting down all our customers. I have no choice but to ignore your comments about the release cycles simply because you are not privy to what is actually being done internally. Furthermore, having 100s of beta releases with minor changes is a support nightmare for us. As I mentioned before, changing the way triggers work goes deep into every part of the code. We are currently investigating two approaches one of which is less complicated but less powerful and the other one of which is extremely powerful but extremely complicated. With kind regards, Michel

Hi Xathros, I am so very sorry for being the bearer of bad news. Have you tried calling IES to see if they are willing to upgrade you? We use NetGear FS108P which is quite good. Cross linking requires something like PowerHome. The main issue is that if you change anything in ISY, then you will immediately be out of synch and will probably have even more problems. With kind regards, Michel

Hi, I will check into this as it seems that the GUI is doing something quite strange. With kind regards, Michel

Hi tbe, Good to hear back from you. I specifically made a build for you to test and explicitly asked for your input but one never arrived. As such, I reverted all the changes. It would've been great if you had actually tested the solution to let us know if it worked with your KPLs. With kind regards, Michel

Hello mpf541, What you need to do is to drop all those devices that you would like to be controlled by one another into a scene as CONTROLLERS. You can find more information here about Multi-Way Circuit: http://www.universal-devices.com/mwiki/ ... ide#Scenes With kind regards, Michel

Hi Moz, Unfortunately no! The main question for me is why is there a bad link in the KPL? Did you have any communications errors during restore? As far as the extra links, the reason they are there is because the device has not been defragmented. Although having extra records does not pose any problems but a restore SHOULD clear all the extra records. With kind regards, Michel

Hello Xathros, Unfortunately the way INSTEON is implemented, the only way you could have ISY hear what you do with another PLM is to cross link all those devices in both PLMs. This is quite a daunting task and no tools currently support this type of configuration. You might want to call IES and see if they would be willing to replace your PLM based touchscreen with the POE version in which case the status of all devices are in synch regardless of where/how the status has changed. IES's POE version automatically finds ISY on the network and configures itself for communications with ISY. With kind regards, Michel

Hi, What we have to do is to make sure that ISY hears the button press (D). Would you be kind enough to open the Event Viewer on level 3 and make sure that ISY hears the button when you press it? With kind regards, Michel

Hi Illusion, Based on the logs, ISY does think that the Front Portch KPL is On. I am not sure why your program would run the else clause unless there's another program that's running it explicitly. Direct commands all get a response back from the device and, as such, either they will be in error (with the ! mark) or they will have the correct status. With kind regards, Michel

Hello apostolakis, As a workaround, you could always use one of the many iPhone apps for ISY: iLinc, TouchSwitch, eKeypad (supports ELK as well). With kind regards, Michel

Hi johnmsch, When the user=system, the 0/null mean absolutely nothing. They are not applicable. 5012 simply means that the Admin Console (or any other ISY client such as iLinc) did not properly say goodbye to ISY. ISY was trying to communicate with it and it didn't respond and therefore, ISY is expiring its subscription by force. With kind regards, Michel

ergodic, You convinced me. Sounds good. It shall be done. Priority = medium. With kind regards, Michel

Hi IM, That's what I heard about 1 year ago. Unfortunately I have not followed up and hoped that they would show up by themselves. I will follow up - and if given permission - I will post back. With kind regards, Michel Michel, Am I to understand that Smarthome is working on implementing S/N measurement in the Insteon devices themselves?? Than would truly be a boon to the Insteon community. Do you know if this would be implemented in individual modules or just the PLM? IM

Hi dss, The hop count only means the number of hops remaining before a repeater stops repeating. I do not think it would give a lot of information if the max count is 3. With kind regards, Michel

Hi Jay, Yes, ISY is compatible with IOLinc but perhaps you might want to try TriggerLinc instead simply because you won't have to run wires. With kind regards, Michel

Hi dss, The first part of grouping devices does not seem very difficult. The second part which requires checking signal ratios is a little bit more involved. For that we have to wait for the long awaited S/N ratio from INSTEON devices. With kind regards, Michel

Hi Jay, I am so very glad to hear you are enjoying your ISY. The main question is whether or not recessed lights, cabinet lights, and under cabinet lights are controlled by INSTEON devices. If not, then the you might want to consider InLineLincs for each set. Then, the rest would be as simple as creating a scene ( http://www.universal-devices.com/mwiki/ ... ide#Scenes ). I do not think dimmers can control low voltage lights. With kind regards, Michel

Hi Oktane, Correct. But, when you add back, and if you want those links, you have to make sure you use the 3rd option. And here comes the risk: if the link is 1/2 or orphaned, then the scenes created by ISY might not actually reflect reality (as much as ISY tries to reconstruct the other half based on what it thinks the other half should be). In most cases, the best configuration is the one that you actually know what you want the function to be and then use ISY to create it. With kind regards, Michel

Hi Joel, Very interesting and mind boggling at the same time. Please do keep me posted. With kind regards, Michel

Hi Brian, I am so very sorry you had to go through this. I should have mentioned the workaround: rename your node. I do apologize. With kind regards, Michel

Hi Brian, Thanks SO very much. Based on your description, I was able to reproduce this issue and thus it's now a bug. I am hoping that it'll be fixed in 2.7.7. Thanks again and with kind regards, Michel