builderb

You could use 'if status of light is not off', then set variable to one if you want a global timer, but you could also use 'if control light is switched on' if you only want this behavior to occur when the light is activated from the store room switch. Program 2 should only trigger when the variable changes, assuming it's a state variable. Sent from my iPad using Tapatalk

So essentially the two-wire switch leaks just enough power through the circuit to power itself, but not to light an incandescent bulb? Interesting. Sent from my iPad using Tapatalk

My thought too. He might need to be connected to the NC contact in this situation. Sent from my iPad using Tapatalk

You need to set up some logic to determine if both phones are gone. Personally, I use a home state variable that is 1 when everyone is home, 2 when only some are home, and 3 when everyone is away. Then I have a few programs based on each phone status to set those variables. I'm headed down the same ibeacon road Teken just pointed you towards for my own presence detection too. I have tried other methods, including wifi and geofencing, but this seems to have the most promise of responsiveness and accuracy that I've seen so far. Sent from my iPad using Tapatalk

Go to Help > About in the drop down menu. It will tell you what version, modules, etc. Sent from my iPad using Tapatalk

Guess I'm not too worried about the ones under my eaves! I had some concerns about putting them outdoors initially. Sent from my iPad using Tapatalk

I've got 5 states. At 0, that's a power interruption and it triggers certain startup programs to run. 1 is All Home, so internal lights mostly, exterior is off. 2 is Some (but not all) Home, so interior lights are on, but so are some exteriors. 3 is All Away, that's the typical weekday when everyone is at work or school, and 4 is Vacation, which is 24 hours of no activity. Schedules that depend on these conditions are kept in different folders that run based on the state number. I also set a Bedtime variable to 1 from a mini-remote taped to the wall next to the bed. The variable is reset to 0 at 4:00am each morning, but nothing is triggered by that. I also have IsDayOff variables for each of us to kill standard morning schedules and heater adjustments if someone is sick or otherwise home unexpectedly. At some point I'd like to be able to put a vacation event in my calendar, and have that translate to control of that variable too, but not there yet. Sent from my iPad using Tapatalk

Before my ISY, I was using Indigo on my Mac for HA. I just got an email from them about a new plugin that is available that aims to provide a framework for virtual devices. The first module for it allows you to create a virtual thermostat from a temperature sensing device, and say, a relay module. So, if you had a temperature sensor, and a small space heater connected to an outlet linc in a small room, you can interact with them as a single thermostat device. Interesting concept.

Other people can probably help you out better there. I'm using the Nest, and I actually am pretty happy with it overall. But it doesn't integrate well. I don't have any z-wave devices myself, but I know several people here do, and can probably speak from experience. There are Zigbee t'stats too. Forgot to mention that. Again, I don't have any direct experience with them either, I only know what I've read. Sent from my iPad using Tapatalk

You might consider the z-wave flavored ISY for t'stat control. Reviews of the Insteon t'stat are mixed. The Nest would require some kind of additional computing power (like a raspberry pi, for example), and some level of comfort with the tools of computer programming, ie github, the command line, etc. I've spent a bit of time fussing with my ISY and my Nest, just to use REST statements to issue static commands. I'm slowly getting there. Anything more complex requires the above-noted additional computing capability. But the whole thing could break at any time if the Nest API changes. I wouldn't use it for client-targeted applications. Perhaps that will change with the new firmware, or if UDI is able to offer a Nest module. But they just announced support for commercial energy management via the z-wave module (edit: or is it via Zigbee?). That's available right now, and it's officially supported (I believe, not trying to speak for UDI here). The rest of it sounds doable. The remote issue kinda depends. I have not worked with the Harmony, but it seems like that would be best for "babysitter proof" installations. BUT that requires line-of-sight to the ISY. unfortunately, the LEDs on the front of the unit are pretty bright, and flicker with activity. Very distracting in an entertainment center. There are workarounds, just be aware of the issue. I like the Insteon remotes actually, but they do not offer interchangeable labels for those, so unless you're willing to make your own, you're stuck with the generic lettering

I just spent like 3 -4 weeks (in my spare time, not straight) figuring this one out. I have a light and a small shelf fan in a laundry room that also doubles as the cat's home at night. I set up an open/close sensor on the door that would change the scene parameters of the light. When the door is open, the light and fan come on when motion is sensed. When the door is closed, the fan runs but the light stays off. Took me forever to figure this out!

The Nest should be able to control a split system. I believe it can control pretty much any system, with the exception of line-voltage and millivolt systems. Regarding the REST stuff, I'm looking into that now. Sign up for a Nest dev account, and you too can peruse their API info. I'll probably spend some time looking into it myself this weekend.

Nothing stopping me . But I can see why it stops UDI. Plus, all I really want is to be able to access and set the home/away state, and read the temp and humidity data. I have no plans to develop anything for sale. I figure I'm pretty safe.

