🛠️ Integration issue: VAV-256215-MOD1 pilot‑wire module

[Tieum3564]

Hello Zigbee2MQTT community,
I’m trying to integrate a VAV-256215-MOD1 device (pilot‑wire module to control electric heaters/radiators). The device pairs successfully and is recognized as model VAV-256215-MOD1. However, the mode function does not work — it isn’t recognized as a valid attribute in Zigbee2MQTT.
🔍 Context
• Device: VAV-256215-MOD1 (pilot‑wire heater module)
• Functionality: Paired and identified correctly
• Issue: mode attribute not supported / not exposed
• Hypothesis: This model seems to be a rebranded NodOn SIN-4-FP-21, but it may use custom commands or slightly different clusters.
📑 What I’ve tried
• Verified pairing and basic recognition in Zigbee2MQTT
• Compared with NodOn SIN-4-FP-21 integration
• Checked logs
❓ Request
• Has anyone already worked on this device or seen similar behavior?
• Could this require a custom converter or mapping for the mode attribute?
• Any guidance on how to debug or extend support would be greatly appreciated.
I can share detailed logs if needed to help identify the missing attribute or cluster differences.
Thanks in advance for your help!

📑 Logs
Here’s the error I’m seeing when trying to read the mode attribute:
`ERR z2m: Publish 'set' 'read' to '0xf84477fffe324d9f' failed: 'Error: ZCL command 0xf84477fffe324d9f/1 customClusterNodOnPilotWire.read(["mode"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4747,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')' | timestamp=2025-11-28 09:52:01

DBG z2m: Error: ZCL command 0xf84477fffe324d9f/1 customClusterNodOnPilotWire.read(["mode"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4747,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')
at Endpoint.checkStatus (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:385:28)
at Endpoint.zclCommand (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:1055:26)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Endpoint.read (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:515:29)
at Object.convertSet (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/converters/toZigbee.ts:205:24)
at Publish.onMQTTMessage (/app/lib/extension/publish.ts:246:36)
at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:252:17) | timestamp=2025-11-28 09:52:01`

[Tieum3564]

I think I have to create an external converter based on that one to make it work:
src/lib/nodon.ts

There should be an issue with the way the mode command is mapped to the zigbee device. I can see it from the z2m frontend with using the dev console to read mode from the customClusterNodOnPilotWire cluster (see log behind).

z2m: Publish 'set' 'read' to 'First-Floor/Bathroom/Switch/Heater' failed: 'Error: ZCL command 0xf84477fffe324d9f/1 customClusterNodOnPilotWire.read(["mode"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4747,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')'

Maybe I have to adapt this part with the correct attribute ID:
const pilotWireCluster = deviceAddCustomCluster(PILOT_WIRE_CLUSTER, { ID: 0xfc00, manufacturerCode: Zcl.ManufacturerCode.NODON, attributes: { mode: {ID: 0x0000, type: Zcl.DataType.UINT8}, }, commands: { setMode: { ID: 0x0000, parameters: [{name: 'mode', type: Zcl.DataType.UINT8}], }, }, commandsResponse: {}, });

but not sure about that ! Any thoughts ???