Author Topic: HOWTO: Using Merten configuration software in conjunction with LinuxMCE  (Read 781 times)

Domodude

  • Guest
Hi all,

I just configured LMCE z-wave lighting together with the Merten "RF-configurator" software and the Merten USB stick. I'll describe it and after I'm sure there are no inconsistencies etc I will wikify it.



WHEN do you need it?
The Merten software is very useful to program their own proprietary hardware functions, such as ramp times when turning off dimmers, but also their color and greyscale in-wall control panels. You do not need to do this if you have a few merten RF switches or dimmers, and do not want to use their advanced controls.

WHAT do you need?
First, a LinuxMCE supported zwave USB interface. See elsewhere on forum and wiki which ones are good. Merten switches, dimmers, and/or pushbuttons (at least one of these!!). You will also need the Merten software, which requires the Merten USB z-wave stick. This stick is not supported by linuxmce as of yet, due to the fact that Merten is less than forthcoming with information about their USB to RS232 chip. That info, I understand, is essential to get the zwave driver to talk to the Merten stick.

HOW do you do it?
Took me a while to figure it out, but it is simple, really  ;D. First configure everything to your liking, using the Merten software and USB stick. As always, you will have to transfer control to a pushbutton when you are done. Then, insert the LMCE compatible stick into your core, and you probably need to reload dcerouter at that point. Go to the web config, then to interfaces, then select 'advanced' at the zwave interface. Select 'send command to device'. Select 'download configuration', and once you get confirmation that the command was sent properly, triple-click the Merten pushbutton that has master control. This pushbutton will need to be close to the core. It will then transfer the configuration to the LMCE compatible stick.

Note that you will need two zwave USB sticks, and at least one battery-operated Merten pushbutton. Please let me know if anything is unclear.

Domodude

  • Guest
Just came home today, to find that things are not working anymore  :'(. I do not think it has to do with the way I set up zwave. What does it mean that ZW_SEND could not be delivered to z-wave stack?

Code: [Select]
36 04/21/09 21:54:39.319 OFF RECEIVED FOR CHILD 23 <0xb6929b90>
40 04/21/09 21:54:39.322 Sending job 0x80f0428 (cb 37) - 0x1 0xa 0x0 0x13 0x17 0x3 0x20 0x1 0x0 0x5 0x25 0xf3 (#\n#### ###%#) <0xb792bb90>
41 04/21/09 21:54:39.326 ACK RECEIVED <0xb792bb90>
41 04/21/09 21:54:39.326 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb792bb90>
36 04/21/09 21:54:39.326 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792bb90>
10 04/21/09 21:54:39.358 Receive string: MESSAGE 67             <0xb6929b90>
10 04/21/09 21:54:39.358 Received MESSAGE 67             0x807a790 device: 220 <0xb6929b90>
10 04/21/09 21:54:39.358 Received Message type 1 ID 193 from 94 to 233 (device: 220) resp 0 <0xb6929b90>
36 04/21/09 21:54:39.358 Received command for child <0xb6929b90>
36 04/21/09 21:54:39.358 OFF RECEIVED FOR CHILD 24 <0xb6929b90>
36 04/21/09 21:54:42.426 No callback received: await_callback: 37 timer: 31 <0xb792bb90>
40 04/21/09 21:54:42.526 Sending job 0x80f0428 (cb 37) - 0x1 0xa 0x0 0x13 0x17 0x3 0x20 0x1 0x0 0x5 0x25 0xf3 (#\n#### ###%#) <0xb792bb90>
41 04/21/09 21:54:42.530 ACK RECEIVED <0xb792bb90>
41 04/21/09 21:54:42.530 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb792bb90>
36 04/21/09 21:54:42.530 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792bb90>
36 04/21/09 21:54:45.666 No callback received: await_callback: 37 timer: 31 <0xb792bb90>
40 04/21/09 21:54:45.766 Sending job 0x80f0428 (cb 37) - 0x1 0xa 0x0 0x13 0x17 0x3 0x20 0x1 0x0 0x5 0x25 0xf3 (#\n#### ###%#) <0xb792bb90>
41 04/21/09 21:54:45.770 ACK RECEIVED <0xb792bb90>
41 04/21/09 21:54:45.770 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb792bb90>
36 04/21/09 21:54:45.770 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792bb90>
36 04/21/09 21:54:48.870 No callback received: await_callback: 37 timer: 31 <0xb792bb90>
36 04/21/09 21:54:48.870 ERROR: Dropping command, no callback received after three resends <0xb792bb90>
40 04/21/09 21:54:48.970 Sending job 0x80f0648 (cb 38) - 0x1 0xa 0x0 0x13 0x18 0x3 0x20 0x1 0x0 0x5 0x26 0xff (#\n#### ###&#) <0xb792bb90>
41 04/21/09 21:54:48.974 ACK RECEIVED <0xb792bb90>
41 04/21/09 21:54:48.974 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb792bb90>
36 04/21/09 21:54:48.974 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792bb90>
36 04/21/09 21:54:52.106 No callback received: await_callback: 38 timer: 31 <0xb792bb90>
40 04/21/09 21:54:52.206 Sending job 0x80f0648 (cb 38) - 0x1 0xa 0x0 0x13 0x18 0x3 0x20 0x1 0x0 0x5 0x26 0xff (#\n#### ###&#) <0xb792bb90>
41 04/21/09 21:54:52.210 ACK RECEIVED <0xb792bb90>
41 04/21/09 21:54:52.210 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb792bb90>
36 04/21/09 21:54:52.210 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792bb90>
36 04/21/09 21:54:55.310 No callback received: await_callback: 38 timer: 31 <0xb792bb90>
40 04/21/09 21:54:55.410 Sending job 0x80f0648 (cb 38) - 0x1 0xa 0x0 0x13 0x18 0x3 0x20 0x1 0x0 0x5 0x26 0xff (#\n#### ###&#) <0xb792bb90>
41 04/21/09 21:54:55.414 ACK RECEIVED <0xb792bb90>
41 04/21/09 21:54:55.414 0x1 0x4 0x1 0x13 0x0 0xe9 (######) <0xb792bb90>
36 04/21/09 21:54:55.414 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0xb792bb90>
36 04/21/09 21:54:58.550 No callback received: await_callback: 38 timer: 31 <0xb792bb90>
36 04/21/09 21:54:58.550 ERROR: Dropping command, no callback received after three resends <0xb792bb90>