matapan

LeeG, Regarding Q2: this is the auto discover scenario. 1. Set up ISY to initiate linking via auto discover mode. 2. Set KPD in linking mode. Expect: KPD to be discovered and show up in Admin Console. Actual: No device shows up in the Admin Console. With other devices, the expected result usually occurs.

I am starting to write a lot of programs, organizing them in folders. The programs appear in a reasonable order in the Program Details tab, with related programs in a folder organized under the folder hierarchy. In the Program Summary tab, the individual programs appear in alphabetical order in a flat organization. The hierarchy is displayed in a column which shows the path. This is hard to read and use. Is there any way to display programs in hierarchical order?

I have some old v1.3 Keypadlincs that could not be auto-discovered by ISY when the Keypadlinc was added to the network. I was able to add them manually to the network by providing the address of the device and specifying the device type. ISY99 is aware of these devices and can talk to them. The firmware version shows up as "v00" if one adds devices manually. I've discovered that this is normal from reading the postings here. Questions: 1. Is it possible for ISY to retrieve the device firmware version and update the Admin Console and its own database via an explicit command? 2. Why are some devices not auto discoverable? Is this an artifact of attempting to discover an older device?

Would the last execution time of a selected set of programs provide some indication of activity, particularly if the programs themselves relied on control changes?

I happened to be setting up Notifications on an ISY-26 with firmware version 2.7.15 when I noticed there was no Customizations tab for entering the text to be sent. Was this feature available in firmware version 2.7.15 for ISY-26?

Doesn't the ISY sync its time to a NTP server? I think my Mac and most Windows machines now have the same capability. So, theoretically, the time wouldn't be that far off, would it?

That's also what I've done as well, using checks for Control rather than status. Going further, I check both cases: If Device is Switched on and The devIce is not switched off The resulting program stays using such a check seems to yield results more in line with one's expectations as well.

Would a Dual-Band PLM and an Access Point near the breaker box provide a possible solution in the scenario described?

Thank you for the reply, LeeG. What is the relationship between the columns and the tree below in the same dialog?

I'm still on 3.1.14 and also experienced problems with incorrect Keypadlinc secondary button status. I'll be upgrading to 3.1.15 tonight to see if the upgrade also clears up the problem for me.

I think I understand the differences between creating a scene to handle mutually exclusive buttons and defining them using the feature in the Admin Console. What I want to understand is how to use the Admin Console's button grouping feature. The Wiki page describing the feature does not match the current UI (3.1.15). What are the checkboxes above the tree list for? Also, the UI warns you can corrupt scenes if you're not careful about how you go about performing this operation. Two questions: What are the manifestations of a corrupt scene - how do you recognize a scene has been corrupted? Second: How does one rectify the corruption once it happens? If I understood the consequences better and how to take care of it, I would probably have played around with the UI to figure it out.

Is there a good explanation available on how to set up Keypadlinc button grouping? I looked at the Wiki page on button grouping. It appears to be outdated, as the screenshots used don't match the actual button grouping dialog. The new dialog (I have firmware version 3.1.14) has a number of sections on the top of the screen with checkboxes. The wiki page doesn't show this. According to the wiki description, one simply drags the buttons one wants to group into one of the available scenes. Is this the way it works in the latest firmware release? I am at a loss as to how one sets up mutually exclusive button groups. I want to set up a group of three buttons where only one of the three buttons can be pressed.

Nice to hear a positive review of LED's, IndyMike. I really dislike CFLs for the communication issues they create with Insteon. Also good to hear that LED's are coming down in price. $10! That's much better than the $28 - $50 I've seen in stores lately.

Has anyone installed an LED for over 9 months yet? I'm curious about a couple of things: - Are LED's Insteon-friendly? Do they interfere with Insteon signals in a detrimental way? - If not, do they degrade over time, like CFL's do? - Did you get a dimmable LED bulb? Does it work well? - How do you like the light output compared to Incandescent or Halogen?

If you're going the AirPlay route, note that there is an app called Airfoil that can take input from things beyond iTunes and distribute the audio via Airplay. So, in the example cited previously using Google Translate, you could use Airfoil to distribute the audio wirelessly to any part of the home near an Airport Express connected to a powered speaker. The other advantage of using Airfoil is that it is Applescript-friendly - easier to manage Airplay output sources using this application than iTunes.

Thank you, Michel.