I assume it's because they have their own plans for something similar? Or possibly because that would compete with the Nest's own energy-reducing potential? Not sure. That was the one "don't" that jumped out at me. The rest were pretty understandable, don't write malicious code, don't copy Nest functions and present them as your own, don't develope software that smears the Nest brand, etc.

I was wondering about this. I had enough success with my Hue lights that I wanted to try my hand at basic Nest communication, so I signed up as a Nest developer so I'd have access to their API documentation. One of their "don'ts" was create demand response programs. A rather unfortunate situation. I assume this means no Nest module will be forthcoming, even with the new firmware capabilities.

I think it's fair to say that the ISY is pretty readily accessible to anyone willing to spend a couple hours reading and playing around with it. Basic schedules, scenes, and triggered events can be easily created. If you stick to Insteon devices, it's all fairly easy DIY stuff. But, you can also get pretty wild with it, which encourages exploration and experimentation. My own background is not at all programming-related, but after a few months I'm already using the network module with my Hue lights and my stereo, mostly with copied code/scripts, but I've also added a few lines of my own attempts at tweaks to stuff I've swiped. It's pretty damn cool when something like that ends up working for you. And there are a lot of people here willing to answer questions.

Fully biased opinion follows! It's actually a PITA to use your phone to control things. That was actually my first HA mistake, discovered when I bought a set of Hue bulbs. Too slow to have to find the phone, launch an app, wait for the devices to load, then take an action every time you want to do something. Plus, if you don't have control of the switch, someone will helpfully turn it off for you at some point, and then whatever you're controlling stops working. I would also say that having all the switches controlled makes the HA system feel integrated with the house rather than feeling overlaid on top of the existing system. I suggest replacing as many switches as possible. That said, I'm not a big fan of the wired-in outlet modules. I'd rather just use a plug in module most times. Regarding KPL utility, here's a "for instance": I have a 6-button one next to the front door. The main switch controls the outside light over the door, pretty standard. But I use one of the other buttons to control some exterior lighting, another to push on my way out the door to set the house to an away state so I'm not running around looking for lights that are on, and a third to turn on the core house lights upon arrival. One note of caution for you though, the switch bodies are considerably larger than a traditional switch, and most homes are not built with the future in mind. Fitting everything back in may well be your biggest installation challenge. And don't discount the utility of the RemoteLinks. I've got several taped to the wall with 3-M command strips where I don't feel like dealing with installing a switch. Yeah, you have to remember to charge them, but I just have a recurring alarm in my phone that reminds me. So far every three months has been working.

Does this mean an ISY with one Port A on it can only control one of these relays? Or is there going to be a way to connect multiple relays to the ISY through that one port?

That's what I did. I have two lights in my office (lamplinc dimmers) controlled with scenes from two of the four extra buttons from the adjacent workroom keypad (button controller, lamplinc responder). I then created separate scenes for each button (it's an Insteon 6 button relay, I created scenes with the button as responder, no controller)), and I can turn those on and off at will with programs that watch the state of the lights. Like I said before, it's been rock-solid reliable in terms of keeping the button in sync with the light. Yes, there's a second or so delay, but that hasn't been an issue for my application. I'm curious to see if the program can be eliminated though. I tried adding the lamplinc to the button control scene as a controller, disabled my trigger program, and tested that, but when I turn the light on/off via the ISY, it had no effect on the button. But, I'm also pretty new to this, so it's entirely possible I'm doing it wrong here. I'm always down with a better way to do something.

Not really. I discovered that somewhere on this forum early on, and the delay hasn't been much of an issue. The keypad button controls an Insteon plug-in relay module, so do I make that the controller to the keypad switch? Will that change the keypad light state no matter what the source of the control was?

If Status 'Office-Light-Desk' is not Off Then Set Scene 'Office Desk Lamp KPL Sync' On Else Set Scene 'Office Desk Lamp KPL Sync' Off I have a scene called Office Desk Lamp KPL Sync, with the keypad button in question as a responder, and no scene controller. When the device Office Desk Light gets turned not-off (ie, any brightness greater than 0%), the program triggers, and turns the keypad button light on. When the light gets turned off, so does the keypad. This has worked flawlessly so far.

You need to create scenes with the buttons as responders as well. This should explain better than I can. http://forum.universal-devices.com/topic/12432-controlling-button-backlights-on-key-pad-dimmer-2334-222/

Any chance of getting a meter on the load / line wires? It would seem to me that if you can test the load side and find power, but testing the line side shows no power upon switch activation, that you have a defective switch. Your wiring sounds like it should be working.

Honestly, 6 programs to do that doesn't sound bad. I've got 6 programs just for presence detection for two people, and another 6 for the state of the house. I'm currently seeing how that home state variable works with folders for the stuff I want to change based on whether any or all of us are here. I'm pretty new to the ISY though, so there may be more efficient ways to do things.

My understanding is, no. There is only expansion space for one radio.