Michel Kohanim

MikeB, Thanks so very much! We appreciate it. With kind regards, Michel

lafleur, Yes, we actually had this fucntionality and removed it due to pool servers not responding (once in a while) and thus causing problems. It's on our list of bugs to look at. Thanks so very much, With kind regards, Michel

jgraziano, Unfortunately, we do not have official (or otherwise) support for EZxxx devices. At the moment, X10 motion sensors are the only ones that can be supported. With kind regards, Michel

marko, Excellent. Thanks so very much for letting us know. With kind regards, Michel

Jim, Got it ... it shall be reviewed and decided upon shortly. With kind regards, Michel

jgraziano, You are not missing anything ... that's precisely the function of the folder condition: to limit the run time of the programs within. You may also want to add other programs in the same folder which are constrained by the same condition as well as use your current program (the output) in other programs (resuse your programs). With kind regards, Michel

jgraziano, Let me see if I got it correctly: You simply want a tab where you can tabulate your X10 codes and assign them names. Then, you would like to use the names, as assigned in the tab, for your triggers. Right? With kind regards, Michel

Hello jgraziano, We have never tested it with 2000 so I do not know! I am so very sorry that you are experiencing this issue. With kind regards, Michel

Frank, Yes, you are correct! With kind regards, Michel

Hi Marko, We did find a bug in ISY. By any chance, did you add your devices using "Add New Insteon Device"? If so, this feature does NOT overwrite existing links and that's what's causing all your problems. As a work-around for corrupted devices, would you be kind enough to do the following: 1. If you are adding your devices by Address, make sure to follow them up with a Restore Device OR 2. Add your device using the "Start Linking" method Please do be kind enough to let me know how it goes. With kind regards, Michel

Frank, I wanted to verify that there's indeed a bug in ISY when: 1. Using "Add New Insteon Device" 2. Choosing "Overwrite existing links" Using the above scenario, existing links are NOT overwritten. This said, however, if you choose the "Start Linking" option and then choose "Overwrite existing links", then existing links are indeed overwritten. You can also follow up "Add New Insteon Device" with a "Restore Device" after the addition into ISY. Thanks so very much for finding this bug. It shall be fixed in the next release. Furthermore, it seems that 350 M.S. actually works all the time with PLMs v56 and above and intermittently with PLMs version 52 and not at all with PLMs version 4A. This is quite interesting and something that we would have to investigate more since, at the moment, this behavior is unexplainable! With kind regards, Michel

Mark, Thank you. Done and included in the next release. With kind regards, Michel

RLIKWARTZ, Please read: http://forum.universal-devices.com/viewtopic.php?t=459 Apologies for the inconvenience, With kind regards, Michel

Hello GPG, This is indeed interesting. None of the past releases have changed anything by the way of communicating with devices. The only change was that ISY "considered" devices with 00 in first/second byte as "group" commands and thus didn't update the status "in ISY" correctly. This had nothing to do with communications on the "outbound" pipe. Please do let us know of the outcome of your experiments. Thanks and with kind regards, Michel

Marko, Thanks so very much for taking the time and going through the trouble of diagnosing the issues. If I understand it correctly, your PLM is reset, your ISY is factory reset, your KPL/SL are reset, and in the first scene you create, the controllers do not control each other but ISY can control both. If this is the case, then the PLM is NOT the culprit simply because ISY can control the scene. Device to device links (i.e. your KPL to SL) do not require PLM to be functional. So, this leads me to believe one or more of the following: 1. We have a bug in ISY ... for which I have already started the root cause analysis 2. Are you sure you are putting both of your devices as "controllers" in the scene? 3. If 2 is "true", then could it be that "one" of your devices (the responder usually) is defective The next step is please allow me to figure out if we have a bug in ISY. This should not take longer than late tonight or early tomorrow morning. If we cannot find a bug/reproduce the probelm, and if the answer to #2 above is "yes", then we have to figure out which one of your devices are causing the problem. Again, please accept my sincere apologies for the troubles you're experiencing. With kind regards, Michel

Rand, You are 100% correct. The minimum delay IS 500 mS. Anything lower simply confuses the PLM and only "random" data is written to the network. The commands to change the delay/timeout/baudrate have been removed from the shell menu system but they are still accessible if you know them! With kind regards, Michel Where did you find the option for Requests Delay? I thought 500ms was the minimum for Insteon (send/receive), but only nerdlincs need to know this. You have confused me now! Rand

Frank, With sincere apologies for tardy reply. I must tell you that, at the moment, I do think that there are too many unexplainable issues in your dealings with ISY (which really trouble me): 1. Querying a device should only take one Progress Bar run. If it takes more, there is a problem 2. If ISY cannot control your scene, it means only one thing: your devices in the scene do not have the responder/slave links in them or the signal is not going out of PLM to the group In short, INSTEON signals do not get to their destinations! All of which lead me to suspect that in all likelihood we will never be able to have a stable system unless we figure out why! So, the variables are: 1. ISY 2. PLM ... you have the Beta PLM so this shouldn't be the problem 3. INSTEON network/powerline/noise issues 4. One or more defective devices on the network In order to ascertain which is the culprit, I would be delighted to send you another ISY and you can redo your experiments. If the other ISY also exhibits the same issues, then it would take the Master of INSTEON to figure out what is causing the signal loss. Again, please accept our sincere apologies for all the troubles you've been experiencing. With kind regards, Michel

Scott, At the moment, it's only receive. We do have plans for transmit but not till much later in 2008. With kind regards, Michel

Rand, Yes! It shall be done ... With kind regards, Michel

MikeB, If the calculator says you have 448 links, then rest assured you have either gone beyond the max links or you are very very close. With kind regards,

maui4marko, Ah, I had totally forgotten that you have the Beta PLM. No, I don't think the PLM is the issue. I think something is "seriously" wrong somewhere. The reason that factory reset/restore device does not fix the problem is that the the responders in the scene have to have a slave link pointing to your KPL. It seems that the responders in your scene do not have that link. Would you be kind enough to let me know what happens if you remove of the responders from the scene and then try adding it back? Thanks and with kind regards, Michel

maui4marko, Thanks so very much for the update. The fact that the status of your devices were always off means that the "links" were not written to the PLM. Two cases: 1. The PLM was locked up 2. You have reached the 417 max number of links allowed by the PLM. How many devices do you have? This said, however, I still can't figure out why your would lose your scenes. This, to me, is a much more serious problem which requires more investigation. Please do let me know if you find other strange behavior. With kind regards, Michel

maui4marko, Apologies for the inconvenience. You do not have to use that link. What you are doing it correct (going directly to the device's URL). We might have a bigger problem than the update to 2.4.13 if you've lost your previously created scenes/updates. Would you do me a favor? Please create one scene, call it Test, add a device into it as a Responder, and then reboot ISY. Please let me know if still have the scene and the device after reboot. With kind regards, Michel

MikeB, As of right now, we would have to count each link in the PLM. In the future generations of the PLM, we would know how many more links are available. With kind regards, Michel