apostolakisl

Also, the older switches need a power cycle before new settings take affect. EDIT: and by power cycle I mean flipping off the circuit breaker or pulling the reset tab.

Nice! I think my wallet and my live-in monitor needs a rest for a bit though. I am still populating my great room with some dimmer wall switches, yet. **sigh** Let me think... Landscape the side yard this year? or CAI? hmmmmmm... I'm sweating now. BACK to reality! Time to get out and blow the snow out of the driveway. Snow banks are almost 8 feet high at front. No typo and it's not letting up this year! Thanks for the tease though! You could probably program a CAI to automatically plow your driveway. Or you could move to Texas. I emailed the guy selling those kits to see if he would sell just the accessories, no board since I already have plenty of boards.

Awesome little board! Is there any prefabricated cases or power supplies for them? I just hit ebay with cai webcontrol and this little kit came up. I think it is exactly what you would want. http://www.ebay.com/itm/CAI-Webcontrol- ... 1e8655b090

I can't comment to the issues ioguy had. I have been real happy with mine (I have 10 of them). I have written some pretty big programs for them, but the nice thing for newbies is you can write something really short and simple. For example, this all the code you need to have CAI post temp to ISY once every 5 seconds. START WEBSET URL1 T1 WEBSET URL2 T2 WEBSET URL3 T3 WEBSET URL4 T4 (etc up to DELAY 5000 END Other steps include connecting the 1-wire sensors to the 1-wire terminal on CAI (up to 8 go on a single bus), connecting power to CAI, and configuring CAI with a user/pass and IP address. CAI has automatic enrollment of 1-wire sensors. Lastly, you need to configure URL1-8 with the IP address, user/pass and the REST language that ISY requires so that the temp gets posted to ISY variables of your choice. Certainly you could get way more complex with your CAI programming and perhaps take ISY out of the loop altogether and just let CAI monitor your temps, process things as per your requirements, turns things on/off, and send email notifications.

Awesome little board! Is there any prefabricated cases or power supplies for them? As far as the box, not that I know of. The wall wart is just a basic, normal, probably already have one, 9v deal.

This thread tells you how to configure CAI to post to ISY. viewtopic.php?f=81&t=10141&p=77241&hilit=watson#p77241 You would still need to write a small program on the CAI to tell it when to post what to where on ISY.

Do you have first hand experience with one-wire temp sensors on the CAI board? Do the one-wire temp sensors work well for ambient temperatures such that they react quickly enough to be effective for HVAC control? Yes, I have used them quite a bit. I haven't done any scientific eval on them to know how accurate they are, but they seem to be pretty accurate. They report .1 degree increments on the CAI and that posts over to ISY. Since it can't do decimals(like ISY), it posts the value times 10. So 25.1 would be 251. Lots of people use CAI with 1-wire to control heaters and venting fans and stuff. I am just using to track temps and send alerts.

Those types usually say that. The Kitchen and Bath caulk silicones typically contain a fungicide to prevent mold. I silicone grease my probe to the side of my PV batteries and cover it with a bit of urethane foam to keep it mostly "thermally in contact" and influenced by the liquid inside. There really isn't any point in making your own. They sell them pre-made water proof. Now I don't know much about fish, so maybe the pre-made ones are poisonous? But they look like stainless steel. http://www.ebay.com/itm/Length-1M-DS18B ... 2c7b9c97fb And they are cheaper than I remember. EDIT: IF all else fails, read the directions. They are stainless steel.

I would use a CAI webcontrol board with one wire sensors. One wire sensors cost pennies each and the cai board is $35 and can handle 8 temp sensors. You can also get submersible one-wire temp sensors for about $5 each. The latest CAI firmware has the built-in ability to push temp measurements to ISY variables. You can set the CAI to deliver those values as you please. For example every so many minutes, or if the temp hits some number, or changes by some number, etc. You can find other threads in here talking about how to configure the CAI for the ISY. You will also need a project box of some sort to put the CAI into and a 9v wall wart.

My other devices that work correctly with non-toggle-off will blink twice I think, then turn off. Yes, I have a KPL with toggle off mode as well. It used to do that blink every time. But I improved communication and now the KPL shuts off when I push it and that is it. Lee could tell you for sure, but I am pretty sure the blink has to do with failed or perceived failed comm.

If pushing directly on the KPL button when it is on does not turn it off, then something is wrong with the KPL. And by backlight, I mean the individual button on/off backlight, not the overall so you can see it at night backlight. That is why I made the first comment about "when you push the KPL button it turns off, right?" with a question mark after it. Have you tried factory resetting it? What if you put it into regular on/off mode rather than toggle off mode. The blink you see I believe has to do with a communication issue. I believe it blinks if it didn't get ack from the target. Xathros has some knowledge of a firmware glitch regarding the non-toggle mode, so I would say that there is a chance it may not be fixable.

What if you push the KPL, then the backlight turns off, right? I think this would happen if you turn the scene containing the KPL off where ISY receives the scene off command, but the KPL does not receive the scene off command. Some of the guys who are more into the Insteon command sequence could confirm, but I believe that is correct. There are a number of situations where ISY has to make assumptions as to the status of a device based on commands received, not actual status reports from the devices. For example, I know for certain that a dim up or dim down of a scene does not report the actual status of the devices, but rather ISY times the length of the the dim up/down and then reports that as the status of the device. If you run a query after a dim up/down, you usually see ISY make a small adjustment to the percentage.

