fix: more support for ZCL non-value

[Nerivec]

Add ZCL-specific wrappers to BuffaloZcl to handle non-values, per ZigBee spec.
Fixes Koenkk/zigbee2mqtt#27102

TODO:

• Current behavior is to use NaN for number non-values (including boolean since using 0/1). This must be checked against uses, and support added where needed.
• Update ZHC, can remove the valueIgnore param that was used to sparsely ignore these non-values.
• zboss adapter uses BuffaloZcl for frame reading, this might break that... @kirovilya

CC: @oddlama

[Koenkk]

Also need to update the Aqara converters to be able to deal with this.

[Nerivec]

I reverted this.
That change was a bit too dangerous (too much typing lacking in ZHC/ZCL payloads). We can do it in a separate PR if the need arises.

[codspeed-hq]

CodSpeed Performance Report

Merging #1424 will not alter performance

_{Comparing Nerivec:zcl-nonvalue (d9986d1) with master (7f47140)}

Summary

✅ 12 untouched benchmarks

[Nerivec]

For ZHC, I guess most of the code should hit:

• tz https://github.com/Koenkk/zigbee-herdsman-converters/blob/b2e45275958f5418e07924800d253156ece1b48b/src/lib/modernExtend.ts#L2441
• fz https://github.com/Koenkk/zigbee-herdsman-converters/blob/b2e45275958f5418e07924800d253156ece1b48b/src/lib/modernExtend.ts#L2464

Both of these should allow using Number.NaN to represent non-value.
The current workaround was to use value_ignore (due to lack of support at parser level), though it's only used in a couple places.

@Koenkk how do you think non-values should translate (ignore, push the equivalent of "N/A", etc.)? At least for tz, it should not ignore the request anymore.

Also have to deal with converters that are not using modern extend yet (haven't looked if any).

[Copilot]

Pull Request Overview

This PR enhances ZCL (ZigBee Cluster Library) support for handling non-values per the ZigBee specification. The main change involves implementing proper ZCL wrappers in BuffaloZcl to handle non-values using specific bit patterns (e.g., 0xFF for 8-bit types, 0xFFFF for 16-bit types) instead of allowing undefined values to pass through unchecked.

Key changes include:

• Addition of ZCL-specific read/write methods that handle non-values using Number.NaN for numeric types and undefined for bigint types
• Updated interface definitions to use Number.NaN instead of undefined for time/date fields
• Comprehensive test coverage for non-value handling across all data types

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/zspec/zcl/buffaloZcl.ts	Core implementation adding ZCL-specific wrappers for all data types with non-value support
src/zspec/zcl/definition/enums.ts	Minor documentation clarification for ARRAY and STRUCT non-value formats
src/controller/greenPower.ts	Type name updates from GPD* to Gpd* for consistency
test/zspec/zcl/buffalo.test.ts	Extensive test additions covering non-value read/write operations and test fixes
test/zcl.test.ts	Test updates to use Number.NaN instead of 255 for non-values and payload size fixes
test/greenpower.test.ts	Removal of a test case that relied on invalid frame parsing

[Copilot]

The comment 'XXX: correct value?' indicates uncertainty about the implementation. This should be resolved by verifying the ZigBee specification for the correct element type to use when writing non-value arrays.

Suggested change

	this.writeUInt8(DataType.NO_DATA); // XXX: correct value?
	this.writeUInt8(DataType.UNKNOWN); // ZigBee spec: Use UNKNOWN for non-value arrays