Setting Zwave Configuration values on Shelly Wave i4 DC (US)

[jim_]

I’m posting to ask a question about setting Zwave config.  I really don’t know much about Zwave deployments or integrations, but I’m not able to set mode 2 on this switch, can anyone suggest if I’m setting the options correctly ? 

As per the manufacture’s bible    https://kb.shelly.cloud/knowledge-base/wave-i4-dc-us

Z-Wave Parameters
Parameter No. 1 - SW (SW1) Switch type
This parameter defines how the Device should treat the switch (which type) connected to the SW (SW1) terminal.

Value size: 1 Byte

Default value: 0
Values & descriptions:
0 - momentary switch (push button),
1 - toggle switch (contact closed - ON / contact opened - OFF),
2 - toggle switch (Device changes status when switch changes status)

 

Testing 
First, I asked Shelly support for a more detailed explanation of modes 1 & 2 as the documentation was vague, this was their reply.                  NOTE: When I requested support for “Mode 2” not working … Shelly support responded, unless the modules are deployed using a certified Zwave controller, they cannot guarantee correct operation.

1.    Parameter set to value 1 (contact closed ON / contact closed OFF):
In this setting, the switch behaves like a traditional switch controlling a normal bulb. The position of the switch determines the state of the output. For example, when the switch is pressed down, the light is ON (power is ON), and when the switch is pressed up, the light is OFF, regardless of any changes made to the output via the gateway or commands.
2.    Parameter set to value 2 (toggle mode):
In this setting, the position of the switch no longer matters. Each time you change the position of the switch, it toggles the state of the output (e.g., ON to OFF or OFF to ON). This happens even if you use the gateway or commands to change the state of the output in between. The switch simply flips the output state whenever it is toggled

Set Mode 0 on switch port 1

Event viewer  == Mon 01/27/2025 15:16:09 : U7 Rest:  submitCmd([ZY024_1],[CONFIG],[NUM.107=1&VAL.111=0])

You’ll see FDUP & FDSTOP value toggle for Scene Button 1 matching event viewer

Mon 01/27/2025 15:17:23 : [ZY024_201N001   ]       ST   2 (uom=115 prec=0)
Mon 01/27/2025 15:17:23 : [ZY024_201N001   ]     FDUP   2 (uom=115 prec=0) <<< button closed
Mon 01/27/2025 15:17:24 : [ZY024_201N001   ]       ST   4 (uom=115 prec=0)
Mon 01/27/2025 15:17:24 : [ZY024_201N001   ]   FDSTOP   4 (uom=115 prec=0)  <<< button open

Set Mode 1 on switch port 1

Event Viewer == Mon 01/27/2025 15:25:38 : U7 Rest:  submitCmd([ZY024_1],[CONFIG],[NUM.107=1&VAL.111=1])

Mon 01/27/2025 15:25:50 : [ZWAVE-CTL-EVENT ] Basic Set from 24.0 unmapped (ignored)
Mon 01/27/2025 15:25:51 : [ZY024_002_1     ]       ST 100 (uom=78 prec=0)    <<< button closed
Mon 01/27/2025 15:25:51 : [ZWAVE-CTL-EVENT ] Basic Set from 24.0 unmapped (ignored)
Mon 01/27/2025 15:25:51 : [ZY024_002_1     ]       ST   0 (uom=78 prec=0)       <<< button open

===================================================================================

Mon 01/27/2025 16:06:23 : U7 Rest:  submitCmd([ZY024_1],[CONFIG],[NUM.107=1&VAL.111=2])
In Mode 2, functions appear identical to mode 1 in event viewer, so what am I missing in the Zwave world to set this to Mode 2 ?

=====================================================================================

p.s. I have one of these units deployed for the past month and appear to be very stable tying them into a DSC panel, hardwired door contacts and multiple standalone motion detectors. If anyone want more detail, please feel free to ping me 

 

[RRalston]

Hello Jim

