geogecko

Martin, I'm still digesting your post. Sub, the problem is the off program. The on works just fine. If I trigger the motion, the light comes on, if I'm moving within the 1 min window, everything is fine, if I don't move for 1 minute, and the off program starts to execute, then it continues to execute, even if I trip the motion shortly after the 1 minute has expired, so 9 minutes later, the light goes off. Then, if the motion happens to be already tripped, I have to wait for it to time out, then trip it again, to send another on command. I wish that the program language used for the ISY was not so basic. Yes, it's far better than HouseLinc ever was, but since most of us seem to be tinkers to begin with, a little more branching, testing, and variables would be awesome. Basically, I need a way to re-evaluate the off condition, if the motion comes back on, when it has already started execution. I think the problem here, is the 10 minute timer, it has no way of being interrupted at all.

Actually, it isn't working, now that I've tested it more. I then enabled the off command again, and it also does not work. What is going on is this. If I make motion, the light turns on. Then, if there is no motion, the light turns off after 10 minutes. However, if there is motion, the light comes on, and I keep moving, after 10 minutes, the light will turn off. The motion will have to have it's internal timer time out, before I am able to then, make motion, and have the light come on again. I'm going to have to think about this one some more. I think you are right that there is going to have to be some weird programming going on to make this work...

That last example seems to work well, with the off command disabled on the motion sensor. The only thing I don't like about doing it this way, is I can't really use the motion as an occupancy sensor anymore, as it's state is always on now.

I'm having issues trying to get a simple motion controlled light to work. Basically, all I want, is the motion to turn the light on, and when no motion is detected for 10 minutes, turn the light back off. I have this mostly working, except when the light gets turned off, because I am sitting really still, I move around a bit, to trigger the motion, and it does not do the commands in the "then" statement, and no matter what I do, it doesn't do anything. I have to wait for the motion's internal one minute timer to time out, then trigger it again, to get the light back on. Here is my program at the moment. I have the 2 seconds in there, because I thought maybe the ISY is having problems if the light goes out, and then is required to go back on right away, but that didn't work, unless it needs to be more than 10 seconds? If Status 'Study Motion-Sensor' is On Then Wait 2 seconds Set Scene 'Study Lights' On Else Wait 10 minutes Set Scene 'Study Lights' Off

Okay, this isn't working. The light keeps going off/on randomly. I think since the sensor is in the same room, when the light comes on, the Dusk/Daw is getting confused. When the room is dark for 3.5 minutes, that statement goes true, then the light comes on, and 3.5 minutes later, the statement is false, and then 10 minutes later, my light goes out... Going to have to think about this one a little longer.

I've had my ISY-99 for less than a week, and love it. I am working on a program, and wanted to see what you guys thought, or if you had any suggestions for doing something different. Basically, I got a motion detector when they first came out, and it's sat in the box until now. I find that I am able to make it way more usable using programming, than as it ever was stand alone (in fact, it was so annoying in stand alone mode, that is what made me put it back in the box). So, what I'm doing with this motion detector, is I have it mounted in my office. I want it to control the office light when it sees motion, and then turn it off after 10 minutes of no motion, of course, only when it senses darkness (notice, I did not want to use sunset, because it can be dark in this room, if the shutters are closed, or if it is stormy outside). Secondly, the low battery warning feature is kind of nice, so I have a program that will send me an e-mail when it gets low (that I will use for all motion detectors, when I get more), but I also thought it would be neat to have a visual indication for the particular light it was controlling, so I wouldn't have to rely on an e-mail. So, what do you guys think? Any way to combine Study Motion and Study Motion Battery?

Well, when you try and change it from toggle to non-toggle, it says to go set the button to on or off (physically), then to come back and hit OK. They were both off, so I just left them at that, so they were set to non-toggle off. Then I tried the program again, and it did not work, so I changed them both back to toggle mode, and now they work. So they are back to the way they were, before I even started, I guess they just needed to be reset for some reason.

And we have a winner! Put them in non-toggle mode, and that didn't work, put them back in toggle mode, and now all of a sudden, they work... Any ideas on what that was all about?

Thanks, found it. They are all in Toggle mode, the same as the other KPL that works.

How do I tell? I used to know how to do that with HouseLink, but have no idea with the ISY.

