ISY Newbie

That part is where I get always confused. Factory reset is by pulling out the tab and pushing it back and holding, right? But you just do the Restore Device from the Admin Console? For some reason, I was lead to believe if you factory reset a deice, you'd have to re-link the device from scratch from Admin Console.

Sorry, I wasn't specific enough. No beeping or flashing. The keypad doesn't turn on or off the lights it's supposed to. The buttons have light behind them, so I think it has power at least.

I have a KeypadLinc dimmer switch with 8 buttons that has gone rogue. I tried the "Restore Device" command in Admin Console, but it didn't seem to work. Is there anything else that I should try before factory resetting the device?

I got it to work. The reason I wasn't able to start the linking process was because I didn't press and hold the set button hard enough.

Well, my question is in regard to Step. 2 Press the set button. I did but the LED light turned green, and I’m wondering if the switch indeed went into linking mode.

I did it this way because I can't read the address of the switch. I thought the "Start Linking" function serves as auto-discovery according to this thread: Can you be more specific about where I did it wrong?

Yes, the firmware and the UI match. I set the switch in communication mode by pressing and holding the set button for a few seconds, which turned the LED into green. Then I ran “Start Linking” under the Link Management menu of the Admin Console.

I'm trying to re-link a on-off Insteon switch that has gone rogue. After factory-resetting it, I pressed the set button for a few seconds to put it into communication mode. The LED light turns green, but my ISY can't discover it. Does the greed LED light indicate communication mode? I thought it should be red.

I have a few outdoors sensors that I can only access with a ladder. This will have to be put off until spring. But why do these sensors need to be written to all of a sudden? I've had the Isy for a few years, but never had something like this - all battery-operated sensors having a green 1011 icon in front of them - before. What could have triggered this? I'd like to avoid it in the future if possible. I don't mind getting a ladder and putting one or two sensors in the linking mode, but not all of them.

If the way to waken up battery-operated sensors is to press the set button, does that mean I have to go around the house and press the set button for all of the sensors?

Yes, that solved it! Thanks so much! A couple of questions. 1. What about all the other sensors that have the green 1011 icon in front of them? Do I have to repeat the same procedure, although they don't exhibit any problem? 2. When I close the door, the "open" variable changes to "off", but the "closed" variable remains blank. What's the purpose of the "closed" variable then?

I did, but it didn't fix the problem. The door/window sensor still doesn't seem to communicate with Isy. The green 1011 icon still appears in front of the sensor. BTW, the green light in the middle of the sensor blinks whenever I open or close the door.

That I understand. But it's strange that every single battery-operated sensor needs to be written to. Some of the sensors are woken up already, judging from the fact that programs to be triggered by them are executed.

Yes. I've upgraded to 4.9 and both UI and Firmware say 4.9 The green 1011 icons in front of battery-operated sensors are not going away. I haven't had them linger for this long before. Should it have something to do with Isy not getting signals from the new door/window sensor?

I assuming it was a question. 4.8. Should I upgrade? I realized that there is a recent update.

I get events from other devices just fine. I do have the green 10101 icon in front of this sensor, but for whatever reason, every sensor has a green 10101 icon in front of it that's not going away.

(I think) I've successfully linked a door-window sensor, as three new ***-open, ***-closed, ***-heartbeat links have been created. But when I open or close the sensor, it's not sending any signal. The only entry in the event log about this sensor is " Date/time : [2D DA 57 1 ] Link 0 : 0FF8 [E20146C538010001] Writing [E20146C538010001]" What's going on?

Now I get what you meant by UI. Both firmware and UI 4.7.3.

Firmware 4.x. UI is ISY portal. It's an insteon dimmer, which I have Alexa switch on/off individually, not part of a scene or program.

I’ve integrated ISY with Alexa, and they seem to work well. One oddity, however, is that the LED status lights on a dimmer wall switch don’t change accordingly. For example, the LED status lights don’t reach the top even when I have Alexa turn on the ceiling lights. Is this a known issue?

Thanks all for feedback. This is exciting.

Is installing a KPL just as easy as installing an Insteon light switch? I'd like to explore that idea too.

- I had harmony a while ago, but I ditched it when it couldn't handle Fire TV stick and required an upgrade to expensive Harmony hub. Now everything is controlled from the iPad through native apps - AV receiver, Fire TV Stick, and cable TV. - still 4.x with no node server. But I can easily install node servers on a 24/7 Windows computer. - Yes, there is a door on the theater, without a sensor yet. I'm exploring adding a sensor too. I want to go back to getting status signal from the AV receiver. That will be the most direct and accurate indicator, as you suggested. Where do I start?

Maybe it's just my family, but watching in the home theater is usually a group event for us. Whenever we are watching in the home theater, the vast majority of the occupants of the house are usually in there, not having to worry about someone else coming down to the basement for no reason. If it was just me or even me and my wife without the kids, I wouldn't feel inclined to go down, turn on the AV gear, roll down the screen, etc. Too much hassle. Maybe I'll just hang a sign on the door: "movie in progress. please knock before entering."

I was away over the weekend. Thanks to everyone for sharing their ideas. As to hardware, I have Denon AV receriver, isy994i, insteon motion sensors and insteon light switches. I don't have a lot of ISY programming experiences under my belt yet, but compared to other programming languages that I've used in the past like Python, ISY programming doesn't look very difficult or complex. Without knowing that ISY can detect some kind of signal from my AV receiver, I thought about adding another MS in the foyer leading to the home theater. Then a program will turn on the lights in the theater ONLY IF motion is detected by both the foyer MS and the home theater MS within a short span of time. Theater MS trigger alone will not turn the light switch on unless the foyer MS was triggered first. Of course, the downside to this is someone outside the theater walking into the foyer (not very likely) and someone in the theater fidgeting (very likely) at the same time. How do you create a condition that will return true if one MS was on within the previous, say 2 minutes of another MS?