I will be installing a ZRF113 relay to control my garage door this week.
Right now I plan on implementing a basic scene in vera that will “ON” and then 5 seconds later “OFF”, this should open/close the garage door properly when wired up to the motors isolated contacts.
However, i think it would be fairly easy to code a momentary-type action in Luup for this to work even better.
I am thinking it should send an ON command, verify the on command was successfull, send an OFF command, and then verify the off command was successfull.
How much of a delay do you think there would be between the on and off commands if coded this way? Would this be fairly easy to do?
Someone could probably even code a luup garage door plugin that would take all of these things into account… including monitoring the door sensor/controlling the door (ZRF113 relay and HRDS1 door sensor combo). Might be pretty cool… and fairly cheap with only about 60-70$ in hardware costs too.
Not sure yet, should be here Thursday but this is my plan…
I have an electrical outlet above the garage door motor in the ceiling, it has 1 free plug. I am going to go to home depot and buy a replacement electrical cord and a PVC exposed outlet box. I am going to wire the replacement electrical cord into the PVC outlet box that I’ll mount to the top of the garage door motor and I’ll plug it directly into that free outlet. The back of the motor has the screw terminals where the wall push button attaches. I plan on just wiring the 2 relay contacts into those terminals along with the existing push button wires. This way the garage door will be able to be operated by the push button or the zwave relay.
I think this is a pretty good non-permanant installation in case a better zwave solution comes along. I can take it out fairly easily/quickly and the module should get great reception (and act a good repeater) in the middle of the garage. The relay actually has an external antenna that can hang outside of the PVC outlet box. I’ll let you know how the actual wiring goes…
HRDS1 sensor came in today, I have it installed on the side of the garage door. Seems to work really well. Vera is reporting it as a motion sensor, but whatever it goes red and green as it is supposed to.
My only gripe: I couldn’t get SMS notifications working at first. And when I did get them to work… it took 27 minutes to receive the text message. Thats just a little ridiculous.
Well the garage door relay functions as perfect as planned… just hooked up the 2 blue wires on the ZRF113 to the 2 terminals on the motor where the existing push button wires connect… now the door opens up via zwave or push button or existing RF remote.
One thing though… if I get home and vera has opened up my garage door because of some software bug… I am going to be pi$$ed.
And I have notifications set up to text me whenever my garage door opens, but the messsage doesnt come for 20-45 minutes if at all. I am sorry MCV but thats deplorable… I mean cmon… whats the point of notifications if they take that long? Certainly not security…
Oh and wait… I cant even see the status of the garage door from my phone if I wanted to make sure it was closed when I was away from home… because sensors don’t show status in ANY mobile version. These are serious security concerns for me…
How do you have the sms notification configured? My cell is on AT&T network, when I choose at&t carrier on the user configuration screen it takes forever to get my notification but if I leave it on “Select Carrier” I get sms notifications instantly.
Which Vera firmware are you currently using? I had an issue back in .616 (pre-Luup) where my choice of Carrier would not “stick”, but notifications got through quickly enough.
Interestingly, a later upgrade to (Luup) firmware revision .862 and later solved that little problem, but introduced some 22+ minute delays between events and notifications. That, too, went away (for me), but several other Vera users still complain of 25+ minute delays.
It makes me wonder when your selecting the carrier if it’s actually sending the txt as an email instead of a real text, but when you don’t select a carrier it sends a real text
I hope someone doesn’t break into my front door while I am sleeping and trip the sensor. It would be quite ironic for my dead body to get a warning message 19min after the tussle
Yes, if they don’t recognize the carrier, then a true SMS is sent instead of an email-style. They need the carrier information so they can form the appropriate “type” of Email address.
Given the ups-and-downs in propagation, I suspect the sendmail on their end is miss-firing under load. I’ve seen quite a few cases lately where 1 event causes 2 emails (with the exact same message code/id), and others I’m getting two distinct message id’s (which shouldn’t happen on anything but the Schlage lock User-enter-pincode events:
If you’re interested you can set your account to send “both” Email and SMS and then compare the timings (I haven’t tried this yet) and also have a look at the headers on the Email to see where your particular delays are coming from.
I would be curious to know whether these delays are results of architectural design flaw, or the particular service MCV uses, which is then possibly just a matter of cost?
I have noticed in the past, unrelated to Vera, that sometimes text messages sent as emails take a long time to arrive, so if that’s how it’s sending them it may not be Vera but the cell carriers network, at which point there’s nothing that can be done.
[quote=“325xi”]I use SMS authentication on Paypal - SMS always comes within 10-20 sec.
So it really depends how and via what system you send it; or it’s also possible that findvera queuing messages for too long.[/quote]
axan, you are awesome, left it as “select carrier” and I got the notification in under a minute as a REAL sms not an email sms, who wouldve guessed? thank you!
the message is also much more simple and straightforward… i like this much better
just lists:
Event:
Device:
Room:
Time:
Vera ID:
nothing more than needed, nice
and it looks like the message comes from the same phone number every time, i can add it to my contacts as MCV and have a threaded list going… unlike the email txts that come from a random number every time.
hopefully this setup at MCV has enough bandwidth to handle all of our notifications and isnt too expensive for them to send direct sms vs email sms. on the other hand, this is an example of a service id be willing to pay for if it works well enough… i would rather pay for sms that comes instant than a free sms 30min late
If I had this problem I’d use the dialer plugin with call notification instead of SMS - there are few benefits:
unlike SMS calls can’t be delayed by provider
notifications become debuggable and troubleshoot-able (i.e. there’s only so many failure points in this scheme, so you know where too look if something doesn’t work)
they’re 100% registered at PBXes call log, even if the call failed or got missed
you can set it up to call a group of numbers (battery dead in mobile phone - SMS missed. Instead call mobile, office, and wife’s phone simultaneously, whoever picks first)
The option where you choose “Select Carrier” has been working fairly well for me. I missed a notification here or there at first. But for the past 2 days it has been consistent… and I have been receiving the sms messages within 30-60 seconds of the garage door opening. I am perfectly happy with that as long as it stays that way.
You should automate it so that when the garage door opens your whole house audio pages you isntantly and say “garage door opened”, then turn on all Tvs in the house, then use the video matrix switcher to show the camera01 in garage the video of the garage on every TV in the house. That is home automation!!!
[quote=“B0SST0N, post:1, topic:164995”]I will be installing a ZRF113 relay to control my garage door this week.
Right now I plan on implementing a basic scene in vera that will “ON” and then 5 seconds later “OFF”, this should open/close the garage door properly when wired up to the motors isolated contacts.
However, i think it would be fairly easy to code a momentary-type action in Luup for this to work even better.
I am thinking it should send an ON command, verify the on command was successfull, send an OFF command, and then verify the off command was successfull.
How much of a delay do you think there would be between the on and off commands if coded this way? Would this be fairly easy to do?
Someone could probably even code a luup garage door plugin that would take all of these things into account… including monitoring the door sensor/controlling the door (ZRF113 relay and HRDS1 door sensor combo). Might be pretty cool… and fairly cheap with only about 60-70$ in hardware costs too.[/quote]
Do you mind to post a picture of HRDS1 contacts on the garage door? Do you use external contacts?
