petesc2

My IOLinc garage kit is working happily with 2.7.3. I linked it to a button on a floating KPL (in an enclosure) and the program to close the door after a set time period is working great now.

I've submitted a similar question to SH support regarding query of IOLinc sensor for the garage door kit. Their reply is that they know of no issues and are happy to exchange the unit for me. If I have to buy two units to make this work, then I wish they had made the sensor and relay as separate units...

Hi Michel, I'm at 2.7.2 right now. I was eagerly awaiting 2.7.3 before finding out the IOLinc firmware issue. SH tech support has not addressed it yet, instead saying it works for them on ISY firmware 2.6.13 or better. I have a feeling this might not be resolved for a while... You're absolutely right about the status when turning on/off the relay. Since I'm starting the timer when the garage door opens, this is exactly where the issue comes from. Using 2 IOLincs is an expensive solution, but the only one for now I suppose... sigh. On the other hand the leak sensor won't have this issue because the relay is not being used, right? Peter

So here's a new finding. The alert text message was triggered at the 5AM daily query all. Apparently the sensor status came back Off, starting the THEN branch and enabling the Garage Door Control program, which also came back with a Off. Now I have a few questions... 1. I'm confused about the initial setting of the sensor. If the garage magnetic sensor is in contact (door closed), or the water sensor is wet, and the set button is pressed in that state when linking with the ISY, does it trigger an On or Off? 2. To create a program that detects status change from door closed to door open, does one use: If Status 'Garage-IOL-Sen-GarageDoor' is Off And Status 'Garage-IOL-Sen-GarageDoor' is not On Assuming Off is magnetic sensor not in contact? I have a feeling this has something to do with the current behavior. Any help would be appreciated!

I need some help with ISY and the IOLinc garage kit. The fact that queries do not provide the status of the sensor is a known issue, and I've given up on resolution for the time being, since UD says it is a firmware issue, and SH says they don't have a problem with ISY 2.6.13 and above. I don't have any links set up with the IOLinc, just control via ISY as follows: Garage Door Status If Status 'Garage-IOL-Sen-GarageDoor' is Off And Status 'Garage-IOL-Sen-GarageDoor' is not On Then Send Notification to All Wait 25 minutes Enable Program 'Garage Door Control' Run Program 'Garage Door Control' (If) Else - No Action Garage Door Control If Program 'Garage Door Status' is True And Status 'Garage-IOL-Sen-GarageDoor' if Off Then // Use Garage-IOL-Rel-GarageDoor to close door, not yet implemented Send Notification to All Disable Program 'Garage Door Control' Else Send Notification to All Disable Program 'Garage Door Control' This program seemed to work ok initially. It would send a message when the door opens, then send another after 25 minutes. If the door is closed before the 25 minute expiry, second message is not sent. However, while I'm away on travel, I get a text message at 5am that the door is open, then another 25 minutes later. You can imagine the anxiety that results. It turned out to be a false alarm, and this was the exact reason I didn't put the control for the relay in the program just yet. Is there something wrong with the logic of the program? Is there something wrong with the sensor status reporting? How can I make this 100% reliable so it can be put into actual use?

Hi LG, What you say makes sense. I can certainly disconnect the lamps and leave just the LampLincs to see if they respond better. There's nothing connected, but I can query the ISY for their status. I'm rather new to Xenon lights. I picked them because they run cooler than Halogens, but not much. Peter

