Garage Door Plugin

I use the PLEG and Day or Night plugins and use them to close my Garage door at sunset … if I forget.

Locked my neighbors dog in my garage once … he does not sleep in my garage any more!

Hi!

Thank you very much for making this plugin :slight_smile:

I need a little help if possible.

as I dont have a sensor, I would like to use the switch input of the module as a sensor. Is it possible?
Can I create a variable or something?

Here goes my setup:

I have a fibaro 2x1kw module ( lights module ) connected to my alarm.

S1 - ( input 1 ) connected to the alarm status ( armed / disarmed )

values : 1 when armed , 0 when disarmed )

O2 - ( output 2 ) connected to the alarm command to arm / disarm, alarm is in toggle mode.

values : 1 for 500ms when on then it drops to 0 ( just to give the impulse I need ).

Can I use the S1 device as DoorSensorDevNum in this app? although it is not a sensor, but a switch?
Can I use the O2 device as DoorSwitchDevNumber ?

Shouldn’t it work? or the sensor needs indeed to be a sensor type device? I believe the O2 as an actuator should work fine.

Thank you for your help.

Right now, the app is in lock mode and I cannot unlock it no matter the status of the DoorSensorDevNum.

Thank you very much for your time and effort!

@Smotics:

Does sensor needs indeed to be a sensor type device?

At this time the sensor needs to be a Security Sensor.
If you want to use a Switch in place of Security Sensor:

You want to edit the file:
I_GarageDoor.xml

In the file replace the strings Tripped with Status (Four occurances)
And set the SecuritySvs variable to the same string as the
SwitchSvs variable.

@Ds514:

Is there a method to have the Garage Door plugin from RTS invert the sensor?

In the I_GarageDoor.xml
Change:
From:

if (luup.variable_get(SecuritySvs, "Tripped", DoorSensorDevNum) == "1") then

To:

if (luup.variable_get(SecuritySvs, "Tripped", DoorSensorDevNum) == "0") then

Hi again, Thank you very very much!

I’m a complete rookie regarding this matter, how can i edit the file? sorry the noob question but this is the first time I’m having contact with this systems.

Once again thank you for your time.

From the menu entry:
APPS → Develop Apps → LUUP Files
You can download the file to your computer.
Edit it with a text editor … like notepad.
Upload the file from the same page … Click the button Restart Luup After Upload then Go

Richard, thanks for your help with this, as well as for your plugins.

thank you very much for your time.

I have changed the file and uploaded it, but the app still does not work, just stays in “lock” and does not let me do anything.

Fibaro modules device type are: “urn:schemas-upnp-org:device:BinaryLight:1”

should I set the SecuritySvs and SwitchSvs with that value?

Thank you!

[quote=“RichardTSchaefer, post:163, topic:167178”]@Smotics:

Does sensor needs indeed to be a sensor type device?

At this time the sensor needs to be a Security Sensor.
If you want to use a Switch in place of Security Sensor:

You want to edit the file:
I_GarageDoor.xml

In the file replace the strings Tripped with Status (Four occurances)
And set the SecuritySvs variable to the same string as the
SwitchSvs variable.

@Ds514:

Is there a method to have the Garage Door plugin from RTS invert the sensor?

In the I_GarageDoor.xml
Change:
From:

if (luup.variable_get(SecuritySvs, "Tripped", DoorSensorDevNum) == "1") then

To:

if (luup.variable_get(SecuritySvs, "Tripped", DoorSensorDevNum) == "0") then

