NC or NO?

BSR - but think of al lthe fun we'd of missed out on :)

Anyway, I want to keep all of my sensors on my SECU16 on the same logic - all with open meaning one thing and closed another. So far the only things I have as sensors on my SECU16 are currrent sensors, and these are NC by what was said here. their circuits are open until they detect sufficient current and then their circuits close. So for my setup, open means off and closed means on (and that's how they appear in CMAX). What's funny, though, is to get this to be read by HS without too much scripting, I had to reverse the inputs (or something like that) in the ADIOcelot plugin (prior to that, HS saw a CMAX on as an off and vice versa). So, given that, given that I use DooMotion, and given that DooMotion see's "on" as motion by default, if I want the door opening to be regarded as motion and it closing regarded as the end to motion (the same way you'd use DM to monitor a regular door 'cept you change the custom status from motion/no motion to open/closed), that means I'd have to have an open door=on in CMAX, which means an open door = a closed circuit, which means I was wrong all along and need a NC swith, so the end result is:

Door open = circuit closed = CMAX on = HS on = DM motion
Door closed = circuit open = CMAX off = HS off =DM no motion

Does this make sense to y'all?

I'll get a sensor at Ratshack (forgive me Martin) this week and see how it works, if it's not what I expect I can return it rather easily. I'll let y'all know how it goes.
 
John, Try again. I almost understand what you said. :o
After all, it is the political season, don't be too clear :)

(Who's on first?)
 
John:

I know what you mean. I also had to reverse the Homeseer logic reported by the ADIOcelot plugin. Thank goodness it gave us the capability to do that.

One thing I am not sure about is why you are using DooMotion. I realize you can name your variables and reverse logic there (via variable names) but is that the only reason you are using it?
 
I use DM for the rest of my motion, door, window and glass-break sensors, so adding the garage door to the group makes sense to me. Right now I have DM indirectly monitoring the other devices (which are a combo of X10 wireless security items and regular X10 wireless sensors), monitored with my W800.

You see, the wife and Ihave a bad habit of leaving the garage door open, usually at night, but once in a while during the day. I'm going to use the garage door sensor setup to alert us that the door is open (via an announcement when we're at home and it's between, say 9pm and 1030pm) and via email and/or a phonecall when we're away from the house (using some of that "vehicle in the garge?" logic electron uses.

Bottom line, I like using DM for this becuase it provides an easy way to handle security-type devices, it lets you use custom status text and images with only a little extra work, graphs activity for you, and lets you add and subtract devives from the "security system" just by checking a box. It's a lot easier for me then a bunch of events and scripting that has to be changed everytime I add or subtract a device, or decide that and existing device should no longer, or should now trigger the alarm.

Perhaps there's an easier way to do this, but I understand the DM way.

As y'all may or may not know, Unlce Sam moves me every few years, so I can't setup a hardwired sucurity system, so I have to rely on wireless. So far, this system is working pretty well and has only given me one false alarm (Something fell in the house, a MS saw it, and I got a call... Oh, but the way, this was on Christmas day while we were at a freind's house for dinner. I checked the cameras from the web, didn't see anything, well, alarming, so I drove home to see what was up. I got home and could see nothing wrong. I then noticed one of the glow-in-the-dark stars we had on the ceiling that had fallen right in front of on of the MS's [We had the stars on the ceiling, becuase given the polution in Seoul - where we lived then - those were the only starts we could see])

JohnBullard - If you print my other reply out and hold it up to a mirror under a blacklight, it'll all be perfectly clear.
 
Ah, I see. I know E has HS call his cell if he leaves the garage door opened after he leaves for work. He can then close it via HS Phone. Sounds like a great idea!
 
Guys, a little update. I've finally had the time to install my sensor and such (I got it from Martin,, since his price - even with shipping - was better than Rat Shack and Rat Shack said it was special order anyway). I now have my Ocelot monitoring the door's open/close status and DooMotion announces the change via a little CAC one-liner for each state. I also have one of the Ocelot's (SECU16, actually) relays tied to the button on the garage door so I can open and close the door remotely (via the web, or with a MainLobby button). The next obstacle I have to overcome is getting HS to tell me when I've left the door between 8PM and 5AM (pretty simple to do, just have to do it) and then, get HS to notify me via email and/or text message to my cell phone (which is accomplished via email) if both cars are NOT is the garage and the door is left open for more than 10 minutes or so after the last car has left. Thank to electron's help, I've got the monitoring of whether or not each of the 2 vehicles are or are not on the road down-pat. Since all these things (Garage door status, vehicle status x 2, and Garage occupancy) are all tracked by DooMotion, I guess I need to go hone-up on DM scripting and CAC. Wish me luck!
 
John,

Please post your code when you have it working...please! (scripts, CAC, CMax, etc) How about a "How To" ?

I would love to do something similar.
 
Back
Top