Thanks Michel, I'll try a few more access points. Too bad I didn't pick them up before the 20% off sale expired last Friday at Smarthome... LG, The kitchen lights are new. I installed them as part of our kitchen remodel. I picked line voltage xenon lights (http://pegasusassociates.com/XenonLineV ... ights.html) specifically to avoid any noise-generating transformers. The light in the bathroom is line voltage halogen. The thing is, they were both installed this summer and had been working and responding properly until the recent updates. However, I didn't have the "all lights" scene until recently also, so I can't say for sure they would have worked back then. I did have to install a couple of inline filters for CFL lights in the past. The difference there is, after the light is turned on, I can no longer talk to it, and I get the no-response blinking on the sender (KPL) indicating there's noise after the light came on. In this case, there was no error blinking, and it only happens on the CL, not a KPL with the same scene. Peter

Here's part 2 to the test: 1. I moved the AP and CL to the bedroom, and right away the SWL did not turn on. 2. I decided to try the off command from the CL, and this time 3 of the LLs in the kitchen remained on. 3. I returned the AP and CL to the kitchen, but this time I tried on and off several times. Depending on the outlet of the CL, either all the lights would come on, or one of the LLs would remain off. For the off command, all lights would turn off except 2 or 3 of the LLs, depending on which outlet I used in the kitchen. 4. If I press the off button one more time, one of the LLs that remained on would turn off. If I continue to press the off button, by the 4th press the remaining LL would turn off. This is only happening on the CL. The same "all lights" scene on a KPL does just fine no matter where I plug it in (it is in an enclosure). Peter

Hi Michel, I did the following tests: 1. I moved one of the APs to the outlet next to the affected SWL. The affected SWL is in a bathroom, so there was an outlet right next to the SWL (on separate breakers). The light now responds to the CL. The AP was originally located 1 room away, in fact, 1 wall away. 2. I moved the other AP to the same outlet as the affected LL. In fact, I piggybacked the AP on top of the LL. Doing this did not change the outcome, one or more of the LLs on the same circuit does not respond. These are in the kitchen controlling undercabinet lights. 3. I moved the AP from the LL piggyback to another outlet just below the lights. I figured piggybacking the AP might be a no-no, so I'll try an outlet nearby. The LLs still did not respond to the CL. 4. With configuration 3, I tried to set the on level for the LLs once again via ISY, using both automatic mode and device reported mode. The LLs still did not respond to the CL. 5. I connected the CL on the same outlet as the AP in the kitchen. Now all LLs respond. In fact, all lights are responding. I got so excited that I began composing this reply. Now I'm wondering, does this mean I need to relocate the CL, or put an AP closer to the CL? Moving the CL would defeat the purpose, since it is used in a bedroom (just above the kitchen and those LLs), but why would it require an AP when nobody else needs it? I guess I should try that next, have an AP and the CL in the bedroom. Thanks for your help Michel. I posted this here originally thinking maybe the on levels weren't being programmed correctly in the CL. Peter

I began noticing strange behavior starting with 2.6.14. I have a ControLinc button (#4) that turns on/off all lights in the house. Starting 2.6.14 I noticed that it does not turn off (only sometimes) one of the lights controlled by a SwitchLinc showing V.35. At first I thought it was a problem with the new firmware on the SwitchLinc and tried to factory reset and relink it several times to no avail. Then I discovered that this scenario only happens with the ControLinc button. I say that because I have the same scene on a KeypadLinc and it functions as expected. After performing a factory reset on the ControLinc, then linking the scene again, all seemed to work, until I updated my ISY99i-Pro to 2.6.15. While all other devices still function normally, the ControLinc button for all lights now seem to have random problems leaving some lights off when turning all lights on, or vice versa. The affected lights include the same SwitchLinc as before, a KeypadLinc, and 2 LampLincs. I went to Smarthome to get the ControLinc replaced, but the new one shows the same firmware revision, and is behaving the same way. Thus far, I've done factory resets on all of the above devices. I think I need some help...

Thanks for the quick reply. I'm glad to hear it is in the queue.

I purchased an ISY-99 pro recently after reading all the positive reviews about the product and level of support. I've come to find all that to be true - the ISY is a great product and the support is incredible! I've been able to get things set up rather quickly with some 25 Insteon devices, created a couple of programs, and rubbing my hands together thinking, "what should I program next?" I find the email notification function on ISY to be a great idea, and want to incorporate it into my grand plan in automated monitoring and control of water leaks, the garage door, thermostat and sprinklers. I would like to be able to add custom messages in the email triggered by different events. However, it seems the only indicator of what happened in the message is the name of the program triggered. Is that correct? Is there a way to add any other text to the message? Does it make sense/ is it necessary to add the option of more details?