Inovelli VZW31-SN Will Not Complete Interview and One Parameter Throws Error When Changing

[JasonJoel]

I have an Inovelli VSW31-SN paired via Z-Wave Long Range - S2 security.

Issue 1: The interview never completed for the Configuration or Indicator classes.

Issue 2: When trying to manually set one specific parameter in configuration Z-Way throws an error like:

Code: Select all

Error: Invalid argument /ZWave.zway/Run/devices[5].instances[0].commandClasses[112].Set(21,1,0)

Parameter information:
21 AC Power Type Select whether you are wiring your switch with or without a neutral wire
0 = No-Neutral
1 = Neutral
Range: 0-1
Default: 1
Size: 1

Edit: Looking at the config command class info for the device, I see it is marked as "readonly: true" for some reason - which is incorrect. Any way to manually change that?

Code: Select all

  21: None (08:33 AM)
        val: None (08:33 AM)
        size: 1 (08:33 AM)
        format: unsigned (08:33 AM)
        min: 0 (08:33 AM)
        max: 1 (08:33 AM)
        default: 1 (08:33 AM)
        title: (08:33 AM)
        description: (08:33 AM)
        readonly: true (08:33 AM)
        reinclusionRequired: false (08:33 AM)
        advanced: false (08:33 AM)

[JasonJoel]

Here's a clean log file with a force pairing attempt.

[seattleneil]

To update the readonly value for device 5 parameter 21, use the following command:

Code: Select all

curl -u admin:[PASSWORD} --globoff 'http://127.0.0.1:8083/ZWave.zway/Run/devices[5].instances[0].commandClasses[112].data[21].readonly.value=false'

Replace [PASSWORD] with your admin password.

To retrieve the readonly value for device 5 parameter 21, use the following command:

Code: Select all

curl -u admin:[PASSWORD} --globoff 'http://127.0.0.1:8083/ZWave.zway/Run/devices[5].instances[0].commandClasses[112].data[21].readonly'

[JasonJoel]

Here's a clean log file with a force pairing attempt.

I can confirm that the interview still does not complete in 4.1.2.

[lanbrown]

Have you tried with long range?

[JasonJoel]

Have you tried with long range?

Yes. Actually I've ONLY tried pairing it LR... Maybe if I get time I'll re-pair it non-LR and see if I get a different experience.

[lanbrown]

LR is new, so there could be teething issues. There is also two beta releases from Inovelli for that model. So the 700/800 series is relatively new and the LR is only available in the North America.

The firmware that Inovelli uses actually comes from the manufacturer of the switch. Inovelli has the design and the functionality that they would like. The manufacturer in China produces the firmware. That is what I have gathered from past experience. So how much testing for LR is done could be an issue since there are several different controllers and then even more so of software choices that run the controller.

It does seem that Z-Way is more picky but also because I believe that they are following the standard a lot more closely than the others.

I do have some of those same switches that I have yet to install. I got about 50 of them in the first batch. I was waiting until the first non-beta release to become available. Then use my test system to pair, upgrade and then unpair the switches to then be installed in their permanent home.

[PoltoS]

Hello!

I've checked the log from JasonJoel and I see that the device does not reply to some CCs:

Association CC:

Code: Select all

[2023-09-23 18:44:08.790] [W] [zway]  Reply not received before timeout for job (Association Get to node 256)

Here I might understand, the device reports the size of the group = 0, but still it have to answer according to the standard.

Configuration CC:

Code: Select all

[2023-09-23 18:44:11.909] [W] [zway]  Reply not received before timeout for job (Configuration Get to node 256)
[2023-09-23 18:44:14.305] [W] [zway]  Reply not received before timeout for job (Configuration Get to node 256)
...

Funny (or not at all), the device is answering to the wrong Configuration Parameter:

Code: Select all

[2023-09-23 18:44:12.151] [D] [zway]  Secure payload: ( 70 05 03 ) -- we ask the param #3
[2023-09-23 18:44:12.185] [I] [zway]  Node 256:0 CC SecurityS2: passing S2 Authenticated decrypted packet to application level: [ 70 06 01 01 e0 00 00 00 ] -- we get back the param #1 instead
[2023-09-23 18:44:14.305] [W] [zway]  Reply not received before timeout for job (Configuration Get to node 256)

So, here Z-Way is just perfect as it shows you that the device has bugs - right after the inclusion you see it. And if it works well in Z-WaveJS is just because the latter is not as good as Z-Way yet

Of course, the device is working perfectly (except for those CCs) so you can use it, but if you don't like the unfinished interview, you can do:

Code: Select all

curl -u admin:[PASSWORD} --globoff 'http://127.0.0.1:8083/ZWave.zway/Run/devices[256].Configuration.data.interviewDone=true'

and same for the Association CC.

Z-Way is flexible enough to fix it

[lanbrown]

1.02 is the latest firmware from Inovelli.
https://github.com/InovelliUSA/Firmware ... 2-1-Switch

You should probably open a bug case with Inovelli so they can work on a fix in their firmware.

[JasonJoel]

1.02 is the latest firmware from Inovelli.
https://github.com/InovelliUSA/Firmware ... 2-1-Switch

You should probably open a bug case with Inovelli so they can work on a fix in their firmware.

Agreed.

There definitely seems to be a device specific issue when paired in LR mode, as I've seen various problems on 3 different Z-Wave LR platforms at this point.

At least it works fine in mesh mode.