The backlight on the KPL may not be turning off for a couple reasons. 1) The lights in the scene were turned off via a mechanism that was not by turning off the scene that they share with the KPL 2) You have a comm issue. If you have a KPL that you want to be a non-toggle off for a single scene, and you want the KPL backlight to always show the status of the scene, then you must put them all into a single scene where the KPL is a controller of the scene. Also, all other ways of shutting off (or on) the lights in question must also be controllers of the scene. In the simplest situation, you might have a single switch that controls the load, and several other switches plus the kpl. All of the switches/kpl will need to be in the scene and all will need to be controllers of the scene. As an example of how it could get messed up, lets say you had another scene that also shut off the lights in question, if you used that scene, then your kpl would not shut off unless it were made a member of that scene as well (at least as a responder). Another example would be if the load switch was only a responder to the scene and not a controller. In that situation, turning that switch off would turn the lights off, but none of the other switches (or KPL) would show that change.

This is mine. I have it beep to warn that it is going to shut off. Of course you need a newer switch that has the beep function. You could change the "is switched fast on" to "is not" if you wanted that particular function to prevent the timer. The "status not off" is if you shut the light off it will kill the timer so you don't get the beeping. If Control 'Alexis Room / Alexis BR-Overhead L' is switched On Or Control 'Alexis Room / Alexis BR-Overhead L' is switched Fast On Or Control 'Alexis Room / Alexis BR-Overhead L' is switched Fade Up Or Status 'Alexis Room / Alexis BR-Overhead L' is not Off Then Wait 29 minutes Repeat 60 times Wait 1 second Set 'Alexis Room / Alexis BR-Overhead L' 14 (Beep Duration) Repeat 1 times Set 'Alexis Room / Alexis BR-Overhead L' Off Else - No Actions - (To add one, press 'Action')

I have only had one episode of "orphan" links and this occurred when I moved some switches around to different locations and used the "replace with" command. Somehow ISY got some links mixed up and allowed some links to remain that were not part of any scene.

First do as LeeG said. Compare the device links tables to the ISY links tables. If the tables don't match, then do a restore device on them from ISY and see if that fixed it. If the tables do match, then ISY is "confused" and believes the link should be there even though it should not. There is no way to just remove that one link from ISY since it is not listed in any scene. To fix this, do the following: 1) Take notes on all scenes/settings/programs you have in ISY regarding the devices that are correct 2) Remove both devices from their folders (if they are in folders) on the main page of ISY admin console 3) Remove (delete) both devices from ISY, 4) Factory reset both device 5) Add them back to ISY as if they were new to your system, name them, and put them back in the correct folders 6) Re-add them to any scenes/programs and put your settings back into them

I think that this is an ideal way to deal with crossed from/to times. It is an illogical condition and ignoring it as a trigger is likely to prevent the most un-intended consequences. If there are other triggers then you are forced to make a decision, and "false" is of course the only acceptable one.

The fact that a from time and to time that are backwards causes both times to be non-trigger events demonstrates that ISY is capable of ignoring triggers in certain situations. It would be great if one of those situations was by putting a disable/enable checkbox next to any clause that can be a trigger.

I believe that a program like that where the "to" time ends up being after the "from" time simply doesn't run at all (doesn't trigger). So neither a "then" or "else" will execute. Edit: Oops. I meant to say "from" time is after "to" time. But the fact that it doesn't trigger is correct. Unless you have some other condition, the program doesn't trigger. And if you have another condition, the time clause will be "false"

Frankly, with everyone going to the cloud, you can differentiate yourself by stressing the fact that your system data is private. But I do agree that we are at a tipping point where HA is quickly going from a niche, hobbyist product, to a widely implemented system of the masses. I think the time is right for you to secure some big time financing so that you can scale up and make the adjustments needed to be a leader, else you find yourself in the dust. It is a great product, but having a great product is only half of it.

But that really doesn't require a cloud service. You could just easily have all those calculations happen locally and use a network connection to query a weather service in your area. There really is no need to send your personal habits to an offsite server. In fact, with some fancy programming, ISY might be able to do that stuff using the venstar ISY actually is ideal since it knows where and when you are in your home based on light usage and/or if you have Elk connected. And if you have a multi-zoned system it would be very smart following your light switch usage throughout the day it would be able to zone the house according to your usage. I suppose an ISY module could be to install an algorithm like Nest has to automatically figure out a heat/cool cycle that works best for you without you having to write the programs.

The Ube light switches seem like the next acquisition here. It's already Android based. That would really get them into your living routine.

I'm sure its all part of the grand government plan to tell us what temperature our houses will be whether we like it or not. Of course certain people will get waivers, like members of congress.

Google already knows where you are if you have an Android phone. Depending on signal strength, they could even figure out what room of your house your in. I still don't get what is worth $3.2B in cash about Nest. It must be that Nest has some patents that are really juicy for a slew of other things. $3.2B would buy you 16 million thermostats at $200. Now figure that the profit on a thermostat is probably less than half of that, you need to sell 32 million of them. Maybe it could be done to a worldwide audience, but that seems like a tall order. There must be something else there. EDIT: Just read that Nest is shipping 40 or 50k thermostats per month. They expect that they could do as many as 1 million per year if things go well. That is pretty far away from selling 32 million at $100 profit each.

To know how your program would function, we would need to see this program (motion detected). Odds are, what oberkc has posted is probably going to do the trick, but you may have special considerations. His program will keep resetting the timer every time one of the motion detectors sends an "on" command, which is usually how people like motion lighting to work.