ZWave issue with Aeotec/Aeon Labs Smart Dimmer 6

Nathan_Fettinger · November 27, 2018, 3:45am

Ubuntu 14.04 box (running OpenRemote 2.6.0 B3).

I am having an issue adding the Aeon Labs Smart Dimmer 6 to my environment. It appears i can send on off commands, but dim and status commands are not sent (command builder completes, but no TX)

Here is the associated device xml:

openremote/webapps/controller/zwave/node24.xml

<?xml version="1.0" encoding="UTF-8"?> AEON Labs BASIC_TYPE_ROUTING_SLAVE GENERIC_TYPE_SWITCH_MULTILEVEL SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL true true ELECTRIC_METER ELECTRIC_METER_SCALE_KWH ELECTRIC_METER_SCALE_W ELECTRIC_METER_SCALE_A ELECTRIC_METER_SCALE_V true COLOR_CHANNEL_RED COLOR_CHANNEL_GREEN COLOR_CHANNEL_BLUE GENERIC_TYPE_SWITCH_MULTILEVEL SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL UNKNOWN UNKNOWN GENERIC_TYPE_SWITCH_MULTILEVEL SPECIFIC_TYPE_POWER_SWITCH_MULTILEVEL COLOR_CHANNEL_RED COLOR_CHANNEL_GREEN COLOR_CHANNEL_BLUE

``

And here is the zwave.log output when I send an ‘on’ command. Everything seems to work fine.

DEBUG 2018-11-26 21:42:00,612 (Z-Wave): Command_Builder DEBUG 2018-11-26 21:42:00,613 (Z-Wave): Command_Builder DEBUG 2018-11-26 21:42:00,614 (Z-Wave): Command_Builder DEBUG 2018-11-26 21:42:00,614 (Z-Wave): Command_Builder DEBUG 2018-11-26 21:42:00,614 (Z-Wave): Command_Builder DEBUG 2018-11-26 21:42:00,615 (Z-Wave): CCMultiLevelSwitch DEBUG 2018-11-26 21:42:00,618 (Z-Wave): Controller_API DEBUG 2018-11-26 21:42:00,618 (Z-Wave): Controller_API DEBUG 2018-11-26 21:42:00,619 (Z-Wave): TX_Session_Layer DEBUG 2018-11-26 21:42:00,622 (Z-Wave): TX_Session_Layer DEBUG 2018-11-26 21:42:00,625 (Z-Wave): TX_Frame_Layer DEBUG 2018-11-26 21:42:00,645 (Z-Wave): RX_Serial_Port_RXTX DEBUG 2018-11-26 21:42:00,648 (Z-Wave): RX_Frame_Layer DEBUG 2018-11-26 21:42:00,649 (Z-Wave): RX_Serial_Port_RXTX DEBUG 2018-11-26 21:42:00,649 (Z-Wave): RX_Session_Layer DEBUG 2018-11-26 21:42:00,651 (Z-Wave): RX_Serial_Port_RXTX DEBUG 2018-11-26 21:42:00,652 (Z-Wave): RX_Frame_Layer DEBUG 2018-11-26 21:42:00,654 (Z-Wave): RX_Session_Layer DEBUG 2018-11-26 21:42:00,655 (Z-Wave): RX_Session_Layer DEBUG 2018-11-26 21:42:00,689 (Z-Wave): RX_Serial_Port_RXTX DEBUG 2018-11-26 21:42:00,691 (Z-Wave): RX_Serial_Port_RXTX DEBUG 2018-11-26 21:42:00,693 (Z-Wave): RX_Frame_Layer DEBUG 2018-11-26 21:42:00,695 (Z-Wave): RX_Session_Layer DEBUG 2018-11-26 21:42:00,697 (Z-Wave): CCMultiLevelSwitch : Building Z-Wave command
: Z-Wave command: nodeId = ‘24’, endPoint = ‘1’
: Z-Wave command: command = ON
: Z-Wave command: paramValue = null
: Z-Wave command created successfully
: Node ‘24:1’ : [COMMAND_CLASS_SWITCH_MULTILEVEL::SWITCH_MULTILEVEL_SET, Value=‘255’]
: Enqueue (queue count=1) Z-Wave function call ‘org.openremote.protocol.zwave.model.commandclasses.CCMultiChannelV2FuncDecorator@1c531b4’.
: Dequeue (queue count=0) Z-Wave function call ‘org.openremote.protocol.zwave.model.commandclasses.CCMultiChannelV2FuncDecorator@1c531b4’.
: Executing Z-Wave function call ‘org.openremote.protocol.zwave.model.commandclasses.CCMultiChannelV2FuncDecorator@1c531b4’…
: Send (repeat count=1) Z-Wave function ‘ZW_SendData(NodeID=24, Payload=[0x26, 0x01, 0xFF], TxOptions=[TRANSMIT_OPTION_AUTO_ROUTE, TRANSMIT_EXPLORE_OPTION_ACK], CallbackID=0x02)’ request (callback ID=0x02).
: Send data frame [0x01, 0x0E, 0x00, 0x13, 0x18, 0x07, 0x60, 0x0D, 0x00, 0x01, 0x26, 0x01, 0xFF, 0x05, 0x02, 0x4E].
: Data bytes read : [0x06]
: ACK -> Data frame [0x01, 0x0E, 0x00, 0x13, 0x18, 0x07, 0x60, 0x0D, 0x00, 0x01, 0x26, 0x01, 0xFF, 0x05, 0x02, 0x4E] transmission OK.
: Data bytes read : [0x01]
: ACK -> Z-Wave function ‘ZW_SendData(NodeID=24, Payload=[0x26, 0x01, 0xFF], TxOptions=[TRANSMIT_OPTION_AUTO_ROUTE, TRANSMIT_EXPLORE_OPTION_ACK], CallbackID=0x02)’ has been successfully sent - waiting 5,000 [ms] for response frame.
: Data bytes read : [0x04, 0x01, 0x13, 0x01, 0xE8]
: Data frame [0x01, 0x04, 0x01, 0x13, 0x01, 0xE8] has been received.
: ‘ZW_SendData’ response [0x01, 0x04, 0x01, 0x13, 0x01, 0xE8] with status ‘RETURN_VALUE_TRUE’ received (callback ID=0x02).
: Waiting 64,966 [ms] for ‘ZW_SendData’ callback frame (callback ID=0x02).
: Data bytes read : [0x01]
: Data bytes read : [0x05, 0x00, 0x13, 0x02, 0x00, 0xEB]
: Data frame [0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xEB] has been received.
: Callback [0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xEB] (callback ID=0x02) with state ‘TRANSMIT_COMPLETE_OK’ received -> Z-Wave function ‘ZW_SendData(NodeID=24, Payload=[0x26, 0x01, 0xFF], TxOptions=[TRANSMIT_OPTION_AUTO_ROUTE, TRANSMIT_EXPLORE_OPTION_ACK], CallbackID=0x02)’ successfully executed.
: Node ‘24:1’ : [COMMAND_CLASS_SWITCH_MULTILEVEL::SWITCH_MULTILEVEL_SET, Value=‘255’] succeeded

