Michel Kohanim

Thanks Nick. Will look into it. I am just afraid we are going to drain the battery for those 5% of the times that we want to do programming. With kind regards, Michel

Hi aLf, Yes: 1. Pull the set button out and leave it out for 10 seconds 2. Push it back in and keep in held in for 10 seconds 3. Right mouse click on it in ISY and choose Restore Device Everything else should be programmed. With kind regards, Michel

Hi jfvalenti, Why don't you use the Wait function with the Random attribute. It seems that the days are Wed, Thu, Fri, and Sat. So, make your condition as follows If On Wed Time is 6:00:00PM Or On Thu Time is 6:00:00PM Or On Fri Time is 6:00:00PM Or On Sat Time is 6:00:00PM Then Wait 0 hours 45 minutes 00 seconds Random Do whatever needs to be done So, the random will pick a number between 0 minutes (6:00 PM) up to 45 minutes (6:45 PM). With kind regards, Michel

Hi again, I think it would be best to factory reset it and see what happens before trashing it. With kind regards, Michel

Hi Glenn, Great! If you are not going to use Modules (WeatherBug, Networking, etc.) there's really no need to upgrade to 99i. Unfortunately, 99i upgrade does not come with a PLM. With kind regards, Michel

Hi Glenn, I have dealt with this exact issue twice over the past week. If I am correct, your PLM has lost ALL its links (sometimes happens after a power surge). Please go to Tools | Diagnostics | Show PLM Links Table and let me know if you get any links in the PLM. After it completes click the Count button to see how many links you have. Usually you can assume that the number of links in the PLM are at least 1.5 times the number of devices you have. So, if you have unusually low number of links or no links at all, then you would need to restore your PLM: File | Restore Modem (PLM). If this works, then it's a good idea to get a replacement for your PLM. With kind regards, Michel

Hi Nick, Are you certain that this is what they do? If so, what command do they send to the MS? There are only certain commands that the MS understands. Your input is greatly appreciated. With kind regards, Michel I don't think they are doing anything secret. You just have a very limited time window, as soon as HL2 receives an on command it sends a command to the motion sensor retrying if needed. Everytime the motion sensor sends or recieves a command it will stay awake for a second or two.

Hi aLf, Yes, you are correct. Sorry for the confusion. With kind regards, Michel

Hi rlebel, Then I am not sure how HL can do this unless they have a secret way of putting Motion Sensors into programming mode remotely. With kind regards, Michel

Hi gmurch, Are these triggers time based or device/status based? If time based, can you make sure your ISY has the correct time? If status based, can you make sure that the Admin Console shows the correct status for your devices when you turn them on/off physically? i.e. does ISY hear state changes? With kind regards, Michel

Hello gmurch, I am so very sorry to hear this. By triggers quitting, does it mean that you ONLY triggers cannot control your devices OR does it mean that you can no longer control any of your devices even from within the Admin Console? i.e. Can you turn on/off a device from Admin Console? Also, what's the status of the programs in the Program Summary tab? With kind regards, Michel

Hi andrewm, Thanks so very much for the update and apologies for not having gotten back to you sooner. With kind regards, Michel

Hi Dave, Welcome to our world and I sure hope that you will enjoy it. In all likelihood you have version 2.7.0 which is the last official version. To check, on the Admin Console, please go to Help | About and you will see the version. Our latest beta is 2.7.6 which you can find here (http://forum.universal-devices.com/viewtopic.php?t=3007). 2.7.7 (Beta) should by out by mid November. With kind regards, Michel

Hi aLf, Have you used the Back Light settings on the Admin Console for your KPL? With kind regards, Michel

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