The other thing that is interesting, is that the new KPL that works with this scene, had to be added manually, because the ISY did not recognize the device. The old KPL, that does not work, was recognized by the ISY. Now that I'm running 2.7.7, I was thinking about wanting to readd the new KPL, since I would think it would recognize it properly with 2.7.7, but I'm not sure how to do that, without erasing all the links, and having to reprogram them. Any tips on that? I'm working on adding my RemoteLincs now, which haven't been in service for a year or more now, mainly due to the 2 year old. I think I will just use them both in the master bedroom, as a his/her's controller on our nightstands.

Thanks for the assistance. For some of your questions, please see the attached images. Yes, you are correct, I don't want the actual KPL buttons linked to anything, because my 2 year old plays with the KPLs on a random basis. I thought, well, maybe that was the reason, so since I have two KPLs with the same two sets of buttons (All On, All Off), I just cross linked the buttons to each other, and that still doesn't work, so I removed those links. The All On Scene works fine from the Master.All On KPL button, just not from the older Nook.All On button. As a side note, I upgraded from 2.7.0 to 2.7.7, and love the grouping feature for things such as KPL's, but is it normal that now the non-load buttons of the KPLs show up as devices? I don't really care for this, because the buttons (other than the load button) are not really considered devices.

The scene test works great, the scene even works from the newer KPL, just not the other one. Here is the event log, after double tapping the All On button on the non-working KPL. Fri 01/29/2010 02:10:12 PM : [iNST-SRX ] 02 50 09.93.F2 00.00.07 CB 14 00 LTOFF-F(00) Fri 01/29/2010 02:10:12 PM : [standard-Group][09.93.F2-->Group=7] Max Hops=3, Hops Left=2 Fri 01/29/2010 02:10:12 PM : [ 9 93 F2 7] DFOF 0 Fri 01/29/2010 02:10:12 PM : [iNST-SRX ] 02 50 09.93.F2 11.CD.BA 41 14 07 LTOFF-F(07) Fri 01/29/2010 02:10:12 PM : [standard-Cleanup][09.93.F2-->ISY/PLM Group=7] Max Hops=1, Hops Left=0

Yep, exactly what I'm doing in the program, and the KPL is in the ISY device list. I think it may be a problem with the KPL itself. I have 2 KPLs setup in the program (they both have an "All On" button), and the newer one works just fine, the older one just blinks when I try and do anything. I'm restoring the KPL that doesn't seem to work. I think it is version 29, whatever that means. The other one is new, within the last 4-6 months.

I have an 8 button KPL that has a non-load button called "All On." After having responders linked to these type of buttons in the past, and our 2, going on 3 year old has found out how to operate KPLs, I want to change something. Basically, I want the "All On" button, when double-tapped (fast on) to trigger a program in the ISY-99, that in turn, turns all the lights on. I've got the program setup, but it never triggers. Does the KPL button have to be linked to at least one responder before this would work? Does the KPL button need to be linked to the PLM or something?

Hmm, after some more looking, it looks like these can be divided up into two categories. Native iPhone apps: iLinc eKeypad ISY Browser Interfaces (both require the Networking Module): TouchSwitch IsyAjax Now I'm trying to decide what type I want to get. The nice thing about the browser interfaces, would be you could use these everywhere (on PC's as well as an iPhone). With the native iPhone apps, you'd be stuck using the standard ISY interface. What are most people using these days? I plan on eventually adding some cameras to the house, would this influence the decision, if I wanted to use the ISY to control them?

I am also interested in replies to this question. Looks like there is iLinc, TouchSwitch, and eKeypad ISY. Is eKeypad really worth the $45 asking price? What benefit does it have over the others?

Awesome work guys. This sounds like a wonderful device. So basically, this thing will learn IR commands sent to it, and then associate them with an Insteon event. I would have liked to see a remote IR solution, such as a Tx and Rx 3.5mm jacks so that you can connect an IR blaster and an IR receiver, so that it doesn't have to be within sight of IR. But, since it will not have to be plugged directly into AC power, this makes placing the unit in IR sight a lot easier, so I guess I'm not worried about that. Is the new 2000 link PLM something SmartHome is developing, or something UD is working on? Is there a time frame for the IR version of the 99.9? December or January? Thanks!

Anyone have a link on what the ISY-99 is all about? A search in here doesn't turn up any threads...