I have several ZooZ Z-Wave devices. I am no expert on this but I do have some experience to share which may help.

First, the device must be awake to receive configuration commands. I looked at your device and since it is apparently continuously powered by DC, it theoretically should always be awake to accept the commands. So I do not think that is your issue.

Second, I have had much better success setting configuration parameters in the following ways:

1) via a program

2) using the Zwave | Set Configuration Menu item for a specific device which provides a dialog like this. Notice you can query the parameter here as well.

Accessed here:

Hope this helps you.

-Rob

Edited January 28 by RRalston

[jim_]

Thanks Rob ... I was hoping someone would twig if I was missing a step ... 

I've using both ways of configuration (both on the pop-up menu and on the root entry page of the console) and while setting mode 0 or 1 work, mode 2 just doesn't take. I understand that Shelly is offering these devices with the expectation they will be deployed into a normalized Zwave enviroment and typically interlink with "other" Shelly modules ... it is what it is

So far all of my installs work in Mode 1, just wanted to have mode 2 available ... I'll keep poking it 

 

[RRalston]

Jim,

After you set the parameter value to 2, then query the parameter, are you saying the retrieved value is not "2"?

Also, try using the XRay menu item and access the "DH Command Classes" for more info you might use when communicating with the vendor. For example, the configuration section should list all of the parameters and current values that can be set. You can also find current firmware data there in case you need to update that.

Edited January 31 by RRalston

[jim_]

Trying not to go down a deep hole here, but a NEW i4 out of the box, same issue

After inclusion to EISY, value shows the default "0" value for switch 1 using the Zwave Config Param pop-up

In event viewer, one see's this using a spring push button, hold count for 1-onethousand, release X2

Sun 02/02/2025 16:08:11 : [D2D EVENT       ] Event [ZY025_201N001] [ST] [2] uom=115 prec=0
Sun 02/02/2025 16:08:11 : [ZY025_201N001   ]       ST   2 (uom=115 prec=0)
Sun 02/02/2025 16:08:11 : [D2D EVENT       ] Event [ZY025_201N001] [FDUP] [2] uom=115 prec=0
Sun 02/02/2025 16:08:11 : [ZY025_201N001   ]     FDUP   2 (uom=115 prec=0)
Sun 02/02/2025 16:08:12 : [D2D EVENT       ] Event [ZY025_201N001] [ST] [4] uom=115 prec=0
Sun 02/02/2025 16:08:12 : [ZY025_201N001   ]       ST   4 (uom=115 prec=0)
Sun 02/02/2025 16:08:12 : [D2D EVENT       ] Event [ZY025_201N001] [FDSTOP] [4] uom=115 prec=0
Sun 02/02/2025 16:08:12 : [ZY025_201N001   ]   FDSTOP   4 (uom=115 prec=0)
 

Changing values are pretty clear in event viewer 

Sun 02/02/2025 16:13:31 : Create REST U7 [/rest/nodes/ZY025_1/cmd/CONFIG?NUM.107=1&VAL.111=1]
Sun 02/02/2025 16:13:31 : U7 Rest:  submitCmd([ZY025_1],[CONFIG],[NUM.107=1&VAL.111=1])
Sun 02/02/2025 16:13:31 : [ZW-TX-A 00296  25.0  ] [ZY025_1] Config Set parameter=1 value=1 (x1) size=1
Sun 02/02/2025 16:13:31 : [ZW-DONE 00296  25.0  ] [ZY025_1] Config Set parameter=1 value=1 (x1) size=1
Sun 02/02/2025 16:13:39 : Create REST U7 [/rest/nodes/ZY025_1/cmd/CONFIG?NUM.107=1&VAL.111=2]
Sun 02/02/2025 16:13:39 : U7 Rest:  submitCmd([ZY025_1],[CONFIG],[NUM.107=1&VAL.111=2])
Sun 02/02/2025 16:13:39 : [ZW-TX-A 00297  25.0  ] [ZY025_1] Config Set parameter=1 value=2 (x2) size=1
Sun 02/02/2025 16:13:39 : [ZW-DONE 00297  25.0  ] [ZY025_1] Config Set parameter=1 value=2 (x2) size=1

 

