[ANSWERED]: Merten dimmer error syncing/including

[UPDATE]
The dimmer finally included after I had reloaded the z-wave controller. Not sure why this would make the difference. Next problem though is the little brother of this dimmer: a remote (battery operated) switch. It's included in the Z-Stick, but it is asleep when I try to include it. Indigo tells me SO quickly, that I have no time to activate the switch. What can I do?
[END UPDATE]


Hi,
I am trying to sync/include a Merten dimmer that's in my Z-Stick S2. I get the following debug info when I try it. It looks encouraging at first but it ends up in error. What's going on?
Thanks,
Mark

Code: Select all

Z-Wave                          Syncing - started for device "008 - Dimmable Power Switch"
  Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 08 01 01 71
  Z-Wave Debug                    RCVD getNodeNeighbors: 01 20 01 80 01 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 5F
  Z-Wave Debug                    . .  getNodeNeighbors: nodeId 008, neighbors: 1
  Z-Wave                          Syncing - retrieved module neighbors list: 1
  Z-Wave                          Syncing - assigning return route to "008 - Dimmable Power Switch"
  Z-Wave Debug                    SENT assignReturnRoute: 01 05 00 46 08 01 B5
  Z-Wave Debug                    RCVD assignReturnRoute: 01 04 01 46 01 BD
  Z-Wave Debug                    RCVD assignReturnRoute: 01 05 00 46 01 00 BD
  Z-Wave Debug                    . .  assignReturnRoute: node 008, success 1
  Z-Wave                          Syncing - assigned return route
  Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 08 04 32 A7
  Z-Wave Debug                    RCVD requestNodeInfo: 01 14 00 49 84 08 0E 04 11 01 72 86 70 85 8E 26 29 27 75 EF 26 2F
  Z-Wave Debug                    . .  requestNodeInfo: node 008, combined class list: 20v1 85v1 26v1 27v1 29v1 8Ev1 70v1 72v1 75v1 86v1
  Z-Wave Debug                    SENT requestManufactureInfo: 01 09 00 13 08 02 72 04 05 33 AF
  Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 00 08 08 72 05 00 7A 40 03 00 01 BA
  Z-Wave Debug                    . .  requestManufactureInfo: node 008, manufacturerId 007A, productId 40030001
  Z-Wave Debug                    . .  requestManufactureInfo: Merten, Wall Dimmer Module
  Z-Wave                          Syncing - retrieved manufacture and model names: Merten - 007A, Wall Dimmer Module - 40030001
  Z-Wave Debug                    SENT requestVersInfoGen: 01 09 00 13 08 02 86 11 05 34 49
  Z-Wave Debug                    RCVD requestVersInfoGen: 01 0D 00 04 00 08 07 86 12 06 02 1B 02 01 71
  Z-Wave Debug                    . .  requestVersInfoGen: node 008, protoVers 2.27, appVers 2.01
  Z-Wave                          Syncing - retrieved protocol version 2.27, app version 2.01
  Z-Wave Debug                    SENT requestVersInfoCmdClass: 01 0A 00 13 08 03 86 13 26 05 35 6E
  Z-Wave Debug                    RCVD requestVersInfoCmdClass: 01 0A 00 04 00 08 04 86 14 26 01 48
  Z-Wave Debug                    . .  requestVersInfoCmdClass: node 008, class command 26 using version 1
  Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Dimmable Power Switch (04 : 11 : 01, base 26)
  Z-Wave                          Syncing - retrieved command classes: 20v1 85v1 26v1 27v1 29v1 8Ev1 70v1 72v1 75v1 86v1
  Z-Wave Debug                    SENT requestAssociationGroupCount: 01 09 00 13 08 02 85 05 05 36 5C
  Z-Wave Debug                    RCVD requestAssociationGroupCount: 01 09 00 04 00 08 03 85 06 02 78 (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD requestAssociationGroupCount: 01 09 00 04 00 08 03 85 06 02 78
  Z-Wave Debug                    . .  requestAssociationGroupCount: node 008, group count: 2
  Z-Wave Debug                    SENT requestAssociations: 01 0A 00 13 08 03 85 02 01 05 37 59
  Z-Wave Debug                    RCVD requestAssociations: 01 09 00 04 00 08 03 85 06 02 78 (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD requestAssociations: 01 09 00 04 00 08 03 85 06 02 78 (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD requestAssociationGroupCount: 01 09 00 04 00 08 03 85 06 02 78
  Z-Wave Debug                    RCVD requestAssociations: 01 0B 00 04 00 08 05 85 03 01 05 00 7F
  Z-Wave Debug                    . .  requestAssociations: node 008, group: 1, num associations: 0, max associations: 5, replies left: 0
  Z-Wave Debug                    . .  requestAssociations: node 008, group: 1, associations: []
  Z-Wave                          Syncing - retrieved group 1 associations: []
  Z-Wave Debug                    SENT requestAssociations: 01 0A 00 13 08 03 85 02 02 05 38 55
  Z-Wave Debug                    RCVD requestAssociations: 01 0B 00 04 00 08 05 85 03 02 05 00 7C
  Z-Wave Debug                    . .  requestAssociations: node 008, group: 2, num associations: 0, max associations: 5, replies left: 0
  Z-Wave Debug                    . .  requestAssociations: node 008, group: 2, associations: []
  Z-Wave                          Syncing - retrieved group 2 associations: []
  Z-Wave Debug                    SENT addInterfaceAssociation: 01 0B 00 13 08 04 85 01 01 01 05 39 53
  Z-Wave Debug                    RCVD addInterfaceAssociation: 01 05 00 13 39 01 D1 (node NAK)
  Z-Wave Error                    Syncing - failed
  Z-Wave Error                    No response from "008 - Dimmable Power Switch". Module might be asleep, or is unreachable.


The log from attempts to include the Merten push button:

Code: Select all

Z-Wave                          Syncing - started for device "011 - Remote Switch"
  Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 0B 01 01 72
  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 011, neighbors: - none -
  Z-Wave                          Syncing - retrieved module neighbors list: - none -
  Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 0B 04 1B 8D
  Z-Wave Debug                    RCVD requestNodeInfo: 01 06 00 49 81 00 00 31
  Z-Wave Debug                    RCVD requestNodeInfo: failed (module asleep or doesn't support command)
  Z-Wave Error                    Syncing - failed
  Z-Wave Error                    No response from "011 - Remote Switch". Module might be asleep, or is unreachable.
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 0B 0D 01 12 00 72 86 70 85 8E EF 85 20 26 50 87
  Z-Wave Debug                    terminatingSyncUI (ignoring -- insideSyncUiCount value is already 0)


Hi,

I finally managed to sync this button. It worked after a few times, when I pressed the button three times and at the same time started the sync in Indigo. This thing goes to sleep in about one second

I can now turn a light on and off with this button, after associating 1 and 2 with a dimmer. I was used to being able to actually dim the lights with the 505119 as well, but that's not working. Is there some special association I forgot to set?

Thanks,

Mark

[matt (support)]

Unfortunately some battery operated modules can be difficult to keep awake long enough for the sync to start. Sounds like you finally got it working though.

The module only supports 2 association groups, so if you tried both of those and it still isn't working then I'm not sure what is wrong. It might be a module configuration setting, but I'm not sure the technical details on what config settings that particular module supports (Indigo doesn't have any of them defined in its model definition currently).

Thanks Matt.

I did some more research, and ended up reading this document: http://www.smarthus.info/support/downlo ... en_bpd.pdf. It mentions that a 5051xx push button can only be connected to one (or more) dimmers, but not to a switch or even the Z-Stick itself; it would show reduced functionality and do only on/offf.
That behavior is consistent with using Merten software: I have a 505119 associated with a dimmer and a mirror heater in the bathroom. Same behavior: because of the heater (on/off), the push button cannot properly operate the dimmer anymore.

Long story short: only associate the pushbutton with the dimmer(s) and nothing else in group 1, that should do the trick.

Mark

Hi Stoutjesdijk and Matt

As Matt have seen I am a brand new Indigo-user (pref HomeSeer HS3 and Zipabox).

I have been struggling VERY much to get the Schneider Electric / Merten radio CONNECT buttons to work in HS3 and I was quite happy to see that it looked like as Indigo has come a little bit further to get these very beautiful but annoying (from Z-wave point of view) switches. As both Matt has pointed out and Stoutjesdijk has seen they go into sleep within a second after you have waken it up...

Normal procedure is to click on any of the 4 buttons (on the 2 channel transmitter) three times in a row quickly and count the red blinks. When the 6th blink is gone (or sometimes at the 6th blink) you have to do your association or update. This part is VERY critical to get it to work and sometimes I can see in the log that I miss the time window when the switch is awake. If one is quick enough you can click multiple times on the action (add association, sync and so on) in Indigo you are trying to perform.

The doc that Stoutjesdijk referred to is very good for us trying to get these switches to work in Z-wave environments. That document helped me a lot! Here is the link again http://www.smarthus.info/support/downlo ... en_bpd.pdf

The good thing with these switches are that they are so really beautiful design and can be used with a lot of different frames from Schneider Electrics model series called EXXACT. I am using anthracite colored switches with solid black glass frame.

Look at the attached picture or on page 26 in the PDF-file for the Schneider product catalogue (link below).


For those of you who can read swedish have a look at the product catalogue (with a LOT of pics so that non-swedish readers can also at least see the beautiful combinations one can create for their switches, dimmers etc)

http://download.schneider-electric.com/ ... g_webb.pdf

Anyway, I have been struggling very much with these switches and it seem to work somewhat better in Indigo which is great.

However, as Stoutjesdijk wrote it is important to only associate a dimmer to group 1 if you want to be able to dim on for example button one (on the 2-channel transmitter) and to for example, as me, to be able to control a roller shutter using the Fibaro FGR-221 roller shutter controller on the 2nd channel.

The drawback with this setup is that you will not be able to see status changes from the switch in Indigo and ONLY the status change from the dimmer connected to association group no 1. Anything that happens on group 3 will have to be polled at the time intervall you are polling the particular device (in my case the FGR-221 associated with group 3, i.e. the 2nd channel on the switch).
This problem is pretty well explained in the document referred to above. Here is a quote from that doc:

"While it is desirable in the case of the 2-gang Merten transmitter to use both transmitters with HomeSeer for the status change features, this is not possible because of the use of the Z-Wave Association Command Class with the Merten devices – the Association Command Class sends an operational (On or Off) signal to the associated device, or in this case HomeSeer, but does not include any information on which transmitter the signal was sent from. Therefore, HomeSeer cannot differentiate one transmitter’s signal from the other."

So the conclusion is that the best way to use these cool and beautiful switches is to associate them directly with the device you want to control and accept the fact that device in group three will NOT create an event that will automatically update the status of the device but rather that you will get the update at the specified update interval that you have set for that device.

Maybe Matt can give some light on this why the device in group 3 is not updating its status automatically in Indigo when the device has its status update set to "Poll device only when activity has been detected"?

Ahh, forgot to report to you Matt that the setting "Enable double-click to full brightness" does not seem to work when using the Schneider Electric / Merten CONNECT-switches. I´ll try tomorrow with a traditional switch connected directly on the input terminals of the Fibaro FGD-211 dimmer.

I can confirm that using a push switch connected directly to the switch input terminals on FGD-211 works fine.
A double-click on the push button puts the light at full strength directly while a single-click puts the light to the latest used dimmed value.
Using the Schneider Electric / Merten radio connect push-button with double click does not bring the light up to full strength though.

Can it have something to do with the fact that the radio CONNECT buttons are configurable to use single surface? Meaning that it actually can control 4 devices using the top left for one device, bottom left for another device, top right for a third device and bottom left for a fourth device?
(Reading the doc at http://www.smarthus.info/support/downlo ... en_bpd.pdf page 2 where it says: "Switching single-surface" parameter number 4?)

[matt (support)]

So you have the module that is receiving the group 3 association (not the Merten) set to poll device only when activity is detected? In that case Indigo is looking for activity from that module, not the transmitting (Merten) module. So it doesn't realize it should be polling. If you turn on debug logging (Interfaces->Z-Wave->Configure... menu item), is anything logged when the group 3 association is broadcast? Indigo may not be picking up any activity because it isn't associated with group 3, although it is possible the Merten is broadcasting some type of command (node info) that Indigo can catch then start the polling sequence. That would probably need to be a different UI option "poll all associated devices on activity" that you would be set on the transmitting module (Merten) and not the receiving module. This will be a feature request since it is going to be non-trivial, but is worth investigating to see if it can work.

Unfortunately, I don't have an ideas/suggestions for the double-click to full brightness not working.

I am using Z-wave debug log ging now when in "test mode" so that I can see in the log window what happens when I try to add/modify/delete etc these "odd" Z-wave devices I have.

It is especially use full when trying to add and sync in these Schneider Electric / Merten CONNECT 1- and 2-channel push buttons. It makes it easier to quickly see if I was able to do the association, add or delete at the right millisecond after the 6th blink of the red LED.

This is the device info

==========
Indigo Z-Wave Version: 1.0.301
Node ID: 26
Model: Transmitter Module
Model ID: 00010004
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:[4] 2:[] 3:[3] 4:[]
Config Values: - none -

==========

and here is the full sync log when syncing in the device:

==========
Z-Wave Syncing - started for device "026 - SchneiderElectric / Merten CONNECT 2-channel push"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 1A 01 01 63
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 026, neighbors: - none -
Z-Wave Syncing - retrieved module neighbors list: - none -
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 1A 04 5C DB
Z-Wave Debug RCVD requestNodeInfo: 01 13 00 49 84 1A 0D 01 12 00 72 86 70 85 8E EF 85 20 26 50 96
Z-Wave Debug . . requestNodeInfo: node 026, combined class list: 20v1 85v1 86v1 8Ev1 70v1 72v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 1A 02 72 04 05 5D D3
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 1A 08 72 05 00 7A 00 01 00 04 EF
Z-Wave Debug . . requestManufactureInfo: node 026, manufacturerId 007A, productId 00010004
Z-Wave Debug . . requestManufactureInfo: Merten, Transmitter Module
Z-Wave Syncing - retrieved manufacture and model names: Merten - 007A, Transmitter Module - 00010004
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 1A 02 86 11 05 5E 31
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 1A 07 86 12 02 02 1B 01 08 6D
Z-Wave Debug . . requestVersInfoGen: node 026, 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 1A 02 85 05 05 5F 27
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 1A 03 85 06 04 6C
Z-Wave Debug . . requestAssociationGroupCount: node 026, group count: 4
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 1A 03 85 02 01 05 60 1C
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 1A 06 85 03 01 0C 00 04 64
Z-Wave Debug . . requestAssociations: node 026, group: 1, num associations: 1, max associations: 12, replies left: 0
Z-Wave Debug . . requestAssociations: node 026, group: 1, associations: [4]
Z-Wave Syncing - retrieved group 1 associations: [4]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 1A 03 85 02 02 05 61 1E
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 1A 05 85 03 02 0C 00 67
Z-Wave Debug . . requestAssociations: node 026, group: 2, num associations: 0, max associations: 12, replies left: 0
Z-Wave Debug . . requestAssociations: node 026, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 1A 03 85 02 03 05 62 1C
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 1A 06 85 03 03 0C 00 03 61
Z-Wave Debug . . requestAssociations: node 026, group: 3, num associations: 1, max associations: 12, replies left: 0
Z-Wave Debug . . requestAssociations: node 026, group: 3, associations: [3]
Z-Wave Syncing - retrieved group 3 associations: [3]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 1A 03 85 02 04 05 63 1A
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 1A 05 85 03 04 0C 00 61
Z-Wave Debug . . requestAssociations: node 026, group: 4, num associations: 0, max associations: 12, replies left: 0
Z-Wave Debug . . requestAssociations: node 026, group: 4, associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Debug SENT addInterfaceAssociation: 01 0B 00 13 1A 04 85 01 01 01 05 64 1C
Z-Wave Syncing - added group 1 association to interface
Z-Wave Debug . . addInterfaceAssociation: node 026, group: 1, associations: [4, 1]
Z-Wave Syncing - complete
Z-Wave Debug terminatingSyncUI

===========

NOTE that when I re-sync the device it automatically adds in the Indigo Z-wave (device 1) into the association group 1 of the switch?!
This makes it impossible to dim the lamp on the FGD-211 dimmer and it now only works as an on/off switch.
If I go into Manage Associations and REMOVE the Indigo Z-wave from group 1 on the switch the dimming works fine and I still see the events and device status in the event log.
I have to remember to remove this association to Indigo Z-wave in group 1 after each device resync in order to keep the dimming functionality.


Here you can see the device data for the FGD-211 dimmer:

=========
10 jan 2015 21:20:18
Z-Wave Indigo Device "004 - Dimmer Switch (FGD211)" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.301
Node ID: 4
Model: Dimmer Switch (FGD211)
Model ID: 0100100A
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 3.52
Application Version: 2.02
Model Definition Version: 8
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 85v1 26v1 27v1 8Ev1 70v1 72v1 73v1 7Av1 86v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, beaming
Neighbors: 2, 3
Associations: 1:[1] 2:[1] 3:[1]
Config Values: 8:1 9:5 10:1 11:1 12:99 13:2 14:0 15:1 16:1 17:0 18:0 41:0
=========

and here is the device data for the FGR-221 shutter controller:

========
Indigo Z-Wave Version: 1.0.301
Node ID: 3
Model: Shutter Controller (FGR221)
Model ID: 03000107
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 3.42
Application Version: 1.07
Model Definition Version: 3
Library Type: 3
Class Name: Multiposition Motor Control
Class Hierarchy: 04 : 11 : 03
Command Class Base: 26
Command Versions: 20v1 70v1 26v3 86v1 27v1 8Ev1 50v1 72v1 73v1 25v1 85v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, beaming
Neighbors: 2, 4
Associations: 1:[1] 2:[1] 3:[1]
Config Values: 41:0 14:0
=========

Both the dimmer and the shutter controller has "Poll device = Only when activity detected" enabled but it is only the dimmer activity that is reported in the event log.
If I add the Indigo Z-wave to group 3 (still removed from group 1) on the push button then I get response in the event log from the shutter controller as well but then the dimming functionality of that button disappears which means I can not move the shutter to a specified level by pushing the down switch and keeping it down until it is in the desired position. However, I do get status updates in the event log for both the dimmer and the shutter controller whit this association setup.

As soon as I remove the Indigo Z-wave from association group 3 of the switch I can again dim the lamp on the dimmer (and get status updates) as well to move the shutter to a specified position using "dimming functionality" of the 2nd button. However, again, no status updates of the shutter controller in the event log anymore then.

As "Stoutjesdijk" wrote in the post posting.php?mode=reply&f=58&t=13159#pr89773 below it is NOT possible to have Indigo Z-wave in either association group 1 or 3 in order to keep the dimming functionality for both the push buttons.

I can see in the event log that NOTHING is being transmitted in this case when I push the channel 2 button, i.e. association group 3.

This is what is being sent sent when I first press on the upper button on channel one (association group 1) for the dimmer (and still no association to Indigo Z-wave in this association group 1):
10 jan 2015 21:37:42
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 04 03 26 03 17 C7
Z-Wave Debug . . requestDimmerStatus: node 004, endpoint None, value 23

and this is what is being sent when I press the down (i.e. dim down or shut off):
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 04 03 26 03 00 D0
Z-Wave Debug . . requestDimmerStatus: node 004, endpoint None, value 0
Z-Wave received "004 - Dimmer Switch (FGD211)" status update is off

I am happy to send you one of my Schneider Electric / Merten CONNECT radio push buttons (have plenty of them... ) for further investigation by your tech guys and to use in your development in case that it would help to create a good solution.

[matt (support)]

Thanks for the information. I'm not sure we can work around the Merten behavior in this case, but I'll look into it in more detail when I add the device definition to Indigo for the Merten dimmer.

Have you looked at this REALLY good tech doc for this switch: http://www.pepper1.net/zwavedb/device/69

I also see the following info in the manual on http://www.merten.com/uploads/tx_seqdownload/5071xx_5072xx_Taster_CONNECT_INT_03.pdf:

Schneider Electric - Merten - 2 channel push button transmitter wall mounted - 50720xx.JPG (47.13 KiB) Viewed 7321 times

and there there are these configuration parameters but how can I set them via Indigo?

Schneider Electric - Merten - 2 channel push button transmitter wall mounted - configuration parameters - 50720xx.JPG (31.97 KiB) Viewed 7321 times

It also interesting to read in http://www.smarthus.info/support/download/zwave/Merten_bpd.pdf:
"While it is desirable in the case of the 2-gang Merten transmitter to use both transmitters with HomeSeer for the status change features, this is not possible because of the use of the Z-Wave Association Command Class with the Merten devices – the Association Command Class sends an operational (On or Off) signal to the associated device, or in this case HomeSeer, but does not include any information on which transmitter the signal was sent from. Therefore, HomeSeer cannot differentiate one transmitter’s signal from the other."

So what makes me confusing is that I have NO association at all between association group 1 or 3 between Merten-switch and Indigo Z-wave. Only associations I have set via Indigo is that group 1 on the switch goes to my Fibaro dimmer and group 3 on the switch goes to my Fibaro shutter controller and with this setup on the associations Indigo is able to catch data/transmission for group 1 events from the switch (and therefore update dimmer status in the Indigo GUI) but no events on group 3 from the switch (and therefore no updates in the Indigo GUI of the shutter controller)?

To get the updates in Indigo GUI to show up for association group 3 also I have to add Indigo Z-wave to association group 3 but then the dimmer functionality of BOTH buttons stops working and the switch now works as a simple on/off switch.

Ok so no help if I send you a switch for testing and RF investigation so that you can use an R/Logic-sniffer to see what is actually being sent when one is pushing button 3 and (channel 2) of the switch?

[matt (support)]

For now you can modify the config parameters using the Interfaces->Z-Wave->Modify Configuration Parameter... menu item. In future versions we might add the UI for the Merten modules.

It appears that when you associate it with the Z-Stick, the Merten changes its behavior and what commands it sends to the other modules you have associated with it (Fibaros). Those modules, when in that mode, broadcast out state changes after they occur.

If you don't associate it with the Z-Stick, then you getting the dimming behavior you want but then the Fibaro's behave differently (they stop broadcasting out state changes).

I don't think any of that has to do with Indigo's poll after activity setting (at least not based on the Event Log snippet you provided above). That is, if you turn that setting totally off you will still see the same behavior you are currently seeing.

Unfortunately, none of this really is in Indigo's control. It is just the quirks in how those modules are working.

While I appreciate the offer for the Merten module, I don't believe it will help (and I also don't have an RF compatible Z-Stick that will be able to communicate with it).

Hi all,

Just wanted to let you guys know that I finished including all my battery-operated buttons (and associating them properly with several dimmers) in a half day. I have quite a few of them. Previously, for example using LinuxMCE, I could never manage to get it done. I am extremely happy that I have basic functionality plus Indigo control!

Cheers

Mark

Hi Mark ("Stoutjesdijk")

I have no problem either to add my Merten / Schneider Electric battery operated 2 channel wall controllers.

In Indigo it is so much easier to manage associations compared to other home automation software platforms that I have tried.

However, my main issue is that the 2nd channel does not transmit its u pdates properly (as written in the thread above) and this causes the state of the device controlled on the 2nd channel to NOT being updated in Indigo. I need to put all devices that I control with the 2nd channel on my switches into polling mode (for example every minute or so) in order to catch the state of those devices in Indigo.

I really wish this could be solved... It is actually currently my only issue to be happy.

I will try my RF sniffer for the European Z-wave frequency 868.42MHz as soon as I have some time over (probably this weekend) and see if I can discover how the transmitted sequence differs between those 2 channels.

I am using this cool kit: http://www.ti.com/tool/CC1110DK-MINI-868?keyMatch=CC1110DK-MINI-868&tisearch=Search-EN with a software that can display the RF packets. I am not sure if the RF packets of these battery operated switches are encrypted? Output will look something like this picture:
http://research.sensepost.com/cms/tools/embedded/zforce/zforce.png

I know that Z-wave uses a proprietary protocol in the Sigma chip but I am not sure if the actual RF packets are encrypted? I am hoping that I will be able to see the difference in the RF packets between channel 1 on the switch (associated to group 1) and channel 2 on the switch (associated to group 3). That might help us in the research of finding the reason why events on the 2nd channel is not show at all in Indigo's log.

I will also try to contact Schneider Electric here in Sweden but my hope to get a useful feedback from them is minimal... I have seen other forum threads out in Germany (where the switch is under the brand Merten) that they have been quite unsuccessful getting Merten / Schneider Electric engineers to give good answers on how to the switch is sending the updates...
(Z-wave fellows at the MiCasa Verde forum having similar issues: http://forum.micasaverde.com/index.php?topic=276.30, same thread next page: http://forum.micasaverde.com/index.php/topic,276.msg27881.html#msg27881 )

I found this thread in HomeSeer forum (now after I have shut down my HS software... ):
http://forums.homeseer.com/showthread.php?t=139256&highlight=merten+connect
Very interesting reading of users with success to get both channels to work in HomeSeer by first using a Merten USB Z-wave dongle and Mertens software to add all Z-wavedevices into Merten software and then transferring all devices from Merten into the battery operated controller (if I understood the instructions correctly) that now will be a Primary controller. Then transfer all the network back into the Aeon Labs Z-wave stick and both channels should be possible to use in Indigo as well as update status!
Unfortunately I do not have a Merten Z-wave USB stick so I can not test this though.

(@Matt: I have attached a TXT-file showing my log from HS3 PRO when I am pressing each of the 4 buttons. As you can see there is data coming in for all 4 buttons. In Indigo I see reaction in the log only on the first chanel, i.e. the upper left and lower left buttons)

Wohooo!

I think I have found a decent option to the messy Merten Radio CONNECT push buttons!!

The new (?) Z-wave wall dual switch ZME_WALLC-S from ZWAVE.ME seems to be a good alternative and they can be combined with different frames and paddles.
http://store.zwaveeurope.com/product_in ... s_id=12686

The fram and paddles called "Paris" looks very clean http://store.zwaveeurope.com/product_in ... s_id=12747 seems nice and clean.

The switch has also the new Z-Wave PLUS standard which has some new nice features:

• 50% improvement in battery life
• 67% improvement in range
• 250% more bandwidth
• Three F channels for improved noise immunity and higher bandwidth
• New lug-n-Play Network-wide Inclusion feature
• Improved self-healing nd fault tolerance with Explorer Frame feature
• Standardized method for Over the Air firmware updates (OTA)
• Improved product information capture for product certification database

And according to http://www.zwave.me/index.php?id=30 even more frames and paddles are (and will be) possible to use. I even see Merten frames and paddles mentioned here so I think I will be able to get the "design" look I have been trying to with my current switches that has black glass frames together with antracite paddles.
(Lots of brochures and info at http://www.merten.com/M-Plan-Echtglasrahmen.239.0.html)

Manual for the switch at http://manuals.zwaveeurope.com/make.php ... ME_WALLC-S

I think I will order one from my "local" Z-wave supplier http://www.m.nu. Price was reasonable and it will be interesting to see if (or when) my Merten frames and paddles will be able to use with the switch. (Actually Schneider Electric nowadays since they purchased Merten.)

(Maybe I should post this as a new topic instead with a different topic header?)