How to refresh Garage door

My garage door doesn’t seem to auto refresh its state but a manual refresh brings the garage to the correct state.
How can I automate the refresh with rule machine and custom action it ask for parameters but I must be using incorrect parameters for refresh?


I expect you could call the refresh command with no parameters. Have you tried that?

Ya, didn’t refresh

I'd give that a go and see if that does what you need.

What devices are controlling your garage door? Is that “garage door control” device a child of one of the community garage door apps? I ask these questions because you shouldn’t have to click refresh.

4 Likes

I agree with @ritchierich. You shouldn't have to refresh. Is your garage controller a non z-wave plus device?

1 Like

It is aeotec garage door controller. Seems to sometime get stuck in open position and refresh fix’s this

I'm not familiar with an (all-in-one kinda deal) Aeotec GDO device -- is the Aeotec part just a relay (for moving up/down)? If so, what are you using to determine the door position?

Are you using a garage door app to tie all that together -- in you screenshots above, it seems that way, but that would be helpful to confirm.

It has a tilt sensor attached to the door

Ah, OK, it is an all-in-one thing... What driver are you using for it?

Looks like user built aeotec garage door controller driver

I would ask the developer of that driver to help -- they would be in the best position to advise.

That is what this post is for?
I dont have any other developer contact details.
Might anyone have this developer contact details please?:pray:
maticslaszlo

In the driver code remarks is states
“You need to setup your own polling “
Does this mean the unit/driver doesn’t auto update state?
Can I setup this “polling” with rule machine ? What should be the trigger for polling?

From what I can find on Aeotec's site, that's a discontinued Gen5 (500-series) device, but it also says it's ZW Plus.

Polling should only be necessary for non-Plus ZW devices.

So it's possible that there was an even older (non-Plus) version of this device that this driver worked for too -- that's one reason the dev may have mentioned polling. Or maybe they were just using that term loosely (i.e. interchangeably with "refresh"). Without any add'l context, it's hard to know why the dev mentioned polling.

If you do end up confirming that polling is indeed necessary for this device, Hubitat has a built-in ZW Poller app.

Thanks for the information and tips!
I have setup simple rule machine to poll device if state changes, will give it some time and report back results.
Thanks :pray: