Michel Kohanim

Hi Matt, Please try Right Mouse Click->Add to Scene and let me know if you are still experiencing the same problem. Thanks and with kind regards, Michel

Hi Mark, As far as I know, KPL 1.65 is already out and we have not had any problems/issues with it (nor reported). If the sticker says 2.75, then you have the latest and greatest with the extended memory! With kind regards, Michel

Hello Mark, Again, I do apologize for all the inconvenience. 1. 1.6 KPLs have some very strange issues/behaviors that we basically had to put workarounds in our code 2. From our experience, if you are doing something physically to the switch that is being programmed, the outcome of the programming is not predictable. Also, depending on the PLM you have, you might experience scene related problems such as a device being turned on by a different scene, or not at all, failed requests, etc. In short, I strongly advise against any physical interaction with your devices while programming (or at least try to avoid as much as possible). With kind regards, Michel

My pleasure Mark and Yes, it does. With kind regards, Michel

Hello markbrown1, First of all, apologies for the inconvenience. We do have 2.7 Beta (2.6.1) release which includes some workaround for the problems you are experiencing. If you are interested, send an email to support@universal-devices.com. Your suggestion is excellent and parts of it will be implemented in our diagnosis release some time in the future. With kind regards, Michel

Hello retsell, The problem is: You have a non-toggle mode and thus the Control will never ever change its state from Switched Off to anything else (after the first time you switch it off, the state will never ever change). Therefore, your condition amounts to evaluating whether or not it's day time. What you might want to consider is to make this button toggle and use the the program to set its status (you have to put the button inside a scene as a responder) when it's day time. With kind regards, Michel

Hello Richard, My pleasure! I really do not know the answer to your question. From our perspective, we have been given a memory map and that's what we base our design on. With kind regards, Michel [quote name="morgan4x4 Looking forward to it' date=' many thanks! Curious, are the differences in KPL 1.6 behaviour variations in the 1.6 codebase, quality control issues, or diferences in hardware? Appreciate the fast response and assitance![/quote]

