do you mean the Timeout before checking if the door opened or closed correctly? setting? Despite having it set to 10 seconds it shows open/closed almost immediately after the door starts moving.
It's useful to know that the door is actually moving. Most folk I suspect will only have an open/close contact sensor that reports closed and by inference as soon as the door moves away from the contact sensor it reports open even when the door is still moving.
It's not a big deal but just something I liked about the other app/driver ... aside from the sensor taking an extra 5 seconds to report the door is no longer moving.
thATS because it is open immediately.. as soon as the sensor says open (it is subscribed to it) it will change to open.. the timeout is not for that .. it is how long to wait to go back and check that it did open (ie fully open) and is still open. . ie it didn't start and then close again due to the track blocked or something.. More importantly for closing too.. ie the dog didn't walk across the beam while it was closing.
To test remove the sensor from the door and keep it closed and see what it does.
I could easily add a acceleration sensor and maybe add an extra state to the app.device ie moving..
i dont think many would find that very usefull.. right now i dont have an acceleration sensor. to test.
Dont worry about the acceleration sensor, it's not a big deal. I only bought one because the other app makes it mandatory, but I didnt like that it overrode the contact sensor status on closing events (the change to inactive is a bit slow on the ST MultiSensor).
@dJOS, Hi, I'm a newbie to Hubitat and would like to understand how you used the Fibaro as the switching relay to control the motor. I've got the same unit and when I'm triggering the open or close form the Garage (Contol), it only turns the output on, and not off again. I'm using christi999 drivers for the smart implant
I couldn't get that driver working for me (same issue), I'm using the stock HE driver configured as per below. The key item here is turning off "inputs connected to outputs".
@dJOS, i'm not sure what i'm doing wrong, but its still not turning off the output. I've tried using the Simulated Garage Door Opener V2 driver and the native Virtual Garage Door Controller. I've removed the custom Fibaro drivers and changed it to the native driver. Even removed the device from the hub and re-added it.
One thing I did find, and this may be your issue, is that nothing really seemed to register or work until the 1st contact sensor detected a state change. I only found this out after opening and closing the door with the Motor itself.
It's also worth noting that the security sensors I have worked in the opposite manner to their labeling, "Normally Open" on mine is a "Normally Closed" Sensor in the HE driver and a "Normally Open" sensor in the Community driver.
You can work this out using a Multi-meter in continuity mode - HE's definition of an "NO" Sensor = a broken circuit when the magnetic sensor is moved away from the main sensor unit.
I think the difference are that ive set the Fibaro up as a S2 Authenticated, not secure. And other difference are that i'm using a Samsung SmartThings Sensor, and not the Fibaro inputs.
S2 Auth isnt an issue, Im using the same mode. The lack of Fibaro sensor is the issue - However you could jump start it by beifly joining the Yellow and blue wires together. After that it should just work.
Im not sure why they have linked the sensors to the outputs the way they have, it's daft.
if its too much of a pain just write a rule in rule machine to turn it off when it turns on.. that is the way i used to have it working in smarthings anyway and it always worked fine.
He hasn't even gotten that far - after inclusion, the smart implants appear to be non-functional until it detects at least 1 sensor state change.
The simplest workaround is to configure the 1st sensor as a security contact sensor and then briefly complete the circuit with the yellow & blue wires.
Is there a way to setup a default delay for closing? I'm looking of way to flash the lights too. Doing that first and then closing. I'm many different ways. I'm trying the flasher, but this doesn't delay the action.
It would be nice if there would be an option to turn on (or flash) a light for X seconds before the door starts closing.
My use case:
I would setup a color bulb to turn red for X seconds when a request is made to close the door.
I have had one situation occur where I manually opened the door while backing in the driveway and then shortly after, my door opening rule kicked-in but instead of opening the door, it closed it. Could have been a problem if I hadn’t noticed it and it had closed just as I started entering the garage!
To help with this, I will add the color bulb in a spot where it will be very obvious when backing in the garage so we will be warned if it is closing while we are backing in.
I guess if your garage lights were connected you could build a rule to flash the garage lights, have a 5, 10 or whatever amount of seconds wait and then open the door. Maybe build the rule with conditionals time of day, luminance, presence or motion in the garage area to determine when the conditionals would become relevant.
What would really be great if there was a way to connect to the MyQ hub which has the audio and visual warnings when the door closes from the MyQ app.
