ACT HomePro ZDM230 dimmer - And the (im)possibility to add the dimmer to OpenHAB1

Hi,

i’m trying to add my old devices to OpenHAB, however i’m running into some issues. I’ve got an old dimmer which i purchased over 10 years ago, and it seems to be partly compliant to the ZWAVE standard. I’m using the 1.9 zwave binding of today.

I’ve tried to add the dimmer to the Zwave database, it’s entry is: http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/362

There’s no XML created, so i’ve created the entry by hand, by scanning the web and using Habmin, openzwave control panel, and the sensys tool. It’s not finished yet, but i think i’m getting there.

However, it’s always dead in Habmin. Also in open-zwave-control-panel. After a lot of patience it does report it’s model and type, and that makes me think i might be able to get it to work.

When i look at the log via Chris’ zwave log viewer, it seems that the device is very slow, and the zwave binding is not waiting long enough for a response?

The switch does reply to commands from OpenHAB, and do see see response in the logfile when a button is pressed.
A part of the log file, parsed by the zwave log viewer is below. I’ve attached the full log file to this message: Log file

19:12:30.000 12
Stage advanced to PROTOINFO
19:12:30.000 12
TX REQ IdentifyNode
19:12:30.000 12
RX RES IdentifyNode ROUTING_SLAVE POWER_SWITCH_MULTILEVEL LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:12:30.000 12
Stage advanced to NEIGHBORS
19:12:30.000 12
TX REQ GetRoutingInfo
19:12:30.000 12
RX RES GetRoutingInfo Found 0 neighbours
19:12:30.000 12
Stage advanced to FAILED_CHECK
19:12:30.000 12
TX REQ IsFailedNodeID Check if NODE 12 is failed
19:12:30.000 12
RX RES IsFailedNodeID NODE 12 is marked as FAILED by controller.
19:12:30.000 12
Stage advanced to WAIT
19:12:30.000 12
Stage advanced to PING
19:12:30.000 12
TX REQ SendData 154 NO_OPERATION ACK AUTO_ROUTE EXPLORE
19:12:30.000 12
RX RES SendData 154 ACCEPTED BY CONTROLLER
19:12:30.000 12
RX REQ SendData 154 NO ACK after 0ms
19:12:35.000 12
TX REQ SendData 155 NO_OPERATION ACK AUTO_ROUTE EXPLORE
19:12:35.000 12
RX RES SendData 155 ACCEPTED BY CONTROLLER
19:12:36.000 12
RX REQ SendData 155 NO ACK after 1000ms
19:12:45.000 12
TX REQ SendData 157 NO_OPERATION ACK AUTO_ROUTE EXPLORE
19:12:45.000 12
RX RES SendData 157 ACCEPTED BY CONTROLLER
19:12:46.000 12
RX REQ SendData 157 NO ACK after 1000ms
19:13:05.000 12
TX REQ SendData 158 NO_OPERATION ACK AUTO_ROUTE EXPLORE
19:13:06.000 12
RX RES SendData 158 ACCEPTED BY CONTROLLER
19:13:07.000 12
RX REQ SendData 158 NO ACK after 2000ms
19:13:10.000 12
Heal stage advanced to STARTING
19:13:10.000 12
Heal stage advanced to PING
19:13:10.000 12
TX REQ SendData 159 NO_OPERATION ACK AUTO_ROUTE EXPLORE
19:13:11.000 12
RX RES SendData 159 ACCEPTED BY CONTROLLER
19:13:11.000 12
RX REQ SendData 159 NO ACK after 1000ms
19:13:11.000 12
Heal stage advanced to SETSUCROUTE
19:13:12.000 12
Heal stage advanced to SETSUCROUTE
19:13:12.000 12
Heal stage advanced to SETSUCROUTE
19:13:13.000 12
Heal stage advanced to SETSUCROUTE
19:13:45.000 12
TX REQ SendData 164 NO_OPERATION ACK AUTO_ROUTE EXPLORE
19:13:46.000 12
RX RES SendData 164 ACCEPTED BY CONTROLLER
19:13:46.000 12
RX REQ SendData 164 NO ACK after 1000ms

Can anyone help me to decide if i need to bin this device (which is hard because i can send commands to it), or that this one is fixable?