Brignolo, We have verified that Windows Mobile/Treo crash the system. We are still trying to figure out what's causing the repetitive logon screen. As far as Admin Console on your mobile phone, well, I think it would be quite difficult till such time that there are much more powerful phones than those out there. But, of course, this may happen very soon! With kind regards, Michel I'm using a Treo 700wx with Mobile 6 and I am experiencing similar problems. Occasionally, things go well...for a while...then I get a IE error message. The Administrative Console in never accessible and it just gives me the UD first screen without login fields. At one point I was able to access the Device menu successfully with my Treo. So much so that I was able to turn several of my devices on and off in rapid succession. This resulted in locking up my 99i to the point where it dissappeard from my network all together. Recyling the power brought it back. I was able to recreate that phenomemon by repeating the fast off/on of some devices. The power cycle fixed it again. Now bear in mind that my PLM is undersized for my devices/programs/*lincs, etc. Tomorrow I will get the new upgraded PLM and will try to recreate the failure. More tomorrow. Joe P.S. It would be really nice to be able to access the Administrative Console with a smartphone.

upstatemike, There might also be a program in ISY which is doing something based on the SG's motion sensor. So, again, having ISY off for a 24 hour period is the best option at this point. With kind regards, Michel

Hello Richard, in the next drop, there will be a workaround for non-toggle mode for versions 1.6 and above with the following caveat: Not all KPLs versions 1.6 and above behave the same! With kind regards, Michel

Hello Richard, Thank you for finding this. We just verified that with 1.6 and above this function makes all buttons non-toggle off. The next step is to see if this is KPL related or ISY related. I shall keep you posted with the outcome. With kind regards, Michel

upstatemike, At this point I think shutting off ISY for 24 hours is the best idea. Questions: Can Stargate control these devices? Do you have any other controller? With kind regards, Michel

accessha, You are 100% correct ... unfortunately - due to short release schedules and since we wanted to be completely functional in all levels - we put all the help/documentation/wizards for last. Hopefully, we'll get to it after our 2.7 release. With kind regards, Michel

Richard, In addition to what Rand suggested (thanks Rand!), you may want to try our 2.6.1 Beta release which has more support for KPL 1.5/6. My other question is: do you have the same issue with other KPLs (say, 1.4 or 1.65)? With kind regards, Michel

Hello upstatemike, Are any of the following devices KPL 1.5 or 1.6: Laundry Keypad Button C Outside Driveway Display Outside Mailbox Light With kind regards, Michel

Hello ResIpsa, If you've setup your remote access using ISY, then the combination of not being able to access it from My Lighting icon and remotely makes me suspect a firewall software on your system. If you wish, you can send me your URL (support@universal-devices.com) and I can check it out for you. With kind regards, Michel

upstatemike, Thanks. I don't think the problem is any of your switches ... I am almost certain that you either ISY on its own (bug) or a program within ISY is the culprit. We just have to figure out which! With kind regards, Michel

Hello upstatemike, Thanks so very much for the detailed response. Please see my comments below. With kind regards, Michel Same button on both keypads should not be the problem. I agree with you! May I humbly suggest a printout of your topology? At the minimum, this will ease the process of finding the link between these devices/scenes. It is possible but I wouldn't delete those scenes till we figure out the relationship between the two scenes (common devices/programs). With kind regards, Michel

Hi Falco, Except for Saturdays, you should normally expect a reply within a couple of hours. If you still haven't received the link to Beta download, please do follow up with another email to support@universal-devices.com Thanks and with kind regards, Michel

upstatemike, I am so very sorry for the inconvenience. This is indeed quite odd: If ISY knows about the status of all the devices in the scene - when they are auto activated - then the problem is only one of the following: 1. Please go to Configuration->ELK ... please make sure both of your ELK IP address/Port are BLANK 2. There's either a program (or a bug) which causes ISY to send that group command. Please do be kind enough to check the log to see who/what issued the command. 3. KPL 1.5/1.6 but that has already been ruled out With kind regards, Michel

Hello accessha, Please see my comments below. With kind regards, Michel You are correct! Correct Correct to some extent: you are modifying the on-levels/ramp-rates of all devices in that scene CONTROLLED by that CONTROLLER only. So, if you have two controllers in the same scene, then each controller has its own ol/rr s for each and everyone of the other members of the scene Correct Option 2 is activated when you physically click on a controller (say a KPL). Option 3 is when the scene is activated by ISY, say your Sunset scene. Yes, you choose option 2: in the scene, click on your RemoteLinc button 1 and then change the ol and rr of your LL as you desire They won't be changed unless you change them explicitly (wherever you see [Applied Locally])

edfinely, Working on both and should be there by the official release. With kind regards, Michel

Hi jonjonbear, Apologies for the misunderstanding. ISY has a configurable "repeat" times; you can also add Wait and Repeat in your programs to repeat certain messages. I really cannot talk about how HomeSeer works, but INSTEON protocol itself only has a HOP COUNT which basically means that each packet "may" be repeated HOP COUNT times on the network till it reaches its destination. Beyond that, PLMs and other devices do not repeat commands unless instructed to. So, I would assume that the repeat issue is either coming from HomeSeer or possibly some noise on the line. With kind regards, Michel

jonjonbear, As far as I know, HomeSeer does not send INSTEON group commands and thus if you turn on/off a group, it will send a sequence of on/off/actions to each device in the scene individually. In order to answer your question, please let me know if you have the same issue with two (or more) switches controlling other INSTEON devices. If so, then ISY will exhibit the same problem and so do any other INSTEON related solutions. As far as X10, nothing is repeated since (in most cases) there are no acknowledgments from the devices. With kind regards, Michel

MikeB, There's a 30 second timeout: you have to be doing something within every 30 seconds (from the previous action) otherwise you'll be logged out. With kind regards, Michel