I went out a little while earlier and I closed the garage door behind me with the old garage door fob in the car. I came back to a door that had been open for a while.
I have a presence sensor that triggers a rule should close all doors when I leave.
So, I tried to simulate it. While not leaving the house, I opened the door, closed it, put the presence sensor in a tin box to simulate leaving, and low and below, I get a notification that two garage doors failed to close.
I go out into the garage, and two doors are open.
So, I simulated it.
Does telling it to close when it's already closed do something bad.
I'm gonna look at the rule, but I think I'm just gonna start from scratch, exclude/include, reinstall app, etc.
edit: couldn't duplicate it again. Probably will reinstall.
If you're using the ZEN16s garage door setting then you should change it to momentary and set the auto off setting to 2 seconds.
Also make sure that the door operating time setting in the app is greater than the actual amount of time it takes for the door to open/close and that the auto off setting is disabled.
I have all the default settings as noted in the app's notes, except for the setting after power interruption, which I've set to "off" rather that "return to mode before interruption". I wouldn't think that'd make a difference, and I was trying to address an issue where all three doors were open after I cut the power for something else. Maybe that was unrelated though, I wouldn't think "off" would hurt.
That I didn't do. I think the door operating time might be a second less than actual. I'll have to correct that.
auto off is disabled in the relay device's settings
That will cause it to check the contact sensors before the door finishes opening/closing which will cause false notifications about it not opening/closing so correcting that should solve part of the problem.
What's selected for the "Switch Type" setting of the relay you're using?
This latest malfunction, with the door opening after I drove away, is confusing. The doors are ruled to close after presence is "away", and I had closed the door manually before I left.
I'm going to let it ride and see what happens. Monitor on app.
Also it's very important to keep the relays OFF before programming anything, the relays need to be off at all times and only activate to "ON" for a couple of seconds to trigger the motor, then they should go back to off. Sometimes 2 seconds may not be enough to activate the motor so if you keep seeing issues, try changing the auto-off timer to 4 seconds to see if it helps.
Thanks, I'll keep that in mind. I did watch the operation, and they did only turn on for a couple seconds, as evidenced by the blue light.
I like @krlaframboise 's idea of taking the app out of the timing mix by using the built in auto off time of the relay, especially since my z-wave has been acting screwy since updating to 2.2.4. It's intermittent, but if it continues, I'll increase the auto off duration at the relay.
That will not change anything, all that setting does is to turn off the relay after a certain amount of time, the important thing is the initial command, if it's not getting it it just won't open the door (or close).
Look at it this way, if you are manually pressing the button, when you press you count to 2 seconds and then let go of the button. Letting go after 4 seconds will not change the fact that you pressed it or not. What is triggering the open/close is if you press that button, no press no open/close.
So what you need to figure out is why isn't it pressing the button, most likely it's not receiving the signal to do so in the first place.
My mesh has been flakey since the upgrade from 2.2.3.
Just now, I went out into the garage, and hit a garage door relay tile on my dashboard and nothing for 10 seconds! Then it opened. No error message. So, even though it was slow, it opened.
Hitting the relay from the dashboard is me, talking to the hub, and the hub talking to the relay. Hitting the relay with the app, is the app talking to the hub, and the hub talking to the relay. So, even if the hub talking to the relay is slow, but working, slowing the app's talking to the hub could affect timing somehow.
I unplugged the relay and tried the garage door from the dashboard. It gave me the same error : garage door failed to open. So, yeah, the relay isn't getting the message in time, likely due to the mesh (my theory).
It happened again with the 4 second momentary at the zen16. Garage door failed to open. Worked okay when I drove away and came back. I wonder if it could be related to this thread, which relates to suspected driver problems with the Ecolink door and window contact sensor.
Yes. Not using the momentary switching aspect of the app, just the relay.
There's a rework of the generic zwave contact sensor driver coming shortly, that interacted with other Ecolink contact sensors to clog the mesh up. I'm not sure that's the problem here though. Looking at the log, and as @nclark said, it seems that the relay doesn't get the message from the hub to activate. And then, it'll work fine the next time. Vexing.
Since putting in a temporary driver for the Ecolink tilt, and rebooting the hub, I've had a couple of successful entrances. Hoping that's it.
edit: 3 for 3 now.
I seemed to have a failed to close this morning, which was a little different. It was 17 seconds from the apps' Turning on Relay Switch, to the device's reporting the relay switch is on. The app sent a Failed to Open report 13 seconds after the app said it was turning on the relay switch.
The difference in the closing example above, and the open example, is that the door did actually close, but failed to to actually open.
Is there any difference in the app between closing and opening? I can see maybe that would be the case. The whole thing could then be attributed to a slow mesh at that point in time.
