Merten CONNECT Move 5082xx

Hi, first time user here. Anyone got experience with Merten CONNECT Move 5082xx? I've got it paired with the Z-Wave controller and can see it in Indigo. I am however unable to understand how to make it do anything. I would assume that I could add an action and say something like "whenever the button is pushed, turn on the lights if they're off, or off if they're on". However, I'm unable to even make a trigger that prints to the log file.

I see the following output when pressing the button:

Z-Wave Debug RCVD basicGetState: 01 08 00 04 00 02 02 20 02 D1
Z-Wave Debug . . basicGetState: node 002, endpoint None
Z-Wave Debug RCVD basicSetState: 01 09 00 04 00 02 03 20 01 FF 2D
Z-Wave Debug . . basicSetState: node 002, endpoint None, value 255 (no node dispatch)


And this is the output when I press "Write to log" during configuration of the Z-Wave module:

Z-Wave Indigo Device "002 - Remote Switch" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.256
Node ID: 2
Model: Remote Switch
Model ID: 00000000
Manufacturer: Unknown
Manufacturer ID: 0000
Protocol Version: 2.27
Application Version: 1.08
Model Definition Version: 0
Library Type: 2
Class Name: Remote Switch
Class Hierarchy: 01 : 12 : 00
Command Class Base: 00
Command Versions: 20v1 85v1 86v1 8Ev1 70v1 72v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: - none -
Neighbors: - none -
Associations: 1:[1]
Config Values: - none -


Any ideas how to add a simple trigger do to some action whenever the button is pushed?

[jay (support)]

Does Indigo change the device state to ON/OFF when the button is pressed (toggle)?

The issue is that Z-Wave scene devices all behave differently - unfortunately there is no standard. We may have to specifically add this device. Be sure to click the Submit Device Information button in the device config dialog and fill out the resulting form so it'll get added to the list.

Thanks for the swift reply, Jay.

How do I check if Indigo has changed the device state? In "DEVICES" I can't see any state for the device, only "Device Details" which only contains "Last Updated".

EDIT: Submittet device report. Some additional information that may or may not be useful: http://www.pepper1.net/zwavedb/device/67

[jay (support)]

Try defining a Z-Wave Event->Z-Wave Command trigger and see what options there are in the config dialog for that event.

Tried setting up as:

Type: Z-Wave Event
Event: Z-Wave Command

When pressing "Edit Event Settings" there are no values selectable in "From:" or "Received:".

[matt (support)]

Can you try Define/Sync of the module 2 or 3 more times, and copy/paste the Event Log result from each.

Unfortunately, based on the original log information above it looks like that module is returning neither a good manufacturer ID nor a good model ID. I can create a device definition that will work so Indigo can translate the commands you are seeing when the buttons are pressed, but I have to have a valid manufacture and model ID to attach our definition to. Hopefully the bad values you got on the first define/sync were just a one time problem, otherwise I'm not sure how Indigo is going to identify the module.

Hi, syncing the device I get the following output:

17 Sep 2014 17:41:55
Z-Wave Debug intiatingSyncUI (timeout in 300 seconds)
Z-Wave Debug RCVD basicGetState: 01 08 00 04 00 02 02 20 02 D1
Z-Wave Debug . . basicGetState: node 002, endpoint None
Z-Wave Debug RCVD requestNodeInfo: 01 13 00 49 84 02 0D 01 12 00 72 86 70 85 8E EF 85 20 26 50 8E
Z-Wave Syncing - started for device "002 - Remote Switch"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 02 01 01 7B
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5E
Z-Wave Debug . . getNodeNeighbors: nodeId 002, neighbors: - none -
Z-Wave Syncing - retrieved module neighbors list: - none -
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 02 04 F8 67
Z-Wave Debug RCVD requestNodeInfo: 01 13 00 49 84 02 0D 01 12 00 72 86 70 85 8E EF 85 20 26 50 8E
Z-Wave Debug . . requestNodeInfo: node 002, combined class list: 20v1 85v1 86v1 8Ev1 70v1 72v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 02 02 72 04 05 F9 6F
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 02 08 72 05 00 7A 00 02 00 01 F1
Z-Wave Debug . . requestManufactureInfo: node 002, manufacturerId 007A, productId 00020001
Z-Wave Debug . . requestManufactureInfo: Merten, Transmitter Module
Z-Wave Syncing - retrieved manufacture and model names: Merten - 007A, Transmitter Module - 00020001
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 02 02 86 11 05 FA 8D
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 02 07 86 12 02 02 1B 01 08 75
Z-Wave Debug . . requestVersInfoGen: node 002, protoVers 2.27, appVers 1.08
Z-Wave Syncing - retrieved protocol version 2.27, app version 1.08
Z-Wave Syncing - retrieved class hierarchy: Controller : Remote Switch : -- (01 : 12 : 00, base 00)
Z-Wave Syncing - retrieved command classes: 20v1 85v1 86v1 8Ev1 70v1 72v1
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 02 02 85 05 05 FB 9B
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 02 03 85 06 01 71
Z-Wave Debug . . requestAssociationGroupCount: node 002, group count: 1
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 02 03 85 02 01 05 FC 98
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 02 06 85 03 01 0C 00 01 79
Z-Wave Debug . . requestAssociations: node 002, group: 1, num associations: 1, max associations: 12, replies left: 0
Z-Wave Debug . . requestAssociations: node 002, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - created device "002 - Transmitter Module"
Z-Wave Syncing - complete
Z-Wave Debug terminatingSyncUI

