Does anyone know if there are two different sensors that generate the "contact" and "door" events or are both generated by the tilt sensor?
I moved my "Garage door is open" automation to an Ecolink tilt sensor because the native garage door tilt sensor was generating false events. Now my Ecolink tilt sensor sometimes gets stuck in the "open" status when the garage door is actually closed.
I was thinking of incorporating the original sensor into the automation as a double check (what are the chances that BOTH sensors could be off? ) and wanted to see which one I should use.. Thanks.
How did those replacement mercury sensors that @aaiyar sent you work out? That should be a cure for the "stuck" sensor.
I have the same setup... the Linear GD00Z-4 GDO was spitting false events all the time. I switched my automation Alerts to only use the Ecolink. I have a Node-Red flow that says "The Garage Door has been Open too Long." Every 90 seconds after it's been open 12 minutes. All driven by the Ecolink, not the GDO. I have the GDO in a Dashboard so I can get a confirmation that way, but for everything else, I use only the ZWave Plus Ecolink Tilt Sensor.
Almost exactly the same setup (including Node-RED). My flow checks every 10 minutes (max 5 times) using a delay node. The "delay" node is cancelled if a "closed" event is received. What I just did, was add the GDO to the flow (filter for only a "closed" event) so that either "closed" event will cancel the delay and not send an alert.
I started with wanting the belt-and-suspenders approach, where both the GDO and the Tilt had to agree, disagreement was it's own alert. But after being woken with an alert at 2am the 3rd night in a row, I completely abandoned the GDO's sensor. I have had no false alerts since.
I used to cleanup my Node-Red flows to discard all the Inject/Debug nodes... but I don't any more. I carefully name them and leave them after finding myself putting them back days/weeks later when I wanted to enhance a flow.
Just packed everything. Post-office in 30 minutes. I'm sending two mercury switches, and two pre-assembled mercury switch-based tilt sensors that I made out of GoControl contact sensors just now. These work really well (even though they are zwave and not zwave+) - I have made several of these that friends are using on C-5 and C-7 hubs.
I added the Virtual Switch"Garage Ignore" for those occasions when we know that the GDO will be open for more than 12 mins. Kids skating with their friends and using the Garage as shade, or gardening are the most common examples. Then I don't want the noise of the alert. When the GDO does close though, that override is reset.
I don't even expose the Linear GDO to Node-Red. It's purely a Dashboard thing and I use a dashboard almost never. Except like today when I opened it to screen cap something
I move from the EcoLink to the GoControl because the EcoLink tilt sensor suck big time. They would report open / close events when they were not moving, and would not report events when they did move. The GoControl has been flawless -- until recently.
Strange - my GoControls have been quite flaky, but not all the time. It seems to happen with extreme temperatures. The Ecolink was more reliable until now. Iām now using the GoControl to verify but automations are driven off the Ecolink status.