Hi Michel,
I have not been checking in as often as I should. I am sorry i did not get to try the build that included button status control. I still think this would be good thing.
tbe
This is a big problem for me. I want to be able change button status on multiple keypads that control a common scene to accurately display current status. In HouseLinc2 software you can do this directly in the scene programming so that the commands are resident in the devices. Because only the load button is available in the scene to set “ON†or “OFF†you can only program a non load button to turn “ON†in a given scene. Because of this you have to create "button scenes" that tell a group of buttons to turn “OFF†because these no load buttons (KeyLink dimmer buttons B-H) cannot be programmed to do this within the initial scene. This adds a ton of complexity to the programming task as well as making the ISY work a whole lot harder than it needs to. The Insteon devices have the internal ability when a button is turned "ON" to send an "OFF" command to any button on a different keypad. This is a huge problem on more sophisticated installations. You should not have to create "button scenes" to accomplish this. You can do this with HouseLinc2 with out having to create "if / then" programming to accomplish it. I do however really like the stand alone processor strategy that the ISY99 brings to the equation. I believe this is well within the theoretical capabilities of the ISY99 and should be implemented. Creating “button scenes†and required programming is a royal pain in the arse and requires the ISY99 to work a lot harder than it needs to. All that needs to happen is an “ON/OFF†option on non load KeyLinc buttons that are responders. My button scenes for whatever reason have been somewhat unreliable working about 70-80% of the time. Which is a whole other issue; see thread “INSTEON Communication Issues - I am having real problems getting my system to play nice