And it now also shows up in "Edit device settings..." -> "Write to Log" as:

Z-Wave Indigo Device "002 - Transmitter Module" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.256
Node ID: 2
Model: Transmitter Module
Model ID: 00020001
Manufacturer: Merten
Manufacturer ID: 007A
Protocol Version: 2.27
Application Version: 1.08
Model Definition Version: 0
Library Type: 2
Class Name: Remote Switch
Class Hierarchy: 01 : 12 : 00
Command Class Base: 00
Command Versions: 20v1 85v1 86v1 8Ev1 70v1 72v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: - none -
Neighbors: - none -
Associations: 1:[1]
Config Values: - none -

Is this helpful or should I try again a few more times?

[matt (support)]

That looks much better – it returned a good manufacture and model ID. We'll look into it...

Awesome. Let me know if there's anything else I can do to test it out.

[matt (support)]

Indigo 6.0.15 is now available, and includes preliminary support for the 5082xx. Let me know if it works correctly after you update and then define/sync the device again.

Great work! The device is now properly reckognized by indigo, but adding triggers that simply writes to log still don't seem to work.

I've added triggers for "Device State Changed" using the device "Device: 002 - Transmitter Module" with "On/Off state" set to "Becomes On", "Becomes Off" and "Has Any Change", but none of them seem to trigger when I press the button.

I've also tried adding a trigger for "Z-Wave Event" with commands from "002 - Transmitter Module" received "On", "Off", "Status Reply" and "Any Command" but none of them seem to trigger either. Maybe I'm doing something wrong?

Pressing the button two times in a row produces the following output:

First time:
Z-Wave Debug RCVD basicGetState: 01 08 00 04 00 02 02 20 02 D1
Z-Wave Debug . . basicGetState: node 002, endpoint None
Z-Wave Debug RCVD relaySetLevel: 01 09 00 04 00 02 03 20 01 FF 2D
Z-Wave Debug . . relaySetLevel: node 002, endpoint None, value 255

Second time:
Z-Wave Debug RCVD basicGetState: 01 08 00 04 00 02 02 20 02 D1
Z-Wave Debug . . basicGetState: node 002, endpoint None
Z-Wave Debug RCVD relaySetLevel: 01 09 00 04 00 02 03 20 01 FF 2D
Z-Wave Debug . . relaySetLevel: node 002, endpoint None, value 255

Doesn't seem to be any on/off state or am I wrong? Wouldn't it be logical for the value to be 0 for off and 255 for on, or something similar?

[matt (support)]

Hmmm... yeah, it doesn't seem to be sending the OFF (0 byte) version.

Based on what is logged, I think it is trying to query the current state of the device first from Indigo then it probably sends the opposite (toggle) of that state. Let me think about this some more and I'll see if I can get you a new version of our Z-Wave library that does this.

Sounds about right. Is that a normal strategy to avoid on-device storage for state information? In any case, let me know if there's anything more I can do and if there are any updates. I'm also venturing a guess that other Merten CONNECT units (see http://www.merten.com/Radio-transmitter ... 148.0.html) use the same approach, so adding support for it may cause other units to work as well?

Any update on this?

[matt (support)]

No, it will be a while before I have the opportunity to get to it.