[quote=“whatuusay1, post:150, topic:167178”]Hi All - I installed the Garage Door App along with an SM103 sensor to monitor the status. The garage door relay is using an itach. The relay contacts ‘press’ the button on an extra remote like in (http://rts-services.com/Vera/Plugin/GarageDoor/ ) The only issue i’ve had is that when I press the unlock button the itach contacts stay pressed causing the wired remotes not to work and ultimately draining down the battery in the remote. The fix is to make the relay contact momentary - i’m just not sure how to do that… any pointers?

Thanks![/quote]
i apologize in advance for being so confused, if i buy global cache itach, i don’t need the Evolve LFM 20 anymore right (for garage door)? right now i have SM103. also, there are so many types, models of GC, may i ask what type do you have? or what’s a good one with reasonable cost? thanks.

I just recently have put together my garage opener. The plugin is a big help.

LFM-20
RS100HC
Garage plugin
Craftsman opener
Veralite latest FW

I am having trouble with the closing of the door. Using my phone I press lock and can here the LFM20 click but the door does not close. Opening is fine. Can the delay be change on the lock side? Maybe it is too short. I can use the LFM20 switch directly and works every time.

From Apps → Develop Apps → Luup files …
Download and Edit the I_GarageDoorLock.xml … find the following code:

    function CloseContacts()
      luup.log("GarageDoor Close Contacts: " .. tostring(GarageDoorDevNum) .. " Contact:" .. tostring(DoorSwitchDevNumber))
      luup.call_action(SwitchSvs, "SetTarget", { newTargetValue="1" }, DoorSwitchDevNumber)
      luup.call_delay("CloseContacts2", 1, tostring(DoorSwitchDevNumber))
    end
    function CloseContacts2(DoorSwitchDevNumber)
        local ContactStatus = luup.variable_get(SwitchSvs, "Status", tonumber(DoorSwitchDevNumber))
        ContactStatus = tonumber(ContactStatus)
        if (ContactStatus == 1) then
           luup.call_action(SwitchSvs, "SetTarget", { newTargetValue="0" }, tonumber(DoorSwitchDevNumber))
        else 
           luup.call_delay("CloseContacts2", 2, DoorSwitchDevNumber)
        end
    end 

Change the 2nd argument to luup.call_delay (a number of seconds).
Change the 1st 1 to 2 or 3 and the 2nd 2 to 3

Upload the file … check the restart Lua after upload and go.

[quote=“RichardTSchaefer, post:170, topic:167178”]From Apps → Develop Apps → Luup files …
Download and Edit the I_GarageDoorLock.xml … find the following code:

    function CloseContacts()
      luup.log("GarageDoor Close Contacts: " .. tostring(GarageDoorDevNum) .. " Contact:" .. tostring(DoorSwitchDevNumber))
      luup.call_action(SwitchSvs, "SetTarget", { newTargetValue="1" }, DoorSwitchDevNumber)
      luup.call_delay("CloseContacts2", 1, tostring(DoorSwitchDevNumber))
    end
    function CloseContacts2(DoorSwitchDevNumber)
        local ContactStatus = luup.variable_get(SwitchSvs, "Status", tonumber(DoorSwitchDevNumber))
        ContactStatus = tonumber(ContactStatus)
        if (ContactStatus == 1) then
           luup.call_action(SwitchSvs, "SetTarget", { newTargetValue="0" }, tonumber(DoorSwitchDevNumber))
        else 
           luup.call_delay("CloseContacts2", 2, DoorSwitchDevNumber)
        end
    end 

Change the 2nd argument to luup.call_delay (a number of seconds).
Change the 1st 1 to 2 or 3 and the 2nd 2 to 3

Upload the file … check the restart Lua after upload and go.[/quote]

THANKS! it worked.

Hi, I really fancy giving this plugin a go, but just can’t get it to work with my mess of devices.

I have a garage door controlled by a single button wall switch, and a contact sensor via my DSC alarm. The sensor works perfectly, but I’m having trouble with the plugin operating the relay.

This is where it gets a little silly due to a large number of devices I want to control in my garage, I am using an arduino with a bank of relays connected via cat5 to my wired network.

I can toggle the relay assigned to the garage door control via http commands, but there is an unacceptable delay between toggling a relay on then off, therefore I have programmed the arduino toggle the relay with the right delay with both the on and off command on the virtual switch within vera.

Is there anything I can do to get this plugin to work with that type of config?

i.e only send the command to action the switch once, not toggle on/off, but still use the nice confirmation of closure checking etc…

thanks in advance

Sorry I missed your response.

See:
http://forum.micasaverde.com/index.php/topic,4773.msg115828.html#msg115828

You might make similar change to this patch for your setup.
This patch toggles a DCS PGM output to command the garage door.

Basically you would modify the CloseContacts() function to poke your arduino to cause the appropriate relay to toggle.

It would not neeed the CloseContacts2(), because your arduino already resets the relay.

No problem at all,

Thanks for the pointer, I’m giving it a try now and hopefully I’ll be able to test it fully over the weekend.

Hi All,

I’m not yet an owner of a VERA but are planning to move my home automation system from Homeseer to VERA.
Have been reading various threads on the forum for about a month now to get an understanding about what I’m getting myself in to.

Ok, now to the point.
I have a garage with 2 motorized doors and was going to use the Garage Door Plugin to monitor and control the 2 doors. I found the Fibaro Universal Sensor FGBS321 that has 2 inputs and 2 outputs + temperature measurement possibility.
So my plan is to use the 2 inputs to detect if the garage doors are closed and the 2 outputs to control the doors.
Does anyone have experience from using this sensor for the purpose of controlling garage doors? Or other experience from this sensor that could be good for me to know?
Like do the inputs and outputs turn up as separate devices in VERA so that there is any chance that they could be used individual for my purpose?

Can someone comment if this has any chance of working?

Regards,

Tomas

I dont use the FGBS321 for garage door control but can tell you the folllowing about it:

(1) The FGBS will create a minimum of 3 devices: one parent and two child devices (inputs 1 + 2) and these will show up as motion sensors. If you add the DS18B20 sensors, an additional device will be created for each DS18B20 added (you will need to Exclude/Include the FGBS if later adding additional sensors).

(2) The outputs of the FGBS cannot be controlled from Vera as they only follow the status of the corresponding input line. I’m still not sure what, if any useful purpose this serves but this makes the FGBS an input only device (binary & temp). There are no controllable outputs.

[quote=“Frasier, post:176, topic:167178”]I dont use the FGBS321 for garage door control but can tell you the folllowing about it:

(1) The FGBS will create a minimum of 3 devices: one parent and two child devices (inputs 1 + 2) and these will show up as motion sensors. If you add the DS18B20 sensors, an additional device will be created for each DS18B20 added (you will need to Exclude/Include the FGBS if later adding additional sensors).

(2) The outputs of the FGBS cannot be controlled from Vera as they only follow the status of the corresponding input line. I’m still not sure what, if any useful purpose this serves but this makes the FGBS an input only device (binary & temp). There are no controllable outputs.[/quote]

Thanks for this clarification Frasier, I suspected that there might have been some limitation like this (this is why I ask before purchase).

OK so back to square one on the garage door controlling setup any recommendations using z-wave?

Regards,

Tomas

Have read this related thread http://forum.micasaverde.com/index.php?topic=4773.0
It has a number of different examples on how to automate your garage door with vera

[quote=“baxy_AU, post:178, topic:167178”]Have read this related thread http://forum.micasaverde.com/index.php?topic=4773.0
It has a number of different examples on how to automate your garage door with vera[/quote]

Thanks baxy_AU! Now I know exactly what to do. How did I miss that thread.

Regards,

Tomas

I’m surprised that there hasn’t been a company yet to introduce and actual, simple zwave kit for this. There’s an insteon one available. Any idea if that would work with this plugin under Altsteon?