KEMBAR78
UNSUPPORTED_ATTRIBUTE-Error on Schneider S520619 · Issue #28775 · Koenkk/zigbee2mqtt · GitHub
Skip to content

UNSUPPORTED_ATTRIBUTE-Error on Schneider S520619 #28775

@dvandonkelaar

Description

@dvandonkelaar

What happened?

Z2M reports the following error in the Schneider Electric S520619 when starting up:
error 2025-09-30 21:19:25z2m: Failed to configure 'Thermostat', attempt 3 (Error: ZCL command 0x70ac08fffe06a3bc/4 hvacThermostat.configReport([{"attribute":"occupancy","minimumReportInterval":0,"maximumReportInterval":3600,"reportableChange":0}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/.pnpm/zigbee-herdsman@6.0.4/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:383:28) at Endpoint.zclCommand (/app/node_modules/.pnpm/zigbee-herdsman@6.0.4/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:1053:26) at processTicksAndRejections (node:internal/process/task_queues:105:5) at Endpoint.configureReporting (/app/node_modules/.pnpm/zigbee-herdsman@6.0.4/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:766:9) at Object.thermostatOccupancy (/app/node_modules/.pnpm/zigbee-herdsman-converters@25.14.0/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:193:5) at configure (/app/node_modules/.pnpm/zigbee-herdsman-converters@25.14.0/node_modules/zigbee-herdsman-converters/src/devices/schneider_electric.ts:2212:13) at Object.configure (/app/node_modules/.pnpm/zigbee-herdsman-converters@25.14.0/node_modules/zigbee-herdsman-converters/src/index.ts:366:21) at Configure.configure (/app/lib/extension/configure.ts:123:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:252:17))

The error is referring schneider_electric.ts line 2212
This line has the following system modes: ["off", "heat", "cool"], which should be correct.

The error is also mentioning an error in endpoint.ts:766:9) at Object.thermostatOccupancy.

What could be the problem?

Occupancy is always detected within the device, which is an input on the module itself. See 'B' in the image below.

Image

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

Connect the thermostat to ZM and the issue

Zigbee2MQTT version

2.6.1

Adapter firmware version

20240710

Adapter

zstack

Setup

Add-on on Home Assistant OS

Device database.db entry

No response

Debug log

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    problemSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions