Add pvvx to Manufacturer Name

[krzysztof-kwitt]

Hello,

It is difficult to recognize what CFW we have on a specific device, so I suggest that we also add the author's name to the manufacturer name field, which will make it easy to find out who the firmware comes from.

For now, it is possible to recognize the author only on the basis of OTA Upgrade (0x19) cluster, which is not very obvious and user-friendly.

I'm not sure what implications this will have, but I think it's worth discussing how we can recognize what CFW we have on the device in a more user-friendly way.

CC: @devbis

[JayFoxRox]

Missing , between 'g' '/'; same issue exists on all following ZCL_BASIC_MFG_NAME

[JayFoxRox]

This should have a new length of 9, not 10.

[pvvx]

ZigBee Cluster Library Specification
3.2.2.2.5 ManufacturerName At tribute
The ManufacturerName attribute is a maximum of 32 bytes in length and specifies the name of the manufacturer as a ZigBee character string.

I'm not a 'manufacturer'.
Don't confuse Zigbee 3.0 standards with Tuya quirks

[krzysztof-kwitt]

I wanted to update the field. This is what it looks like in Zigbee2MQTT.

This field can be used as a fingerprint in Zigbee2MQTT.
https://github.com/Koenkk/zigbee-herdsman-converters/blob/0fcaeef8210c6c2635abe85c37e2a26c6f17d4f3/src/lib/types.ts#L35-L40

The word manufacturer in this case can be interpreted in different ways.

• The person who physically produced the physical hardware.
• The person who produced the digital software.
  In my opinion, this fragment of the specification does not specify that it is to be the manufacturer of the physical goods. In most cases, the manufacturer of the digital and physical parts is the same company, but in the case of Tuya, as in this case, we have a different software manufacturer and a different hardware manufacturer.

This is important for me to solve problems like: Koenkk/zigbee2mqtt#21165
Do you have another idea for recognizing whether your CFW or CFW authored by @devbis is installed? I am thinking about recognition based on software version (static list) for already released versions of your and devbis CFW. Newer versions will be recognized based on the new Zigbee manufacturer's name

[devbis]

@krzysztof-kwitt A better option is to add pvvx to device model name as z2m uses zigbeeModel as a primary recognition property. E.g. LYWSD03MMC/pvvx

[pvvx]

Due to the distribution by "ModelIdentifier" and "ManufacturerName", many Tuya Zigbees do not work. The firmware version is different, but the name is the same.

[devbis]

It is applicable only to original Tuya firmwares with proprietary cluster with datapoints. Doesn't make sense for custom firmwares.