``

Unfortunately, this is all I get when I send the ‘dim’ command (command does not appear to be case sensitive, tried both)

DEBUG 2018-11-26 21:43:41,534 (Z-Wave): Command_Builder : Building Z-Wave command
DEBUG 2018-11-26 21:43:41,535 (Z-Wave): Command_Builder : Z-Wave command: nodeId = ‘24’, endPoint = ‘1’
DEBUG 2018-11-26 21:43:41,535 (Z-Wave): Command_Builder : Z-Wave command: command = DIM
DEBUG 2018-11-26 21:43:41,535 (Z-Wave): Command_Builder : Z-Wave command: paramValue = 30
DEBUG 2018-11-26 21:43:41,535 (Z-Wave): Command_Builder : Z-Wave command created successfully

``

Nathan

Nathan_Fettinger · December 21, 2018, 2:29am

BUMP. Been several weeks with no help

rainerhitz · January 7, 2019, 11:20am

For general instructions on how to configure Z-Wave devices see Manual Configuration Procedure.

1.) Stop the controller
2.) Edit the section in the nodeX.xml file so that it looks like the following:

<associations>
  <association-group id="1" capacity="5">
    <association>
      <node>1</node>
    </association>
  </association-group>
  <association-group id="2" capacity="5" />
</associations>
<parameters>
  <parameter>
    <number>80</number>
    <value>2</value>
    <size>1</size>
  </parameter>
</parameters>

``

3.) Start the controller

I’m a bit confused why the DIM command doesn’t work. You could try to configure the DIM command so that it addresses the first endpoint of the device explicitly (see ‘Sub-Device Addressing’ section in Designer Z-Wave Commands

If the node ID of your device is 24 the commands should look like the following:

Z-Wave nodeID: 24:1
Command: DIM

Z-Wave nodeID: 24:1

Command: STATUS

``

The STATUS command doesn’t work because the so called lifeline association from the device to the controller hasn’t been configured (the device doesn’t know where to send the status update). In order to configure this association you have to edit the nodeX.xml file in the directory /webapps/controller/zwave (see also Association Configuration)… In addition I’ve found in the following document that parameter 80 has to be configured: Manual Aeotec Smart Dimmer 6.