Hi, What is the most effective way to search for forum postings related to a topic? After reading the recent posting regarding a program that would intermittently trigger itself, and the response regarding the Keypadlinc 2D error, I tried searching the forums for this. The searches on the terms 'KPL 2D Keypadlinc' result in errors because the search terms are "too general". Really? What is the KPL 2D error? I've heard it's the culprit for the sporadic communication error messages in the Admin Console. If I read related postings on other sites correctly, other control applications avoid these errors and other similar issues like the v35 Switchlinc errors. Is there a technical reason why the same can't be done with ISY? How does one designate the load device for the topology feature in the Admin Console? The resulting webpage generated is a very, very handy map of an installation. BTW, I noticed some early Keypadlinc devices I have (v.1.3) have firmware versions reported as "v00" - is this normal?

OberKC: I was actually think more along the lines of a motion sensor, not a contact sensor for a door, for the same reasons you cited. The closest I've been able to come to is trying to find a countdown period which eliminates the false readings but which isn't too long so as to be energy inefficient, then adding a manual override condition in the form of a third program which just checks to see if the circuit was manually turned off or not and adding the logic to the other two programs accordingly. I'm curious if anyone has found better occupancy check that more closely follows the user's intent and optimizes energy savings without becoming a detriment to the equipment being controlled (minimize on/off cycles as much as possible).

What are the functional differences between the Insteon and X10 motion sensors, beyond the communication reliability aspect of these devices? There's the fact that Insteon motion sensors have a state that can be readily checked, whereas the X10 device does not. But one can accommodate state checking by creating a simple program as a retainer for the X10 motion sensor's state: Motion Sensor On State Check: If X10 'A1/On (3) is received Then Run Program 'A1 Motion Sensor State' (Then Path) Else -- No Actions -- Motion Sensor Off State Check: If X10 'A1/Off (11) is received Then Run Program 'A1 Motion Sensor State' (Else Path) Else -- No Actions -- A1 Motion Sensor State: If -- No Condition -- Then -- No Actions -- Else -- No Actions -- The status of the program 'A1 Motion Sensor State' tracks the motion sensor state - True means the motion was sensed, false means no motion. I know, more work just to track the state of a motion sensor, but the cost differential is pretty big - if you deploy lots of sensors, that's a lot of money. Any real functional advantages of using the Insteon motion sensor?

The general objective is to qualify occupancy, to discriminate between a quick in and out of a room vs. true occupancy in the fastest way possible. "Buffering" checks using a motion sensor on entry and exit seems to be one approach. Not sure if there are any better ways. I've coded the exit check in two programs: Program Test1: If Status 'Sensor' is On and 'Target Device Controlled' is Off Then Set 'Target Device Controlled' On Else -- No Actions -- Program Test2: If Status 'Sensor' is Off and Program 'Test1' is False Then Wait Set 'Target Device Controlled' Off Same kind of program for entry check, but that's not optimal; for lights, that might be okay, since most people turn a paddle on by themselves manually. For climate control, a buffered entry check isn't optimal because it takes a while for the temp to adjust, and the shorter the wait time, the better. I'm wondering what a better entry check might be, to discriminate between a quick in and out of a room and a true occupancy scenario.

Thank you LeeG for the explanation regarding program evaluation and when they occur. I am still trying to wrap my head around event programming, especially evaluations and preventing infinite loops. In a different example, say you want to check on a change of state several times before committing a device state change - taking multiple state samples. In pseudocode, I imagine the logic would work like this: if is ON then turn on else wait 1 minute check the if the is still OFF then turn OFF So, in ISY, is this best done in 3 programs, where the first program sets the target device on if the trigger device is on, with the else clause passing off to another program, which evaluates the previous program state, along with the trigger device state, etc? Or, is there a better way? As a debugging aid, is there a good way to get the program summary page to refresh automatically when program states change?

LeeG: Here's one program that runs through the Then path, but evaluates to False on the summary page. It's my garage door opener program: If Status 'Garage -Sensor' is On And Control 'Keypadlinc Garage Door Button' is Switched On Then Set 'Garage - Relay' On Wait 5 seconds Set Garage -Relay Query Else - No Actions - I know the program runs through the Then path because the relay is energized and the garage door opens. Based on what I read in the Wiki, I think the program should evaluate to 'True' after execution. It does show up as False through in the Summary.

According to the Wiki's Condition page: "The program state is set to True when the program enters the Then path and False when it enters the Else path. Folder conditions can be set based on the program state. This state is also reported in the Status column in the program summary table." I have some programs that are evaluated and run the Then path, yet their status shows as "False". I am running firmware version 3.1.14. Is there anything which would contribute to the program state being evaluated as "False" when it did run through the Then path in the program?

What are the amperage requirements for the Venstar thermostat? I found a 24VAC AC adapter supplying 1.25 amps. Is this a suitable supply?

I have a 7 day programmable Venstar thermostat with the Insteon adapter installed. Is it possible to query for the program settings for Morning, Day, Evening and Night and use this as part of the logic in a program?