Zconnect 8ch Switch

[dgaust]

I recently purchased a ZConnect 8CH Switch Module. It is identified by Zwave-JS as a ConnectHome product but there is no device in the database

I grabbed the manual (https://zwave.com.au/wp-content/uploads/2021/10/ZWave_8ch_switch_manual.pdf) and have started to develop a json file for the configuration, but am running into a strange issue when setting the values.

As an example, there are 8 parameters (one for each channel), and there are five values that can be set depending on the that set the behaviour of the switch depending on the type of switch it is.

For example

PARAMETER # 8 - SWITCH # 8 SETTING
Select the type of command that will be sent to the 3th or 11th Association groups, depending on the state of the switch and
its type.
0 - Turn off by pressing / while holding dim down when a monostable switch is connected (Default);
1 - Turn on when pressing / hold down and dim up when a monostable switch is connected.
2 - Bistable button. It has two fixed positions: ON (contact closed) or OFF (contact open).
3 - Scene activation depending on the state of the switch when a monostable switch is connected (see table of scenes). When
this value is selected, it is necessary to add the controller to the 2nd group of links;
4 - Monostable push button switch. Each subsequent press of the button switches the device from 3th group to the opposite
state. Holding down the button will send an up / down dim command to the device from the 11th group.
5 - Bistable push button switch. With its help, you can switch from one possible state to another when changing the position of
the switch button.

However, if I set a value at either 4 or 5, it immediately gets set to 3. The below is an extract from the zwavejs2mqtt debug log.

{
      "time": "2022-06-15T05:45:11.279Z",
      "event": "value updated",
      "args": [
        {
          "commandClassName": "Configuration",
          "nodeId": 28,
          "commandClass": 112,
          "endpoint": 0,
          "property": 8,
          "newValue": 4,
          "prevValue": 2,
          "propertyName": "Switch 8 Setting"
        }
      ]
    },
    {
      "time": "2022-06-15T05:45:12.333Z",
      "event": "value updated",
      "args": [
        {
          "commandClassName": "Configuration",
          "commandClass": 112,
          "property": 8,
          "newValue": 3,
          "prevValue": 4,
          "propertyName": "Switch 8 Setting"
        }
      ]
    }

Would anyone have any suggestions about what I"m doing wrong
8channelswitch.txt
?

[AlCalzone]

I can't tell 100% without a driver log, but I'd guess that the device does not accept setting the value to 4 or 5. Are you sure you have the correct manual for your firmware version?

[dgaust]

Not 100% how to grab the driver log, but I set the logging to debug (in zwavejs2mqtt) and downloaded the log. The offender is node 28.
zwavejs2mqtt_2022-06-15.log

It's difficult to tell re: firmware as it seems to be a particularly niche product and not that well documented. I've emailed the Australian distributor, so if it's the firmware hopefully they have something. As 4 is the value I really need to use.

[AlCalzone]

That's not the correct log, but you were close:
https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/generating-logs?id=driver-logs

[dgaust]

Thanks for the pointer. Hopefully this is the right one (Still node 28)
zwavejs2mqtt_2022-06-15.log

I tried two different ways of setting the parameter, using the config option from the json file I made (which is quite possibly wrong)

And the basic configuration that appeared when there was no device json specified.

Looking at the logs, it looks like slightly different commands were issued.

2022-06-15 21:19:48.282 DEBUG SOCKET: Event ZWAVE_API emitted to QEf1wgnpNnjp8uHdAAAB
2022-06-15 21:19:48.287 INFO ZWAVE: Calling api writeValue with args: [
  { nodeId: 28, commandClass: 112, endpoint: 0, property: 8 },
  4,
  {},
  [length]: 3
]
2022-06-15 21:19:48.289 INFO ZWAVE: Writing 4 to 28-112-0-8
2022-06-15 21:19:54.175 INFO ZWAVE: Node 28: value updated: 112-0-8 3 => 4
2022-06-15 21:19:54.177 INFO ZWAVE: Success zwave api call writeValue true
2022-06-15 21:19:55.222 INFO ZWAVE: Node 28: value updated: 112-0-8 4 => 3
2022-06-15 21:19:56.063 DEBUG ZWAVE: Node 28: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'minBatteryLevel
2022-06-15 21:19:56.064 DEBUG ZWAVE: Node 28: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'batteryLevels
2022-06-15 21:19:56.065 INFO ZWAVE: Node 28: value updated: 128-0-level 80 => 80
2022-06-15 21:19:56.066 INFO ZWAVE: Node 28: value updated: 128-0-isLow false => false
2022-06-15 21:20:01.872 DEBUG SOCKET: Event ZWAVE_API emitted to QEf1wgnpNnjp8uHdAAAB
2022-06-15 21:20:01.877 INFO ZWAVE: Calling api sendCommand with args: [
  { nodeId: 28, commandClass: 112 },
  'set',
  [ 8, 4, 1, [length]: 3 ],
  [length]: 3
]
2022-06-15 21:20:05.897 INFO ZWAVE: Success zwave api call sendCommand undefined
2022-06-15 21:20:08.384 DEBUG ZWAVE: Node 28: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'minBatteryLevel
2022-06-15 21:20:08.384 DEBUG ZWAVE: Node 28: mapping value(s) of property 'level' (level) from CC 128 (Battery) to node property 'batteryLevels
2022-06-15 21:20:08.385 INFO ZWAVE: Node 28: value updated: 128-0-level 80 => 80
2022-06-15 21:20:08.387 INFO ZWAVE: Node 28: value updated: 128-0-isLow false => false

[AlCalzone]

Hopefully this is the right one

nope, I can tell by the filename:

[dgaust]

Yep, that was me skim reading again unfortunately and picking the wrong part of the UI.
zwavejs_2022-06-16.log

[dgaust]

So I have got feedback from the manufacturer that options 4 and 5 do not exist (as AlCalzone noted earlirer) and was mistranslation of the manual.

So using the scene option (3) to try and trigger a scene. To do that, I need to create a group with the right endpoint and the controller, which I have done

I'm getting a different error now when I trigger the scene, something about about the payload being invalid and the message dropped (could be user error).

2022-06-16T04:03:55.584Z DRIVER   Dropping message with invalid payload
2022-06-16T04:03:55.584Z DRIVER « [Node 028] [REQ] [ApplicationCommand]
                                  └─[SceneActivationCCSet] [INVALID]
2022-06-16T04:03:55.584Z SERIAL » [ACK]                                                                   (0x06)
2022-06-16T04:03:55.998Z SERIAL « 0x0110000400080a600d0101310504220260f4                              (18 bytes)
2022-06-16T04:03:56.000Z DRIVER   Dropping message because the driver is not ready to handle it yet.

zwavejs_2022-06-16 (2).log

[AlCalzone]

#4748 - this will go into next release probably.

[dgaust]

Thank you.

[AlCalzone]

It did. 9.4.1, zwavejs2mqtt should follow soon

[dgaust]

Thanks, I'll finish off the config file so I can contribute something back, and make a donation to the project. Much appreciated you making the effort.

[dgaust]

And just confirming this made it into the zwavejs2mqtt addon for Home Assistant, and the device is now working as intended.