Updates to match 2.14 firmware (previous 2.08)

[michaelkkehoe]

2.10

• Add parameters P54(Double down to value of P56)
• Add parameter option 3 to P22(Switch Type) - Single-Pole Full Sine Wave

2.12

• Add parameters P55(Double Up to level)
• Add parameters P56(Double Down to level)

2.14

• Add P25 (Increase non-neutral power output. This may cause flickering or aux switch problems with some bulbs. Adjust max level to fix this)
• Modify P56 range 0 to 254 (allow double tap to turn device off)
• Add P100(LED Scaling ) 0- VZM31 ; 1- LZW31
• Add P123(Use different scene numbers via the aux switch)
• Add P125(Send “move to level on/off” to bound devices that matches default level remote and local)

[epower53]

Apparently the 0-100 ranges @EricM_Inovelli provided for parameters 55 & 56 were a result of him lifting the parameter definitions directly from the Hubitat driver, which uses percentages rather than a 2-byte number converted to decimal. Since the z2m converter does not convert to percentages, the 0-100 range for parameters 55 and 56 is not correct. Please adjust the max value for parameters 55 and 56 to be 254. Forum user mamber tested all the way to 255, and found that the switch only responds if the values for these parameters is in the range 0-254. See this forum post: https://community.inovelli.com/t/blue-series-2-1-firmware-changelog-vzm31-sn/12326/425

[edwardgarza]

Yup, I think 255 gets remapped to 254 in a few places?

zigbee-herdsman-converters/devices/inovelli.js

Line 935 in 1abb64d

(isNaN(brightness) || brightness < 0 || brightness > 255)

zigbee-herdsman-converters/devices/inovelli.js

Line 1061 in 1abb64d

brightness = Math.min(254, brightness);

zigbee-herdsman-converters/devices/inovelli.js

Line 980 in 1abb64d

const fallbackLevel = utils.getObjectProperty(

[michaelkkehoe]

@epower53 @InovelliUSA @edwardgarza Could you confirm if you actually see the new attributes in the 'Dev Console'? When I install the converter, it isn't able to pull these values.

[epower53]

@epower53 @InovelliUSA @edwardgarza Could you confirm if you actually see the new attributes in the 'Dev Console'? When I install the converter, it isn't able to pull these values.

I don't see these in the Dev Console, either. I think that the manuSpecificInovelliVZM31SN cluster definition must also need an update. I had assumed/hoped that adding new parameters to the converter would do it, but it seems there's another file that needs additions. @InovelliUSA @edwardgarza can you confirm this is correct, and if so point us in the direction we need to go?

[epower53]

@nathanfiscus confirms- we need to update the cluster definition. I don't have a good pull request capability... @michaelkkehoe would you mind submitting the PR for this? We need to add the new parameter definitions to zigbee-herdsman/src/zcl/definition/cluster.ts. The definition for manuSpecificInovelliVZM31SN starts on line 4926.

[michaelkkehoe]

@epower53 Yeah I'll start on it.
@InovelliUSA could you please confirm the data-types.

[michaelkkehoe]

Koenkk/zigbee-herdsman#695

[InovelliUSA]

@epower53 Yeah I'll start on it. @InovelliUSA could you please confirm the data-types.

Datatypes look good.

[Koenkk]

Thanks all!