This rocks. I’m really glad you got this working. Now all I need is a sexy woman’s voice telling me that there is an intruder in my driveway. I’m working on that one still.
Created a scene, pasted the luup code, put the ids for my lights and changed local count to 3. On the events tab, I chose the driveway sensor, then said when sensor is tripped for the type of trigger.
I’ve tested the scene and it works as advertised (pretty cool actually).
However, it does not look as if the scene is triggered when the sensor is triggered.
I just reset the sensor settings back to 1 for status and tripped, which is the default. This means the sensor shows as open until the driveway alert is triggered and then it shows as closed. I updated the scene and checked the box that says tripped as part of the event. I am hoping this is asking if the sensor is currently tripped, but I could be way off.
I changed the sensor settings back because with changed settings, the sensor would show as tripped and stay tripped instead of going back to non-tripped state. While it would be nice to have the correct graphic showing the state, the more important part is that the whole thing works.
I’ll test more tomorrow. I am about 90% there and once I have everything working, I will provide a detailed summary.
the audio im trying to get this going some time soon… one can attach a usb-audio device on the vera and use openwrt audio driver… thats as far as i got… the speakers built into ip-cams are not really supported by their manifacturers and this is still a new thing which needs api input or rtsp rather then a quirky webpage to push a button on a flash app (i like silverlight better… not coz its microsoft but it lacks all flaws and security holes which flash has…
very glad that you got it working… you could add a delay in the scene for a long as the gate is opened (i assume it close some time after opening) and there re-arm the sensor i think.
edit: or even better… use the other 3 ports of the 3000 device and add another doorsensor to detect if the gate is opened completly . could also attach a doorsensor under the door of the gate in the ground and put the magnet under the gate itself to see if the gate actually opened or it just didnt close properly.
yu the trigger needs to be set in the scene itself… above the scene editor u see this trigger tab where u can add a trigger
add this and tell it to be trigger of the doorsensor. so if it goes of it trigger the scene.
i dont understand this scene editing very much… it seems the advanced tab is the only place i can really tell what im doing lol
if a normal editor program would be build up like a decent solid oak tree, the vera ui would look more like a lost wild bush which you will have to find first in the tropical rainforest and try n catch it.
I’d try to first make the scene work with the reversed sensing. Sounds like you want the scene to trigger when the sensor is not tripped (i.e. the door or window is closed / the magnet is near the sensor in a standard application)?
That should not require any manipulating of variables (which will throw off the logic).
[quote=“oTi@, post:25, topic:170764”]@triangledave,
I’d try to first make the scene work with the reversed sensing. Sounds like you want the scene to trigger when the sensor is not tripped (i.e. the door or window is closed / the magnet is near the sensor in a standard application)?
That should not require any manipulating of variables (which will throw off the logic).[/quote]
very good point… sometimes the logica sounds more logic then it is logical lol
That seemed to do it. Reset the logic back to default and the scene was triggered this morning. For the time being, I’ve set notifications on the scene so that I get an email when the scene is triggered. Will test a little bit more and then summarize.
I like the idea of the audio notification.
Once I’ve got the driveway sensor working well, I’ll be getting the dakota doorbell that uses the same receiver and probably an IP camera.
Summary:
Vera running UI4
-
Purchased and installed Dakota Wireless driveway probe alert kit with WPT-3000 transmitter, WR-3000 receiver and magnetic sensor probe. Installed and configured device according to instruction manual.
-
Purchased Everspring SM103-1 Z-Wave Door / Window Sensor. Selected this sensor because it was ready to accept a remote wired reed switch (or external magnet sensors).
-
Joined the sensor to my Z-wave network according to instructions (pretty simple and straight forward) Note-while I was able to join the sensor right away, it took a while for the sensor info to fully update in Vera (in Vera it now shows battery status and the triggered status (open or closed sensor).
-
Tested sensor with magnet that comes with device. Status icon would change to show open or closed sensor.
-
Used 24 AWG wire (thin speaker wire) to wire the sensor to the Dakota driveway receiver. (pic included) . The Dakota has 4 com ports to support other devices and receivers. You can also program the receiver to play a choice of alerts. I chose Westminster, which the instructions say is also channel 2 (com port). I am not sure if this means that the signal is only sent out on channel 2 if you are have selected the Westminster alert. To be safe, I wired ran the wires to channel 2. Very easy, you just need a small screw driver.
A suggestion on this discussion was to touch the wires coming out of the Everspring sensor together. I did that and touching them together changed the sensor status from open to closed on Vera.
-
With the door/window sensor now connected to the Dakota receiver, Vera shows the sensor as open. The sensor shows as closed only when the driveway alert is triggered. I fiddled around with the Everspring sensor settings in Vera changing the triggered and alert from a 1 to a 0. This kind of worked to show the icon with a normal state of closed and a triggered state of open. However, this somehow messed with the logic of the scene I created, so I reset to Everspring to the default settings and it shows a normal state of open.
-
Created a scene. On the Events tab, I selected the Everspring sensor, selected the event trigger to be "A sensor (door/window/motion/etc) is tripped), I gave the event the name of “visitor” Finally, I selected Yes for the question of Tripped?
I then went to the LUUP tab and pasted this code that I found on the forum (thank you!) for turning off and on Christmas Tree lights) I put the device IDs for the lights that I wanted turned off and on and I set the local count to 3 (which ends up blinking the lights two times). These changes are right at the top of the script. (script sample attached).
To Do: I would love to figure out how to incorporate a voice notification, so if anyone has any slick ideas, I’d like to hear them.
Next Step: I will be ordering the Dakota doorbell that uses the same receiver and go through the same process with that receiver (I’ll need to get another Everspring sensor as well). This will finally give me a Z-wave doorbell. I will create a similar scene for doorbell trigger. As a future step, I plan to get an ip camera. With the camera and my sqremote set up, I’d like to figure a Luup script to pause whatever is being watched on TV, change to camera feed for 30 seconds, change back to original source and un-pause. Once you become a Luup guru, the options are pretty wide open. My Luup-foo is not strong yet.
Hopefully this information is complete enough to help anyone else who wants to do something similar. If I am missing any details, please let me know.
Thank you,
I will be doing this. Let us know if/how you setup the scene to show the video in the SQ remote as that was one of my goals to get rolling this summer but originally with the doorbell. Thanks for paving the way, and i’m looking forward to your report on the doorbell also!
Sent from my SPH-D710 using Tapatalk
not sure how this dakota thing works but cant u attach 2 wires at the gate to port 3 for example so it sends a on-signal ?
or does it need a special com-port daughterboard ?
Da_JoJo, Not sure if I am understanding the question. My guess is that signals are sent to all the com ports.
well you have this 4 ports on it. i wonder if this are relais or are these used for com-port data ?
Excellent work! I’m glad to see home hacking stuff like this.
You know you can set up a luup.is_night, or something similar, to turn on a porch light or entryway light but only after dark. Along with tons of other cool automated tasks. But that one is what I will be hoping to accomplish.
Thanks for the play by play.
[quote=“mundyb, post:33, topic:170764”]@triangledave
Excellent work! I’m glad to see home hacking stuff like this.
You know you can set up a luup.is_night, or something similar, to turn on a porch light or entryway light but only after dark. Along with tons of other cool automated tasks. But that one is what I will be hoping to accomplish.
Thanks for the play by play.[/quote]
now i dont own a entryway or driveway or porch but this gets me to think in a wholeother persfective. i have this doorbell i can automate instead of getting a new z-wave one and attach a fibaro to the light on the hallway to auto turn it of when i go into my bedroom 
main goal would be getting video+audio through my phone and so see who is in front and automaticly open the door. now where is my wallet lol
I am guessing the 4 ports are relay ports. If I have a chance, I’ll look through the manual.
subscribed for later reading
In case anyone is still reading this post, The different channels correspond with the different tones/chimes that the receiver will make. Each sending device (3000 series in this case) can have its own unique chime (up to 4 devices) You select which tone/chime by setting dip switches on the sending device. Each tone/chime corresponds with a channel out. You could wire each channel to a different z-wave sensor to trigger different scenes for each device (driveway alert, motion sensor, doorbell, etc). All of the devices will all sound on the receiver with its own unique tone.
I have finally set up a z-wave doorbell with the same system and have started a thread to work through the luup coding, but the doorbell and zwave connection are operational. http://forum.micasaverde.com/index.php/topic,12587.0.html
I have been using the Dakota with a Everspring window/door sensor without issues for half a year. If someone drives down my driveway Vera starts a timer that waits 5 minutes for a valid door code otherwise it flashes the outside LED strobe lights for a few minutes and pushes a message to my phone. The only thing I did was wire the Everspring sensor to an external power source.
I am now thinking of replacing the Everspring sensor with a FIBARO Universal Binary Sensor FGBS-001 when they go on sale in the US in January 2013. This small device has two digital triggers so I can wire up both the Dakota magnetic sensor and a beam sensor. As a bonus it also has 4 temperature sensors inputs that I can wire inside and outside the house to monitor environmental issues. I expect that the replacement should save a lot of money and reduce the number of zwave devices and space on my control panel.
Tremendous thread!
I’m hoping someone with EE knowledge can help me with a potential alternative to the Dakota. I’m able to do a hard-wired solution, preventing me from having to manage batteries in the wireless transmitter.
Might someone take a look at page 5 of the PDF (link below) and tell me a) if this will work with a window sensor and, b) which terminals to use?
For those interested in the product, it’s here: MIER DA-500 Driveway Alarm
Thanks in advance!
Use connectors 7 & 8 (Normally Closed) to connect to the door switch.
After I added my driveway activity I was able to automate a few things based on this activity.
If you want to have triggers based on entering or leaving the garage you can use
the Program Logic Event Generator plugin.
Since the driveway activity sensor is likely to be close to the house, since it’s powered, you would need to compare the trigger times of the Garage Door Opened, and the Driveway activity for departure. I have a long driveway and the Garage Door is closed before I get to the activity sensor … so I use the Garage Door closed trigger. For arrival I also use the Garage Door Opened trigger.
Two Triggers:
GarageDoor - When Garage Door is Opened
Driveway - When switch attached to Driveway Motion is triggered.
Then you can have two conditions:
Leaving = (GarageDoor; Driveway < 2:00)
Arriving = (DriveWay; GarageDoor < 2:00)
You could easily add the Day and Night plugin and then add a trigger for
Night - Day or Night indicates night.
Then an addition condition:
ArrivingAtNight = Night AND (DriveWay; GarageDoor < 2:00)
Then you can turn on lights in your house automatically when you arrive at night.
You can use the leaving scene to turn off lights and setback the thermostat.
I actually ARM my leaving scene, because I do not always want my house to go unoccupied. I pass through a hallway. If I turn the light on/off/on it arms my Leaving Scene.
Additional Trigger:
Hallway - Light is turned on
Updated condition:
AutoShutdownHouse = (Hallway @ 2 < 30) and (GarageDoor; Driveway < 2:00)
I use that condition to Turn Off all lights, HVAC to unoccupied, Lock all Doors, and audibly confirm with a spoken Vera Alert to my cell phone.