Aeotec Garage Door Controller ZW062

Hi,
The manual for Aeotec Garage Door Controller ZW062 is very vague about the 'motor control' cable connection.
Can anyone confirm how this aspect works?
Is it merely a momentary close of circuit to mimic an on wall toggle switch or something more sophisticated?
https://aeotec.com/z-wave-garage-door-controller - says "Simply connects to your garage door’s existing motor via two cables."

I am looking at this because my current solution uses a relay & sensor solution that seems to have stopped working with Indigo 7.3 (the device now reports as a relay without the sensors).

Any experience with the ZW062 most welcome!

regards
MM

My supplier here in NZ http://www.activeautomation.co.nz/z-wave-products says yes, the opener does simply replace the low voltage toggle switch.

So I have this working with Indigo on a single panel tilting door (although the manual says this does not work - sectional doors only).

After much cussing I realized the on the door sensor was upside down, hence the door was never reporting things correctly.
Once that was corrected the device messages and state was all good. Yay!

However, by default the device sounds 10000 million decebel warning sounds when it is activated.
Obviously required in some countries but not needed here!

To mute the sounds I need to send raw commands. I am really a bit perplexed about what to enter in the send raw command box to the device.

Can someone please help decipher/translate into Indigo speak?
https://aeotec.freshdesk.com/support/so ... controller

https://aeotec.freshdesk.com/support/so ... rm-sounds-

Many thanks in advance!

You don’t need Send Raw.

You need Set Configuration Parameter.

Param 37, 4 byte size.

I’ve not read the calculations but you can probably work that out yourself?

You need the decimal/integer version, not the hex version.

Perer


Sent from my iPhone using Tapatalk Pro

[matt (support)]

I hate it when they combine multiple settings into a single multi-byte configuration parameter. It makes it impossible to use Indigo's current declarative device definition model to define the UI for it, whereas if they used 4 individual 1 byte parameters it would be simple.

The docs I have also mention that parameter 44 can be used to set the volume, but I don't have that UI enabled in Indigo because when I tried it it wasn't useful. My comment in the device definition said the volume setting wasn't actually used then the controller was activated (I don't recall under what circumstances it was actually used).

Param 44 is to TEST the current volume of the ringtone, not SET it.

Obviously I don't know how you process params from your UI, but I would presume it is possible to (with some work) take the UI values of four settings, then calculate them into the required 4-byte value?

AnotherSphere, if you don't want alarms OR LED flashes, set the value to 0. This turns them off full stop.

If you want flashes, but no sounds, set them to 16777216.

Note you need to set params 37, 38, 39 and 40 (Door opening/closing/unknown/closed).

[matt (support)]

Param 44 is to TEST the current volume of the ringtone, not SET it.

Good to know, although it would be nice if it did set it. The earlier documentation I had didn't specify that.

Obviously I don't know how you process params from your UI, but I would presume it is possible to (with some work) take the UI values of four settings, then calculate them into the required 4-byte value?

Oh, definitely possible but not with how the declarative UI model currently works. That is, requires code changes and not just json/xml given the current state of things.

Param 44 is to TEST the current volume of the ringtone, not SET it.

Good to know, although it would be nice if it did set it. The earlier documentation I had didn't specify that.

http://manuals-backend.z-wave.info/make ... 0-17085731

Awesome! Thanks everyone. I now have a door that does not sound like the alarm from the state pen!
The joy of the internet and timezone - go to be frustrated with tech, wake up with fresh answer.
Thanks again.

Update - long power cut lost the settings.
So I made an action group that I could execute on demand to apply the settings.
I might also do an on startup get and a conditional trigger to apply it in a self fixing way going forward.