Testing the spring loaded switch in mode 2, same 1-onethousand count push / release  ... same ON / OFF as mode 1

NOTE how the functional output jumps from Scene Button 1 >>> to >>> Binary Switch in Mode 1 or 2 

Sun 02/02/2025 16:16:05 : [ZWAVE-CTL-EVENT ] Basic Set from 25.0 unmapped (ignored)
Sun 02/02/2025 16:16:06 : [D2D EVENT       ] Event [ZY025_002_1] [ST] [100] uom=78 prec=0
Sun 02/02/2025 16:16:06 : [ZY025_002_1     ]       ST 100 (uom=78 prec=0)3e
Sun 02/02/2025 16:16:07 : [ZWAVE-CTL-EVENT ] Basic Set from 25.0 unmapped (ignored)
Sun 02/02/2025 16:16:07 : [D2D EVENT       ] Event [ZY025_002_1] [ST] [0] uom=78 prec=0
Sun 02/02/2025 16:16:07 : [ZY025_002_1     ]       ST   0 (uom=78 prec=0)
 

 

AND ... in XRAY, Config confirms mode for switch 1 does change when this value is observed 

Switch 1 > Integer  DATA devices.25.instances.0.commandClasses.112.data.1.val = 2 (0x00000002)  verses 

Switch 2 > Integer  DATA devices.25.instances.0.commandClasses.112.data.2.val = 0 (0x00000000) etc

In the end, It is what it is ... 

 

[jim_]

JUST FYI

To close this post ...  a good solution to detect simple switch closures.  The Wave i4's a very inexpensive compared to other ZW switch detectors on the market   

After many emails with Shelly support, the conclusion is as follows:

The i4 have two purposes 

1. The main one is to be used with a button (spring loaded switch) in order to trigger the scenes (or other automation) with the Command Class Central Scene which is usually used in the Z-Wave remote controllers. 
2. The second is to be used by a toggle switch (normal On Off switch) this feature was added on users request. The main purpose of that is to report the state of an attached sensor (switch no button) so On or Off.

There is a toggle function, but requires a value 0 (zero) mode and the switch speed is ~500 milliseconds as shows in these traces. As documented, value 2 (toggle) is specific to " Command Class Central Scene "  using specific switch(s) and ZW controller 

 

Normal 1 second button (on / off) :  where messaging follows button closure

Thu 02/20/2025 13:55:52 : [ZY025_201N001   ]     FDUP   2 (uom=115 prec=0)  <<<<<<<<<<<< button closed = FDUP
Thu 02/20/2025 13:55:53 : [ZY025_201N001   ]   FDSTOP   4 (uom=115 prec=0)  <<<<<<<<<<< button open = FDSTOP

Fast ~500ms button cycle (on / off) :  where button cycle changes the messaging state 
Thu 02/20/2025 13:57:04 : [ZY025_002_1     ]       ST   0 (uom=78 prec=0)   <<<<<<<< Transition from previous state to OFF (ST 0)

Next Button Cycle
Thu 02/20/2025 13:57:07 : [ZY025_002_1     ]       ST 100 (uom=78 prec=0)  <<<<< Transition from previous state to ON (ST 100)

 

Also worth mentioning, in value 1 mode, the EISY controller can set the initial state to either ON or OFF for each switch 1-4, so  function can be set to follow on / off  or  off / on  which is a big PLUS when integrating with 3rd party equipment. e.g. if your connected to a generic motion detector where the relay operates normally closed, trigger to an open.

I have 2 x i4's deployed, 4 standalone motion detectors, 2 connected to door switches (parallel) DSC alarm and NVR alarm out ... all controlling lights